Event JSON
{
"id": "cf1f6f53344a97039ba3f06f48c788b564940420834ac9957f3e722c929ba87a",
"pubkey": "1a92c4f09cef90b9f3f8a8b948b45ddc739df02ce3e40ae1e61c5f3bbd5af039",
"created_at": 1691316200,
"kind": 1,
"tags": [
[
"p",
"83211688d74e23b5b47eed0b284aa77350f4bd2823fbc513abe9b9a60bba99f9",
"wss://relay.mostr.pub"
],
[
"p",
"7a782f19a831130622d08a5aaf38d1d252e352dca4b16683ccb7d93171e8f10f",
"wss://relay.mostr.pub"
],
[
"e",
"9167dfd03c5efc464aed224e2c763675be9c1146f4e536c7bc06d76706a34a5c",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.gamedev.place/users/njamster/statuses/110842098539990152",
"activitypub"
]
],
"content": "nostr:npub1svs3dzxhfc3mtdr7a59jsj48wdg0f0fgy0au2yataxu6vza6n8userp66u I read \"a limitation of the protocol\" as \"a limitation of ActivityPub\" since that is the protocol Mastodon is using. It's true that the Mastodon API doesn't support this feature and that's what stopping clients from implementing it, but that's on Mastodon itself, not the protocol it's using. As far as I can tell, ActivityPub doesn't do anything to prevent this feature from being implemented as described.",
"sig": "ede453a9b3fab65f6c0ab875fb63c1fdb75dae91ebc782f33dd90ba4bccfaec10ec4bd507ddedc5a70733d6215b09beea4e6752a6cf720e05daa406881bcd535"
}
