It should be pretty obvious that a decentralized network that many use specifically to not be connected to centralized networks houses mostly people who do not wish to have their posts bridged to B...
That’s is not the right analogy. No one is making the bridge and saying “I can take the content from person A on Lemmy and sell it on Bluesky”. they are just saying “Here is a copy of what Person A posted on Lemmy”.
In terms of copyright, why is it okay from someone on a different Mastodon server to relay content from a Lemmy server and even redistribute it (through, e.g, RSS readers), but it’s not okay for a bridge to redistribute it to a Bluesky server?
Those examples are all forms of linking back to the content which is still hosted by the original server in which it was posted. Effectively they are sharing links to the content over the content itself, because if the hosting server removes the content then it is no longer available through those other mediums. And yes there are caching mechanisms involved, but those fall to the personal use case because the cache is not made publicly available.
For these bridge services to work, they are creating and hosting duplicates of the content. That is the biggest difference. If BlueSky actually federated then they would not be rehosting the content either.
Lemmy’s federation model is that all posts and comments get replicated across all instances. If an instance goes down, the copied content still will live in my instance. It’s not just caching.
That’s is not the right analogy. No one is making the bridge and saying “I can take the content from person A on Lemmy and sell it on Bluesky”. they are just saying “Here is a copy of what Person A posted on Lemmy”.
In terms of copyright, why is it okay from someone on a different Mastodon server to relay content from a Lemmy server and even redistribute it (through, e.g, RSS readers), but it’s not okay for a bridge to redistribute it to a Bluesky server?
Those examples are all forms of linking back to the content which is still hosted by the original server in which it was posted. Effectively they are sharing links to the content over the content itself, because if the hosting server removes the content then it is no longer available through those other mediums. And yes there are caching mechanisms involved, but those fall to the personal use case because the cache is not made publicly available.
For these bridge services to work, they are creating and hosting duplicates of the content. That is the biggest difference. If BlueSky actually federated then they would not be rehosting the content either.
Lemmy’s federation model is that all posts and comments get replicated across all instances. If an instance goes down, the copied content still will live in my instance. It’s not just caching.