Event JSON
{
"id": "ad3fae75a6977d2142f51aaf240d7ab968a44efa42ffe2d8db56b27aab847edb",
"pubkey": "e653eb60b2db5edf906d354c2825bf00a80dfab1b1766cd97805155e8fcc0db3",
"created_at": 1710948033,
"kind": 1,
"tags": [
[
"p",
"55e6ff7bd45b38b4478974411f4a505987725b9e783480d19998c6b3f3e0eff4",
"wss://relay.mostr.pub"
],
[
"p",
"d1c57757ad22b24d62a0357f385b931e402073e2028f3a8142e094b6bf8d1c6f",
"wss://relay.mostr.pub"
],
[
"e",
"a60510bfc441c15cd0a6cd2ca18c853538fcb051f198fa04ac2b42cb51cef10b",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://phpc.social/users/ramsey/statuses/112128690308960912",
"activitypub"
]
],
"content": "nostr:npub12hn07775tvutg3ufw3q37jjstxrhyku70q6gp5venrrt8ulqal6qygln26 I think this would violate the shared-nothing, stateless nature of the client-server relationship described by the protocol. In practice this wouldn’t be difficult to do, though. In HTTP/2 and HTTP/3, the client and server basically keep open a channel that they can send messages back-and-forth over, but with the semantics of HTTP, the client only sends requests and the server only sends responses. (1/2)",
"sig": "ccbde51002461d3f0e87e5331595a1db0031e67a8a171598e3a33809b3dc74428dd593dc514857497ede95b9a73a987c80c0f49a654c9baca97c64a41d241012"
}
