How do we get an instance removed?
How do we get an instance removed?
It looks like a new spamming tactic will be to set up your own instance and then just mass spam to other instances from there. Case in point, vive.im I've been noticing spam in one magazine from a user of this. I banned them, but they can still post for some reason. Decided to visit the instance and it looks like some default front page with '3' active users. If you look at the user's account on there they've made 12k posts already and seem to have a script set up to push their blogspam 3-4 times per minute.
-
We need a clear process to report and get these kinds of things removed quickly.
-
Bans need to work properly and stop these users from posting.
-
@ernest , that server has no Public info at all - can we limit/silence or defedrate it ?
-
Seems like manually approving new instances before they are allowed to push content to Kbin would be a good idea. Shouldn't gatekeep but blindly accepting them means playing an endless game of whack-a-mole.
-
i don't agree. I think it is important to maintain a blacklist instead of a whitelist where people would then submit what they need to add which will then will need to be approved etc. It will decrease the federated experience.
-
IMHO: We should retain automatic federation approval but with automated de-federation for bad behavior. Thresholds could be increased for "merely very active" instances so they don't get automatically defederated while newcomers get the threshold for "plebs" 😁
Example: If your instance has just a handful of users spamming like crazy or any number of users spamming the same content/links that would put your instance over such a ban threshold pretty fast.
-
This doesn't seem ideal though, because newer instances will be silenced and never get a chance to grow. In any case, it would be reasonably easy to create a kbin and load it up with fake accounts anyways, to get the numbers up. A more standard approach is to simply look at the traffic coming from smaller kbins and if they are sending lots of requests, automatically remove the instance. This could still be caused by one bad actor making it's way onto a newer server though.
-
-
As a user on kbin you can block a whole domain. That definitely works on the post level and I would assume the comment level as well but I haven't tested that part.
-
Unfortunately I'm looking at this from the perspective of a moderator, and the issue is that despite being banned, they can still post to the microblog.
-
-
That does not work unfortunately...
-
-
I'll try to take care of it today and potentially clean up the activity. For now, I've limited the traffic from that instance. I'm currently working on additional tools for moderators.
-
Thanks Ernest. I definitely think if we've blocked a user in a magazine the microblog shouldn't be picking up stuff from them, and we need to be able to turn on automatic hashtag pickup or not.
-
Hey Ernest, not sure if you did something or not, but still picking up posts from this guy
-
-
@crossmr thanks for this post, this server has been involved in spam for almost two months so I alerted the microblog side of fedi
I noticed dnc@vive.im was followed by two kbin.social users, and kbin has an "interesting" feature where a microblog post goes into the magazine named after its first hashtag (if it exists), hence why your subs are getting them
i think the two kbin.social users might have followed this user by mistake. i checked their profiles and they both look legitimate to me.
-
I would like some kind of content-warning type situation, but where I can define what kind of content I want to restrict. And then, somehow, instances have tags associated which then apply to all of their users so that I can have a warning that users of a given instance have a reputation for sharing content that I would like a warning about first.
I would still want the content to be posted, but I would prefer that it requires me to actively unhide the content and default to always seeing it.