{"type":"rich","version":"1.0","author_name":"codonaft (npub1al…7rg94)","author_url":"https://nostr.ae/npub1alptdev5srcw2hxg03567p4k6xs3lgj7f6545suc0rzp0xw98svse7rg94","provider_name":"njump","provider_url":"https://nostr.ae","html":"\u003e Clearly you are doing this. When you request a feature in GrapheneOS, then you request the Graphene team to work on this solution.\n\nNope, this is out of context.\n\nI *used to* request this in the past (before publishing this meme) here on Nostr, but as soon as I noticed they ignored my messages, I did research and found their \"criticism\" of the similar request:\n\n\u003e What you're requesting is that we add things which are easily detected by unsophisticated adversaries\n\nWhich is a strawman argument. The duress pin behavior is currently clear without any tools: a device reboots, shows an error.\n\nAnd in the same response they have:\n\n\u003e Keep doing it and you'll be suspended\n\nBecause somebody suspected that they are targeting some unexpected scope they can't properly explain.\n\nTwo very bold mistakes in one comment. This would be insanity to ask them for any request after reading all this.\n\nAnd what scope is that really? I don't know for sure yet. I received an independent response here, a good one:\n\nnostr:nevent1qqsxfetl54z0lr43s5p6lxk6hygyjgkp8sun8tn2mv83dencr6dl87gprpmhxue69uhkummnw3ezucm0v3hkuctxwshxxmmdqy28wumn8ghj7un9d3shjtnwd4skjmpwd35sygpjvd68tmqz2maaw4zhrt422tz52nym670m0tzmn86nhpk0ew2j0g730lnp\n\n\u003e protecting whoever else\n\nIs the phone owner's security part of the scope? Hello, nostr:npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5? I know you won't respond to me. All this is for the records.\n\nUsers have no idea what Pandora's box they are carrying with them."}