The things that I like nostr for are these:
- If something can work on nostr, that means it can work on a real p2p backend too. But nostr is easier. So if I'm doing a proof of concept, or a demo, or a hackathon project, building it on top of nostr makes more sense than doing the laborious task of making it actually p2p.
- Sometimes I build systems where you interact with peers, and it's not critical for you to be online *all* the time, but your messages should stick around for at least a few days if you *go* offline. E.g. an asynchronous trading platform could work like this: you list an offer, people can post a purchase order while you are offline, and then you can come back in a few days to finish up. Nostr, unlike "real" p2p system, has built in message caching. I don't consider it reliable for long term periods, but it's good enough if you post your messages to multiple relays and don't need them to last more than a week or so. For this kind of protocol, nostr seems like a *better* fit than a real p2p backend.
- It has started to work well as a social media platform for me. I check it about once per say and post messages here a few times per week, and I meet people on here and make plans for work and pleasure. It's not as good as twitter for this, but nonetheless, at least for me, it has finally become useful for its original social media purposes.
Super Testnet
npub1yx…c399s
2025-06-12 00:22:07 UTC
in reply to nevent1q…65zl
Author Public Key
npub1yxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96s8c399sSeen on
wss://nos.lolPublished at
2025-06-12 00:22:07 UTCEvent JSON
{
"id": "d762283a2ecabeae377c18f2112493f2171d126a25cc025e386c07448622e342",
"pubkey": "2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975",
"created_at": 1749687727,
"kind": 1,
"tags": [
[
"e",
"932e631dba2b33ab7444b4fbe56a349d85e5d6c9132726b3bc66e3eee7634d99",
"",
"root"
],
[
"e",
"5db655ac494a8c67bcb24f02451dbd13d9582a59328b712a812f225f1aa78a74"
],
[
"e",
"1d1018ae128323b87896858beb7d941f504a35158c5a1f72e4d465dfe4e4ee64",
"",
"reply"
],
[
"p",
"2183e94758481d0f124fbd93c56ccaa45e7e545ceeb8d52848f98253f497b975"
],
[
"p",
"a87b402ac081c8849b9d5bd4e39f2287f25709d3e3f79e784af1e8b38fefbdf1"
],
[
"p",
"2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331"
]
],
"content": "The things that I like nostr for are these:\n\n- If something can work on nostr, that means it can work on a real p2p backend too. But nostr is easier. So if I'm doing a proof of concept, or a demo, or a hackathon project, building it on top of nostr makes more sense than doing the laborious task of making it actually p2p.\n\n- Sometimes I build systems where you interact with peers, and it's not critical for you to be online *all* the time, but your messages should stick around for at least a few days if you *go* offline. E.g. an asynchronous trading platform could work like this: you list an offer, people can post a purchase order while you are offline, and then you can come back in a few days to finish up. Nostr, unlike \"real\" p2p system, has built in message caching. I don't consider it reliable for long term periods, but it's good enough if you post your messages to multiple relays and don't need them to last more than a week or so. For this kind of protocol, nostr seems like a *better* fit than a real p2p backend.\n\n- It has started to work well as a social media platform for me. I check it about once per say and post messages here a few times per week, and I meet people on here and make plans for work and pleasure. It's not as good as twitter for this, but nonetheless, at least for me, it has finally become useful for its original social media purposes.",
"sig": "a4eb411ad841536c6e1218d53a87231f0b410b08141f33adfed02e662cd16c821f2f35c53211127bd29778f08af8d759e2a3d1f3c0bb75694206eb1f28c51a53"
}