Hacker News: veegee

New comment by veegee in "As AI gobbles up chips, prices for devices may rise"

veegee — Mon, 29 Dec 2025 14:18:45 +0000

Real consequences need to be implemented such as prison time or ideally death penalty. But sadly we’ll never see that happen

New comment by veegee in "Ubiquiti SFP Wizard"

veegee — Sun, 02 Nov 2025 09:05:35 +0000

It won’t get much better because that’s just a limitation of how 10GBASE-T works. There’s never a good reason to use it. Always just use a DAC or fibre.

New comment by veegee in "Ubiquiti SFP Wizard"

veegee — Wed, 29 Oct 2025 01:29:23 +0000

DAC is always the best option for short runs in terms of cost and compatibility.

New comment by veegee in "The Programmer Identity Crisis"

veegee — Tue, 21 Oct 2025 18:51:29 +0000

Sounds like a mediocre developer. No respect for people like you.

New comment by veegee in "Compare Single Board Computers"

veegee — Mon, 20 Oct 2025 01:22:21 +0000

This is actually pretty terrible. Apart from the things “okanat” said, the site is a nightmare in terms of UI and extremely buggy. I didn’t realize modern websites could get this bad.

New comment by veegee in "The best YouTube downloaders, and how Google silenced the press"

veegee — Sat, 20 Sep 2025 02:13:42 +0000

Very easy to remove it with an HDCP remover like HDFury, or even an HDCP downconverter and then using the known master keys to decrypt that.

New comment by veegee in "The best YouTube downloaders, and how Google silenced the press"

veegee — Sat, 20 Sep 2025 02:03:32 +0000

Yes actually you can. But you don't even need to go that far, there are HDCP converters that do it for you and convert to HDCP 1 (whose master keys have been made available) or just plain HDMI. See HDFury etc.

New comment by veegee in "32“ E Ink screen that displays daily newspapers on your wall (2021)"

veegee — Fri, 07 Jul 2023 16:21:26 +0000

If Docker is in any way _required_, it's still a dealbreaker.

New comment by veegee in "Shipping forgettable microservices with Rust"

veegee — Fri, 24 Jun 2016 16:58:59 +0000

I'm not a fan of Go, but the connection pooling in the standard library doesn't leak. You're just not closing the Rows object if you encounter an error. It automatically closes if you fully iterate through it. But if you stop part way, you have to manually close it or the connection will not be returned to the pool.