Specifically, the idea of nested lists really appeals. One list with sub-branches following the same implementation. Likely simpler to code, interoperable, and easier to use across the whole of nostr.
Login to reply
Replies (2)
Nostr has lists… but it’s poorly implemented.
This is why clients all need to implement lists so you can select which of your people lists you want to look at. The kind:3 "contact" list is such a blunt instrument.
View quoted note →
I am aware. I'm just concerned that Vitor will implement some wild thing (again) that doesn't make any sense in the larger nostr-verse. (Like he did with his edit "feature" in amethyst. 🙄)