hodlbod

@sant0s12 I mostly agree with all of that, but we should wait for implementations of those moderation models to happen before adding them to the spec. As for reposts, I'm...

Interesting question. Even if there are valid use cases for paths/query strings, a client can't tell if these are minor configuration options, or consist of an entirely separate data set....

Why not `wss://jp.relay.com`? I'm not saying this is the right solution, but you don't necessarily need paths.

> relays and relay hints must be specified at the root path I feel like this would only be a short term fix, as relay providers could still differentiate by...

> It seems to me the root here is simply poor relay selections. I suppose though that the user doesn't have much control over other peoples' selections, or relay hints.

@erskingardner

We can add a table when it's needed. Namespace and url are both there, and the point of linking is to not have to put the categories into the NIP...

I like the idea of having something like this. It would be nice to have it more explicit that you might have public and encrypted data coexist in a list....

I like this PR in theory, but the migration is the difficult thing, plus forcing everyone to support lists and sets violates the "multiple ways to do something" principle. With...

I've been waiting for someone to build this, I think it's a great idea. I haven't looked closely at it, but you should consider modeling this as an extension (using...