←back to thread

89 points rw_grim | 1 comments | | HN request time: 0s | source
Show context
relyks ◴[] No.42211603[source]
Am I reading this right? Is the only protocol being supported now the most recent version of IRC? Are there plans for others? Part of Pidgin's "calling card" has been its ability to support many different chat protocols. However, that's become difficult since most protocols have become walled gardens and harder to reverse engineer. I'd imagine supporting Matrix, XMPP, Signal, other protocols with open specifications, etc. would be a good idea
replies(4): >>42211609 #>>42211624 #>>42211652 #>>42211827 #
rw_grim ◴[] No.42211624[source]
yes all the other protocols will eventually be supported. we're a small team of open source developers and these things take time..
replies(2): >>42212017 #>>42212890 #
dig1 ◴[] No.42212890[source]
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

replies(2): >>42213447 #>>42216372 #
1. arghwhat ◴[] No.42213447[source]
Presumably because the old API was broken/lacking/etc. Calling the resulting porting work "unnecessary" without even considering why the API might have been changed is not fair.

The pidgin project is 25 years old, and libpurple is 17 years old. It's entirely fair that a rework is required, and much appreciated that this work is continuing.