Event JSON
{
"id": "db85810a20ef246f931810e5e0bddab0eb63ad3ecd18ee228c32099c7cdf4422",
"pubkey": "1bab79497d21d691bc1a610c8efc29348ec84016e274f7bbd8132d3ea70795f5",
"created_at": 1707299781,
"kind": 1,
"tags": [
[
"p",
"80dfcad77c1192b509a2cad9c979927532021ff0c8016e9240343f59473ad371",
"wss://relay.mostr.pub"
],
[
"p",
"463e7cc1340eff21e7246d6037328084b5fc65fbc33e859c2830231d4a122798",
"wss://relay.mostr.pub"
],
[
"e",
"a5b8d4caf74c0304e351ff1f3ef15303052ac0812af7489bfc20c507bbfc57ab",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://nondeterministic.computer/users/martin/statuses/111889598466532229",
"activitypub"
]
],
"content": "nostr:npub1sr0u44muzxft2zdzetvuj7vjw5eqy8lseqqkayjqxsl4j3e66dcstsqvwj atproto is built on the assumption that anybody should be able to index the network, which implies that all content needs to be available through public APIs. But DMs are very different — they don’t need any global indexes. Something like XMPP or Matrix could be used for DM transport, and the DID document could link the atproto user identity to their DM server. Still needs careful design to ensure a good UX and good security (eg. end-to-end encryption), though.",
"sig": "431dcfd81817eb778580fefd8272ebd654684a5808d5b345f0c5594b841ebd576108428cbff48b67a1ac307c38ce90053d2aaf4ca92cc539a9446e1c28e76dd1"
}