purple-discord

The last time I followed Pidgin development was a while ago, but I'm actively using it for various protocols (slack, discord, googlechat, skype), so I'm curious about the decision to break the API. I understand that the Pidgin community is small, so claiming that "the other protocols will eventually be supported" seems unrealistic. This change requires the community to take on unnecessary porting work and we are already dealing with constant protocol changes, playing whack-a-mole with protocol providers. For instance, this guy [1] is doing incredible work, but I doubt he will want to invest his time in unnecessary rewrites unless someone steps in to assist with each plugin. [1] https://github.com/EionRobb/purple-discord.git

I note that if you are using one of the alternative clients (like Pidgin with purple-discord), they can store local logs that you can then index and search. There is also Harmony for managing your account without touching the Discord website. Note that using unofficial Discord clients can get you banned. https://pidgin.im/ https://github.com/EionRobb/purple-discord/ https://github.com/taylordotfish/harmony/

There are already reimplementations of the client side of some of their protocols (which are just JSON HTTP requests), including account registration, without running any JavaScript (parsing the JS is needed though). These are of course against the ToS and can get you banned though. https://github.com/taylordotfish/harmony/ https://github.com/taylordotfish/librecaptcha/ https://github.com/EionRobb/purple-discord/

Thanks for the issue, I've subscribed to it. https://github.com/jftuga/chars/issues/2 According to the page, several machines and operating systems used CR as EOL. While the systems are all obsolete, files from that era that use CR as EOL could persist and be transferred to modern systems. Clearly those are weird on modern systems, so they should be warned about in a linting situation, which I would like to use your project 'chars' in. Having different EOL chars within the same file is definitely a thing, usually by mistake. I had to fix a bug about this recently: https://github.com/EionRobb/purple-discord/pull/416

There is a plugin for it: https://pidgin.im/plugins/ https://github.com/EionRobb/purple-discord Its about the same as any other Pidgin protocol (no audio AFAICT), with some support for some of the features of Discord like reactions. It gets updates for new features sometimes. The author has written a lot of different libpurple plugins and is quite busy though. Note I've heard you can get banned from Discord for not using the official client.

There are already libpurple plugins for various chat systems, for example Discord: https://github.com/EionRobb/purple-discord/

There's a pidgin plugin for discord. While pidgin is dated and has issues, the existence of it shows that even modern chat systems could be made fast. https://github.com/EionRobb/purple-discord

The Discord plugin for Pidgin doesn't require copying cookies: https://github.com/EionRobb/purple-discord/

I am currently contributing on libraries for libpurple (the central library used in Pidgin) and Spectrum to improve the transports between those 3rd party networks and the XMPP one. Also with the integration of those transports within the Movim project. Recently I was able to bridge Discord and Slack and working on Instagram (to finally have a decent way to use Instagram DM on desktop). See https://github.com/EionRobb/purple-discord, https://github.com/EionRobb/purple-instagram and https://movim.eu/ :)