I think that could be done.
Discussion
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?
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.
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.
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.