I just learned that Nostur also doesn't implement Nostr correctly and cannot see nostr:npub1u3jp6rhdw8fdps8k3nf4pr2slnd3j49vrnx6y6wahda8397zyc2qw7q7na's feed. I was under the impression that it did for many months. nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe
Ditto is another one I hoped would implement Nostr correctly, but nothing. nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p
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.
Do you think there has to be more awareness (education) around this topic for Nostr (client) developers? With research, documentation, best practices, easy to understand code examples (dos and donts) and more?
Nostur is showing me the events most of the time, but sometimes it's not loaded. To me it seems to happen random with the notes you're reffering to.
Isn't that what I'm doing here?
But yes, I think some more concrete examples could help.
For you yes :D
But devs coming to the first time it's probably a topic they must not overlook? Especially when there is no real consensus on this (yet). Sometimes it's good to have offer a hand for some grip instead of getting lost with the risk of devs leaving the ecosystem.
