@design_RG @mngrif @arteteco Seems I'm going to reluctantly have to vote to silence neckbeard, pl, and FSE.

Giving safe harbor to individuals who evade bans and complete inaction regarding resolving it is too big a risk to the safety of our users. If they can no longer block users they wish to block they have no protection against harassment. Since this individual threatened to murder someone it is particularly concerning.

As was seen I reached out to the admin of all three instances and after a long talk none were willing to take action to ban or contain the user in any way.

For these reasons I reluctantly need to vote for a silence.

Any votes from the rest of you or discussion left?

@freemo @design_RG @mngrif @arteteco

I'd like to register my support for letting the affected user deal with this himself using the "Hide everything from example.com" feature.

The following is on QOTO's about page.

What won't get you banned:
Anything that can be solved by a personal block

Why not apply the same standard to silencing instances as to banning users?

@freemo @design_RG @mngrif @arteteco

I'd be more supportive of an instance silence if we had the feature proposed here. That would make silencing an instance merely an overrideable default, and I have no problem with the mods trying to set up sane defaults to ensure new users have a generally decent experience off the bat.

@khird

I entierly agree, if users could override a silence and effectively unsilence an instance that would be a very valuable feature i would support. In fact that would solve a lot of other problems too now that i think about it (would totally make the isolate gab movement pointless for example).

@design_RG @mngrif @arteteco

@freemo
If you already reached some conclusion feel free to not include me, I was late and as we've always done who's present takes the decisions, otherwise it would slow us down a lot.

Maybe just open a topic on discourse linking the discussion on mastodon, for transparency?

@khird @design_RG @mngrif

@arteteco

I was traveling and getting setup in my USA home, so I put this topic on hold. No actual decision was made.

Now that I'm situated I want to come back to this as well as hear your input. I'd rather avoid silencing... perhaps an interim option is to create a "suggested block list" that we offer to users and encourage them to block those instances, of their own choice, and detail the reasons, leave it up to them.

Then maybe I can implement a feature where the suggested blocklist is automatically applied to users accounts by default but they can select to opt out as they wish.

The problem has continued, and has gotten worse, so I dont think the instances that have done nothing in response should just be ignored. Thankfully most of the instances contacted were all quick to resolve the issue on their end.

I can start a discourse topic to discuss.

I will update everyone effected as a decision is reached, but for now letting those involved know that no silence has been enacted yet.

@khird @design_RG @mngrif @casualwp @hrisskar @snow @AtlasFreeman @p @nepfag @redneonglow @Lumeinshin @march @jack @sjw @FBI @mewmew @nosleep @jasonl8446