3 ms·
Was it that pidgin didn’t keep up with features, or more likely that one by one the major platforms pulled xmpp support to the point where there was no reason f
by WD-42 2y ago
Was it that pidgin didn’t keep up with features, or more likely that one by one the major platforms pulled xmpp support to the point where there was no reason for a normal person to use pidgin?
- shadowgovt 2y agoIt was both, and part of the reason platforms pulled support is that keeping up with XMPP was bad ROI. You're Facebook. You want to provide an instant messenger you can iterate on quickly. You can put the work into making it XMPP-shaped and working with the community (whatever they means... Are you going to slip ship targets because Pidgin doesn't work as a client for your implementation?). Or you can just write and ship your own service and client at your own pace and not care about any other developer's needs or wants because you're trying to serve Facebook users, not developers.
- singpolyma3 2y agoThere were never any major platform with good XMPP support except for Google Talk anyway. So not sure about "one by one".
- WD-42 2y agoFacebook? Or was that something else. All I remember is a golden age when between google and Facebook I had like 90% of my non work contacts available to chat with on pidgin. And my work used xmpp internally, it was glorious.
- singpolyma3 2y agoFacebook had a poorly maintained gateway into their chat system which spoke XMPP c2s (no federation). Was pretty much a hack to get people to stop asking for a Linux client until the web app became the only desktop option anyway.