Event JSON
{
"id": "a3eb17cf8d1d7003b5a12c3575694c5724cedaa9cd37a1a457327b24228ac12a",
"pubkey": "2464a99bb3a2cface2d500032721fbdb4f036b4c92624d2039a11cc2d6a744a4",
"created_at": 1715932449,
"kind": 1,
"tags": [
[
"p",
"33cb33d5a6bf09380fd6fd11699e5e06e5ada3fe82354e4aa32606a2c2c805ca",
"wss://relay.mostr.pub"
],
[
"p",
"8b157600ebbfe6da4f39269667901eca60ea12dfa58ded990a743d6840d82c71",
"wss://relay.mostr.pub"
],
[
"e",
"026d929a49ded0e24492e701b62fa1d0fe9d7b04bb33b7b1aaa137f255b3233d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.alexn.org/users/alexelcu/statuses/112455349029070933",
"activitypub"
]
],
"content": "nostr:npub1x09n84dxhuynsr7kl5gkn8j7qmj6mgl7sg65uj4rycr29skgqh9q92jlxu In fairness, this is probably Firefox's fault. Given Twitter.com worked just fine in Firefox, they'll likely have to update their rules.",
"sig": "ac92517996461f76ae97ccfac05022d5a7036cc97dd042dfc0f5d5bbf05adf8783625c272f1d7522166ed71f18fd4d034effbbd43a503e1cd247fcd4d56c0eec"
}
