The exchange is about Meta’s upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!
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.
Idm meta joining tbh. At least this means your friends can be on something and you won’t be obligated to use a meta app to talk to them, peer pressure, etc
Your first mistake is setting a minimum expectation for a Meta product. They’ve not promised it will do any of that and they already have you thinking it will based on nothing but rumor.
I don’t entirely disagree. An open standard should be open. I am expecting shenanigans from Meta from the classic “Embrace, Extend, Extinguish” playbook though.
To avoid a Google XMPP repeat, I think the anti-Meta disfederation alliance might be the right path. Some instances can just outright refuse to Federate with corporate instances, others could have strict conditions, and more laissez faire instances will always have a backstop if (when) Meta starts playing badly.
It’s tough to say though. Microsoft was the largest contributors to Linux for a few years, out of self interest. Optimizing Linux for running on Azure. Still, the Linux kernel guarded itself well, and Linux is fine.
Of course in the Linux kernel, you have lots of large corporations “cooperating” in some sort of standoff. If Meta, Twitter, Google, Microsoft all started using ActivityPub, you could find a similar situation emerge. The popularity of Gmail doesn’t let Google break email so badly that it doesn’t work with Outlook (or Yahoo, AOL, etc).
Until they pull an iOS sms situation, where non-iOS applications are missing their “exclusive features” and go as far as to break conversations through incompatibility, and then your friends are badgering you to “just join the 21st century and get an iphone already,” but with Meta-branded apps. There’s no way in hell Meta will play nicely with anything outside their ecosystem.
Exactly, they might play along in the beginning, even stretch it by putting all the non-Meta conversations in green text. But once their instance becomes the largest one, they’ll start making it difficult for everyone else.
I do mind. EEE is a well established strategy. This time won’t be different than every other time so massive tech company pretended to embrace open standards.