Alternatively, setup your own instance is my best advice. If you have some technical skills to setup one. That would help decentralizing the most of course. If you need to help. We are happy to help.
Is there a still a concern for self hosters of public instances regarding CSAM content? And if so, any guidance on how to mitigate it?
I am very interested in self hosting, but I am worried of its legal repercussions, especially since I am an immigrant in the country where I live and afraid to get in any legal trouble.
Child Sexual Abuse Material (CSAM): Service providers are required to report any CSAM on their servers to the CyberTipline operated by the National Center for Missing and Exploited Children (NCMEC), a private, nonprofit organization established by the U.S. Congress, and can be criminally prosecuted for knowingly facilitating its distribution. NCMEC shares those reports with law enforcement. However, you are not required to affirmatively monitor your instance for CSAM.
By my understanding, you don't have to setup proactive monitoring for CSAM being federated in, but if you specifically spot CSAM or it is reported to you then you are legally obligated to report it
I would not risk it if you're at risk of getting kicked out or something, especially if your host country is stricter on that type of content. Just join one of the existing instances and subscribe to whatever Lemmy communities you want to see federated with it.
@matcha_addict@melroy It's not possible to stop every instance of a user posting illegal content. What's important is that you have a clear policy, and a moderation team that consistently and proactively enforces that policy.
As long as you report the content and act fast if such kind of material is on your site. Also you can disable account registration, so it only you and maybe some friends you know that have an account.
Last but not least, you can also block domains in Mbin. I blocked some domains I just do not want to federate with!
NSFW site
Like lemmynsfw (dot) com.
And yes you can add that in the admin panel yourself.
Even if I disable account registration, I may still be liable if somehow the content ended up on my instance due to federation right? Or is that not a concern?
Well.. the answer is always yes. But you can mitigate the problem further by not only disable account registration but also check the setting "Force users to login before they can access any content".
So in the end, that means that nobody can see any content without logging in. And since you are the only account, only you can see the federated content.
I feel like dark theme is often tricky on different monitors - If the font is too heavy it'll look awful, if it's too light it might look bad on low resolution displays. Combined with different colour contrasts on different screens, and it gets really difficult to know what people will end up seeing.
The headline - "MBIN SERVERS" - looks great on my 4K monitor, but slightly less good on a worse one. The same goes for the text stating that "Also view servers on FediDB and Fediverse Observer", but it's not so bad for the white text. The hyperlinks, however, might suffer from a lack of contrast with the background (a slightly too dark blue) combined with very thin text on low resolution monitors.
I guess brighter hyperlinks could also benefit the names of instances.
It's not something I ever noticed myself when using the site, but keeping it in the back of my head while looking at it I can see why some might have some problems with it. :)
yeh I agree, the hyperlinks needs more contrast. And also on the homepage the sub-title "A federated content aggregator, voting, discussion and microblogging platform (By the community, for the community)", can also have more contrast.
I also believe the text (especially headings maybe) can use a more bolder text. @jwr1@kbin.earth Try to set font-weight of 400 on the .font-extralight CSS class instead of 200.
@Aatube@kbin.melroy.org if you want to share your problems in more details, please help us out you can join the issue chat on Matrix if you like. And ideally share some screenshots if that would help to explain the problem. Another approach is to create an issue at GitHub (which does require a GitHub account): https://github.com/MbinOrg/mbin-website/issues/new
Or explain the situation here in this thread in more detail is also possible, but that is up to you.