Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Release: OLED Mode extension for Chrome

github.com

Post reply on HN
Print view View original

11–20 of 38 posts

Re: Release: OLED Mode extension for Chrome

#11

Post by wtcactus »

eknkc wrote: post #4
vultour wrote: post #3

From the name alone I assumed this was going to move the browser UI around to prevent burn-in. Has anyone attempted this yet? Perhaps as a native feature?

Is burn in still a thing? Early gen OLEDs had abysmal burn in and I had devices with static ui elements like status bars etched into screen in a couple of months. It feels like history now.

Yes, OLED burn in it’s still very much a thing and it didn’t improve significantly- or at all.

You can see this YouTube channel (my go to when choosing monitors) and the tests they did on that particular subject: https://youtu.be/k-NOoMklpPM

Re: Release: OLED Mode extension for Chrome

#12

Post by RestartKernel »

> This extension is a static browser-side script which leverages React's dynamic rendering and live component updating mechanisms. At runtime, it waits for the DOM to finish loading, then injects content into a dedicated element (#__oled). Using ReactDOM.createRoot, it mounts a themed layout component that wraps the core UI, enabling declarative reactivity and efficient DOM updates.

Why does a global theme need to load React? More importantly, why does a code repository contain minified, if not obfuscated, code?

https://raw.githubusercontent.com/FreelanceProgrammingServic...

Re: Release: OLED Mode extension for Chrome

#14

Post by WindowsDev »

RestartKernel wrote: post #12

> This extension is a static browser-side script which leverages React's dynamic rendering and live component updating mechanisms. At runtime, it waits for the DOM to finish loading, then injects content into a dedicated element (#__oled). Using ReactDOM.createRoot, it mounts a themed layout component that wraps the core UI, enabling declarative reactivity and efficient DOM updates. Why does a global theme need to lo…

That React stuff is for the interface. It contains transpiled "minified" code so to cut back on the file size. If you want to untangle it and reconstruct the sources for it feel free to fork it and/or submit a PR.

Re: Release: OLED Mode extension for Chrome

#16

Post by WindowsDev »

vultour wrote: post #3

From the name alone I assumed this was going to move the browser UI around to prevent burn-in. Has anyone attempted this yet? Perhaps as a native feature?

It currently does not, just handles applying a uniform black theme across all domains. Good suggestion though, I will look into implementing this today. (My idea is, to use a custom zooming offset determined by the date- applying a random zoom % between 0 and 116 while keeping font size original, not too obvious to the person but enough to shift the pixels around a bit.

Re: Release: OLED Mode extension for Chrome

#17

Post by throw60289 »

WindowsDev wrote: post #15
nyanpasu64 wrote: post #5

TBH I wonder what's going on with the hyper-generic username of "FreelanceProgrammingServices", profile picture, and the HN username of WindowsDev who has made three GitHub submissions of their own work and posted one comment.

[flagged]

Why do the JavaScript files in repo "Chrome-OLED-Mode" reference sdmextension[.]com, a known C2 server in a Chrome extension malware campaign identified by GitLab Threat Intelligence? Is this a copy of the malicious "Super dark mode" extension? (ID: nlgphodeccebbcnkgmokeegopgpnjfkc)

https://gitlab-com.gitlab.io/gl-security/security-tech-notes...

Re: Release: OLED Mode extension for Chrome

#19

Post by WindowsDev »

throw60289 wrote: post #17
WindowsDev wrote: post #15

Earlier quoted context omitted.

[flagged]

Why do the JavaScript files in repo "Chrome-OLED-Mode" reference sdmextension[.]com, a known C2 server in a Chrome extension malware campaign identified by GitLab Threat Intelligence? Is this a copy of the malicious "Super dark mode" extension? (ID: nlgphodeccebbcnkgmokeegopgpnjfkc) https://gitlab-com.gitlab.io/gl-security/security-tech-notes...

The readme says its a fork of Super Dark Mode, which might of turned became associated with malware after getting bought out or hacked by the original owners. >We assess that the threat actor acquired access to at least some of the extensions from their original developers, rather than through a compromise. The threat actor has been trojanizing extensions since at least July 2024.

But for several years it was a legit extension used by over 300,000 people and it worked beautifully. You found a reference to their old domain in their old extension which is not surprising. If you remove this reference it still works. Can you show that the reference in the code is malicious?

Re: Release: OLED Mode extension for Chrome

#20

Post by frfl »

nyanpasu64 wrote: post #5

TBH I wonder what's going on with the hyper-generic username of "FreelanceProgrammingServices", profile picture, and the HN username of WindowsDev who has made three GitHub submissions of their own work and posted one comment.

This all feels very off. Part of the readme, and I hate to say it as it's almost become a trope at this point, feels like it was AI generated.

Plus the commits are "file uploads". Plus the minified multi-MB source files.

My spidey senses are tingling.

Post reply on HN