I thought your spec was being made compatible but not identical
Discussion
It is, but it's all been rolled into nip 29. See more details here: https://github.com/coracle-social/flotilla/issues/83
Can you write a longform on this nip29 saga some day, so we can learn from it? I enjoy your articles on nostr development
Have you seen this one?
nostr:naddr1qvzqqqr4gupzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqqxnzdenxgenzve4xyurgvfk9an8aq
Yeah now that you mention I read this a while back.
I also commented on it but somehow left it in draft.
...Reading through these and the issues associated with it is very useful but still leaves some confusion in my mind.
Managed/unmanaged groups, nested groups, combination of these, rooms, relay support, relay implementation dependency, feature detection...this is the most confusing spec in that I really find it hard to identify the use-case I want to go with.
But this won't stop me from taking steps toward my plan. I think I know now which way to go.
Yeah, there is a lot of essential complexity in groups
Endlessly confusing haha, at least for me.
I love the shallow chat replies, by just quoting one (or more!) messages.
However:
Still don't think we need a new kind1.
Still think #rooms are a problem to a solution.
Still don't see h-tags as a flexible solution for targeting publications. (i.e. non-editable)
Still need communities to be keys/profiles.
Don't see myself embracing NIP-29 soon. We'll see.
First I have widgets to build 😉