this post was submitted on 23 Jun 2023
792 points (100.0% liked)
Technology
37708 readers
181 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Google is actually a great parallel here, because of what they did to XMPP (the federated chat protocol). They implemented it for hangouts/gchat. It was a good on-ramp that allowed people to talk across platforms. Then Google created a bunch of features that only worked internally and not with XMPP. Then they removed XMPP.
XMPP didn't work on mobile. You had to have the app running to receive messages, and the battery wasn't large enough to keep the CPU powered up all day.
Google was right to abandon XMPP and pretty much every other platform did it at the same time. It's a shame they all chose proprietary solutions but XMPP was never really an option once smartphones entered the picture.
Somebody not being able to message me while I'm offline is a fantastic feature that I wish we still had. I miss that.
IIRC Slack did something similar with IRC.
@abhibeckert @dark_stang where are you getting all of this from?! Apps run in the background all the time, and there were mobile XMPP clients around back in the day. Pretty sure even Skype did XMPP for a bit.