71
Is OLED burn-in still a problem? (lemmy.world)
submitted 8 months ago by to c/asklemmy@lemmy.world
28 comments fedilink hide all child comments
 

I'm seriously considering an MSI MAG monitor. Do I need to adjust my workflow? I do lots of desktop work on my computer and I really don't want to hide UI elements. I also do some gaming of course. I'd say it's 70% desktop work and 30% gaming (though it varies). Do any Lemmings have any experience in this matter? Thank you!

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 8 months ago (6 children)

extremely dumb question, but why aren't there screensavers that will invert the average pixel use when you're not using it, opposite of safety, definitely not for office work, but home use?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 8 months ago

    OLED monitors typically have burn-in prevention and repair features built-in. They sometimes have a mode where the brightness can fade in and out depending on their use or one where pixels are triggered on and off repeatedly to help reverse existing burn-in.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 8 months ago (3 children)

    If the screensaver is saving the information of what a pixel has been on average, there's all sorts of potential for leakage of sensitive information onto a part of the computer that shouldn't have that information.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 8 months ago (2 children)

    i mentioned that problem, definitely not for sensitive work. however, it'll at best would leak what program someone uses regular by static UI elements. give some random noise (or an aesthetic variant) and it'll be really hard to figure out what someone was doing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 8 months ago (1 child)

    definitely not for sensitive work.

    I would argue that desktop software capable of doing this (storing and using past pixel values to calculate some sort of output) violates the principle of least privilege, so that an OS that supports this kind of screensaver being possible shouldn't be used for sensitive data, even if that particular screensaver is disabled.

    Better to harden the OS so that programs (including screensavers) can't access and store the continuous screen output.

    That's one of the problems we have with Windows Recall. We don't even want the OS to have the capability, because we don't want that data being copied and processed somewhere on the machine.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 8 months ago

    I thought it'll just keep a tally of the brightness of each subpixel. not like how bright they are at each point (ie, a recording), but just store their sum and how long was it "recording" to get the average of each pixel. still has a safety concern, but it'll be hard to extract usable data, beyond which programs I'm using. make the running average for a week rather than a session, and the best you'll guess is which program I use the most.

  • permalink
  • fedilink
  • source
  • parent