I just learned that Nostur also doesn't implement Nostr correctly and cannot see gitlost (npub1u3j…q7na)'s feed. I was under the impression that it did for many months. Fabian (npub1n0s…lahe)
Ditto is another one I hoped would implement Nostr correctly, but nothing. Alex Gleason (npub1q3s…d26p)
Honestly I don't know what you're thinking, if this is really so hard to do we might as well stop this joke of a "protocol" right now and go back to Twitter.
Not to mention there is not a standard way for devs to implement it. You can implement it wrong or “right”? The idea that we are getting upset at devs for not implementing nostr right is silly. What is the right way? No one has ever done this write up.
How about write a tutorial or nip? This is much more productive than just shitting on devs for doing the simplest thing when they first get started (relay pool). I guess fiatjaf (npub180c…h6w6) is calling me and many others for not implementing “fiatjafs vision”, but what is this vision exactly? following relay hints? this doesn’t solve everything, the relay hint in a note could be down.
nevent relay hints? nevent didn’t even exist when I started building a client. How is this “obvious”? How do you select the ideal relays for many different types of queries without blowing the connection budget? What client is fiatjaf (npub180c…h6w6) building that has this perfect algorithm? Please teach us.
It seems:
-there are various implementations, which don’t fulfill fiatjaf’s criteria of finding the notes on the smaller relay
-there is lack of clarity surrounding the “correct” approach to implementation (if such a thing exists)
-there is some tradeoff between performance, data query volume, and finding notes/events
So it could be that the full solution is somewhere, and there is no or difficult to find documentation, or there is a partial solution with unanswered questions such as the above.