Forgive me if I’m wrong, but external content that gets federated to your server is entirely based on the subscriptions of users native to your server? So as long as no native users of kde subscribes to NSFW content it shouldn’t really end up on their servers. As far as I know, content is not synchronized between servers just because they know of each other.
Assuming paragraph one is correct, then KDE can achieve a NSFW free server by merely limiting who gets accounts on their own server; as they should. This is just like Google not handing out @google.com addresses to every gmail user. Federation would still allow users from any instance to interact with the kde communities without problem. This means no one can make magazines/communities on the KDE server not related to KDE and any content moderation of KDE’s communities would just like any other.
Malicious instances are more likely to be talking about instances abusing the federation apis in order to spam or otherwise cause havoc, not about that instances content policy.
Forgive me if I’m wrong, but external content that gets federated to your server is entirely based on the subscriptions of users native to your server?
No. There is also the profile of the user. If a remote user can post on your instance then you can see his profile. Just click on the link that I pasted in my top comment, (you downvoted it btw), click and see by yourself:
Tell me that this is acceptable content on an instance from Mozilla for example. This is the profile of another user who also downvoted me. Just open his profile and tell me.
So as long as no native users of kde subscribes to NSFW content it shouldn’t really end up on their servers. As far as I know, content is not synchronized between servers just because they know of each other.
True for the magazines, but not true for the profiles for example. It’s leaking. It is the attitude that matters, and the accountability. The big groups will never play this mouse and cat game, they will make it a club.
Damn, I had not considered this angle. I can see that being a problem, wonder why we’ve done it this way with Lemmy/kbin and not just redirect to the host instance like mastodon does. Surely, for instances that don’t want to federate certain kinds of content, this would be the way to bypass this whole issue.
My initial thought that prompted this entire chain is that I think we should try our damnest to ensure that the fediverse as much of a coherent network as possible, it will have problematic communities and servers and surely we are going to have to expel the absolute rotten apples, but accepting the diversity of the system and dealing with it locally.
I am not advocating for tolerating illegal content here, just to be clear. I’m all for moderating them on a community level or server level if needed be, should they not fix the underlying issue.
In essence, the less likely any outside entity can demand we change in order to benefit them, the better. KDE/Mozilla/Meta whoever should do their down due-diligence and decide how they want to approach the fediverse, blemishes and all in order to make the site they want to make.
I don’t think it is unreasonable for the KDE instance to have to redirect profile as an example if they find content in them to be possibly questionable.
Forgive me if I’m wrong, but external content that gets federated to your server is entirely based on the subscriptions of users native to your server? So as long as no native users of kde subscribes to NSFW content it shouldn’t really end up on their servers. As far as I know, content is not synchronized between servers just because they know of each other.
Assuming paragraph one is correct, then KDE can achieve a NSFW free server by merely limiting who gets accounts on their own server; as they should. This is just like Google not handing out @google.com addresses to every gmail user. Federation would still allow users from any instance to interact with the kde communities without problem. This means no one can make magazines/communities on the KDE server not related to KDE and any content moderation of KDE’s communities would just like any other.
Malicious instances are more likely to be talking about instances abusing the federation apis in order to spam or otherwise cause havoc, not about that instances content policy.
No. There is also the profile of the user. If a remote user can post on your instance then you can see his profile. Just click on the link that I pasted in my top comment, (you downvoted it btw), click and see by yourself:
https://kbin.social/u/iluvroris
Tell me that this is acceptable content on an instance from Mozilla for example. This is the profile of another user who also downvoted me. Just open his profile and tell me.
True for the magazines, but not true for the profiles for example. It’s leaking. It is the attitude that matters, and the accountability. The big groups will never play this mouse and cat game, they will make it a club.
That is correct, I did downvote your comment!
Damn, I had not considered this angle. I can see that being a problem, wonder why we’ve done it this way with Lemmy/kbin and not just redirect to the host instance like mastodon does. Surely, for instances that don’t want to federate certain kinds of content, this would be the way to bypass this whole issue.
My initial thought that prompted this entire chain is that I think we should try our damnest to ensure that the fediverse as much of a coherent network as possible, it will have problematic communities and servers and surely we are going to have to expel the absolute rotten apples, but accepting the diversity of the system and dealing with it locally.
I am not advocating for tolerating illegal content here, just to be clear. I’m all for moderating them on a community level or server level if needed be, should they not fix the underlying issue.
In essence, the less likely any outside entity can demand we change in order to benefit them, the better. KDE/Mozilla/Meta whoever should do their down due-diligence and decide how they want to approach the fediverse, blemishes and all in order to make the site they want to make.
I don’t think it is unreasonable for the KDE instance to have to redirect profile as an example if they find content in them to be possibly questionable.