 Actually effective strategies against #Meta to prevent an #EmbraceExtendExtinguish are difficult, but they start from asking "what will actually help here." I maintain that preemptive #DefederateMeta is ineffective for this and that defederating from those who won't defederate from meta does more harm than good. But what will help is thinking about the roadmap and getting there first. What will help is building a robust and thriving community around #ActivityPub and other fediverse protocols. 4 comments
 @hrefna Implementing the how the most desired #ActivityPub features function (technically and in the #UX) before #GAFAM decides for us, will protect us more than the whole #Faceblock debate, regardless whether our instances decide to #DefederateMeta or not. Just imagine if it's possible to easily move posts from Mastodon.social to Facebook, but not the reverse? Or if people deciding what instance to use are told they can only use #Meta to have their messages be secure and *cough* private? ๐คข ๐คฎ  Yes, the solution is obvious. It is also unfortunately theoretical. In practice no matter how often you say we should collectively evolve the specs, the dynamics in grassroots ecosystem is that everyone moves individualistically and by doing so implicitly chooses to be weak. Everything fragmented, no cohesion, little synergy. The advantage that companies have is that they can pay people to be dilligent and dedicate to the boring chores, stick to a task and complete it. Btw, an interesting aspect to #Meta's entry that I haven't yet seen mentioned.. It's not just Meta to worry about. When they launch and the press release proudly mentions their 'open standards' approach, then this will be trigger for an unprecedented influx of businesses adding #ActivityPub support and joining the #Fediverse. Meta will basically indicate to the market: this technology ecosystem is "good to go", economically viable and we're in it. #Metaverse-like hype ensues. |
Gregory's Server
Meta is looking to implement post importing. That's been a feature request since forever (see https://github.com/mastodon/mastodon/issues/177 and https://github.com/mastodon/mastodon/issues/12423 ).
Secure messaging is another example.
These are things that if meta implements them and does even a halfway decent job then #meta controls the standard.
Want to prevent that?
Get there first or at least have a strong offering on how to do these things out of the gate. Let _us_ as a community control the standards that we use.
Meta is looking to implement post importing. That's been a feature request since forever (see https://github.com/mastodon/mastodon/issues/177 and https://github.com/mastodon/mastodon/issues/12423 ).
Secure messaging is another example.
These are things that if meta implements them and does even a halfway decent job then #meta controls the standard.