Event JSON
{
"id": "8b21e7439d6d1fb193f8f16111517fc0785766a40a3ae4f24f3b27fbf482ffd7",
"pubkey": "00ac78edcaf7b85772fb55f14e26011d4857cf3fa8b337164411fb7bef6d2312",
"created_at": 1688245770,
"kind": 1,
"tags": [
[
"p",
"fc3ee9eac1226d28983115b526ab21e0e889373d75bf385cb36d4a73128fc89a",
"wss://relay.mostr.pub"
],
[
"p",
"40c5eea5a8e635e95a5f2693c79b6e78e27d2cfb59ba9e2f85e46ad229fe9aca",
"wss://relay.mostr.pub"
],
[
"e",
"4dfd0f71e6bc79397fed617d0c18dc2c8dd95f47da79c6e1ad7feafb9f957891",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://mastodon.social/users/Elucidating/statuses/110640874815922673"
]
],
"content": "nostr:npub1lslwn6kpyfkj3xp3zk6jd2epur5gjdeawklnsh9nd498xy50ezdqfz9c2x it's super clear in the aftermath that Twitter didn't understand how it was ddosing itself and thought this would somehow fix the problem rather than being the website down.\n\nExtremely funny.",
"sig": "09a8cbd0ae4700edf0a298c65b40f41073ded1d1f749b35f3db1196729e999c64f7e6c50ff898fd00c25d457415720ab56a51bd557bdf61292bd3f0c48002862"
}
