Why is this down voted? I think it’s good to hear explanations to see if OP (or anyone) understands what they’re building and what issues they look to solve.
Politely, that sort of thinking leads us to the monopolies of today. Why use Lemmy? what does it provide Reddit doesn’t already? If each of the 4 listed used “it already exists” as a reason not to try we wouldn’t have the others. We need choice and 40 of everything as long as it’s maintained.
True, choice is nice, but too many choices can be worse than not enough choices. Too many devs spread out across too many projects slows progression.
I would prefer, however, newer projects fork the originals so that can build upon the already great software we’ve come to love. Almost like building an addition to the mansion instead of trying to build from the ground up in the same amount of time. Way more work solving similar problems.
Your commit patterns suggest you use AI for more than you share here.
A feature lands, then 15-60 minutes later a fix commit occurs. This is pretty typical when a second agent reviews the work of the first. I run the same pattern myself.
Here are some examples that I see just on Nov 14:
the HA cluster rolling update (22 files, about 2,500 lines at 17:11, review fixes for a start race, downgrade protection and worker hardening at 18:06),
GeoIP enrichment (19:30, review fixes at 19:43),
and the world map and geo-watch (1,650 lines at 22:00, review fixes at 22:14).
These are backend features (cluster sync, crypto, update worker). Nobody writes that much Rust by hand that fast.
Tons of comments like an AI would write. You’re certainly using AI to write tests, too.
It’s okay to use AI for hobby projects, but when you’re offering a product to the public, the public deserves to know the products provenance.
Like I mentioned in the post, I do use AI to assist with testing, comments, code reviews, and coordinating parts of the project which is pretty standard these days to catch edge cases early. The crazy commit speed, though, is mostly because I build and test everything locally on my private Gitea server first and then push it step bystep to GitHub which makes the timestamps look way faster than they actually were.
To keep things completely transparent going forward I’m going to drop the Gitea middleman and push straight to a dev branch on GitHub so everyone can see the real time progress.
In the next days I will publish on the github the complete AI usage so its more transparent to everybody
I find the AI disclosure rules for this community to be well thought out and reasonable. Please follow them. It doesn’t take very long to put together the compliant tags and disclosure text.
I see comparisons to pihole, but how does it compare to Technitium, especially since it supports clustering.
Honestly glad you are doing this, because I was a bit bummed that the only DNS filter I found that easily supported HA was written in C# (personal preference/prejudice). I’ll give this a go when I find some time to ϲнαπgє τнє ⲅμππίπg ϛψϛτєϻ
5
[deleted]·
Collapsed, score -6 is below -5. 3 replies hidden.
Is the company id by AS number? If so I think that would always show the hosting provider but not the actual operator. Like anyone hosting on GCP would be using a Google AS, or do I have that wrong?
The company attribution is domain-based a compiled in catalogue mapping registrable domains to the operator (connect.facebook.net to Meta, etc.), so hosting AS doesn’t matter there. The limitation is that it’s a curated set not exhaustive. The world map is the ASN part you mean: offline IP-to-ASN, which does show the host (GCP, Cloudflare). So “who” comes from the domain, “where” from the AS.
Comments
“Contributors: Claude”
Please refer to rules 7 and 8 of this community.
What does this offer that the other major systems don’t already provide?
[deleted]
Why is this down voted? I think it’s good to hear explanations to see if OP (or anyone) understands what they’re building and what issues they look to solve.
Good to know there’s some competency.
Politely, that sort of thinking leads us to the monopolies of today. Why use Lemmy? what does it provide Reddit doesn’t already? If each of the 4 listed used “it already exists” as a reason not to try we wouldn’t have the others. We need choice and 40 of everything as long as it’s maintained.
True, choice is nice, but too many choices can be worse than not enough choices. Too many devs spread out across too many projects slows progression.
I would prefer, however, newer projects fork the originals so that can build upon the already great software we’ve come to love. Almost like building an addition to the mansion instead of trying to build from the ground up in the same amount of time. Way more work solving similar problems.
It0s a valid questioning when you see that Claude is
among the developersthe developer.Slopware. To the list it goes.
How much Claude is in this?
Reading some of the replies here would lead me to assume they’re relying on it very heavily.
[deleted]
Your commit patterns suggest you use AI for more than you share here. A feature lands, then 15-60 minutes later a fix commit occurs. This is pretty typical when a second agent reviews the work of the first. I run the same pattern myself.
Here are some examples that I see just on Nov 14:
the HA cluster rolling update (22 files, about 2,500 lines at 17:11, review fixes for a start race, downgrade protection and worker hardening at 18:06),
GeoIP enrichment (19:30, review fixes at 19:43),
and the world map and geo-watch (1,650 lines at 22:00, review fixes at 22:14).
These are backend features (cluster sync, crypto, update worker). Nobody writes that much Rust by hand that fast.
Tons of comments like an AI would write. You’re certainly using AI to write tests, too.
It’s okay to use AI for hobby projects, but when you’re offering a product to the public, the public deserves to know the products provenance.
Like I mentioned in the post, I do use AI to assist with testing, comments, code reviews, and coordinating parts of the project which is pretty standard these days to catch edge cases early. The crazy commit speed, though, is mostly because I build and test everything locally on my private Gitea server first and then push it step bystep to GitHub which makes the timestamps look way faster than they actually were.
To keep things completely transparent going forward I’m going to drop the Gitea middleman and push straight to a dev branch on GitHub so everyone can see the real time progress.
In the next days I will publish on the github the complete AI usage so its more transparent to everybody
I find the AI disclosure rules for this community to be well thought out and reasonable. Please follow them. It doesn’t take very long to put together the compliant tags and disclosure text.
I edited the post :)
[removed by a moderator]
Most people would just ship their logs to something like Graylog if they need this type of analysis.
[removed by a moderator]
Interesting, thanks for sharing.
I see comparisons to pihole, but how does it compare to Technitium, especially since it supports clustering.
Honestly glad you are doing this, because I was a bit bummed that the only DNS filter I found that easily supported HA was written in C# (personal preference/prejudice). I’ll give this a go when I find some time to ϲнαπgє τнє ⲅμππίπg ϛψϛτєϻ
Is the company id by AS number? If so I think that would always show the hosting provider but not the actual operator. Like anyone hosting on GCP would be using a Google AS, or do I have that wrong?
The company attribution is domain-based a compiled in catalogue mapping registrable domains to the operator (connect.facebook.net to Meta, etc.), so hosting AS doesn’t matter there. The limitation is that it’s a curated set not exhaustive. The world map is the ASN part you mean: offline IP-to-ASN, which does show the host (GCP, Cloudflare). So “who” comes from the domain, “where” from the AS.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
[Thread #170 for this comm, first seen 17th Nov 2026, 20:00] [FAQ] [Full list] [Contact] [Source code]
This post is closed to comments.