Nostr Web Client

>the Outbox model is as complicated as it is and often not supported because it's complexity

>>wut? What is so complicated about the outbox model? Also, the fact it is often not supported is because most developers did not realise that was the intended way of doing things, a notion that fairly recently got more traction. So whether it is too complicated to implement is something that remains to be seen, but certainly not the reason why it is not commonplace today.

Nuh 1y ago

Here is Kademlia algorithm:

1. you ask the closest nodes you know about, about a key.

2. some will answer either data, some will respond with the even closer nodes they know about.

3. you repeat step 1 for the nodes you were told about from step 2 until you run out of nodes you haven't visited already.

You can implement this in a month in a new programming language that you are still learning. Better yet you can graph one of the 100s of implementations and get access to millions of nodes.

Now, what is the simplest algorithm for the Outbox model if I am trying to dind the Outbox relay of a key that hasn't published their profile to a relay I am already connected to?

Is it only simple when we all have one relay in common? Because everything is simple when there is one central reliable source of truth.

nostr:note1ft33hptz4csg4p7kmdvx692fra5m07ufz5ye5mtyrngqz2s6rzuqc6gvs8

Reply to this note

Please Login to reply.

Discussion

Ronin 1y ago

I'm not wizard level like most devs around here but either nostr uses an algo like this, or clients "ask" and some services (dvm) provide that, or there should be some well known list of relays specialized in user profiles/relays.