3 ms·

https://letsblock.it https://letsblock.it has been on a slow but steady growth trajectory since it's January ShowHN[1]. The public instance served 290 customize

by xvello 4y ago

https://letsblock.it https://letsblock.it has been on a slow but steady growth trajectory since it's January ShowHN[1]. The public instance served 290 customized lists this week, and operations / project upkeep are a pretty light time commitment. It's a companion project to uBlockOrigin, working towards improving the internet's signal/noise ratio by filtering out low-value content and nags. While cosmetic filtering is very powerful, its learning curve is steep, so the project provides customizable templates maintained by the community. I'll be giving a talk about the project, titled "Designing an Open-Source project for low maintenance" this Thursday at Ory Summit[2] and will share the recording on HN once it's public. You can still watch the conference's live-stream for free! After that, I'll need to update the website's copy and simplify some UX, to prepare for another visibility push later this year. [1]: https://news.ycombinator.com/item?id=30057442 https://news.ycombinator.com/item?id=30057442 [2]: https://ory-events.vercel.app/ https://ory-events.vercel.app/

infogulch 4y ago
Provocative choice, explicitly excluding Facebook/Meta filters.
- xvello 4y ago
  I'm interested to understand why you find this provocative. My ambition is to build a dependable service that will be up for several years to come. For that to happen, I need to limit myself to a scope I am comfortable maintaining in the long run, instead of burning out under scope creep. Until the maintainer team grows, I would be on the hook for updates and fixes, and I refuse to create an account on any of that company's sites.
  - infogulch 4y ago
    > I refuse to create an account on any of that company's sites That makes sense. Would you be opposed to having filters for the company's sites given someone else willing to maintain it?
    - xvello 4y ago
      FYI, I have such a call to maintainer [1] for a "Twitter cleanup" template similar to the "Google search cleanup" one [2]. There is definitely a need, but it seems over my current carrying capacity. For Meta's properties, I would wait for the maintainer to have a track record of contributions before being comfortable opening that door. [1]: https://github.com/letsblockit/letsblockit/issues/269 https://github.com/letsblockit/letsblockit/issues/269 [2]: https://letsblock.it/filters/google-search-cleanup https://letsblock.it/filters/google-search-cleanup

by xvello 4y ago

infogulch 4y ago

Provocative choice, explicitly excluding Facebook/Meta filters.

xvello 4y ago
I'm interested to understand why you find this provocative. My ambition is to build a dependable service that will be up for several years to come. For that to happen, I need to limit myself to a scope I am comfortable maintaining in the long run, instead of burning out under scope creep. Until the maintainer team grows, I would be on the hook for updates and fixes, and I refuse to create an account on any of that company's sites.
- infogulch 4y ago
  > I refuse to create an account on any of that company's sites That makes sense. Would you be opposed to having filters for the company's sites given someone else willing to maintain it?
  - xvello 4y ago
    FYI, I have such a call to maintainer [1] for a "Twitter cleanup" template similar to the "Google search cleanup" one [2]. There is definitely a need, but it seems over my current carrying capacity. For Meta's properties, I would wait for the maintainer to have a track record of contributions before being comfortable opening that door. [1]: https://github.com/letsblockit/letsblockit/issues/269 https://github.com/letsblockit/letsblockit/issues/269 [2]: https://letsblock.it/filters/google-search-cleanup https://letsblock.it/filters/google-search-cleanup