Email or username:

Password:

Forgot your password?
Top-level
Kev Quirk

@stevenroose I think block is so they can’t see your stuff. For you not to see them you need to mute....I think.

@Gargron

5 comments
Steven Roose

@kev @Gargron Well I want others not to see them, under my post.. F.e. when they are trying phishing or just spamming.

Kev Quirk

@stevenroose you can't do that. Having the ability to do something like that would mean we can all effect what others see and the whole thing would fall apart.

The only thing close to that would be taking action for your instance (as an admin) but that would still only affect users on your instance alone.

@Gargron

Steven Roose

@kev @Gargron Hmm so it's not possible also f.e. to block people from replying to my tweets? I mean me removing a reply is quite similar to blocking the user to reply in the first place, right?

If I remove a reply, that shouldn't result in a disparity of what various people see, no one should see it.

I would basically ask my server to not show that reply in the list of replies when someone queries replies to my post..

That seems all pretty reasonable to me.

Eugen Rochko

@stevenroose @kev This assumes that a post is the source of truth of its replies. In the fediverse's current model, the source of truth is the author of a post, i.e. being a reply to something is a type of metadata on an otherwise independent post.

Steven Roose

@Gargron @kev Hmm, yeah I understand that.. And I get that that's important. So what are the options to fight spam then?

(1) contact the spammer's server's admin
(2) ask your admin to block the spammer's entire domain

So (1) is obviously preferred. But it both demands a lot of energy from admins and it doesn't help if domains have loose policies or are intended for spam.

And (2) is actually similar to what I requested, just delegated to the server admin. The spammer's post can still exist.

@Gargron @kev Hmm, yeah I understand that.. And I get that that's important. So what are the options to fight spam then?

(1) contact the spammer's server's admin
(2) ask your admin to block the spammer's entire domain

So (1) is obviously preferred. But it both demands a lot of energy from admins and it doesn't help if domains have loose policies or are intended for spam.

Go Up