this post was submitted on 16 Jun 2023
96 points (100.0% liked)

/kbin meta

200 readers
2 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
96
Spam and porn are flooding kbin already (kbin.social)
submitted 1 year ago* (last edited 1 year ago) by frasassi@kbin.social to c/kbinMeta@kbin.social
99 comments fedilink hide all child comments
 

There is a substantial amount of spam and NSFW posts on the All page coming through already. Most NSFW posts aren't being tagged as such and are coming right through. I am not sure how this can be weathered but we need something in place fairly soon, I feel like we are days away from rivers of bad stuff, especially via some of the federated instances.

EDIT: I personally don't care much about the NSFW aspect, more in the lines of what a newcomer will be seeing when they get to the main page. 99% of the newcomers don't know / care about federation and have no idea how to turn that off. Liability for the server owner is also an element of consideration.

you are viewing a single comment's thread
view the rest of the comments
[–] aroom@kbin.social 2 points 1 year ago* (last edited 1 year ago)

it may have the same effect but it's not the same feature. if you block domains, like you block magazines or users, you get to have an ensemble view of all those in your user settings. that kinda make sense.

and I can't find where the instances defederated with your technique are listed. maybe you know where?

edit: syntax

EDIT: this doesn't block the instance, but only the domain. new tool coming soon, confirmed by the main dev:

domain blocking existed long before federation. It serves as a way to block sources like youtube.com, spotify.com. Blocking instances will be a separate option in the user profile soon. I will submit a pull request.

https://codeberg.org/Kbin/kbin-core/issues/118#issuecomment-942720