Absolutely. It’s interesting to see the slow but sure mass adoption of password managers as a reasonable middle ground. Then LastPass goes and nukes all that trust.
Nostr is the opposite of a blockchain. Nodes never reach consensus by design. Yet here we are talking peacefully. It’s kinda beautiful.
Also, Twitter pulled the ol switcharoo with their API. Give the data to everyone for free until you reach scale and then pull the plug.
Wow, this is amazing. It’s like watching Momento. It’s no wonder nostr looks like this. Fiatjaf has already lived through this entire cycle.
Even if the original publisher goes rogue, disappears, whatever… the data itself is future proof. You’ve reduced the dependency risk, and that can scale across developers. Network effects in the data itself.
True, but ipfs is not backwards compatible. It’s got it’s own stack vs here is a json object and anytime you encounter this object you can be certain the payload is the same. The objects themselves now have mobility.
The web has never had a good solution for assurance that a resource at a uri was the same at another, or that the content wasn’t changed.
nostr.io does it as well. It makes sense for p and e objects to be linkable as resources. Sockets are great for streaming but urls are the dna of the web.
Yes! An episode with an immutable event id and payload means it can be referenced anywhere on the web. Comments, clips, payments. Podcast Index should be all over this idea if they aren’t already. It makes the index more resilient and shareable.
It should definitely be categorized as a reader application for the content policies, it also will exempt it from the in-app purchases policy. Good ol Damus Reader. 🙂
He actually really just wanted to use that sexy new npub. 😆
Hmm, yeah that’s right. Both objects pass as valid but I glossed over that I had wrapped the content as a string. Good topic to discuss.
Exactly, if you don’t want someone to see something specific don’t publish it on a public network. Money is information, but Nostr is not money.
If we don’t have a hybrid public/private relay infrastructure then we failed to use this protocol properly.
I run it on a Protectli and it’s been great. Nice little piece of hardware. Would recommend.
Indexing services will be required leading to controversy over centralization.
Idea I’d love to validate. Is there a way to encrypt and broadcast messages in a 1-of-N multisig where every current follower is a signer? Broadcast encrypted dm’s? Thinking specifically about permissioned location sharing.
Great, very helpful thanks! How does a relay know if it has the most current version of an identity? Is that up to the relay operator to merge/sync with other relays?
Architecture question. Are all messages in the Damus iOS app served from a single nostr relay? Trying to understand if I’m seeing federated users/messages and the role of the relay.