The human lens filters most light at the peak of the given spectrum for free retinal (383nm), and so once you get to 450nm like an LED, the hazard data in the visual range is 100x less sensitive, see Fig 1 here:
It bears repeating that computer screens have <5% the hazard-weighted irradiance of a blue sky. (Can't make a direct comparison with lasers.)
Not sure the conversion to white light is correct, and it is unclear to me right now if this much retinal is available in vivo.
If you guys ever wanted to figure out your app on a smart TV (or apple TV), I know there'd be a lot of thankful people!
Also, I'd love to contribute to the ongoing dev of f.lux (I don't think I've had to pay for it?) How might I?
Huge thanks to the author from me as well!
Then you can assign it to the Accessibility Shortcut and turn it on or off by triple pressing the Menu button.
Also, you can be below threshold for circadian responses just by being very dim.
I know very little about this so I'm genuinely curious.
"15.4-inch (diagonal) LED-backlit display with IPS technology; 2880-by-1800 native resolution at 220 pixels per inch with support for millions of colours"
What possible laptop alternatives are out there that are better for eyes?
One example of this is hiking in fresh snow for hours, no sunglasses, meaning exposures well above 10,000 cd/m2 to "white light".
Computer screens are way dimmer - an hour of iPad use is .0365 J/cm^2.
http://www.nature.com/eye/journal/v30/n2/full/eye2015261a.ht... is a good summary.
For long-term exposure (AMD risk) we have very little data, so understanding the mechanisms (such as above article does) can help.
If so I would argue f.lux does a lot more. For one thing you can choose the hue it goes to, but also unlike the Windows 10 one which (AFAIK) is simply on/off, f.lux will adjust based on a schedule which means that you don't typically notice the effects (as the change happens slowly). This, combined with the ability to change damn near every parameter it uses, makes f.lux significantly better.
Edit: apparently windows does have hue adjustment and sunset/sunrise activation/deactivation available. TIL.
EDIT: HN is becoming more like Reddit every day, I see. Ridiculous. Down-voted for pointing out the existence of helpful features. EDIT: might have been my fault.
And I assume you understand that since you edited that line out.
Since our update last year (v4) f.lux stopped doing this and does a lot of other tricks to reduce impact on framerates too.
I presume that they used a laser because they anticipated that it would potentially take years to see a result from a non-coherent blue light source, far exceeding their available funding, patience, and ability to keep uncontaminated cell cultures going.
Applying a blue laser with unknown irradiance to a retinal cell line from a single human genetic source in vitro is very, very far from proving a link between blue light and diseases such as macular degeneration and RP.
All this demonstrates is that coherent blue light is capable, under certain circumstances, of interacting with retinal to produce cell damage.
Any relationship to human disease on the basis of this paper is pure speculation. Advising people to wear "blue blocker" sunglasses or avoid cellphone screens (or take Vitamin E!) is pure fantasy made up by the scientific press to sell your retinas.
Isn’t the other “sniff test” that we haven’t seen a huge increase in age related retinal diseases since the introduction of computer monitor and handheld devices?
If these sources had such a big impact, it would be obvious from incidence numbers.
I used f.lux for 2 years. I found that I would stay up way past my bedtime, glued to the computer screen, and end up with correspondingly tired & fucked up eyes.
So I got rid of f.lux, and after that, I would go to bed at a more proper time. When the screen starts irritating my eyes, it's a direct indication that it's time to close the computer and get the hell to sleep. Ever since that, my eyes have done a lot better, because I no longer push to stay up way past my bed time.
So the only solution I have figured is to be regimented about my screen time. I love working late at night and now have to tell myself to turn the work off. That kinda sucks.
Btw, It happened both with my previous laptop with LCD screens and the current LED screen.
For a few months I got hooked to Mobile gaming, and that just multiplied the problem! So I drastically cut down on my mobile time and that helps. My mobile had an LCD screen btw; so LED or LCD doesn't seem to be a factor for this particular problem.
I also found retina display helped reduce eye strain.
Thank you for reading/writing out your interpretation of the article so clearly (highlighting points others are likely to trip on not coming from a related background)
Part of my ritual of setting up a new monitor is to turn down the brightness and increase the contrast. They almost always default to very bad values. Brightness, temperature and green/blur balance are all off for an office setting.
In the worst case the backlight was capable of outputting twice as much light as I really needed.
I suspect part of it is also planned obolescence --- when the backlight is running at full brightness, its lifespan is greatly decreased. Now the aforementioned monitor is approaching 15 years of age and brightness has reached 20/100, so there's still plenty of life left in it.
I wouldn't mind having to create multiple display profiles for this, but right now, flux seems to only support non-LUT based, Matrix based calibrations and only if they have VCGT headers, and then only based on those headers.
But this seems highly problematic.
Take a look at this page here for why:
I assume you based the current mechanics of f.lux when it comes to handling color profiles based on what the quickgamma homepage says about this:
Apple has been using the LUT since many years for its operating system built in color management. In fact, Apple has registered the private ICC Profile tag video card gamma table (vcgt) with the International Color Consortium (ICC). This tag is used in a dedicated Monitor Profile and holds the gamma values, which are then loaded into the LUT by a loader program.
Hardware based Monitor Calibration Systems also use the vcgt tag, which in this case contains the correction data to achieve the monitor calibration. Because Windows did not provide a LUT loader, each calibration program had to provide its own LUT loader program. ...
Things changed when Windows 7 came along and provided its built in calibration loader, which not only loads the LUT at system start up, but also takes care of Standby and Hibernate.
As you might notice, the two stories from those pages seem to conflict?
Right now, when I use Windows to load my icc profile, I get correct colors. Same if I use the DisplayCAL profile loader.
However, if I start f.lux during the day (where f.lux shouldn't mess with the colors at all) I get semi-incorrect colors - they end up "more correct" than when I have no color profile loaded at all, but still VERY incorrect.
Is what you want more like "don't mess with the operation of color profiles when f.lux is disabled or otherwise shouldn't be adjusting the screen?"
1. Don't call me Shirley.
2. I in fact do, in a way:
>I'm not sure what the point would be for color profiles when you're explicitly opting for distorted color reproduction with f.lux.
I opt for __linear distortion__ of a non-linear function. What f.lux ought to do consists of shifting the whitepoint coordinates of the current color profile. Which has the point of only distorting colors in a way where my brain can adapt to it.
But that's not exactly what f.lux does - it already DOES try to account for color profiles, but it does so incorrectly.
I was very happy when I found f.lux. Finally something replacing my own tool I wrote for my Atari.
The main benefits with f.lux is you can easily set brightness and on/off with keys in any program or game, no need to navigate with mouse in menus.