Event JSON
{
"id": "c73a589914fa88b616249238afa1010663f03492ae561a50c3d92214e5a3803e",
"pubkey": "97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322",
"created_at": 1701314828,
"kind": 1,
"tags": [
[
"p",
"3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d",
"wss://relay.damus.io/",
"Mazin"
],
[
"p",
"a3eb29554bd27fca7f53f66272e4bb59d066f2f31708cf341540cb4729fbd841",
"wss://relay.damus.io/",
"signal_and_rage"
],
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef",
"wss://relay.damus.io/",
"JeffG"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"wss://relay.damus.io/",
"mikedilger"
],
[
"p",
"0c99877612291bd818b3dd92f2852b823557b3744c3cb10470865c7a56a4929b",
"wss://relay.damus.io/",
"pjv"
],
[
"p",
"0c99877612291bd818b3dd92f2852b823557b3744c3cb10470865c7a56a4929b",
"wss://relay.damus.io/",
"pjv"
],
[
"e",
"615511074de45ab7cb4a2eb2b1d0a75e6c2a533ba6156c64338bf13251c389ec",
"",
"root"
],
[
"e",
"666745f27f229a5b24a82ac5d849dc4b23b9dde4f0beec0b6d4f9c71a3669cca",
"mention"
],
[
"e",
"ddfe7b473dc0c17a69dafcb1c24d737fe1aa5ccbd135995e5f45aac85ff25f8e",
"",
"mention"
],
[
"e",
"d927e5aa706db6777018dbf904589e0ca028a438064f54c2f9cd2c66ebeb38c3",
"wss://relay.damus.io/",
"reply"
]
],
"content": "Most of my opinions about nostr's architecture come from a conversation I had with a friend of mine who used to work at Twitter. He explained that Twitter is only able to deliver relevant content quickly by pushing it to a huge network of special purpose caches. This is easily done with nostr relays in theory, the hard part is coordinating how caches (relays) get primed. I think some combination of push and pull will be necessary - if indeed the problem can be solved without central coordination.",
"sig": "e1e9abf105671ed6c2ba9537d75d66be4496a233ba77620418a77810247ed87f2016f7f69bd2d8ff4b4d1a5540acb4e7e24a2c2eeda131c7dfa4c48f665c1a23"
}
