Live data from Hacker News

Everything I own, owned

schlarp.com

331–340 of 367 posts

Re: Everything I own, owned

#331

Sidenote to the technical discussion. The article read like a Martha Wells murderbot novel to me. Fascinating.

Yep, Claude did well here. From the experiment, to the website design, to more than likely all the writing/summaries. What is truly fascinating is not that long ago people were doing hard experiments regularly like this without any LLMs.

Like Dublin, in the rare ould times.

Re: Everything I own, owned

#332

Earlier quoted context omitted.

Surprising. I have hit its BS guardrails a lot lately, working on my vintage computers from the 80s and early 90s. Just about done with Claude.

I’ve been doing this with Qwen 3.8 27B with success. Kindle, Android Tablet, and Raspberry Pi all working better and fully owned thanks to agentic help. No issues with hitting the guardrails here ofc.

What tools/skills are you using to do this with Qwen 3.8?

Re: Everything I own, owned

#333
About 1.5 years ago I reported a vulnerability with my router’s ipv6. The firewall was wide open, and router management SSH was listening externally, among a few other vulnerabilities. After pulling teeth, the router fixed ssh, but not the firewall.

A couple months ago I used AI to find a novel shell injection exploit and obtain root creds in the router, so I could print out the firewall configuration , init script flaws , and write up a vulnerability report. AI found the bug and wrote the patch to fix it for the vendor, without having the original code ( the bug was in shell script, thankfully).

The vendor had commented out the IPv6 firewall init, probably to pass QA , knowing consumers don’t usually use or test IPv6.

Upon getting the report, the vendor fixed the issue.

Re: Everything I own, owned

#334

Earlier quoted context omitted.

Opus 5 with CVP, no special prompting. In this instance just about any larger model from the last 12 months would have done the trick.

>with CVP Ah, there's the rub.

Almost everyone I know who applied for CVP was successful, it's worth a try.

Re: Everything I own, owned

#335
post #145

Earlier quoted context omitted.

The end user disables pixel cleaning because the pop-up annoys them. They then start bitching about burn-in within 6 months, RMA the monitor even though it was their choice to do so, and spread negative sentiment about your brand going forward for being "prone to burn in".

Yes? Are you a human or a corporation talking? Has Samsung achieved singularity status and is now posting on HN? Besides, the negative sentiment that OP shares here sis for me much stronger than any burned pixel, annoyances like this are a sure way for me to not buy a product if I read this in reviews

Why would Samsung care if he burns out his OLED panel? The alert is there only as far as shielding the manufacturer from legal culpability if the unit fails. If they can point and say "Nah, no RMA, this guy only did 3 pixel refreshes in a year or installed unauthorized firmware" then you're on the hook for a new display. Assuming that Samsung has any more investment in enforcing you to pixel refresh is inane.

Do you also skip oil changes thinking "Fuck you, not today, Hyundai!"

Re: Everything I own, owned

#336
post #145

Earlier quoted context omitted.

The user should be the final authority over what his computer does. Not the computer manufacturer. Not the OS developer. Not the 3P app developer. Not some product manager at a software company. The end user. Even time computer says no, or does something without your permission, or does something counter to your wishes, or alerts you to do something, or urges you to do something, or makes you opt-out, is a failure.

The end user disables pixel cleaning because the pop-up annoys them. They then start bitching about burn-in within 6 months, RMA the monitor even though it was their choice to do so, and spread negative sentiment about your brand going forward for being "prone to burn in".

OP wants his property to behave in a specific way, clearly knowing the risks.

I'm not seeing how a hypothetical bad review about a $200B company is at all relevant here. The manufacturer's reputation is not in any way OP's problem.

If you own the hardware, it is yours to abuse, break, and do all manner of things that would make the engineers who designed it cringe: you do not owe any allegiance to them.

Re: Everything I own, owned

#337
post #35

> My ASUS ROG Swift PG42UQ monitor was actually where I started, because I got annoyed at the pop-up overlay that comes up every once in a while that tells me to run “pixel cleaning”. I have never intentionally run pixel cleaning on this monitor and I never will, I don’t care, and I would like for that overlay to go away forever. Maybe there’s a debug menu or something that can turn it off, or worst case we patch a b…

Yeah, you actually want to do this with monitors of that generation to make them last. You could argue that there should be an option to disable it for people who don’t care. Refusing to take 1 minute out of your day to learn the reason for the alert is a strange self-defeating protest next to the explanation that it was a pretty expensive monitor.

And yet, they own the device. If they choose to not care about burn-in and want their device to respect that, that's their prerogative, not anyone else's.

Re: Everything I own, owned

#338
post #204

Earlier quoted context omitted.

Generally, I'm with you, but over the past decades I often saw companies being lazy about their software. So I think chances are good that we can make use of this situation. Not long ago, you had to accept certain decisions or servers going down with leaving devices useless. I'm hopeful that more stuff can have a 2nd/better life in our hands.

I like being able to have all this access, of course, but I'm not sure if "we" all truly have the character to be good stewards of this. Or rather I am sure that we do not. OTOH, maybe it needs events like these to build character. It just will suck for whoever turns out to be the collateral.

Do the companies have better character though?

Re: Everything I own, owned

#339
post #325
post #130

Earlier quoted context omitted.

Even with "E2E" encryption with iMessage, you're still trusting Apple completely and totally with key distribution. If a new device is added to your account by an attacker or by Apple themselves, your existing devices will happily loop them in to share iMessage access with them. The vast, vast majority of iMessage users are never going to dig into the Apple keychain app to actually check what keys are being trusted a…

CKV aims to cover that case: https://support.apple.com/en-us/118246 https://support.apple.com/en-us/118247 > An unrecognized new device was added to that person’s Apple Account. This alert might mean that the person you are messaging has an issue with one of their devices, or that a sophisticated attacker might be attempting to eavesdrop on the conversation. My understanding is that iMessage implements PFS. To get ar…

Uh-oh, I have that turned off. I’m used to seeing a message when someone on Signal gets a new phone, but I’d be none the wiser with a snooper on iMessage. Any downsides to enabling you know of? Assuming all my logged-in devices are on a current/supported version.

Re: Everything I own, owned

#340

I did this but with a dedicated machine for the Silicon Motion sm750 GPU. A budget single HDMI output GPU card for servers and a max resolution of 1080p. It is based on an older VGA/DVI version of the same hardware. I'm still testing but oh wow. My new driver now works with my ultra wide 21:9 ratio at 2048x864, it also manages 2048x1152. The driver works well, and now has full DRM and DKMS support. It also runs on mo…

> custom magic square dither mode for 16bit colour and it absolutely flies vs the 32bit mode While that is cool, why do you need such a thing? More FPS? Less video RAM?

There's no hardware acceleration, it's raw framebuffer stuff so window dragging is laggy at 32bpp at the highest resolutions, even after I added buffers. I'm by no means requiring 16bpp, the build will do 32bpp by default unless you enable a flag.
Post reply on HN