cross-posted from: https://sh.itjust.works/post/181146
I am assuming many of you have heard about the potential of Meta creating an ActivityPub enabled client (TheVerge, PCMag etc. have made articles). I was just wondering what people's thoughts are on this, and if it came down to it should instances in the fediverse defederate from it considering it could be a case of Embrace, extend, extinguish.
There's a DefederateMeta magazine at !DefederateMeta@fedia.io if you're interested, which includes an anti-meta pact on cryptpad with the responses viewable on a seperate website if you care to see which instance admins have agreed.
I'm just curious what my fellow sh.it.heads think of this development in the fediverse, any input is appreciated!
Reposting at the request of can, within the context of c/agora should this instance defederate from any future Meta activity pub enabled clients? From my understanding it is more so a Twitter-clone and I'd argue a more severe problem for Kbin / Mastodon, but it is still worth discussing here.
If meta wants to harvest data they would just create boring no-name servers to pull down the data that they want. De-federation isn't going to stop that.
The goal isn't to create a system where there are no corporate instances. The goal is to create a network that doesn't rely on corporate instances.
This idea that we use use de-federation like a weapon will cause the Fediverse to fragment and then we're back where we started: 50 different social media services and a fragmented social media experience. De-federation isn't a super downvote button, its use should be limited to boring server-related things (spam, complying with laws, etc).
The strength of federated social media is that it is all available for everyone at all times via one account. Breaking the network into small chunks or having some central group decide who gets to have access to social media is the exact thing that the ActivityPub protocol is suppose to help people escape from.
save