Nostr Web Client

nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpzpmhxue69uhkummnw3ezuamfdejszxrhwvaz7tmddahxzepwdf3r2dfwvdhk6w3cxqurqqgdwaehxw309ahx7uewd3hkc0v9nh0 I was wondering is #notedeck going to be able to support a relay-centric moderated community column? I am thinking of a column scoped to a specific relay with auth and supporting either hodlbod's [NIP](https://github.com/coracle-social/nips/blob/relay-chat/xx.md) or NIP29.

I see issue #376 that single-relay column is planned ideed but what about functionality related to semi-closed groups? Is this perhaps possible with #nostrscript -enabled columns?

Context:

I am exploring possible options to create a discord-like space on nostr where I can hang out with Freedom Tech builders.

So far #flotilla seems to be my best bet from nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7208x3z but it is not optimized for easy and performant widgets that I need to have the best possible nostr experience tweaked to perfection for me and members. I would just share the required columns for the group and they could add it to their nostr experience.

The discussion in my relay would be moderated but it can exist alongside whatever ppl prefer to add for themselves.

Reply to this note

Please Login to reply.

Discussion

jb55 11mo ago

it won't be a column it will be a separate app within notedeck

hodlbod 11mo ago

NIP xx is only an obsolete draft, flotilla follows NIP 29 now

Five 11mo ago

I thought your spec was being made compatible but not identical

hodlbod 11mo ago

It is, but it's all been rolled into nip 29. See more details here: https://github.com/coracle-social/flotilla/issues/83

Five 11mo ago

Can you write a longform on this nip29 saga some day, so we can learn from it? I enjoy your articles on nostr development

hodlbod 11mo ago

Have you seen this one?

nostr:naddr1qvzqqqr4gupzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqqxnzdenxgenzve4xyurgvfk9an8aq

Five 11mo ago

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.

hodlbod 11mo ago

Yeah, there is a lot of essential complexity in groups

Niel Liesmons 11mo ago

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 😉