this post was submitted on 25 Jun 2023
14 points (100.0% liked)
/kbin meta
110 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Red alert:
https://lemmy.kde.social/instances
lemmygrad.ml lemmy 0.18.0
burggit.moe lemmy 0.18.0
They seem to federate everyone, including the weird CP guys.
Honestly they should only federate with instance from official, hand picked, high standards projects, kernel, gnome and Co. They don't want to take any risks with an instance like ours.
edit: the demonstration for it is the person who downvoted my post: https://kbin.social/u/iluvroris (visible in the activity tab)
even his profile is nsfw. This is exactly the reason why kde must NOT federate with us, because of freaks like iluvroris. That's the harsh reality. As long as we accept nsfw, we cannot and should not be federated by big brand like KDE. We have to pick who we federate and it cannot be everyone.
I don't agree with this.
We should work towards better tools for letting people tailor make their own feeds to show the content they want to see, not call for defederation based on content or ideology.
It's not there. Even the admin of lemmy recommends to not federate everyone:
There will always be malicious instances, if you allow every instance by default then you will have to fight against an infinite amount of child porn. Non stop. It will last 24 hours until the admins of respectable instances like KDE or Mozilla defederate everyone by default and only federate on-demand, after vetting.
We have to decide where kbin.social stands in term of federation. But I can tell you one thing is that KDE and Mozilla will never, ever tolerate the slightest nsfw on their instance.
Is this the reason why my single-user instance can't subscribe to any https://kbin.social magazine? I'm not even getting an error, just "Subscription Pending". That sounds kind of broken and different to how Mastodon is dealing with that issue.
Do I somewhere need to apply to be able to subscribe to any /kbin magazines? If so where do I do that? Is there a email I can sent my application to? Or is the idea that if you have a single user instance you create a new user on every instance to find some meta-magazine where you can ask to be able to subscribe to a magazine on that instance?
Or are small instances not part of the design?