Attached: 1 image
Yeah, that's gonna be a hard pass from me thanks, Rachel.
Zero interest in having a conversation with #Meta "off the record" or otherwise.
Sharing this purely to be as transparent as possible with our members.
The exchange is about Meta’s upcoming ActivityPub-enabled network Threads. Meta is calling for a meeting, his response is priceless!
The people who would use a Meta variant will use it, and people like us will not. This reminds me of the interview with the Mexican restaurant that spawned Taco Bell. The lady who owned it essentially said, “I’m glad he (the founder of Taco Bell) was able to take our teachings and turn it into something. Good for him.” If they build proprietary code, that’s nice. ActivityPub will still be the same open-source code it’s always been, and all of the Fediverse stuff will still exist. It kinda sucks that Meta is trying to make it seem like they’re the good guys, but in the end there isn’t much they can do to the already established stuff beyond make their own.
Edit: also, if they do try anything, we at least have previous data and most of the people who care about freedom to privacy here that I’m sure we could come up with something. We’re not getting blindsided like with Google and XMPP back in the day.
Once Meta joins in, a new set of dynamics are going to develop between old fediverse uses and new meta/fediverse users. If Meta adopts an “EEE” approach such as the ones described in the article, there’s going to be disruption in the user experience from which the fediverse might never fully recover
Edit: clarification on the last sentence, my main concern is that a growing niche protocol such as ActivityPub might be destined to irrelevancy after Meta is done with the Extend & Extinguish, similarly to what happened to XMPP
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
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.
Except they can build proprietary code on top of it and take over open-sourced activitypub adoption
It’s just another way to kill competition
The people who would use a Meta variant will use it, and people like us will not. This reminds me of the interview with the Mexican restaurant that spawned Taco Bell. The lady who owned it essentially said, “I’m glad he (the founder of Taco Bell) was able to take our teachings and turn it into something. Good for him.” If they build proprietary code, that’s nice. ActivityPub will still be the same open-source code it’s always been, and all of the Fediverse stuff will still exist. It kinda sucks that Meta is trying to make it seem like they’re the good guys, but in the end there isn’t much they can do to the already established stuff beyond make their own.
Edit: also, if they do try anything, we at least have previous data and most of the people who care about freedom to privacy here that I’m sure we could come up with something. We’re not getting blindsided like with Google and XMPP back in the day.
The “extend” part is fundamental before they can actually get to the “extinguish” stage: https://ploum.net/2023-06-23-how-to-kill-decentralised-networks.html
Once Meta joins in, a new set of dynamics are going to develop between old fediverse uses and new meta/fediverse users. If Meta adopts an “EEE” approach such as the ones described in the article, there’s going to be disruption in the user experience from which the fediverse might never fully recover
Edit: clarification on the last sentence, my main concern is that a growing niche protocol such as ActivityPub might be destined to irrelevancy after Meta is done with the Extend & Extinguish, similarly to what happened to XMPP