15
[Proposal] Content Filtering
(lemmy.zip)
I'm working on a new filtering engine that I think will be like nothing you've seen yet.
Basic overview:
- There will be a list of filters you can browse
- E.g. US Politics
- You select the filter list(s) you are interested in
- The filter list will receive updates.
- Say a new political event happens and a new name floods the news. The list can be updated dynamically to include the new name without you having to do anything.
For those of you that are tech savvy:
- Filter lists will live on GitHub
- You can fork an existing filter list.
- You can create/host your own filter list for other Blorp users.
- You can open pull requests for existing filter lists.
- There will be some tools within Blorp to debug your filter list
Other notes:
- I don't plan on letting you build these filter list from within the app. They are far too complex to edit easily within the app.
- But that complexity means you can do far more than other apps
- Block a post
IFit mentions a US state (e.g. "Texas")ANDit mentions "shooting" - Block a post
IFit mentions "ICE"ANDit mentions ("detention"OR"deport") - Block a post
IFit's by a specific list of usersANDit mentions a specific word
- Block a post
- The goal is to create more collaboration between users and make it easier to cut through all the noise on Lemmy and PieFed
How are you currently using filtering in Blorp, Voyager, etc?
- What type of content are you currently trying to block?
- Are your filters very unique to you, or something that could be shared as a list?
I’m not too worried vendor lockin. I’m not using anything that specific to GitHub. I’ll probably put the filters behind filters.blorpblorp.xyz so I can always point that domain to a different location later if I need to move off GitHub.
Edit: I think I can get around codeberg pages not being high availability by cached the filters. Then when we are able to pull the most up to date version, it will update the cache. I was going to do this anyway in case you subscribe to a filter and it gets deleted. If it gets deleted, the filter list will still be cached.