It surprises me that they copied the suboptimal tablet-like UI layout of the official client. It's gotta be an MDI app with each chat in a separate window :)
I still don't get why so many channels that should probably be on IRC moved to Discord. Yesterday I tried to share the output of an strace and apparently I have to pay to emit more than 2000 characters. Login to Discord is something that shocks me: every single time I'm told that I'm logging in from a new computer (wrong). Confim I'm human. Then need to check my email. Confirm. And relogin. This at least to me happens every single time. Reported to Discord obviously in vain. Never experienced such a login disaster in my life.
What is wrong with IRC and mailing lists that everyone jumped to Discord? Since I have started to use Discord couldn't find a single good thing about it.
> You might be able to use Mingw-w64, but you might run into trouble running the final product on anything newer than XP
I rarely see a maximum system requirement.
* from the recent commit "V1.07 works on Win95. But you have to install a different LibCrypto, LibSSL, and also install the WinSock2 update."
Download for the Win95 version: https://github.com/DiscordMessenger/dm/releases/tag/v1.07a
According to the author's bluesky posts, there's a few features missing from Win32s compared to regular Win32 that prevent this from being ported even further back to windows 3.1 easily.
Minimum system requirements: 64 Mb RAM.
Hear that, official Discord?
---
Now, considering this project will be hunted down and DMCA-ed or C&D-ed soon, has the original author considered separating the generic messenger UI code from the transport code to make the codebase usable for less ... jealous ... services?
Time to stuff this into BoxedWine (https://www.boxedwine.org/) and we'll finally have a fast, lightweight chat client for Discord!
Just beautiful. 64Mb of RAM and snappy due to native UI framework use. Compare it to the sluggish 1.2Gb of RAM that Teams uses (when not in a video call).
Someone needs to get around to doing this for Microsoft Teams.
Somewhat unrelated, but it's crazy to see how durable Windows APIs are. I, for unrelated reasons, last month, opened Guitar Pro 4, which had been laying around in my warez folder (copied many tines accross hard drives) since I pirated it circa 2004 as a teenager, and it worked perfectly in my machine running windows 11. Even though I love Linux, that doesn't happen over there, right?
Open protocols are eternal. Proprietary garbage lasts as long as the company does.
Maybe it's just my laptops (MacBook Air and Pro). But every time I open it, it's always "updating" (plugins?) before I can use it. Opening it in the browser is much faster.
Looks like the security/integrity of SSL isn't taken too seriously as the build recommends to use a hex editor to replace "_strtoi64" and "_strtoui64" with "functions likely to return 0 such as iswxdigit" in order to successfully link OpenSSL on windows 2000 and earlier. Unclear what impact such a hack would have on the integrity of the crypto operations performed by OpenSSL?
Cool, but Bitlbee can proxy any IRC client (even for DOS and Windows) against some server and use your accounts (even Mastodon) over IRC.
I used to love cordless. I could be on an old Sparc machine or even DOS on a 486 and access Discord.
Unfortunately the only thing alternative clients for are good for now is getting banned.
If you use [1] you can run it on Windows 3.1.
That's a fun project. But I wonder: is it a good idea to connect to the internet from these old systems?
So many good memories when seeing such design... I wonder why things got so complicated nowadays
How long until they get slapped with a trademark claim?
It looks so snappy and efficient
[dead]
[dead]
Cool project, but it is missing central features of Discord such as voice and screen sharing.
Just a gentle warning: try out alternative Discord clients with a non-important account first. A few years ago, I used ripcord¹ and got automatically banned by Discord - probably because I had started the original Discord client on the same computer, and this triggered some heuristics. Discord's first-level support was not willing to reinstate my account, and I had to² track down their head of security on Twitter to get my account reinstated.
¹) https://cancel.fm/ripcord/, no new releases since 2021
²) I'd not generally suggest this approach. However, since COVID we have been using Discord a lot for informal communication with our students. Losing access to a dozen course servers mid-semester was a huge problem for me.