Event JSON
{
"id": "4070d194674775bf4da42389b87702985753730cf3885e7607ac04de548db109",
"pubkey": "92f68fed5cb8a1b7ad9933ae71712caeec1f24303d971cdfe40567809244e9e4",
"created_at": 1739562659,
"kind": 1,
"tags": [
[
"p",
"dbd981bf1d349a0c99e1b52c1803eb8e77856f1d9337f1340f09a23de99a7484",
"wss://relay.mostr.pub"
],
[
"p",
"4fc78a5e007004d824437030f189c4a74a87c1d9f3b6c64b1d0717a41890caca",
"wss://relay.mostr.pub"
],
[
"e",
"da87e35c2e64a48738a2f14c3720c5d05257ab552803979d26aee7352691f82f",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://techhub.social/users/Ctrl_R/statuses/114003978473039560",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqm0vcr0caxjdqex0pk5kpsqlt3emc2mcajvmlzdq0px3rm6v6wjzqm7ulpn \nI understand the point of view of making it a feature... I don't see why it is considered bad, though, to show a public post via a fetch when there is otherwise no other way implemented to quote a post. If the feature is implemented and a user marks a post as unquotable, then I'd understand it being bad form for a client to circumvent that and allow it to be quoted via a fetch anyway.",
"sig": "7866ba3716f02d311dcadf79a3135e5fe18fe986312360eef3d4fd683efff9f74dfc210225469be47e1bbbcc7fe33366c50b44c4fb8cb671cabcd86760efb123"
}