Recent submissions

Comment · 2 days ago
Interestingly when I asked about that string the first time on Opus 5.5 it actually repeatedly refused to do anything. It did say it was allowed to talk about the refusal itself, which of course is just post-hoc reasoning, but wouldn't do anything else after that and kept responding with (IIRC) "I can't help with that".

Now that I've tried it again it doesn't refuse at all. So perhaps just some part of the model still tuned towards that.

Comment · 9 days ago
It's almost a shame it includes the private key and doesn't bruteforce it in-band for every request.
Comment · 11 days ago
It's indeed Stockholm syndrome. It's (Ghidra decompiled) AArch32 firmware, but they define the datatype themselves with that name.
Comment · 11 days ago
Comment · 11 days ago
Comment · 25 days ago
I'm customarily adding a "LLM disclosure: no LLM was used while drafting this issue text" to issues now (when that is true), to at least give some explicit signal that two humans are talking. Of course the text you write yourself is often distinct from slop grenades, but emphasizing that can't hurt.

And of course, you can write that and still paste completely slop, but nobody seems to be doing that yet, and if they would it's probably not convincing.

Comment · 29 days ago
Certainly! You can watch a talk about the operations behind the Home Computer Museum here: https://media.ccc.de/v/mch2022-140-homecomputermuseum-the-ma...

There's also a page here that contains the budget for multiple years, although the totals from 2027 on don't sum correctly from the different sub-budgets: https://www.homecomputermuseum.nl/informatie/organisatie/bel...

Comment · 1 month ago
It even goes both ways: you can geolocate the user, and you can sell the BSSID data for future lookups. Not sure how valuable that still is in 2026 now that every mobile phone is adding that to the Goople databases, but it was in the past.
Comment · 1 month ago
> Is there anyone who has done a technical write up and investigation into the firmwares?

I extracted the firmware and filesystem of a webOS 3.5 and webOS 24 TV previously so I could remove the spying bits and get an internet connected TV back. I asked Claude Opus 5 to do some analysis on the ACR implementation yesterday. I haven't had time to check it myself, so it might give some insight but take it with a grain of salt. Also because I'm not entirely sure I extracted the complete filesystem for the webOS 24 TV.

See the documents temporarily hosted here [1][2][3]. You can find the Markdown originals in the HTML source. The Markdown has also been pasted here [4] (although the forum software has sometimes inserted a lot of tildes).

LG uses the "Alphonso SDK" for ACR, a company which it seems to have a majority stake in [5].

WebOS itself is actually pretty neat once you get root on the device. It still has open source releases, uses a well documented service bus, the UI apps are unobfuscated Javascript. It's a genuine Linux TV if only LG allowed you to get root and would not install spyware by default. Secure boot unfortunately does prevent you from messing with the boot process.

If you want to know anything specific, let me know. There's also a pretty active Discord (ugh) community here [6].

Personally, I'm most interested whether LG and other device manufacturers are getting informed consent for ACR in European markets, and what the consent screen looks like. I doubt that many consumers actually know what they're consenting to, which might be a GDPR violation.

[1] https://scriptbase.org/lg-tv/webos-24.html

[2] https://scriptbase.org/lg-tv/webos-3.5.html

[3] https://scriptbase.org/lg-tv/comparison.html

[4] https://gathering.tweakers.net/forum/list_message/86090672#8...

[5] https://www.adexchanger.com/tv-2/lg-grabs-a-majority-stake-i...

[6] https://openlgtv.github.io/

Comment · 3 months ago
> I bought Qty 10* of HC520 (12TB) SAS drives for $1000 about 3 weeks ago, avg age is about 2.5 years, still well within its rated lifetime.

That's cheap indeed. Enough headroom for some failing disks too. How is the noise and power usage? I didn't look at SAS drives at all, because my impression was that they're very noisy. I can place my NAS in a closed off room, but it's not too far away and I was afraid SAS drives would be audible through the wall. At the same time, the shucked drive I'm using presents itself as an WD Ultrastar, which comes very close to a SAS drive, and isn't very noisy.

Comment · 3 months ago
Comment · 3 months ago
> I’m running an 8-drive ZFS RAIDZ2 pool. I’m wondering if you know — are the free space recommendations around ZFS cargo or real?

I'm not entirely sure, but it seems to me that free space (and the 20% reservation) is mostly a proxy for fragmentation, and you can therefore better look at fragmentation directly. That would mean that if you mostly store large files, there shouldn't be a lot of fragmentation even at high utilization. The whole "ZFS changes allocation algorithm from 80% usage on" is something of 10+ years distant past, and lots of things around the allocator have been improved. It's also something that probably isn't too different from the performance of other filesystems at high utilization, so it shouldn't be exaggerated.

Comment · 3 months ago
It was €329 per hard drive (through a reputable store), and I chose the ASRock B650M-HDV/M.2 mATX motherboard combined with a Ryzen 5 8500G. Stock CPU cooler, replaced the Jonsbo case fans with Arctic P12 Pro PST LN. I only slightly regret the PSU (MSI MAG A650GL), which could be quieter. Not that it's very noisy, and it's a great PSU otherwise, but I should've chosen one that just shuts the fan down at low power usage.
Comment · 3 months ago
Not a great time price-wise to be building a NAS, but I have been doing so for the last two weeks. Inside a Jonsbo N6 case, which is pretty nice with an 8x SATA backplane and drive bays (unlike the earlier Jonsbo variants).

I ended up on shucking 4x the 14 TB WD Elements Desktop. They contain helium drives, the WD140EDGZ in my case, and are about a third cheaper than 4x the 12 TB WD Red Plus drives (which are air-filled). The shucking was easier than I expected too, and the performance seems very comparable. The warranty is a definite downside (European, so no Magnuson-Moss), but I think I can even get them back in their enclosure should they fail during the 2-year warranty period.

I've put some second hand 256 GB M.2 SSDs in there as boot drives. It was a bit of a struggle to get it to work in a way that failure of one of the drives doesn't hold up booting, combined with LUKS, TPM keys and ZFS on root. Learned a lot about systemd-boot which I have never used before, but feels a lot saner to me than grub ever was. So now I have a large script which debootstraps a Debian based NAS into being.

I noticed that there are a lot of ZFS myths and cargo culting. For example TFA mentions ECC RAM, which in some circles is a must-have because ZFS would wreck your pool during a scrub otherwise, which is a myth. It's also very expensive, especially this year. You also don't need much RAM for ZFS, L2ARC doesn't use much RAM at all, to name a few others.

Still doubting about setting `dnodesize=auto` (which is the default), because there are some horror stories about that [1]. And it seems impossible to find a cloud storage provider with reasonable prices that supports `zfs send`. Rsync.net upped their minimum order to 10 TiB recently, which is far too much for my use case.

[1] https://github.com/openzfs/zfs/issues/11353

[2] https://www.rsync.net/products/zfsintro.html

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton