Nostr Web Client

nostr is not complicated, are you kidding me? the devs that went crazy (which is like most devs pretty much), they didn't go crazy outside of nostr, in some sandbox, they did it inside, so you can't just pretend the result of all that craziness is some kind of optional add on. It's air pollution, it's everywhere, you can't not breath it in.

jb55 1mo ago 💬 4

I built a working version of damus in a weekend, its not complicated

Reply to this note

Please Login to reply.

Discussion

jb55 1mo ago 💬 1

and this was before vibe coding

hodlbod 1mo ago

Nowadays a working version would never get built

JOE2o 1mo ago 💬 1

compare that weekend to now is what I'm saying. I'll bet that was before 32 baskin robbins of relays, and bunkers, and giftwraps, and MLS, and Cashu, and DVMs and double ratchets, and caching servers, and I don't know what else. bluetooth?

jb55 1mo ago 💬 1

Everything you listed can be ignored. None of the things you have listed is in damus for example. You pick the level of complexity you want to expose yourself to.

JOE2o 1mo ago 💬 1

I'm not talking about Damus getting complicated, I'm talking about nostr getting complicated.

jb55 1mo ago

nostr will become infinitely complicated, its designed to be extended. people can and should ignore most of it because its things that are likely not useful to their specific use case

CappyNate🍁 1mo ago

You're also a phenom 🤣

But yes, NIP overload is a real thing. Few are needed.

weev 1mo ago

from the perspective of users it is extremely complicated. I understand that from the perspective of a competent developer it is not complicated, but ideally from the perspective of users it should function relatively equivalently to the very earliest Twitter clients and interface. Extremely minimal and simple. And everything should just work. If the average hears that there are different protocol formats for DMs, you have completely lost the plot and the game