The answer is simple: it is always a new kind.
Another victory for interoperability right here: https://github.com/v0l/snort/pull/153
Thank you, #[0]!
This was just added to NIP-19 by #[2] and #[1].
nostr:nrelay1...
Yes, I do. I prefer TODO statements in the middle of the code.
I should just have my repos say: "instead of opening an issue, open a pull request that inserts a TODO statement in the appropriate place".
#[0] I just learned that it is possible to do what you wanted to do in #[1]:
Check this out: https://twitter.com/fiatjaf/status/1619284639037935618
The trick is to return a Redirect header with the nostr:... URL in there. I can recommend https://redirect.name/ for setting up a redirect without having to run a server.
Thank you https://nostr.band/ for allowing me to find #[0]'s note in a sea of garbage.
See also https://www.figma.com/file/pUyfdfIh0DplK9ehDPil5a/Nostrrr?node-id=0%3A1 and https://media.cleanshot.cloud/media/15345/7eVnEqoEvQerBV8EpY57BJapBwKytnurF9YR4Vgf.mp4?Expires=1674921528&Signature=ITz5WCtA9Rzb6bSEKidrt01y1xSnCCpro5l~nN8zWK9jE91XelL-Lse0igNQdlQJ55CEvjt~fNxNADYL7Zduh6rNTlhSlpVM3S9hUJJTBPLLHmN5YiD0qDjJ1wlM4R3LP0twmcui0PdYCkIB9Q7by~QV67MvjpfGXWGwP6e1OrS9M0zFF5nowy5iaJqFso6erf5Hu8qvbKNaTorXiSYKdXzWJNwYhB1ESophpdm8EDwnae5KyzzhQ6hWFX-RLri~yF1~SsUvVoZJ98sUrNNf2kReJV-t7m9DNmSlHCchePNEAyK4u6evW6JeBJ24UanSwoY~ujWcHVdGmnMSNziBCQ__&Key-Pair-Id=K269JMAT9ZF4GZ
Why do we need GitHub Issues when we can just complain about the clients in real time here and tag their makers?
Some good news here.
What do you think of this idea of having relay-local "global" feeds? 
I don't think that kind of automatization will go a long way. It is probably simpler for the client to categorize relays in named groups -- or have some magic algorithm that cluster together relays that seem to be related to some groups.
I am very aware that there is nothing anyone can do, but I reject that things must necessarily go down this terrible route. I am unsure about your answer, you seem to think that feature creep is a bad thing, but you also wants to contribute to it?
I agree that a subset of Markdown that looks okish is not harmful at all. Maybe we can push that as the compromise? There is a chance it will work.
I don't know. A language filter is ok.
No, I didn't know that existed, but I barely use Google these days. When I search in English I get results in English, when I search in Portuguese I get results in Portuguese.
You like Markdown, I like Markdown too. Do you want Markdown to become a requirement for the Nostr protocol?, that is the question.
Contents are not powered by algorithms. They literally show stuff from people you follow. My timeline has most posts in English about Bitcoin, some posts in Portuguese from Brazilians, and sometimes Turkish, Italian and Russian from Bitcoin people that decided to interact with their fellow countrymen. I just skip these weird languages. Twitter does nothing to prevent me from seeing them.
Also, time is on our side. Currently all Nostr users are nerds who think writing Markdown is the epitome of human wisdom and feel very proud to have memorized that horrible syntax, but once normal people start joining they won't care at all about Markdown and will just write plaintext like they should.