4 ms·
Adium (https://adium.im/ https://adium.im/) used to be the MacOSX native version (port) of Pidgin. It seems they still recommend it. However, Adium seems kind o
by albertzeyer 6y ago
Adium (https://adium.im/ https://adium.im/) used to be the MacOSX native version (port) of Pidgin. It seems they still recommend it. However, Adium seems kind of dead? Last commit (https://github.com/adium/adium/ https://github.com/adium/adium/) was in 2016.
I build a MacOSX app bundle for the original Pidgin long time ago (https://sourceforge.net/projects/pidgin-macosx/ https://sourceforge.net/projects/pidgin-macosx/). At that point in time, this was not so trivial, as the GTK support for native MacOSX was experimental (http://www.gtk-osx.org/ http://www.gtk-osx.org/). You could simply use the X11 GTK version but I rather wanted to have a native version. I have no idea what the current state is with GTK on MacOSX. This Pidgin build is obviously very outdated now (from 2009), and probably does not run on recent MacOSX versions (they are frequently breaking backward compatibility...).
- olq 6y agoLooks like work is being done in a branch: https://github.com/adium/adium/commits/adium-1.5.11.asher.1011fix https://github.com/adium/adium/commits/adium-1.5.11.asher.10...
- PaulDavisThe1st 6y agoGTK on macOS is completely fine, unless newer versions of GTK have borked it. We use GTK2 for Ardour (cross platform DAW) and there are almost no issues. I did contribute numerous important patches for the quartz backend along the way.
- TingPing 6y agoGTK3 is slightly better than GTK2 on macOS and GTK4 is getting a lot better with a paid developer working on it.
- rw_grim 6y agoPidgin will be in Gtk4 one day.. But right now we're still trying to replace deprecated API that we're using with Gtk3...
- rw_grim 6y agoGtk3 has a Quartz backend and Pidgin 3 will be native on Mac OS. It builds and runs now, but packaging has been a pain so I haven't worked that into our CI yet.
- deleted 6y ago[deleted]
- pmlnr 6y agoAdium is a frontend on libpurple. The frontend can be sort of happily dead if the backend - and it's plugins - are updated.
- Wowfunhappy 6y agoBut as I understand it, Adium can't just use the same plugins as Pidgin, they're very similar but need to be modified a bit. I ran into this ~ 6 months ago when I was trying to make Slack work in Adium. The plugin for Slack was outdated. There was a newer libpurple Slack plugin, but it wasn't compiled for Adium. I attempted to recompile it, but I couldn't seem to manage it, all of the tutorials on how to do it were super confusing... (If anyone knows how to make Slack work in Adium in 2021, please let me know!)
- chipx86 6y agoI worked on Pidgin (Gaim, at the time), and was the original author of libpurple (now libgaim). Adium was a sister project that was originally completely different, but utilized some of our Protocol Plugins (aka prpls — basis for the name "libpurple"). It later utilized libgaim when it reached a certain level of maturity. I don't know whether Adium eventually moved fully onto libgaim. I seem to recall it only used it selectively, but I stopped working on those projects years ago. Been very happy to Pidgin's maintenance resume. Gary Kramlich's been doing a fantastic job reviving it, and I'm hoping the same will be done for Adium in time. We really need a modern multi-chat/IM client for the modern era.
- chipx86 6y agoThis typo-laden response brought to you by Very Little Sleep. If it wasn't obvious, libgaim became libpurple, not the other way around. Too late to edit the parent comment, but felt I should clear that up.