I think he wanted to add more categories, like inbox/outbox/archive, etc. The above issue is more of a NIP 01 thing actually, e tags are defined as "["e", <32-bytes hex of the id of another event>,
I think nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c wanted to do a few changes to it but I don't know what those are.
But we have to make event/relay finding easier.
Discussion
If we want to use NIP65 to only advertise to others, then there isn't much to do. But if we want to use it for the user's own applications (which I think we should, we need more)
On the advertising, I think read/write labels are terrible because they need a point of reference (who is reading/who is writing). Each user should just have "home" relays where all of their posts are supposed to be found. There is no need to specify read or write. If I am writing a DM to you, I will send it to all your home relays. You send to my home. If we happen to share the same "home" relay, both apps should use that.
On the user's own needs, there are other labels like "search" (which NIP-50 relay to use for searching things), "global" (which relays to use when on a "global" view), "notification" for all relays to use when searching for notifications (today's read), etc.
We need public and private relay lists, similar to NIP-51.
I realize 'read' and 'write' are confusing because it depends which side is doing the operation. But if we change it (by adding "outbox" to mean the same as "write") then many clients who haven't coded for the change yet will get relay lists they don't understand. I think it is too late to fix this aspect. I wish we could.
I agree we need both public and private relay lists. NIP-65 is the public one. It is not intended for configuring your own client, which very likely needs more information, even client-specific information.
I don't think a home relay is sufficient because there are plenty of more complex situations it wouldn't cover. For example, I may post to a paid relay, but I cannot expect people to copy me in on a thread at a paid relay that they may not be paying for.
IMHO NIP-65 is finished and stable. The only thing that makes sense to me to add is a DM marker for where people should send you DMs (some people might want that to be a more secure relay that only swallows events and doesn't serve them).
> I don't think a home relay is sufficient because there are plenty of more complex situations it wouldn't cover. For example, I may post to a paid relay, but I cannot expect people to copy me in on a thread at a paid relay that they may not be paying for.
Sure, but in practice, people have to add tons "read" relays to download all notifications from everywhere to account for Nostr apps that are not following NIP65 directions yet (it's optional after all). The overcrowding of read relays breaks the concept of the preferred/home relays.
Clarifying that NIP-65 should only contain home relays is important.
Adding tons of read relays in practice to pick stuff up is very different from telling people "these are the several relays I read from". You can advertise 2 read relays, and actually read from hundreds of relays if you like.