Mine has been strictly MRU forever. When I look at this video, it does not resemble the software on my LG OLED TV at all. There must be several platforms or generations.
Whats your thoughts on this being a temporary phenom, that will last until big corp applies AI's to resist this? Reading your article I get the feeling that the only security measures that you ran up against were just the obscurity defeated by disassembly. Plenty of posts here going "enjoy it while it lasts" but since you are actually working in the security field I'm curious about what you think of bigcorp pushback against this sort of thing?
I suspect the bar will raise for some devices, but most will continue to be made cheaply and with poorly-defined requirements and threat models, and "it works" will continue be the only bar they're measured against before release.
I understand what it does, I think the alert is annoying. It takes at least five minutes and automatically runs when the monitor is off. I’ve had it for a few years and have no burn in issues despite not doing this every eight hours on command.
Agreed.. and it has an incredibly frustrating and hostile UX.
I've been sharing my screen in work in meetings and suddenly screen nagged, and then I'm struggling to find the dumb buttons under the monitor and confused which button does what to make it go away.
I would rather suffer burn in than be nagged. I've had other brand OLEDs that haven't been this annoying, so I'll never buy an Asus monitor again.
AOC/Agon OLEDs also have the annoying nag that fires repeatedly to say "Your monitor will go into pixel cleaning mode in 10/5/4/3/2/1 minutes". I still haven't figured out how to easily defer that, and it's super annoying when in the middle of a Rocket League match that the monitor just turns itself off to pixel clean for 10 minutes.
Interesting that it can’t reestablish the connection, as the application level protocol should support it just fine. The client should notice the GRE (game rules engine) TCP socket is broken, and reset everything. When you reconnect, the front door service should notify you to a GRE session still in progress, and the client should be able to rejoin that. At least, that’s how it works on desktop.
My guess is that they get the parameters for the current connection from the phone context and then use a nonstandard library to establish the connection for maybe performance reasons. But then I think they did not bother to implement a mechanism for reconnecting.
Just wanted to say thanks for nix2container. I’ve been using it to do some deploys to AWS (ECR) and my iteration time between builds is down to single digit seconds.
reply