A proof-of-concept Slack client for Windows for Workgroups (WFW) 3.11 with tests. As there are no native HTTPS APIs for the ancient version of Winsock on WFW, a HTTP-to-HTTPS proxy like this one I've written is needed.
Screenshot of the app
Video of the app in action with a modern Mac Slack client on the side for verification.
To compile and run the application, you'll need Visual C++ (VC++) 1.52 running on a 32-bit Windows OS up to Windows 10. Windows 3.1 is not required. I use a Windows 2000 VM as it is the oldest and lightest 32-bit Windows OS with full Virtualbox support.
Coding the app can thus be done on a native Mac or Windows OS with modern text editors.
Even though a 16-bit app can run on modern 32-bit OS, I still recommend occasional testing on a native Windows 3.1 system as VMs are too perfect sometimes.
- Install Windows 2000 VM on a host PC. If you want to share files out of the Win 2K VM, set the network to
Bridged
. - Install VC++ 1.52
- Set up Virtualbox shared folder between the host and Win 2K WM
- Map a network drive to the local shared folder
- VC++ 1.52 can see a network drive and open the
w31slack.mak
- Just click Project -> Rebuild all.
The w16slack.exe
binary should be available in the same directory.
I wrote a custom unit test framework as I could not find a testing framework for C89 that'll work with VC++ 1.52. 2 Go Programs acting as mock servers are required to be run to test the network APIs.
go run mockprox.go
will reply the GET and POST requests by replaying the contents of theou*.txt
files.go run replay.go 30000
will replay whatever was received on a pure TCP socket connection. This is- Edit the file
tstconst.h
to suit your system especially theTEST_MOCK_SERVER_IP
- Open the file
test.mak
- Build Project as per normal and you'll see the following
- First create an app for your associated workspace.
- Add these permissions to your app
channels:history
,channels:read
,chat:write:user
,groups:history
,identify
,im:history
. - Issue a user token to yourself https://api.slack.com/custom-integrations/legacy-tokens
- Start up http-to-https-proxy
- Modify the file
w31slack.ini
configuration file to suit your needs - Start up the
w31slack.exe
- Profit!