Open david0178418 opened 2 years ago
I like this idea, I think we had it filed somewhere on the previous repo to assist in sidebar categorization also. We can see if this would work in the preference data where we store following/notifications - not sure if other apps that use the structure would break or overwrite when they sync. That area is also going to be getting a revamp, so something like this can be taken into account.
I think the ability to create folders in the left panel (where followed channels are) would be very useful. In this example there are music channels, software channels, news channels, crypto channels and even more. It would be useful to have an "Add folder" button at the end of the list, and then move the channels inside the created folders, so that users can expand a folder and scroll the channels inside it.
Is your feature request related to a problem? Please describe. I often skip subscribing to users specifically to avoid having my feed getting too noisy and unmanageable. And other times, there are channels I'd like keep track of, but may only be in the mood for their type of content on specific occasions, such as horror or creepy pasta during Halloween.
Also, if I'm just generally in the mood for a particular type of content such as news or gaming, this would, help zero in on that content without needing to be channel specific.
Describe the solution you'd like Having the ability to categorize channels and view that subset of my subscription feed would allow me to narrow it down to the subset of related channels I'm looking for.
Example mockup:
Describe alternatives you've considered Without a way to group channels, there's no way to accomplish this that I'm currently aware of.
Additional context To accomplish this, there would of course need to be additional UI elements to make the categorizations and matching changes in the API. I haven't done a deep dive on the API yet beyond just poking around after getting it running. But I'd imagine that this would be an Odysee specific value-add stored in the postgres. Assuming this is a feature you guys would want to incorporate, I'd make the related ticket in that repo and start there.