The technical implementations seem interesting. But, who scrubs the toilets in this social network? Who does the boring, dirty jobs required to clean up after users?
> No provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider.
Wikipedia expounds to say:
"The statute in Section 230(c)(2) further provides "Good Samaritan" protection from civil liability for operators of interactive computer services in the removal or moderation of third-party material they deem obscene or offensive, even of constitutionally protected speech, as long as it is done in good faith."
My understanding is that you (if you're American) would be OK as long as you're not the source of it and that it's incidental to your operations, like your intent is to make a message board for normal conversational stuff and it's not called "Totally Not Child Porn Wink Wink.com".
One nice feature of Mastodon in particular is that you can configure it not to cache content from specific servers. I use that to avoid hosting images from particular servers that specialize in stuff with a high "ick factor". If a use really wants to follow users on those servers, they can, but then that server is the one serving images to my user, not me. I like that setup.
> One nice feature of Mastodon in particular is that you can configure it not to cache content from specific servers. I use that to avoid hosting images from particular servers that specialize in stuff with a high "ick factor". If a use really wants to follow users on those servers, they can, but then that server is the one serving images to my user, not me. I like that setup.
I wasn't aware of this feature; can you point me to a source for how to set that up?
Now set Severity: None, click Reject media files, then Create block. There - now you're not disconnected from them at all, but neither are you hosting their media.