Daily random nostr thoughts:
Nostr is the identity and content management layer for the internet.
- These events are verifiable such that you can determine from a signature that it came from a specific pub key. So you can control your identity and all the content that is associated with your identity as well as verify other’s events / content.
Running a Nostr relay is the data ownership layer of the nostr content.
- If you own the relay, while you can’t verifiably tamper the events, you can delete them, however. So you do have some control you can exert over other users content.
- imo, you only own content if you are also running a relay, as you cannot guarantee persistent long time storage otherwise. It does help make your content resistant to censorship though by being able to distribute it to a network of relays.
These layers are parallel and interoperable with other protocols similarly to RSS, SMTP, Bitcoin and the Lightning Network. It could even house metadata about the protocols and networks built on top of said protocols.
Nostr can be used to distribute to other protocols, networks and platforms programmatically.
Due to the simplicity of events, it makes it really easy to gather information that isn’t tied to someone’s government issued ID, maintaining some degree of privacy.
Maybe making it possible to generate enough open data of all kinds to train an open source AI model. Perhaps a path way to monetization for relay operators and reasons to persist data?
IMO, nostr is already inherently a better spec / tech and more secure than something like smtp / email for example. Nostr Id / NIP05 represents a lot more than a direct messaging address. Google reads all of your emails whereas we could use the encryption to secure the content. Service providers could restrict outside users from being able to query anything other than what they are able to produce valid signature for a particular pubkey as authentication.
I could make a case for RSS too, but we’re on the road to adoption and it’s not really practical to make those claims just yet.
Thoughts?
zantoshi / santos
npub1fk…ednwk
2024-06-06 02:30:22
Author Public Key
npub1fkvjh50p9amcvce5eclalcszqduehlhmsjm76hx3zy5sx3g40ddqqednwkPublished at
2024-06-06 02:30:22Event JSON
{
"id": "fcd92b16f347431478a438c044257e76a0f7f507dc2d8aa9d951b50741ee3f02",
"pubkey": "4d992bd1e12f77866334ce3fdfe20203799bfefb84b7ed5cd111290345157b5a",
"created_at": 1717633822,
"kind": 1,
"tags": [],
"content": "Daily random nostr thoughts:\n\nNostr is the identity and content management layer for the internet. \n- These events are verifiable such that you can determine from a signature that it came from a specific pub key. So you can control your identity and all the content that is associated with your identity as well as verify other’s events / content. \n\nRunning a Nostr relay is the data ownership layer of the nostr content. \n- If you own the relay, while you can’t verifiably tamper the events, you can delete them, however. So you do have some control you can exert over other users content. \n- imo, you only own content if you are also running a relay, as you cannot guarantee persistent long time storage otherwise. It does help make your content resistant to censorship though by being able to distribute it to a network of relays. \n\nThese layers are parallel and interoperable with other protocols similarly to RSS, SMTP, Bitcoin and the Lightning Network. It could even house metadata about the protocols and networks built on top of said protocols. \n\nNostr can be used to distribute to other protocols, networks and platforms programmatically. \n\nDue to the simplicity of events, it makes it really easy to gather information that isn’t tied to someone’s government issued ID, maintaining some degree of privacy. \n\nMaybe making it possible to generate enough open data of all kinds to train an open source AI model. Perhaps a path way to monetization for relay operators and reasons to persist data?\n\nIMO, nostr is already inherently a better spec / tech and more secure than something like smtp / email for example. Nostr Id / NIP05 represents a lot more than a direct messaging address. Google reads all of your emails whereas we could use the encryption to secure the content. Service providers could restrict outside users from being able to query anything other than what they are able to produce valid signature for a particular pubkey as authentication. \n\nI could make a case for RSS too, but we’re on the road to adoption and it’s not really practical to make those claims just yet. \n \nThoughts?",
"sig": "f7a237bbc07e07ff7c162ce45b8e098dd6e149f2023da364010cb372c6a5905f3fa4916d7f8b17ed980cbd088ff188fe09d51cafc6d3775b88acf975b24369ff"
}