Not how it works. Also your use of “becomes a publisher” suggests to me that you are misinformed - as so many people are - that there is some sort of a publisher vs platform distinction in Section 230. There is not.
My main Fediverse profile is at @hybridhavoc@darkfriend.social
Not how it works. Also your use of “becomes a publisher” suggests to me that you are misinformed - as so many people are - that there is some sort of a publisher vs platform distinction in Section 230. There is not.
Repealing Section 230 would actually have the opposite effect, and lead to less moderation as it would incentivize not knowing about the content in the first place.
That’s true and fair.
… I feel like you can do this with the Mastodon admin already. Preferences > Administration > Custom Emojis. Enter in the domain whose emojis you want to see / get, search. Click the “select all” checkbox at the top, copy. If there are multiple pages, go to the additional pages.
Here is an explainer on architecture. It might be helpful. https://blueskyweb.xyz/blog/5-5-2023-federation-architecture
Seems like there is a lot of people in this thread that are confused about BlueSky federating even means. BlueSky’s plans for federation have nothing to do with the fediverse. It’s about enabling federation with other AT protocol services, including self-hosting a personal data server.
The path forward I think would be some sort of a bridge service. Think of it as a translation layer that could take in updates from both ActivityPub and AT, and present to the opposing side like it were native. Something similar was developed for nostr to communicate with the fediverse, and it seems at least feasible in this case as well.
Unfortunately it seems like development on Tumblr has been reduced to a skeleton crew. I wouldn’t hold my breath for ActivityPub integration on that front now.
I would like to see some sort of bridge built to allow communication between AT protocol services and ActivityPub protocol services.
This is frankly bizarre. I don’t understand how you can even write that and reasonably think that the platform hosting the hypothetical defamation should have any liability there. Like this is actually a braindead take.