GrapheneOS turns 10 this year, quality work takes time and all of this definitely didn't pop out of nowhere suspiciously. IMO this has been the best past 12 months for GrapheneOS so far. Several vuln disclosures, duress password, Vanadium content filtering and more in a small span of time. We definitely appreciate people coming to support GrapheneOS in droves the past 12 months.
It wouldn't make sense for us to be malicious for many reasons, not every GrapheneOS team member is working in private (e.g. the founder) and we have a Foundation registered in Canada with multiple directors. We participate with the broader cybersecurity community with vulnerability disclosures and such. There's nothing wrong with concealing your identity but in our case, we have reputation and our professional lives on the line not to be evil. How we work is very different and open in comparison to real sting operations ran by governments or scam products owned by criminals.
We dont deny certain people want to break us. We will never say we are impenetrable, but we are aware our work is targeted by threats aligned with governments such as in the leaked Cellebrite documentation where they discuss their failures with GrapheneOS. These people deceit the public with vague and misleading information to discredit us. Our effort the past year is down to fighting back on this attack and our fight is completely in the public eye for people to watch, we already survived a hostile takeover attempt, so we we're very sure we're here to stay.
final [GrapheneOS] 📱👁️🗨️
npub1c9…7sqfm
2024-07-19 17:31:02
in reply to nevent1q…23rx
Author Public Key
npub1c9d95evcdeatgy6dacats5j5mfw96jcyu79579kg9qm3jtf42xzs07sqfmPublished at
2024-07-19 17:31:02Event JSON
{
"id": "b6257d9eff4458799b5c6d9d4744bc051c0c42a899c178f290c856ffc511d071",
"pubkey": "c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185",
"created_at": 1721403062,
"kind": 1,
"tags": [
[
"e",
"ca95eb8eed573995c8f520c2f8f1daff0da1ff93de63824ab6c44b32cf3e3910",
"",
"root"
],
[
"e",
"0321511a64fcf7d008eb56b199a1315ea06e949bf0e63c1c0e8574377b7ce9fc"
],
[
"e",
"6198cb2a36874e23688a46199dbc6c1da86362b867a0fc5e242199716ca303b8",
"",
"reply"
],
[
"p",
"d0debf9fb12def81f43d7c69429bb784812ac1e4d2d53a202db6aac7ea4b466c"
],
[
"p",
"c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185"
],
[
"p",
"f3f2589280adfd611d4693a24dd711f6b49053aeb5c856c5baa50318c12d20ef"
]
],
"content": "GrapheneOS turns 10 this year, quality work takes time and all of this definitely didn't pop out of nowhere suspiciously. IMO this has been the best past 12 months for GrapheneOS so far. Several vuln disclosures, duress password, Vanadium content filtering and more in a small span of time. We definitely appreciate people coming to support GrapheneOS in droves the past 12 months.\n\nIt wouldn't make sense for us to be malicious for many reasons, not every GrapheneOS team member is working in private (e.g. the founder) and we have a Foundation registered in Canada with multiple directors. We participate with the broader cybersecurity community with vulnerability disclosures and such. There's nothing wrong with concealing your identity but in our case, we have reputation and our professional lives on the line not to be evil. How we work is very different and open in comparison to real sting operations ran by governments or scam products owned by criminals.\n\nWe dont deny certain people want to break us. We will never say we are impenetrable, but we are aware our work is targeted by threats aligned with governments such as in the leaked Cellebrite documentation where they discuss their failures with GrapheneOS. These people deceit the public with vague and misleading information to discredit us. Our effort the past year is down to fighting back on this attack and our fight is completely in the public eye for people to watch, we already survived a hostile takeover attempt, so we we're very sure we're here to stay.",
"sig": "98759aa7c6347a4917f9282ea6343d6f3380d6dd2bee626025a33f65069442c128ccb05152fdd7e5c3b8facc9b567073e7236f1758589f1021bc5b2bfaa735c2"
}