view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Google chat was using a different libpurple backend that is not xmpp and I am relatively sure you misremember what Pidgin was able to do a decade ago with XMPP.
Hmm ok. So Google just had something in between that presented as XMPP to pidgin? Google's original chat was open so it was easy to connect to. I know that presented as XMPP because I still have the old account on my system (yeah I'm really bad about deleting stuff that no longer works). Then a few years ago Google decided to put their chat behind Oauth2 authentication, which required a specialized pidgin plugin and a bit of manual setup to get it to work. Those are the two versions of Google chat I've worked with. Before that I was using Yahoo chat, but we all know what a joke Verizon made of that.
So during this time I would log in to the same account both from home and from work. I think you might be right though, that all new messages only appeared on the latest machine to log in. And that appears to still be the case using Openfire.
After Google updated their chat, when I got in to work the new setup sent a copy of all the messages I hadn't already seen on that client since the last time I signed in, so there was always a full history. Again this setup used an XMPP account in Pidgin, but it's certainly possible that the plugin which worked with the Oauth2 authentication provided some new features to pull the history down? The odd thing was that some of my chat during the day would show up on my computer at home, but not all of the messages, and I never really understood what the difference was.
Regardless, is there a newer XMPP client you might recommend which is somewhat similar to pidgin's look&feel, but actually provides a history when connecting from multiple machines? It would certainly be nice if all messages from myself and the people I spoke to were shown on both machines while they are simultaneously signed in, but I can make do without that. However I really do need the history to show up when I sign in to the next machine, and I'm hoping at some point to also get a client set up on my phone (gotta join that 21st century at some point!).
Server side you need "message carbons" and "message archive management" (MAM) enabled to have that work. I never used OpenFire, but it is standard on other XMPP servers.
I think PSI uses a similar UI cincept, but it is also not updated anymore. I would recommend Gajim instead.
Thanks, that's some good info to track down! I actually loaded up Gajim on my desktop last night and it does seem to be better suited to the task.