Their overly permissive moderation and the content in their podcasts wasn't a valid reason for us to block it. Blocking on a case-by-case basis worked fine without collateral damage.

Unfortunately, their community is a very receptive audience for the kind of fabricated stories and spin being propagated as part of the attacks on GrapheneOS and it has become a bigger and bigger issue.

We recently found the system administrator of the instance is involved in the harassment, and it's now blocked.

https://grapheneos.social/@GrapheneOS/110954050193388835