indieweb
Per Channel Filters
It may be useful for users to have filters per channel. For example if a user only wants to see original content from people they are following eg. excluding likes, reposts, bookmarks etc.
Tweet decks supports filters per "channel" to; show only tweets with a certain type of media, hide a keyword, only show a keyword and exclude retweets
I'm going to add this to Aperture first before trying to add it to the spec. This will let me iterate quicker on the UI and feature set without having to have clients update. This does mean the limitation is that the filters can only be adjusted through Aperture's own admin UI, but I'm okay with that limitation for now. Since they are channel-wide filters, rather than per-feed filters, it's unlikely that I will want to be able to change them from arbitrary clients very often anyway.
A compromise might be a way to discover the link into the backend admin UI. Then the reader could send the user directly to the right channel/feed settings instead of the user having to manually navigate the backend UI.
I haven't started work on this yet, but I do want to introduce filters to Lighthouse. I have some ideas on what I would match on at https://git.jacky.wtf/indieweb/lighthouse/issues/26 but I do have some things I'd like us to consider (I do plan on implementing the following but don't expect anyone else to as of yet):
- Allowing filters to be shared across channels—this would probably require treating filters a bit like syndication targets in Micropub (referenced by an ID)
- Being able to name a filter—this helps with understanding what it's doing at a glance and when wanting to apply it to one or many channels.
- Including if a filter can cause an item to be omitted from a feed. My use case for this is to surface transparency about why filtering can happen and finding other items affected by this filter.
(Originally published at: https://jacky.wtf/2022/4/ru/ruCXBaS1BFT11MMLNIpOy8mr)
