Event JSON
{
"id": "6a945b68264ea675a753a7ae904c23a203616ccc45e4368c6ea4c74524a6ff53",
"pubkey": "dc0371d60e4af10abf91a211da7b396d6b66ec6fbfadaf71a9886d7bf6be0e49",
"created_at": 1742931583,
"kind": 1,
"tags": [
[
"p",
"0a31612a98df1a94626077fba1989e77921223fef27842755aeb98b9fa41e927",
"wss://relay.mostr.pub"
],
[
"p",
"80c22a3f9bbdf0c245d57179851410b48497764fca16fbdb8463e446b585ce5a",
"wss://relay.mostr.pub"
],
[
"e",
"d295019ef6a4728c7bb3216ed1730bf96d4a8aa4cda000a5a4751bbb33a0a21f",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://toot.cat/users/EveHasWords/statuses/114224764277152706",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqpgckz25cmudfgcnqwla6rxy7w7fpygl77fuyya26awvtn7jpaynsq4cfuw I'll grant you I don't use Windows most days, but I've never run into a case where Chrome was incapable of updating itself in the background on a standard Chrome install on Windows. Whereas Chrome on Linux is incapable of ever installing its own updates even when you use the official, Google mandated installation method.",
"sig": "8f7f3e024b469f3bf1b4b85b8dff32a35e86bf90952a29becfba3af3da275cb2aa878492924fe28b09a5fa5435cfc97f799e7bbc3662172153cad7a151d90c4c"
}