Event JSON
{
"id": "b4a97957b07bd7569b1dfa9763296994419bb0ee0d81daaf8128d3d8f4fa680e",
"pubkey": "06af31dcfefa0340ad608f45694a8d7821f3b9c865375a5269ef5ad48c569a43",
"created_at": 1748202638,
"kind": 1,
"tags": [
[
"p",
"5b3a7414e933d3683c2b89d83f516c7a971781b4cb3d3a33c9c07fa5d6b74fac",
"wss://relay.mostr.pub"
],
[
"p",
"5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"wss://relay.mostr.pub"
],
[
"e",
"667af0a6c8ea1ff51925f40e0214743b7925939ff06a13920856b94883ad23ff",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://nerdculture.de/users/fluchtkapsel/statuses/114570208122820433",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.mostr.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqtva8g98fx0fks0pt38vr75tv02t30qd5ev7n5v7fcpl6t44hf7kq5fm8mr Without piling more on GrapheneOS, my take is that the pragmatic approach would be to just include espeak-ng until a better solution comes up. If companies want to use GrapheneOS, they can simply remove this component.\n\nSecurity concerns? IMHO, after initial setup there's no need for espeak-ng anymore and can be replaced by something else.\n\nBut of course, that's just my position. I guess it's too late for a pragmatic approach now.",
"sig": "6deca170cc21c367f500d4e539ef489b65cc93cfa30bcf39d88450f58e1f5944ed7f241158bef23e7c7b4e7f055640a358972fae7a42e9b5f1fe91a52eac2209"
}