@lina@vt.social test
Backup/admin account. You're probably looking for @lina.
Backup/admin account. You're probably looking for @lina@vt.social.
Backup/admin account. You're probably looking for @lina.
@lina@vt.social test
Backup/admin account. You're probably looking for @lina.
@SiteRelEnby@transfem.social @floralia@girlcock.club All good. And yeah, blogs/etc can be a sign of "this is not a person I want to interact with" but themselves don't necessarily indicate they've lashed out at other people directly before, or that moderation already failed.
I guess the takeaway is, if you feel attacked (valid) and just need to vent, drop the hashtag.
Backup/admin account. You're probably looking for @lina.
@SiteRelEnby@transfem.social @floralia@girlcock.club While the reports were appropriate (and the person has since been suspended), I don't think calling for fediblock in response to a single incident is useful, worthwhile, nor productive.
Decentralized instance moderation does not scale to "every random person who is an ass or crashes out on every random instance". Quick remote moderator action is useful chiefly to deal with trolls who are targeting others by *initiating* interaction (in practice, at the account level, it's mostly useful for quick reaction for spam or phishing before local instance moderation reacts). In this case, the person in question was not tagging anyone indiscriminately, and remote mod action is not warranted nor useful. Just report, block, and let the moderation process handle it please.
If and when the process fails and the individual in question is demonstrably a longer term repeat offender, that's when you should start considering public escalation (and at that point the lack of mod action from the instance would be concerning).
Backup/admin account. You're probably looking for @lina.
Backup/admin account. You're probably looking for @lina.
Backup/admin account. You're probably looking for @lina.
Backup/admin account. You're probably looking for @lina.
Test from staging