Hacker News: p4bl0

New comment by p4bl0 in "Minimal Phone 2"

p4bl0 — Fri, 18 Sep 2026 19:37:42 +0000

Like a lot of similar devices, it looks cool, but, just like a lot of similar devices which have a physical keyboard, it will probably never be released with anything else than a US qwerty keyboard, so I'm already out.

Update: didn't scroll down enough! Indeed they have. Neat.

New comment by p4bl0 in "Forgejo <=16.0.3 Critical RCE"

p4bl0 — Thu, 10 Sep 2026 18:57:08 +0000

They also have a releases RSS feed. I have those in my mail client (Thunderbird) directly for the projects that I must closely follow critical updates of.

New comment by p4bl0 in "Git hosting that never leaves Europe"

p4bl0 — Sat, 05 Sep 2026 10:03:06 +0000

That's awesome. Thanks for working on this!

New comment by p4bl0 in "How to Create a Tor Exit Node (2015)"

p4bl0 — Fri, 04 Sep 2026 21:11:11 +0000

> you may get law enforcement knocking on your door with questions

If you host an exit node on your home internet connection, the daily thing you will struggle with is not law enforcement, but rather the fact that your public IP will be blocked by most big websites to the point that simply browsing the web will become a pain.

Statichost.eu – European static site hosting

p4bl0 — Fri, 04 Sep 2026 20:34:49 +0000

Article URL: https://www.statichost.eu/

Comments URL: https://news.ycombinator.com/item?id=49569896

Points: 506

# Comments: 246

New comment by p4bl0 in ".name Termination"

p4bl0 — Fri, 04 Sep 2026 12:14:07 +0000

Update report: they are still categorically refusing, even for third-level customer who are alone (and have always been for 20 years) on the second-level they use. It makes no sense.

New comment by p4bl0 in ".name Termination"

p4bl0 — Fri, 04 Sep 2026 05:46:45 +0000

The .name predates the TLD well-off crap. The first huge bulk of new TLDs happened in 2014, .name dates back from 2001, just like .info or .coop.

Also, .name filled an actual need for general non ccTLD: companies had .com, organizations had .org, Internet related stuff had .net, there was .gov, .edu, .mil, and ccTLDs, but nothing made for individuals. It filled this use case, it actually made sense.

New comment by p4bl0 in ".name Termination"

p4bl0 — Thu, 03 Sep 2026 20:57:45 +0000

> There should be a conflict resolution to gracefully degrade the third level to 2nd level when there is no competing name on the second level.

Yes. I've been asking VeriSign for this for years, and they always refused.

New comment by p4bl0 in ".name Termination"

p4bl0 — Thu, 03 Sep 2026 19:51:13 +0000

Not at the very beginning, but then it became possible.

New comment by p4bl0 in ".name Termination"

p4bl0 — Thu, 03 Sep 2026 19:47:37 +0000

Another thing that should be obvious and yet they refuse to do: when there is a single third-level customer for a given second-level, offer them a way to get the second level domain. I've been asking VeriSign this for 15+ years, they always said no, even if at some point they confirmed that there were no other third-level than mine under that second-level domain. They're insane and should not be in charge.

New comment by p4bl0 in ".name Termination"

p4bl0 — Thu, 03 Sep 2026 19:42:57 +0000

Really? Mine have been discontinued without notice something like 15 years ago!

New comment by p4bl0 in ".name Termination"

p4bl0 — Thu, 03 Sep 2026 16:28:06 +0000

At the beginning of the existence of the .name TLD you couldn't do that, you were forced to register firstname.lastname.name and provide an ID to justify registering this specific domain.

With it you got an email redirection from firstname@lastname.name to the address of your choice. At some point this feature was discontinued (I assume when VeriSign took control of the .name TLD), a bit after it was decided (again by VeriSign) to allow registering first level .name domain. My main email address stopped working from one day to another without me being warned in any way.

