Live data from Hacker News

Pidgin: The Universal Chat Client

pidgin.im

81–90 of 181 posts

Re: Pidgin: The Universal Chat Client

#81
post #76

Earlier quoted context omitted.

Honestly, it's mostly a matter of Adium having lost its purpose. Most of the IM networks it originally interacted with no longer exist or are no longer open to third-party clients, and the ones that remain (mostly XMPP and IRC) aren't necessarily a great fit for Adium.

I’ve been surprised recently by the availability of plugins for libpurple (the lib on which Adium is based) which supports Telegram, Signal, Facebook …

Modern IM networks aren't a great fit for libpurple because they fundamentally work differently.

"Old-school" IM networks like AIM were simple to work with from a client perspective -- you connect to the network, you send and receive messages, and that's it. There was no real support for server-side message history, multiple clients, mobile clients, or offline messaging, so third-party clients often just implemented their own local history instead.

Newer IM networks like Telegram are usually designed from a mobile-first perspective -- the Telegram client protocol is designed around the concept that the server has a definitive view of history across all chats, and the client synchronizes portions of that history to local storage to display it. It certainly isn't impossible to adapt this to a design like libpurple/Adium/etc, but it's an awkward fit and is likely to fail to support features which don't fit into that model, like chat messages being edited or deleted by the other party in the conversation.

Re: Pidgin: The Universal Chat Client

#82
post #7

I really miss Adium ( https://adium.im ) which was based on Pidgin's libpurple. Adium had such a great user experience. It was built with native widgets and also incorporated chat themes that were implemented using WebKit's rendering ( https://www.adiumxtras.com/index.php?a=search&cat_id=5&sort=... ). It was fast and memory friendly given that it was a native app and the themes were just small templates offering a di…

The messaging app on the Nokia N900 was also based on libpurple. You had all of your Google Talk and Skype contacts and chats, together with SMS in a single place.

Re: Pidgin: The Universal Chat Client

#83
I used to work a little bit on Pidgin. A lot of the core maintainers have moved on. I think it's just grim (Gary Kramlich) at this point. It's very clean C if you're interested in contributing to an open source project.

Re: Pidgin: The Universal Chat Client

#84
post #7

I really miss Adium ( https://adium.im ) which was based on Pidgin's libpurple. Adium had such a great user experience. It was built with native widgets and also incorporated chat themes that were implemented using WebKit's rendering ( https://www.adiumxtras.com/index.php?a=search&cat_id=5&sort=... ). It was fast and memory friendly given that it was a native app and the themes were just small templates offering a di…

There's still third party clients. I use Ferdi, which is the open-source equivalent to Franz and Rambox.

Re: Pidgin: The Universal Chat Client

#85
post #7

I really miss Adium ( https://adium.im ) which was based on Pidgin's libpurple. Adium had such a great user experience. It was built with native widgets and also incorporated chat themes that were implemented using WebKit's rendering ( https://www.adiumxtras.com/index.php?a=search&cat_id=5&sort=... ). It was fast and memory friendly given that it was a native app and the themes were just small templates offering a di…

The ironic thing is the protocols are now almost all dirt simple but I perceive the risk of being C&D’d for making alternative clients to not be worth the risk.

Re: Pidgin: The Universal Chat Client

#86
post #12

Earlier quoted context omitted.

Similar. 1. IRC 2. ICQ 3. MSN 4. IRC (again) 5. Skype and Facebook 6. WhatsApp 7. Facebook again 8. Still Facebook (very sticky) 9. IRC + Slack (some communities) + Discord (some communities) + Facebook/Whatsapp + Signal + Telegram + Matrix + Zulip Yeah, I think we need a new libpurple.

Part of the lack of 'new libpurple' is that companies have grown much more adept at/focused on removing third party clients. Discord in particular, IIRC, will even ban users for using third party clients.

This was a problem even back when Gaim (now Pidgin) was at peak popularity.

I used to be a dev on the team, and we had our accounts banned all the time. Some of the IM services didn't mind us being there (MSN seemed more than fine with it, and we reportedly had fans within the team there, though future protocol versions made it harder for us to figure out).

Yahoo wanted us off and did everything they could to keep us from connecting. Changing auth schemes to increasingly-elaborate obfuscated methods, at one point throwing pages of what looked like equations at us.

AIM would have been fine with us if we had used TOC (their open source protocol), but OSCAR is where all the features were at. They didn't outright ban clients, but my understanding is that their lawyers were involved at one point (though I think mainly due to the name "GAIM").

But you're right, they are removing third-party clients more. And fewer protocols are unencrypted plain text, which makes it harder as well. Still, work continues.

Re: Pidgin: The Universal Chat Client

#87
post #2

oh pidgin. Throughout my life (as a millennial) chat went this way: 1. IRC 2. IRC, Yahoo messenger, Aol Instant Messenger, MSN Messenger (mostly based on your ISP in the early days) 3. All + Skype (video!! wow!) + Google messenger. *This was when pidgin was invaluable* (there was also some Duck app for macOS?) 4. Skype started charging and since everyone was on Facebook, everyone moved to Facebook messenger. Text mes…

Haha, nice.

My journey was:

1. ICQ, because my gamer friends used it.

2. Added IRC, while it felt already outdated, somehow a bunch of my Japan-nerd friends used it.

3. Added AIM, YIM, MSN, because girls and my parents used them.

4. Switched to Trillian, because it wasn't managable otherwise.

5. Everyone moved to Facebook Messenger.

6. Everyone moved to WhatsApp

7. Now and then some friends switch to Signal, Telegram, or another "secure," alternative to WhatsApp.

8. Started working remote and everything is Slack and Zoom.

9. Dabbled in Web3/crypto and everything is Discord

Re: Pidgin: The Universal Chat Client

#88
post #64

Aaah I used it a long time ago, it was then called Gaim I believe. I also used the similarly named but jabber only Gajim. Good times :)

Indeed. Originally it was "GAIM" (due to the original purpose being a GTK+ AOL Instant Messenger client), which AOL wasn't thrilled about. We changed it to "Gaim", which I think they had less of a problem with, or at least we had hoped they would.

Internally at least, we called it "Gaim's An Instant Messenger". I'm not sure if we formalized that or not. It's been too long.

And then to fully move away from that branding situation, it was renamed to Pidgin. This was mid-2000s, after I moved away from the project, so I don't have any insight into the name change beyond the history.

Good times for sure!

Re: Pidgin: The Universal Chat Client

#90
post #2

oh pidgin. Throughout my life (as a millennial) chat went this way: 1. IRC 2. IRC, Yahoo messenger, Aol Instant Messenger, MSN Messenger (mostly based on your ISP in the early days) 3. All + Skype (video!! wow!) + Google messenger. *This was when pidgin was invaluable* (there was also some Duck app for macOS?) 4. Skype started charging and since everyone was on Facebook, everyone moved to Facebook messenger. Text mes…

As an Indian millennial, my journey was a bit different:

1. Yahoo messenger (2001/2 - First internet experience)

2. Yahoo messenger + Text (2003/4)

3. Text + Skype (2006/7)

4. Whatsapp + FB Messenger + Skype (2010)

5. Whatsapp/iMessage + Instagram (2016/17)

Post reply on HN