You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.
This is probably the furthest from some of the other things in this agreement (it's basically making a rule across servers), but I think that this will help reduce the need to block other instances greatly. In essence, my proposal is that servers hosting potentially illegal content properly tag their posts. I've been in positions where I am forced to block instances because of things like lolicon that I can't properly filter out. However other kinds of content, such as piracy, leaks, and other questionably legal materials might be good to tag. How we define what is to be tagged is still a question that I think warrants discussion. It's a small thing that would greatly reduce the amount of instance-wide blocks.
The text was updated successfully, but these errors were encountered:
I kinda get your point here, but I feel like that is a bit tough to enforce since the things in the covenant are mostly about communication and prevention of blocking someone straight ahead.
I've been in positions where I am forced to block instances because of things like lolicon that I can't properly filter out.
Preventing illegal media from being stored on your server or media proxy can be done without really harming the network integrity, as far as I know both Mastodon and Pleroma offer the tools to completely reject media from an instance.
Even if we were to try to police media tagging with this self-imposed guideline, instances that post this content untagged simply would not adopt it then, avoiding responsibility per se.
Preventing illegal media from being stored on your server or media proxy can be done without really harming the network integrity, as far as I know both Mastodon and Pleroma offer the tools to completely reject media from an instance.
Where I live drawn child porn is treated like child porn of real children. Even linking to it in any capacity might be a liability. Many places are the same.
Even if we were to try to police media tagging with this self-imposed guideline, instances that post this content untagged simply would not adopt it then, avoiding responsibility per se.
They're not doing enough to keep the network operational and running in my opinion. They're essentially forcing anyone outside the US or the few countries that allow that stuff to block their instance. Blocking media might still put the operators under liability. It puts a lot of people in the crossfire when it's an instance like Pawoo where there are plenty of users who don't post that kind of stuff.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is probably the furthest from some of the other things in this agreement (it's basically making a rule across servers), but I think that this will help reduce the need to block other instances greatly. In essence, my proposal is that servers hosting potentially illegal content properly tag their posts. I've been in positions where I am forced to block instances because of things like lolicon that I can't properly filter out. However other kinds of content, such as piracy, leaks, and other questionably legal materials might be good to tag. How we define what is to be tagged is still a question that I think warrants discussion. It's a small thing that would greatly reduce the amount of instance-wide blocks.
The text was updated successfully, but these errors were encountered: