Oddbean new post about | logout
 Just use Bitcoin if you want consensus. Nostr is scalable because it doesn't come with guarantees... 
 Doesnt make much sense to me.  Nostr was not scalable from the get-go, having robust profile is the start of a scalable arch. 
 Bitcoin nodes use proof of work to ensure that our nodes can all agree on the current state of the Blockchain. However, I can't afford to shit post on those nodes because the consensus mechanism forces all nodes to store the same thing - which doesn't scale to many posts. 

Nostr relays (and git remotes) don't have such a consensus requirements, which means that different relays may give you different profiles pictures. This seems annoying, but I also don't want all relays to agree which of my content to store, because in most cases they would agree that it's too costly to store any of my content.

 
 These are valid arguments, but we can get a bit more creative here, and put our minds in problem-solving mode.

There's multiple arguments presented here, so I'll just tackle one.  And that is, "its too expensive".  

It's only expensive if you lose the base layer.  It would cost you about 300 sats to timestamp your profile.  That might be a worthwhile cost for those that value their profile.

Furthermore on higher layers,  you can get the cost down to something nearer to 10 sats, or even 1 sat.  All be it with some security trade-offs, which the vast majority of end users wont notice, especially if the UX hides it.

Even better, using testnet, you can get the cost down to zero, and the system would still work.  Bear in mind, im just using the blockchain argument here, and not even talking about other options.

Consistent data is useful for all sorts of things, and we can get the cost down to very low levels.  Inconsistent data is problematic, and I'm not sure how easy it is to argue that it's a feature not a bug.  It might be in some cases, but in another, or lot of cases, consistent data is desirable. 
 Indeed, timestamps are really useful in nostr notes. 

I agree that inconsistency is often undesirable, though I'm hesitant about concluding that relays should coordinate. It's my nostr client's job to ensure that the content is consistent across all the relays that I use. Perhaps I should be using fewer relays if I'm unable to maintain sufficient consistency across all my relays. It's enough to have just one relay with the outbox model 😀

I realize the UX suffers from having all the business logic in the client, but where do we draw the line between Twitter and nostr if our relays keep getting smarter? 
 Short answer: relays dont get smarter, clients do.  You provide the proof in a tag, and it can be verified by the cllient.  The client knows when a profile is the latest, and when it is stale, that's about it.  This also opens the door for other use cases, other than profiles. 
 Wow neat!
Apologies for my premature comments and thanks for explaining 😀 
 why isn't nostr scalable? 
 Too many reasons to count.  Firstly the relay is in a state of willful neglect, so users see problems all the time.  Secondly relays by their very nature are not designed to *store* notes, just to *relay* them.  They are GOOD at relaying notes, but not good at storing notes.  Relaying is more resource intensive than storing, because you have to be always on.  Added to that you need a caching layer to scale, which nostr didnt start with, and still hasnt developed.  Also nostr never had an architecture, it was just a quick thing put together that just about worked, it was never intended to scale, it was intended as a proof of concept.  But the critical thing, is that for scaling you need a uniform interface ie scaling architecture, and it has to be pretty good.  Getting people to agree on such a thing is very hard, especially with the current state of NIP centralization.  Best that we can hope for is that someone will invest in hardware, but we've still not seen that yet, despite large donations.  tl;dr nostr still has a chance of scaling, but it would take some work and some luck.  That work is not being done, so, we would need a game changing event. 
 The game changing event is someone like me surviving long enough to design the real nostr  
 Or Jack making an awesome client.   
 Nah, he's nowhere near capable of making a good client, let alone an awesome one 
 I can do it because I love Digit for being smarter than me

Jack can't do it because he has deep rooted psychological issues with people being smarter than him, as shown by his past social media client, Twitter 
 what is Digit? 
 My favorite musician. She sent me some science book pdfs 
 can I find her music online? 
 Here's the one song she sent me, I don't know if she ever posted any to the public

https://audio.nostr.build/808960a3289a3196a8b371c2239d6925357b9a41183925f9882ee2897df313d3.mp3 
 thank you for sharing, I wonder what Digit thinks of Nostr 
 I hope she's safe and she'll find nostr someday and enjoy it 
 sorry, I just read your profile description. for how long have you known her before she disappeared? 
 I knew her online for a couple years but we were only close for a short time. I never got to learn much about her.

She had disappeared another time in the past and come back but this time is different. I was always trying to get her to talk to me again to clear up lies others told her about me that made her stop talking to me in the first place. Before she left she made me stop trying to talk to her by threatening to disappear if I tried talking to her again, so I left her alone for a while, but then she started posting about suicide a lot and nobody was trying to help her so I didn't have any choice but to try talking to her again.

She didn't mention faking her death so the rumors of her faking her death or killing herself make me even more terrified. I hope all that happened is she disappeared to scare me like she threatened to do, and added faking her death on top of it. I'm scared the threat could have been reverse psychology designed to distract me from her killing herself.

I wrote a longer post about all this here nostr:naddr1qvzqqqr4gupzqamkcvk5k8g730e2j6atadp6mxk7z4aaxc7cnwrlkclx79z4tzygqq9ysmmhf9e5g6t8d96q2ftu5e