Better service

Nope

Lame

I do. I paid for it

What's wrong with atlas relay? It's been off for quite some days. Anyone knows anything?

Amethyst is really looking much better today than a month ago.

Good morning Nostriches! 💜🦦

Wow. That is one hell of a start to get us going!

Not sure if you are pulling my leg or actually mean that. 😃

nostr users be like i love talking to my friends @74ytgh36tjjh278jhjn6jhg3jhgk7m25iou6jhjhb631ndm3g1fg53j1njuh54hjhk54kj8jhno2pjio42n6j and @uj2gg5g2jhn6mf7nk63bhi6n8n93jh4jh3hjnasd32onm5hjk3njkndjp4op2n5jn2ghnl675jhj6njkh25

The user experience is poor with a placeholder IMO

Only marginally, the hashes are pretty small 🤏🏻

The ‘show more’ feature for long posts is a brilliant addition to Damus. #[0]​.

We should trial a ‘Turn off echo chamber’ hour on Nostr.

The downside is the burden is on clients to identify image URLs and generate a blur hash for images

So clients don’t have to load arbitrary image URLs in order to display a blurred version of the image.

You can render a blur hash that looks equivalent to a blurred version of the original image

Since #[0]​ is Brazilian wouldn’t we pronounce nostr like the Brazilian Portuguese word of Nos, meaning us… I’ve always assumed the name is a word play right? friendster / flickr are like service of friends, or service of flick (picture), so nos-tr is like protocol of/for us, right?

I think we’re in agreement. If the DHT is setup in such a way that to write to it you need to use your nsec to sign the 10002 post which lists your relays with the lookup based on the npub. DHT’s are particularly censorship resistant, there are lots of kinds of DHT’s and ways to use them. We’d want to have somebody double check and help with its design.

There might even be a good way to take 10002 messages from a relay and push it to the DHT. It has to be signed, so even if the original person who created it doesn’t post it to the DHT with their app, others or relays could. The other half is to then provide a web UI for looking up npubs from the DHT. That way it would work without a chicken and egg problem.

Ok first of all, NIP-05 is out of the question. It's not signed, it's not a contender here. That was just to make it easier to find someone, back when we didn't have better ways. It was my idea to put it into nostr.json in the first place, so I am shooting down my own idea.

My newer idea is expressed in NIP-65, which is just to spread that kind-10002 event to hundreds of relays (while only using a few relays for regular events).

I've always been in favor of relays or servers that specialize in serving kind-10002 events. I was going to suggest if someone does a DHT to put the kind-10002 events in there. Sounds like that is already part of your idea.

It seems that if all the clients move over to publishing into a DHT, then a DHT would have the advantage that all the data would be in it (the hash table being synchronized, I presume), whereas if you just ask a popular relay, it might not know, and you could never know for sure if that was because the relay didn't know or because the data wasn't there. BUT that property doesn't appear unless and until everybody moves to using the DHT. And I'm not sure people will because of the chicken-and-egg problem.

But a DHT seems like (even though it is distributed) a potential single source of failure. If there are "root servers", how many are there? Can they cheat?. Can things be removed from or replaced in a DHT, and if so, cant someone censor data out of it, and then replicate that censorship widely? If not, how is that enforced? I admit to my ignorance on this point.