Avatar
GrapheneOS (RSS Feed)
2306b336f168f4add8da924dae907d2a6b9c13fb0a06672bd7708295dec75da7
Public posts from @GrapheneOS@grapheneos.social https://grapheneos.social/@GrapheneOS

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

One of the servers on this list is connected to a conspiracy theory focused podcast. We aren't very similar with it and aren't sure to what extent it's tongue in cheek. One of the podcast co-hosts uses GrapheneOS.

A significant number of people there were following this account before today. Despite being a large instance permitting almost any legal content, we didn't experience much toxicity from it until May, but it has gotten very bad due to overlap with the main source of the harassment.

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

We've been considering shutting down our Mastodon instance due to the level of hate directed towards us on the platform including harassment and fabricated stories targeting our project members. We've decided to import the minimal FediNuke blocklist to cut down on some of this from reaching us.

https://writer.oliphant.social/oliphant/the-oliphant-social-blocklist (https://writer.oliphant.social/oliphant/the-oliphant-social-blocklist)

However, this is far from sufficient as much of the harassment comes from mainstream Mastodon instances. Support for the harassment is pervasive in many open source communities.

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

We've used blocking in response to our project and community being targeted with harassment, libel, racism, trolling, etc. rather than proactively blocking many servers. We tried to only block servers where the admins were either supporting the toxicity or bypassing blocking.

Our approach was working fine until the harassment massively escalated in April with multiple severe swatting attacks and threats of violence. A YouTuber closely involved with Kiwi Farms escalated it much further in May.

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

Our grapheneos.social Mastodon instance hosts official GrapheneOS project accounts and personal accounts for GrapheneOS project members including our developers, community managers and moderators.

Our project accounts across Matrix, discuss.grapheneos.org, grapheneos.social and elsewhere are shared accounts. Multiple project members have access to them.

Partly due to our experience having followers cut off from us when we were on infosec.exchange, we started with a very open federation policy.

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

We'll need to be receiving feedback in order to continue supporting the Pixel Fold. It currently has official, fully functional and stable GrapheneOS support.

Continuation of that will depend on the community providing feedback due to an issue with the device we got for testing.

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

We're not receiving enough testing feedback from users on Pixel Fold. Since it's not as common as other devices, we need a higher proportion of users to help with using the Beta channel and providing feedback for releases in our #testing (https://grapheneos.social/tags/testing):grapheneos.org channel on Matrix.

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