@profcarroll Bridging content to Bluesky without consent violates users copyright to their content because Bluesky extracts a broad license to all content posted on their platform and transfered over their protocol. Bridge builders do not have the right to grant these wholesale licenses, so any such bridge is illegal. Just because you can technically do something does not make it legal or ethical.
@profcarroll Such bridges also violate Bluesky ToS which requires the poster to assert they have the legal right to post the content, since they don't.
Let’s forget Bluesky/ATProto entirely and limit ourselves to the fediverse. Fedi instances themselves have different TOSes and run on different software. If a fediverse instance asserts a TOS similar to Bluesky’s, and posts from other instances federate into it, has that TOS been violated? When, and by whom? How about copyright? If someone doesn’t want their posts federated into that instance, can they assert that their copyright has been violated? By whom? What’s their recourse?
Questions like these predate the fediverse entirely. When you view a web page, copies (both ephemeral and durable) are made in servers, caches, and devices along the path to your computer or phone. If your favorite web site has a TOS that forbids scraping, you may still have many of its pages stored in your browser cache. Have you violated that TOS?
Web crawlers and search engines, even more so. robots.txt is nice, but it’s not a TOS. Here, we actually do have case law and precedent, eg Google News, Cambridge Analytica, etc, but they’re complicated.
I’m not trying to be difficult here, I’m honestly struggling with how to think about all this. TOSes and copyright are useful, but way underpowered for handling the complexities we’re piling on top of them here. We’ve already started inventing techniques outside them to provide these kind of norms and consent, eg https://www.tootfinder.ch/ ‘s “searchable” profile tag for opting in. That kind of thing seems maybe more promising to me!
@snarfed.org Actually, most Fedi instances do not have a ToS, they have a privacy policy wherein they describe what they will do with the data, publish it etc. This creates a narrow implied license which gives the instance the right to publish it, but does not convey any other rights including no right to sublicense the content. So you still have pretty much full ownership of your content, except the instance can publish it.
@snarfed.org The difference with these corporate sites is that they take a license https://bsky.app/support/tos :
"By making any User Content available through the Services, you hereby grant to Bluesky and its subsidiaries, affiliates, licensee, successors, and assigns (the “Bluesky Parties”) an irrevocable, non-exclusive, perpetual, transferable, worldwide, royalty-free license, [...more]
"with the right to sublicense (through multiple tiers of sub-licensing), to use, copy, modify, adapt, crop, edit, creative derivative works, distribute, publicly display, publicly perform and otherwise exploit in any media now known or hereafter devised, your User Content, in whole or in part, in connection with (i) providing the Services and Content to you and to others; (ii) promote and market Bluesky and our Services..."
@snarfed.org They define their Services as the Bluesky app and the AT Protocol. So effectively they are saying that anything transferred over the AT Protocol becomes subject to their license. Which is pretty crazy.
These problems don't exist in the Fediverse (as much) because no one is taking draconian content licenses away from the user.