Subnostr

That is in many ways the goal. It's a question of "which level of the protocol will control the lists of communities and, in turn, create nested lists of them."

As of now, one can create an application that nests NIP-51 lists. I believe there is value in doing so, but it's a question of how it benefits the application, or a question of what application you are trying to build (with nested lists).

I envision giving users the ability to create nested lists of communities that can scale to become national or global communities. It's a question of how, though.

Bored Satoshi 1y ago

then you should stop calling them "lists" and start calling them communities people can follow or join.

The difference is: you're suggesting people to maintain these lists. Instead communities should be open for anyone to join.

For example: /bitcoin community is something like an open forum you and I can follow.

I have been thinking about this for a while now. This requires a different NIP.

Reply to this note

Please Login to reply.

Discussion

Tekkadan, ゲロゲロ! 🐸 1y ago

There is no escaping the individual management of a user's follow list. While I agree with you, there are two problems at hand that are not entirely solved by community lists.

We need both.