> 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…
The Internet seems rather reluctant to explain what exactly "pixel cleaning" does, but based on the vague useless "explanations" I could find, I suspect it's a sort of "flat-field correction" where it calibrates the pixel drive current to darken the less worn and/or brighten the more worn ones so it eliminates the burn-in effect. This obviously leads to a vicious cycle where more worn pixels are driven harder and hen…
Everything I own, owned
321–330 of 367 posts
Re: Everything I own, owned
#322Re: Everything I own, owned
#323Earlier quoted context omitted.
While it’s impressive work from the LLM and a TS implementation is novel, there’s at least a couple of pre-existing Python REs eg. https://github.com/jya-dev/supernote-tool :)
It seems like most of these "an LLM solved this in only X hours! " could have been "I found an open source solution that did what I needed with X minutes of web search." Which doesn't mean that the LLM definitely couldn't have accomplished it without the prior art (in either the training set or explicitly in a a web search). But it does seem to be a trend.
Re: Everything I own, owned
#324> I haven’t actually been brave enough to write a modified firmware to the thing yet - it’s a pretty expensive monitor - but I’ll get there at some point. Honestly if you don't have working patches, it's really not owned. I would love to get a better understanding of how to safely iteratively patch firmware. I bricked a router last week trying to add a TFTP boot path to the boot partition. It just sucks that it's so…
If you're prepared to get out a soldering iron and/or chip-clip, you can usually back up and restore whatever IC stores the firmware you're modifying, giving you a recovery path. > we also need good glitching tools There are a lot already, what do you feel is missing?
Re: Everything I own, owned
#325Earlier quoted context omitted.
The teardown showed this is the 1% right? Also I thought you could trust iMessage if, unlike everyone, you disabled iCloud backup (and, unlike everyone, so did the recipient). Perhaps a way for the feds to be able to pin dumb criminals while giving investigative journalists & dissidents a way to stay safer.
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…
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 around PFS and access older messages, one needs to get their hand on a backup, which needs fully enrolling a device, not just messaging key exchange hackery.
And as far as trusting Apple with key exchange, well, if you're running their OS and hardware, I suppose that trust of key exchange is the least of your concern (or part of the whole deal anyway depending on how you look at it)
Re: Everything I own, owned
#326Wait,what? Claude let you do this, but if I want to debug my own Python code it refuses because "cybersecurity"? WTF Anthropic? Is the trick not using Python?
You can request for Cyber Verification Program (CVP) access from Anthropic
Re: Everything I own, owned
#327Earlier quoted context omitted.
I find whenever I do this I run into the bullshit cyber guardrails. What model are you using and how are you prompting it?
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.
Ah, there's the rub.
Re: Everything I own, owned
#328Earlier quoted context omitted.
ch341a programmer with a clip attachment. That's basically it. A 10 USD investment. No soldering unless flash chip is SMD.
Please make sure you fix the 3.3 V output if you get that device. Most revisions have a PCB layout issue that will output 5V even in 3.3 V, which has bricked stuff before. There are many ways to fix it, one trace cut and one jumper is how I did it. https://libreboot.org/docs/install/spi.html#do-not-buy-ch341...
Re: Everything I own, owned
#329Vendor is PetKit btw.
Re: Everything I own, owned
#330I 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…
That you verified? Seems like 1/3 times when a model says things like this it is way off.