HN user

mrbuttons454

384 karma
Posts0
Comments90
View on HN
No posts found.

This is great information, thank you for posting!

I think there is a line between security, and keeping a device useful in the long term. I think the threat of people installing listening malware on the car via an evil-maid type attack is low.

However, when these cars are 10+ years old, and are in the hands of those willing to tinker, I think the ability to open up the software and customize will be a great thing. Hopefully communities form around creating modifications they find useful, and prolongs the life of the devices.

Seems much better than the end-users ripping out the factory head unit to install the Aliexpress "Android Tablet" style units, which likely have much worse security and engineering than the Honda units they'd be replacing.

Claude Fable 5 1 month ago

Is there a Qwen that I can run locally that is anywhere near these frontier models?

Papercuts like this are why I moved away from macOS.

I will say, I don't love the use of LLMs to write these bug reports. It's probably fine if reviewed, but at least review for things like "worked on macOS 25", which obviously didn't exist. If that wasn't caught, how sure are you that the rest of the report is accurate? We all want the bugs fixed, but people are going to start throwing out the obviously LLM written reports rather than have to validate each claim, since the author probably didn't.

MacBook Neo 5 months ago

I have the chonk. 10/10 would chonk again. I miss the 12" MacBook form factor for an email/web/dumb terminal machine, though. Would love something like that with great Linux support. Bonus points for cellular.

I haven’t had much time with it, but I’ve had to set the split in the BIOS. There’s probably a way to do it from within Linux though. Also hoping some progress is made on using the AMD NPU in Linux. I know it only recently got kernel level support.

He found a sideloadable JIT server + VPN setup. It seems super sketchy honestly, and it's a shame that people have to go through this to enable a feature that should just be available. There is no legitimate reason to block access to JIT.

I've been running Debian on servers for 20+ years now. And in the last few years I've been running it on my desktop, sort of a toe in the water. Debian hasn't let me down, and I'm very familiar with it.

I was on my way out the door before the Apple Silicon launch. They managed to briefly bring me back in, but the software is only getting worse. It's a shame too, because I do believe Apple has the best hardware.

Keyboard shortcuts have been a big pain point, but I'm adjusting. I'm using Plasma 6, and trying to use the defaults vs emulating the mac shortcuts. Print screen as a screenshot button makes considerably more sense to me than Command-Shift-4, and Meta+Print Screen captures just a single window.

Logiops + Plasma's multi desktop support has given me something very similar to the multi desktop experience I had before, and the pager in the taskbar is a big improvement.

The tiling in Plasma needs work. I initially loved it until I released that when I arranged the tiles differently on one desktop, it changed them on the others... Hopefully that gets better.

I have been a Mac user since the classic mac days. I waited in line for the first iPhone.

macOS/iOS 26 are bad enough that I've begun switching to Linux. I preordered a Clicks Communicator and Pebble Round 2. Switching from a Macbook Pro M4 to an Asus ROG Flow Z13 with Debian.

macOS 26.3 updated clang and broke my emscripten workflow.

I tried to unrar a file but the version of unrar provided in homebrew is deprecated because it's no longer signed/blessed. I ended up SFTPing the file to a Linux box, extracting, and bringing it back.

My son wanted to try a Java minecraft app on his iPhone, but it required insane workarounds to enable JIT to get acceptable performance. This isn't a technical limitation, it's put in place specifically to protect Apple's walled garden, and their precious services revenue.

Despite the thousands of dollars spent on these devices, I don't feel like we own them. We can't run code without the platform owner's permission. We are at the mercy of the platform owner, that has been making increasingly worse decisions.

I'm really enjoying trying the available alternatives. My hope is that enough of us get fed up, and develop a thriving ecosystem in the open source world. I'll certainly be contributing back the things I build.

I started with Red Hat 6 (not RHEL) as a kid, because it was what was included with the book on Linux that I was gifted. Some time around 2000, I was given some retired beige powermac G3 desktops, and I switched to Debian for its PowerPC port. I've been with Debian ever since.

So maybe pick something with the realization that they may stick with it for decades. :)

I also kept Windows on dual boot so I could play UT99 with friends. The social aspect is also important. My son is comfortable using our Debian machines, but also has Windows on his primary desktop so he can play Roblox and Minecraft Bedrock with school friends. I wouldn't want him to lose that.

I bought one as soon as they were released, as well as the keyboard case. It never really worked correctly, but I loved the concept and wish they would have succeeded.

I know it's a niche product, but I'd love a pocket sized Debian device with cellular, decent standby time, and a physical keyboard. Anything out there I should look in to? I've tried to make various GPD devices work, but they are too big, and the standby time isn't great.

I'd be sure to charge them before storing them for the next show. Most batteries don't like being stored for long periods in a low SoC state. And I'm sure the tamper requires a functional battery.