When this happened I've emailed VeriSign and my registrar at the time, and tried several time since then, to be able to register the first level domain I'm the only one using, but they categorically refuse, despite recognizing that a single subdomain has ever been registered. They kept saying that I could just let the domain expire, wait for the grace period, and register it once it's liberated, hoping that no one does it before me, and without any solution for the downtime in the mean time…

And now this… fuck VeriSign -_-

New comment by p4bl0 in "Why do so many tools have JSON config files?"

p4bl0 — Wed, 02 Sep 2026 19:32:56 +0000

Hey, thanks for Caddy! It's awesome :).

e is a customizable self-aware Emacs-like editor written in Chez Scheme

p4bl0 — Sat, 29 Aug 2026 06:35:28 +0000

Article URL: https://github.com/paveluv/e

Comments URL: https://news.ycombinator.com/item?id=49487506

Points: 51

# Comments: 23

New comment by p4bl0 in "Bye, Bye GitHub"

p4bl0 — Fri, 28 Aug 2026 22:10:56 +0000

I agree. GitLab UI was great and the simplicity of its CI/CD is unequaled on other forges. It's sad that Forgejo went with the actions model from GitHub which introduce a lot of useless complexity. But it seems that Woodpecker CI [1] could be a good candidate to replace GitLab CI, as it uses very similar concepts and workflow description files.

[1] https://woodpecker-ci.org/

New comment by p4bl0 in "Bye, Bye GitHub"

p4bl0 — Fri, 28 Aug 2026 22:05:31 +0000

GitLab is also getting worse and worse. They're going full-in on AI and each new release is more cluttered with useless features and requires more and more resources to run smoothly. After six years self-hosting a GitLab instance for a few hundred users (among which a few dozens are quite active), I abandoned this summer and I'm currently migrating the instance to Forgejo.

When Search Eats the Web: A Model of Corpus Erosion Under Generative Extraction

p4bl0 — Tue, 18 Aug 2026 07:40:52 +0000

Article URL: https://arxiv.org/abs/2608.15896

Comments URL: https://news.ycombinator.com/item?id=49342641

Points: 1

# Comments: 0

New comment by p4bl0 in "Immich 3.0"

p4bl0 — Fri, 03 Jul 2026 09:16:44 +0000

I teach a free software development course to my undergrad students. It's really exciting to stumble upon one of the work they did for my class in the wild (it's the first listed bug fix — which is the last of the three pull requests this student got merged in Immich during my course). I feel so proud! :)

New comment by p4bl0 in "A field guide to the modern front end for developers who hand-wrote HTML"

p4bl0 — Mon, 29 Jun 2026 14:47:38 +0000

This is too oddly written to read in its entirety and I don't get the point. I mostly still do things like it says it worked in 2008. The difference with the "modern" workflow with 1400 packages and a build system is that web pages I put online just work, unlike most modern website which are horribly bug ridden and take ages to load and render.

New comment by p4bl0 in "Obfuscation: Building the Final Boss of Cryptography"

p4bl0 — Mon, 29 Jun 2026 08:50:06 +0000

I really don't understand that some people are still trying to sell blockchain-based electronic voting. But anyway, I just wanted to tell a fun anecdote about the impossibility of making an obfuscater that works for any arbitrary program, or rather, since this is trivial for Quines [1], that it is possible to protect any program from obfuscation by making a simili-Quine of it. Given a program P, it is possible to construct a program Q(P) that takes an additional optional boolean input that defaults to false and which, when this additional input is false (i.e., by default), behaves exactly like the program P, but when called with the additional input set to true, acts as a Quine instead of executing P, thus outputs the source code for Q(P) (which is constructed to includes P's source code). This is guaranteed to work basically because an obfuscater cannot change the behavior of a program without breaking indistinguishability. I remember having a lot of fun working on that as an undergrad a long time ago [2].

[1] https://en.wikipedia.org/wiki/Quine_(computing)

[2] https://eprint.iacr.org/2011/497.pdf