Subnostr

GM frens!

There’s an idea for a project that I’ve been bouncing around and I was wondering what the nostriches would think of this idea. I call it Nostr Channels. The idea is that you can open up your fav nostr client, select a “Channel” and see a content feed that corresponds to that particular channel. The kicker is that your web of trust does the work of associating content with specific channels.

Does this sound like a feature you’d like to see in a client?

If so, what are some “channels” you’d like to see?

And if you had to pick one or the other, would you want content curation to happen by pubkey or by individual notes?

I’m interested in any thoughts you may have!

Reply to this note

Please Login to reply.

Discussion

Sikto 2y ago

Would channels be like selecting specific relays?

david 2y ago

I’m thinking it would be like selecting a set of pubkeys. So for example, the channel for monetary policy from a bitcoiners perspective would have ppl like Lynn Alden. Or the channel for nostr development would have all the nostr devs.

Sikto 2y ago

Ah, I see. Curated lists around subject matter. And our web of trust would be the curators?

david 2y ago

Yup. I would add nostr:npub1uyz4w2w4rcphk0q5arzkutrecgscxwzajj4dkvh9mjyqjtxslm6qea8632 and nostr:npub1a2cww4kn9wqte4ry70vyfwqyqvpswksna27rtxd8vty6c74era8sdcw83a to the channel on the Fed from a bitcoiner perspective but maybe my WoT would know of some other good sources I’ve never heard of.

Sikto 2y ago

How would it work for individuals who write about or cover multiple disciplines. Would they be added to multiple channels?

david 2y ago

Yup, no reason not to do that.

Potentially, users could make several alts for different topics. Although that may be more trouble than it’s worth.

Another option would be to curate content at the level of the individual note. That would have its pros and cons. Ultimately, content could be curated using both methods simultaneously: curation of pubkeys and curation of notes.

I’m thinking initial rollout would curate pubkeys though, not notes. Easier for clients to incorporate that way. Just swap out the list of pubkeys in the filter they’re already using for the content fees.

Sikto 2y ago

Would curating notes be by the author of the note. Ie they would select which “channel” to broadcast to?

david 2y ago

To keep things simple, probably the answer to that would be: no, at least not at first.

A feature like that could certainly be added later, though.

captain ☦️ 2y ago

Can this be implemented in a simple web client that generates profile lists which other clients such as Amethyst can select?

david 2y ago

I think that could be done.

captain ☦️ 2y ago

If I want to designate someone as a curator of, lets say "Cypherpunk Bitcoiners", but other people use "OG Bitcoiners", is there a way to resolve this namespace mismatch?

david 2y ago

That’s the kind of thing that DCoSL can definitely handle, although for the sake of simplicity we probably would not do that on initial rollout.

david 2y ago

We would use DCoSL to maintain a list of Channels. Each channel is referenced by its event ID, which means that two Channels can have the same name. No more name squatting! But if two Channels with identical or almost identical names are created, there would be a several ways DCoSL deal with that problem. One would be to merge them. Another would be to accept one and reject the other. Either method would potentially require adding a new item to the list of Relationship Types between Channels.

Bc of tue complexity, initial rollout would probably not address this issue. But ultimately, your WoT would decide what method to use.

david 2y ago

I could imagine making it super simple for devs to incorporate channel selection into their clients. All they’d need would be a channel selector. Then your feed would be generated from the curated list of pubkeys instead of your follow list.

It would not be necessary for the curation (association of pubkeys to a channel) to be implemented in every client.

david 2y ago

Perhaps on initial rollout, the list of “Channels” would be a NIP-51 list.

And each Channel would have its own NIP-51 list of pubkeys.

Devs add a selector to their client to pick a channel, fetch the list of pubkeys, and use that for the content.

Gradually, the NIP-51 lists would be replaced by Crowdsourced Lists.

david 2y ago

The first list to be crowdsourced might be something like: the list of pubkeys for the Channel on Nostr Development, which basically would be a list of nostr devs.

Rasha 2y ago

Good morning 🌞

david 2y ago

PV! 😊