Followup: May 7 raid threats
A followup article on the raid threats that happened on May 7th.
Last updated
A followup article on the raid threats that happened on May 7th.
Last updated
About a month ago, we disclosed all details we have of the raid threats that were made to a connected server of the official instance on May 7th. Despite this disclosure having potential to restart conflict, we at UnifierHQ and HYP representatives have agreed that disclosing all information for disclosure purposes only would be best for the sake of HYP members and other connected servers.
Unexpectedly, we got contacted from a PNW representative a few weeks after we posted the article.
Unfortunately, this wasn't some kind of offer for a peace negotiation, or a notification that action has been taken on their side in light of these conflicts, but rather a request to remove some content from our article. As their points were valid, and I didn't want to cause misunderstandings within the Unifier community, I decided to modify (not remove) some content to prevent misunderstanding.
This is definitely not what I would've wanted from a representative of the alliance that made me have a mental breakdown for a week or so, but it's still a bit nicer having someone talk to me about the issue instead of ignoring me or saying I'm being "oversensitive".
On September 21, we noticed something strange: the raiders' Discord server was apparently deleted.
I initially thought my cover was blown, and that my account was banned from their Discord server (I joined with an anonymous one, but I made sure I wasn't banned in my main account beforehand so I wouldn't be ban evading). I attempted to rejoin the server on the same account, using the same public invite link we'd found on the owner's profile. If I was banned, it'd show "This user is banned from this guild" (this is how I checked if I was already banned or not, if my main is banned then my entire IP is banned), but instead, I got an "Invalid invite" error:
So we asked our second witness we contacted in our disclosure article, and they also said that the server was missing from their server list as well. This led us to conclude that their server was most likely deleted or banned from Discord.
Update Oct 17: We have received confirmation from another server that the server was deleted.
Not really. Like I said in the previous article, Vic is still dead set on raiding HYP's Discord server. We don't know when raids will happen, nor who will pull off the raids, so we always need to stay prepared. But, if the server was indeed deleted or banned from Discord, he will have significantly less firepower against HYP now, so HYP's raid defense systems and our RaidGuard Plugin should suffice for the time being.
Threats such as these are why we develop things such as Safety Alerts and Under Attack Mode, so servers can better protect themselves from an incoming raid, and minimize the impact it has on the wider Unifier community. We put user safety as our top priority, so even if there's significantly less organization between raiders that make raids much less likely, we still want to prepare for the worst.
We ask the PNW members that took part in the harassment, either by directly contributing to the harassment, endorsing the hateful behavior, or/and taking no action as someone with authority against the perpetrators, to take better action against behavior like these instead of dismissing them in the future, because harassing others and threatening to raid their servers is definitely not something we'd want to see, especially because this whole ordeal was caused over .
And instead of blaming UnifierHQ for "causing drama" within their community, they should instead reflect on their own behavior and negligence that has escalated the conflicts to this point, which is what led to their permanent bans from Unifier. Especially since we didn't create the drama, we were only doing our jobs protecting our community, and they started the drama themselves.
Even if we won't be unbanning them under any circumstances, we believe this is the bare minimum they should do.