GrapheneOS Foundation Transition Clarification Update:
We're continuing to make progress towards moving stewardship of GrapheneOS to the non-profit GrapheneOS Foundation. We'll be replacing our previous announcement with more detailed info on our website. We removed the thread here since it was being misunderstood and misrepresented.
There has been a significant effort to spread fabrications and spin targeting our project members with the clear aim of directing harassment towards them. Our founder stepped down as lead developer due to extreme level of harassment including multiple extreme swatting attacks.
We explained in detail how we were moving forward by transferring responsibilities to the GrapheneOS Foundation and the new lead developer. We explained it would be a long process. We don't understand how what we posted was so widely misinterpreted as someone leaving the project.
We have a team of 6 full time developers that's growing along with people working on the non-profit organization. Nearly all have been involved for many years. We've avoided other project members being targeted with significant harassment by minimizing their public exposure.
Due to the extreme attacks on GrapheneOS, most of our project members aren't comfortable with a public facing role. It's why there are so few interviews with our team, and part of why it's so difficult for us to build up the non-profit since people don't want to become targets.
We have a substantial amount of funding available to the non-profit that's not yet being used because of the difficulty in expanding the team under these adverse conditions. We could have 12 full time developers or more, but we don't because of these attacks on the project.
The way we've protected our team led to increasingly more targeted harassment towards the only person who had a public-facing role. The attacks shifted from technical misinformation to bullying/harassment based on misrepresentations/fabrications referencing the past harassment.
MetropleX [GrapheneOS] ⚡🟣
npub1gd…7cn8c
2023-09-30 14:08:19
Author Public Key
npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8cPublished at
2023-09-30 14:08:19Event JSON
{
"id": "9b7fdd68d9ec09ea83ffc3128571dbbd6ab946a04ea241847342b39a166e7ec5",
"pubkey": "43637a311a15f1c253b5d60778ab7544ac639b88e168e7224a900d4a41283183",
"created_at": 1696075699,
"kind": 1,
"tags": [],
"content": "GrapheneOS Foundation Transition Clarification Update:\n\nWe're continuing to make progress towards moving stewardship of GrapheneOS to the non-profit GrapheneOS Foundation. We'll be replacing our previous announcement with more detailed info on our website. We removed the thread here since it was being misunderstood and misrepresented.\n\nThere has been a significant effort to spread fabrications and spin targeting our project members with the clear aim of directing harassment towards them. Our founder stepped down as lead developer due to extreme level of harassment including multiple extreme swatting attacks.\n\nWe explained in detail how we were moving forward by transferring responsibilities to the GrapheneOS Foundation and the new lead developer. We explained it would be a long process. We don't understand how what we posted was so widely misinterpreted as someone leaving the project.\n\nWe have a team of 6 full time developers that's growing along with people working on the non-profit organization. Nearly all have been involved for many years. We've avoided other project members being targeted with significant harassment by minimizing their public exposure.\n\nDue to the extreme attacks on GrapheneOS, most of our project members aren't comfortable with a public facing role. It's why there are so few interviews with our team, and part of why it's so difficult for us to build up the non-profit since people don't want to become targets.\n\nWe have a substantial amount of funding available to the non-profit that's not yet being used because of the difficulty in expanding the team under these adverse conditions. We could have 12 full time developers or more, but we don't because of these attacks on the project.\n\nThe way we've protected our team led to increasingly more targeted harassment towards the only person who had a public-facing role. The attacks shifted from technical misinformation to bullying/harassment based on misrepresentations/fabrications referencing the past harassment.",
"sig": "3fefb1edd78feb3614910e04253c34ec83c84a739beb5adec21c03fe739256952a8b7c91317b44fab0c61244c17fb285b34eaa1dafb733fa17a529c1a7c25955"
}