/kbin meta

6 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 2 years ago

165

We should defederate from lemmynsfw (kbin.social)

submitted 1 year ago by LollerCorleone@kbin.social to c/kbinMeta@kbin.social

282 comments fedilink hide all child comments

The mods there have decided to allow underage looking content, skirting close to CP. Unless we want such disgusting stuff on our feed, I think we should defederate from that instance.

Pinging @ernest as well.

you are viewing a single comment's thread
view the rest of the comments

[–] Friend@kbin.social 8 points 1 year ago (1 children)

I have taken the executive decision to turn federation off for a similar reason.

I was recommended a vile post on the sidebar from m/random which I definitely never want to see the likes of again. I did report it but since it was from another server I don't really know where that goes.

I'm not going to turn federation back on again until I find a way to prevent it. Perhaps we should start a blacklist?

[–] 0xtero@kbin.social 11 points 1 year ago* (last edited 1 year ago) (2 children)

You can blacklist sites you don't want to see.
Go to https://kbin.social/d/<the instance domain name you want to block>
For example: https://kbin.social/d/sh.itjust.works

On the right side-bar, in the Domain box, you'll see this you'll see this
Click on the block symbol and you will not see content from that domain again.

(hopefully)

[–] Friend@kbin.social 6 points 1 year ago* (last edited 1 year ago)

Thank you and I appreciate the write up but I had actually already blacklisted a few domains.

Unfortunately that did not prevent the post from appearing in m/random because it was from a domain that I had not already blacklisted.

I simply do not want to have to act reactively once I have already been exposed to the vile content. At that point my experience is already ruined whether I block it afterwards or not.

Another reasonable approach might be to block m/random which I might consider doing if I am tempted to enable federation again, but for now I'm just going to play it safe and stick to kbin.social.

[–] bing_crosby@kbin.social 1 points 1 year ago

Ah that's good to know, thanks very much for the info.