Event JSON
{
"id": "19253a855b7d99f3c091f6139bad8207a190fa39048d62ec6d5949a84346a68e",
"pubkey": "27a3982cfffbba2ecd32b4333a9158f66a2020126ea40c5add0071f76ddb0906",
"created_at": 1683381703,
"kind": 1,
"tags": [
[
"p",
"082d8eb8c22c78365b80c817bb52829e03abe58d1747189a47c40ba06a5fdd5e",
"wss://relay.mostr.pub"
],
[
"p",
"e789bceb291e2eab9e1f0e99983525af0dbc65f8e347be4330c8a2ef2dc9aa5b",
"wss://relay.mostr.pub"
],
[
"e",
"be9962bd2c13fab3b2e24103c780b8553ff33080b568bd748c9e7a0400c0c121",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://mastodon.social/users/LibertyBeta/statuses/110322103340707603"
]
],
"content": "nostr:npub1pqkcawxz93urvkuqeqtmk55zncp6hevdzar33xj8cs96q6jlm40qrjz65u Wow, near thread. I feel like we still haven't hit the sweet spot. ActivityPub is nice because of the low hardware req, but the data accumulated for say a Mastodon instance is still large. \n\nAT/Nostr don't fix this, but it's the defining challenge I think.",
"sig": "72e9b1c6fbb3b80627859c253ff21c236cfbff90d1a7ff7f696c04dc35a9d4120b8e075ab0e862b9a7e72ad258549bdff3fada52b60dc7bf73ae7551de6d6ead"
}
