HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
letsblockit
letsblockit
Go2022–2026
letsblockit / letsblockit · Archived

letsblockit

Remove low-quality content and useless nags, focus on what matters. A community-maintained uBlock Origin filter set.

4Distinct people
6Mentions
0Explicit recommenders
768GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Remove low-quality content and useless nags, focus on what matters. A community-maintained uBlock Origin filter set.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2022-07-10 17:46:23 UTC to 2026-02-15 06:32:00 UTC.

01232022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

6 sources
SEEKING VOLUNTEERS: https://letsblock.it - https://github.com/letsblockit/letsblockit/ A companion project for uBlockOrigin that curates a corpus of content blocking templates, and provides the server to create you personal list of content blocking rules. The official instance just hit 800 active lists and a lot of template suggestions have been filed recently. The easiest way to contribute is to create new templates, fix or extend existing ones. You need to learn the uBlockOrigin syntax and how to properly target the right elements, happy to mentor! See recent PRs for examples and https://github.com/letsblockit/letsblockit/blob/main/data/fi... for documentation. The server itself is built with Go and HTMX, it's pretty low-maintenance, but there's interesting improvements if you want to toy with it (need to open issues for these).
In Ask HN: Looking for a project to volunteer on? (February 2024)
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 [2]: https://letsblock.it/filters/google-search-cleanup
In Ask HN: What not-profit-seeking project are you tinkering with this week?
Gin and Echo cover similar feature scopes (the HTTP plumbing around your business logic, that you write in handler functions), but I chose Echo for my project[1] because: - it ships a pretty extensive collection of middlewares that will get you to 80% faster - the documentation[2] is really well written and accessible to new web developers: most "must have" features have a cookbook page, so you don't have to google for blog posts. - it does indeed use a custom handler function signature, but in my opinion this one is better (returning errors instead of handling them locally in each handler). You can still use handlers and middlewares written for other frameworks (for example the great statigz[3] handler) through the `echo.WrapHandler` and `echo.WrapMiddleware` functions [1] https://github.com/letsblockit/letsblockit [2] https://echo.labst
Read the rest
In Labstack/echo: High performance, minimalist Go web framework

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.