- cross-posted to:
- technology@beehaw.org
- cross-posted to:
- technology@beehaw.org
Server indexes of places for newcomers to join can be instrumental for Fediverse adoption. However, sudden rule changes can leave some admins feeling pressure to change policies in order to remain listed.
Its probably good to federate so that Threads users can leanr about alternatives and migrate to a better instance on the fediverse
Just to be clear, threads can federate with an instance that is not defeated with them, and in this case threads users can see all the Lemmy content, but not the other way around.
So this means that we can just keep posting anti Facebook content all the time and they will serve it to their users or will have to be blocking it.
The more I think about it, the worse it seems for threats to federate.
What’s the number of Threads users compared to Lemmy? If the number of Threads users greatly outweigh the number of Lemmy users, then we’d simply be drowned out by all the Threads posts. That’s part one of Embrace, Extend, Extinguish.
Extend adds functionality to Threads that Lemmy either can’t support or won’t support for a while due to development time. People migrate to Threads because Lemmy is “missing” functionality. Plus, though I’m not clear on the exact legal specifications, proprietary code can be added to open-source code, and the proprietary code would be copyrighted. In other words, Lemmy devs would have to figure out a way to interact with and mimic Threads’ proprietary code using open-source code.
Extinguish is when Threads’ support of Lemmy is eventually dropped. The users left on Lemmy have suddenly lost a huge amount of content, and they’re left with fewer users than before Threads enabled federation.
Right, so that means when someone on Threads is complaining about Threads, Lemmy users can’t chime-in and say “uhh, just register on here and thats not an issue, guy”
Well, meta plans to federate with at least some instances… Right? Else their users won’t be able to speak either.