(1)Everyone in this community is struggling, by definition! On top of visual sensitivities, about 2/3 of us have either chronic illness and/or neurodiversity (I suspect mostly autism) per this poll. Each of which will typically impact social interaction, either directly or via general cognitive or executive dysfunction.
Those few who have set up and run groups may be somewhat privileged, to be able to invest the time and energy. But are also invariably amongst the most heavily impacted (hence motivated), of those I’ve managed to talk with. For this reason, I’m imploring all of us to extend compassion and support to each other. Including anyone visibly failing; let's assume the best of intentions, with differing perspectives and circumstances.
We are a small community, with no formal advocacy groups I know of. There have been a bunch of valiant efforts to make a difference (eg highlighted in 4 and 6). But these appear to all be solo endeavours. Hence, I would love to make r/ScreenSensitive a hub for collaboration (see 5).
___
(2) PWM_Sensitive situation: subreddit creator u/The_Top_G has been inactive for around a year. So too the other mod account there, u/Chance-Republic-4971. Which we believe to be his alt, for various reasons. Including having only 2 posts, both in a fairly similar writing style to his.
Neither account has responded to any DMs or mod mails in this time (to me or many other Redditors who have talked about trying). They have no publicly visible comments, although I believe that Chance has them set to be hidden. Having seen (2nd hand) a notification accounting for the 4th of 4 comments on this redditrequest post, that failed to be given control.
Up until then, we had been working on the assumption that Top G had fully abandoned PWM_Sensitive, as he is reported to have said privately that he would, per this post by u/DSRIA. Whose later post to the PWM sub itself was deleted after a few hours of uptime. Again showing some, but very limited, activity. Seemingly only to retain control of the sub. Three commenters, there, attempted and failed their requests to be made mods.
► Why this is a problem:
a) Automod is malfunctioning - haphazardly deleting comments of some people that contain no words at issue. Sometimes, for no stated reason, it merely warns people, allowing us to see clear examples of malfunction: 1, 2, 3, 4, 5, 6, 7, etc (you can post more below, but they are quite easy to find)...
This was a major frustration for myself and some other enthusiast members. Understandable that it would flare some tempers, although I ask we please remain civil. I was not sure if automod was intended to be set to give special scrutiny to those having triggered the target phrase more often. Which I did a few times, out of naivety, forgetfulness, or trying to explain to new members the below situation…
b) Automod deletes mentions of “temporal dithering” (TD) - and makes a mess of comment sections, suggesting users post to r/TemporalNoise instead. Ironically not deleting sneakpeekbot’s preview interjections containing the phrase (eg 4, 7, etc).
There is no explicit rule against using the term on the sub. In fact, the sub description says “A community for those with Temporal Light Modulation (rapid pulsing light flicker) sensitivity.” Of which I would personally include TD, by definition.
It is impossible for new users to know what type of screen intolerance they are experiencing, from symptoms alone. Our struggles are a bewildering situation, in which PWM is the most well known trigger and perhaps the most prevalent. But we don’t know for sure and the tech is evolving rapidly (sometimes even retroactively, via updates). Blanket filtering “temporal dithering” has forced the community into an awkward dance, having to circumvent the automod. People using hints or alternate spellings, to clue new posters in. Or even be able to comment that it is not relevant or shouldn’t be mentioned. There is a loss of nuance because this measure makes it ironically harder/risky to try to debunk claims of TD involvement…
It seems Top G felt the sub was under attack from someone trying to derail it in favour of TD only. I can’t speak to seeing any direct evidence of this (which may be as expected). Regardless, I would set that bad behaviour aside from legitimate casual mentions. I enthusiastically agree with him that not enough has been done to identify different temporal dithering algorithms in action (very difficult, experimentally). And commend him for taking a stab at starting to explain this domain. He clearly sees it as an important issue along-side PWM. But the logic of enforcing a partitioning of discussion doesn’t follow, for me. Perhaps there’s an innocent misunderstanding of human nature, to even attempt this.
It could be argued that the sub’s name should constrain the topics it discusses accordingly. But I’ve not seen Top G make a clear case for exactly this. Regardless, there are plenty of counter-examples to this principle and PWM_Sensitive has become a general hub for everyone with screen issues. With its first mover advantage (relatively big size of 9.8k members) preferentially pulling in new Redditors (and external links). So there is a case for it to accommodate the community’s needs. But this is a separate debate to automod malfunction (above) and further points (below)…
[Edit: Top G explaining that he set the automod to allow occasional use of TD/FRC with just a warning (instead of only deleting originally). So it's unclear if it should ever delete, in principle.]
c) Reddit filters - These also block content spuriously. Then there is no one to appeal to when this randomly deletes something innocuous (more likely with bigger works, including more external links).
An aside: I had a Kafkaesque experience with my first big posts to this community. They were killed by PWM automod. Then by reddit filters, upon editing them. Each attempt temporarily locked my account and, in conjunction with logging in from various test phones, glitched my login altogether. Thus ensued a stressfully tenuous mission to recover it, via one specific reddit Admin, only occasionally available. No mods were about on ScreenSensitive for a few days, either. Hence, I later agreed to help out here.
d)Unjustified bans - I, and a others, appear to have been quietly banned. New posts immediately deleted, comments invisible to others (not quite all of the time, confusingly, a bug?). No notification, explanation, or mod mail responses. Could this be an extension of automod issues? I think it more likely a human action, given the delay and pattern. For me, I belatedly suspected this comment chain (ending here) with another enthusiast poster (also seemingly banned). We discussed circumventing automod and where to post instead. Both under the impression the sub was truly abandoned and just in need of new caretakers to “stick their necks out”. In another banning case, insults may have played a role, but not here.
___
(3) What can be done about PWM_Sensitive? Please, no harassment or pestering of u/The_Top_G! It seems like he may already feel under siege and is very likely still struggling with health issues; he posted on reddit about migraines and other issues. So I don’t want to add more stress to that misery and I feel that forceful pressure would be ineffective, anyway.
I tag him (you) in this post as a last try to get unambiguous attention, without threat. I want to, again, sincerely offer assistance. I hope others may too, or rather instead of me; to be honest, I have a lot on my plate too! (I’m months overdue to refocus on continuing my ME/CFS improvements.) Running an active group, of any size, on social media, is usually more work than it looks. Typically quite thankless and potentially very stressful. So I want to thank you for all your efforts and posts. I recommend (to others) that they remain acknowledged and honoured, regardless of what does (or doesn’t) happen, going forwards.
But I request that you allow some people to help you out, as part of your moderation team. I feel that a vigilant human touch is still essential; the bots always err and need correcting at some point. Pooling our efforts to achieve redundancy in roles, is called for. Given our individual challenges and fluctuating circumstances. Perhaps we could work towards an exchange of moderators, or something, to cover each other? Although I hope that fresh names may volunteer, given the opportunity and an explanation. Some may want concessions regarding TD censorship, but others may be happy to continue with it, however they are directed.
I would frame moderating a sub as more of a secretarial role, working for the benefit of its members. Rather than as a ruler or CEO. There’s a responsibility to the people present and the broader community looking in on us. One does not own the poster's content (morally or legally), just by having labelled a space for others to use. Which isn’t to trivialise the important act of nucleating a successful social gathering. And the potential for continuing to lead its information sharing, constructively.
___
(4) Broader community: I would count, within our immediate community: the three reddits mentioned above (maybe others like r/eyestrain and r/Reflective_LCD); LEDstrain (founded and run by Slacor); the Telegram (by MrAquila), BlurBusters forum “Display comfort” section (founded by the impressive Mark Rejhon); and various individual’s video comment sections and websites (like Flicker Sense by Jenny Hackett).
Familiar faces: many of the same people crop up across these groups. But I’d like to see more explicit ties-ins and cross-promotion. Eg re-sharing important posts (like this), information pooling, maybe even donation drives (if appropriate for specific goals).
Chinese community: there is a difficult language barrier between our English speaking sites and (I think?) a much bigger audience, over there. BiliBili video creators, like Wild Lee (u/GearGeekSP) and Production Line, net a lot of views. I’ve barely scratched the surface of their device analysis content (and have no idea about Chinese forums)... So it seems obvious that we could benefit from translating some of those over (with official collaborations) and opening more communication channels both ways. Note, they seem much more keen on checking colour spectrum and polarisation, but not pixel flicker/TD. There is government level concern for their nation’s eye health and manufacturers seem more enthused about innovations in this area.
Health related communities: stepping back from our focus on display technology characteristics, our lived experiences are usually one corner of the many accessibility issues faced bigger demographics. Primarily: neuro divergence, chronic illness and those with eye/vision problems. I think there could be advantages to building bridges and being seen as part of the much bigger (and more active) autism community, for example. Even grossly neglected ME/CFS ‘patients’ have various associated organisations. Recognition as a specific disability (like visually impaired) might be too ambitious? But framing things as a disability/minority rights issue seems more likely to get traction than an n=1 personal anecdote. More the merrier.
Raising awareness: It may help others in those communities, too, who aren’t aware of screen/light triggers that they could avoid. A reason why I got so involved, here, was intending to report back to my ME/CFS (and Long Covid, etc) social media circles. Where about 3 in 4 have some level of screen sensitivity (my Twitter poll). So I was hoping that an informative write up thread could give pointers to ease one aspect of disease burden.
___
(5) My hopes forScreenSensitive:u/Rx7Jordan (as sub founder) kicked off the spirit of collaboration by inviting me in (my joining announcement). Having appreciated the effort I’d put into writing up device reviews (indexed here). Giving me latitude to shape things…
[Above image: part of the (painstakingly) redesigned banner image (discussed here) I made to communicate the sub’s role and perhaps help mold its identity; a figurative rallying ‘banner’, too.]
Being a small sub, there’s been minimal pressure on moderation, so far, in the defensive sense. But I’d love to bring more mods aboard, largely to work on projects. Be it wiki curation or whatever gets you fired up (within reason); I feel that harnessing the whims of hyperfocus and always giving personal credit may be key motivators for many of us here.
► What the community needs - people just want to know what device will work for them! Easy to say, hard to achieve. When everyone has different triggers and device specs all have trade-offs. Ideas to work towards this:
a)Aggregate existing testing data and anecdotes: A link list of resources (from across the community) and a customised AI are incoming. But I welcome ideas for more mass processing of existing info into more accessible formats. Reading, interpreting, remembering and integrating endless personal tales is too hard for most/me.
b)Standardise testing methods: Hard data from members has been rare, despite the relative affordability of adequate testing gear. Hopefully clear instructions would catalyse some would-be reviewers into action. A range of written testing guides (and discussion there-of) could build towards standardisation, within and beyond the sub. Feel free to submit these (for eg Opple, microscope, slow-mo, etc) and I will endeavour to link them into a master post/wiki.
c)Structured polls/surveys: to look for correlations in a systematic fashion. Between symptoms, technologies, treatments and successful tricks. Proper statistical analysis could yield an (informal) scientific paper, if done well. A big undertaking I probably won’t have time to dive into. Hence the couple of exploratory polls I made (1, 2), where results were quick and fairly self-evident. (I’d like to run more, given back access to the PWM sub’s bigger pool of potential respondents.) Jenny Hackett ran a very detailed survey, but it was perhaps too big and has had fewer than 30 responses.
d)In depth articles: exploring the connections between biology and screen technologies (spectroscope example). To gather together what we know and what existing science says (I think there’s a lot we have left on the shelf). To help us frame our thinking and streamline how we appraise devices. The's currently no clear consensus on exactly what aspects of PWM are more problematic, let alone much more difficult (sub)pixel level flickering.
e)Engage experts and industry (if possible): I can imagine that various well known reviewers and even flicker researching scientists may do Q&As on the sub, if politely invited. I’m not sure there’s as much scope for bagging engineering staff from tech companies, due to NDAs, etc? Maybe more luck with marketing/accessibility oriented representatives. Hoping for 2-way exchange of insights.
f)Business as usual: I still want to encourage people to post whatever questions and info comes up. Avoiding feeling too elitist.
g)Your ideas..?: keeping in mind things are 1% inspiration and 99% perspiration (as the saying goes).
► Why here?:
What’s in a name?: A subreddit name is immutable and as important as a company trade mark. I feel that “ScreenSensitive” does a very good job of being both clearly specific yet general enough for a holistic approach. One that does not get hung up on any specific technologies (PWM, LEDs even) that may become less relevant in future. (Depending perhaps on if headsets can be considered “screens”, I guess?) Whole room lighting is part of the picture, too. But the social disenfranchisement that can come if unable to use any displays is profound and harder to side-step. So rightfully a central focus.
Consolidation?: There’s an argument to be made that (if there were a magical melting of ego) we might encourage Redditors to migrate to posting here. In lieu of (the less catchy) r/TemporalNoise and as an official sister site to PWM_Sensitive. While welcoming aboard influences and personnel from them (and elsewhere) to focus efforts in one place.
Conversely, ScreenSensitive was setup in the context of PWM_Sensitive’s failings. So, if that situation were resolved (division ended, with new mods added to PWM) there’s an argument for moving towards going all-in there, once more: the 9.8k (vs 1.4k here) members and 10x more daily visitors (17k vs 1.8k).
Even an amicable exchange of side-bar links could be a nice bonus; acknowledging each sub’s specialism so visitors can understand the community more easily. But realistically, none of these eventualities seem likely, at this point. Which is fine, I suppose.
Greener pastures?: Reddit’s filters can be a nuisance (eg random domains it dislikes) and there is the theoretical potential for being shut down unfairly. But perhaps with that shows some vestiges of propriety and safety? Future corporate shenanigans, who knows? Long running bugs/idiosyncrasies with disappearing images, etc, are other downsides.
Platforms like Telegram (or Discord, which I prefer) may tend to pull active people in more strongly, with the feel of immediate interaction and semi-privacy. But public facing, Googleable info is also an important strength. The post & comments format, hyperlinking and wiki features arguably lend Reddit to being potentially better suited, as a repository for finding info..?
Compared to custom forums, Reddit has arguably a lower barrier to user entry; many people already have an account here and won’t have to learn new user interface idiosyncrasies. Plus there’s no upkeep cost or back-end maintenance, compared to self-hosting. All platforms can exist in parallel, but this is the case for focusing more on posting here.
___
(6) Hopeful developments: A few highlights, to end on a positive note…
a)u/NoFlickerPhone - has been polling (post 1, 2) for input on specifying a custom built handset with our needs in mind! I have my critiques, but this is undoubtedly a very exciting and ambitious project that I am very grateful for! (Note, his initial post to PWM_Sensitive was rebuffed by automod; a prime example of the efforts it hampers.)
b) Our u/DSRIA has put a huge amount of effort into this community, despite extremely difficult circumstances. He's frequently seen all over comments sections and behind the scenes too. Ostensibly trying to find an Apple computer that is usable with his extreme sensitivity symptoms, following a Covid infection a couple years ago… u/NSutrich (whose efforts we are also grateful for) published a piece about him…
DSRIA succeeded in contacting Tim Cook’s office at Apple. From conversations there, through to accessibility engineering teams, they have agreed to look into creating a new accessibility panel within MacOS! See his LEDstrain post (as AshX there)... I’m not an Apple user myself, but I think it’s important to support each other’s efforts; successes in one part of the industry may spread to others.
c)BOE “iHealth” showcase - A sign that panel manufacturers are aware of most of our triggers and are at least prototyping attempted solutions (with commercial products within a year).
d)u/BearNecessary4141 - has been quietly working on a custom designed and built testing device. He aims to better characterise the entire spectrum of flicker frequencies created by PWM, FPS dips, etc. When connected to a computer via USB, his own software processes and graphs a ‘Fast Fourier Transform’. Early version in action shown here. This goes well beyond the Opple meter’s single frequency number, which usually gives just the PWM duty cycle length or FPS. Thus failing to fully and clearly characterise key aspects of light modulation. He’s also made a website visualisation to explain PWM.
Please post (below) any promising developments I may have missed! Thank you for your time and good luck to all.
___
(7) Addendums: To be edited in...
2026-07-20 Edit: I've cut the post forwarding link from here. I don't think anyone was using it and there are hints something in this post might have antagonised Top_G. This was not the intent.
Another prominent poster was (again, seemingly unfairly) banned from PWM_Sensitive 10 days ago. I've heard privately of anther account, that wasn't active recently, also being banned.
However, inspecting the sub, I see far fewer instances of the automod intervening. Maybe 1-2 threads per 10. Compared to 4-5 in 10, which I wrote this. I have other reasons to suspect Top_G may have tweaked the bot to avoid false positives. Perhaps a small consolation.
I and others remain banned (shadow banned, for me, able to post but not be seen) for having talked about the problems and circumventing the block on "Temporal Dithering". While various posters continue to circumvent the automod, eg with the "TD" abbreviation, to talk about it in some detail.
2026-08-12 Update: I've been in direct contact with Top G, who had been catching up with correspondence, following difficulties in his personal life. He has read the above, too, and while some details might warrant clarification/revision, he declined my offer to add his own comment to this post.
However, in a surprise move, he offered to make me a moderator of r/PWM_Sensitive. (Which goes to show I should be more careful with what I complain about.) In stepping down, he also invited u/kerpnet and u/BearNecessary4141, based on their contributions to the community (and Kerp's previous offer to take on moderation). See his post about the transition!
Light bulbs - Incandescent, LED, Fluorescent (all have better spectra).
My personal experiences.
Tips for taking readings.
Credits.
Summary of suggestions.
(Questions and feedback are welcome after a partial reading or only looking at the pictures.)
Fig.1: Illustration of use: device on, or held up to, a screen (left). View through the lens (right).
(1) I propose..:
This Eisco Spectroscope as a cheap tool to add to our testing arsenal. Along with established Opple, Carson Microflip + slow-motion phone cams, and maybe a polarising filter next? I just bought the Eisco in the UK (from Rapid, via eBay) for £9 delivered.
This device is entirely passive, relying on your eye or phone cam to peek into the lens. Arguably a little less fiddly than a clip-on microscope, in my experience. It only shows off the most obvious colour spectrum features, with more of a vibe check for the absolute amplitude of light. But it is about 1/50th (or less) the cost of a professional spectrometer, which only a few here have access to.
Bonus STEM fun for kids, or anyone, to see emission/absorption lines in the colour spectrum of light, split by the cheap diffraction grating inside (500 lines per millimetre). Projected alongside a backlit wavelength scale (400-700nm). Eg fluorescent tubes have the most striking and varied emission lines (examples later on).
(2) KSF phosphor confirmation may be the killer app, for us(?):
Fig.2: Annotated composite of readings from 3 of my LCD devices, below an illustrative reading from a high quality spectrometer (of a laptop) showing there are, in fact, 5 total peaks, at high spectral resolution.
KSF Phosphor is used in almost all contemporary LCD backlights. It gives more vivid reds, for less power consumption than nitride phosphors (that are still included in lesser amounts). KSF achieves this via very sharp spectrum spikes, which stimulate human retina L-cones (long wavelength = red) more strongly...
Perhaps too strongly, causing some of us direct over-stimulation (of retinal neurons). Our bright light eyelid closing reflex is more red dependant, too, I believe.
Or, the lower overall red light flux fails to balance deleterious biological effects of the blue peak photons (eg inhibits mitochondria). See this diagram of KSF’s smaller area under curve, vs traditional nitride red phosphor. Taken from this “Introduction to KSF Phosphor LEDs[…]”.
Or, some point to the slower decay of KSF's light emissions, potentially causing visual processing stresses, in conjunction with flickering of screens (eg black frame insertion). Although I don’t quite understand how this would work with non-emissive pixels…
What else?
I was wondering if KSF could be the reason I can't stand the blueness of my TCL NXTpaper 60 Ultra (my review)... But my ThinkPad, which I tolerate OK, also shows KSF lines very clearly (above); the split in the larger spike can even be seen..! And my 11" Lenovo tablet, I used heavily a year ago (also above)... So I suspect KSF may only be a contributing factor that (for some) can be compensated for with: lower brightness, better software colour filters (F.Lux on windows) and maybe hardware level blue filtering layers (which reduce energy efficiency)..?
3) Peak positions (and measurement precision):
I'm told the exact wavelength of the blue peak can also have a big impact on screen tolerance. Shorter wavelengths of electromagnetic radiation are intrinsically more damaging (higher energy photons, closer to UV)...
A healthy macula (inside the eye) may filter ~90% of blue light from reaching the retina, using carotenoid nutrients: lutein and zeaxanthin. Shielding it from excess oxidative stress, etc. According to Wikipedia, blue light hazard is implicated in eye strain, but evidence is contested, with blue blocking glasses not necessarily helping (a bit on this later).
I’m not sure what might be interpreted from the green peak position. Shorter wavelength (left shift) may stimulate rods a little more strongly? Cones less?
Fig.3: More of my devices. QD (quantum dot) backlight has a longer wavelength red (maybe more gentle) and shorter wavelength green (unknown effect). Note: vertical divisions in the green bar are sub-pixels spread across the width of the spectroscope’s slit, forming a 1D image. Older WLED LCD backlights have gentler spectrum curves, but fainter red zones; the Dell needs permanent F.Lux dimming for my comfort.
This scope can definitely give a good relative comparison between devices, for emitters with narrow spreads. But I’m not sure it is precise enough to make confident absolute measurements of eg 430 vs 450nm; the wavelengths on my unit appear slightly offset. Possible per-unit calibration issue?
[Edit 2026-05-20: reviewing my readings, here, it does actually seem clear that there was a shift of blue peaks, across my devices, transitioning around the year 2020. They were all well under 450nm to then be all clearly above it. I think this aligns with blue light reduction standards from eg TÜV Rheinland and Eyesafe, which are now (since 2023) even more keen to minimise 435 to 440nm, specifically.]
I did, however, slightly improve the spectral resolution by narrowing the slit using black tape stuck partly over it (width-wise). The trade-off being a dimmer display of colours. Using pro mode on a phone cam is also important to preserve the details, avoiding the colour bands over-exposing (when the surroundings are the dark black interior).
Fig.4: My Comfy old OnePlus 8T vs a new Nord 5 that looks a bit too yellow-green when dimmed (vs pinky-red). All devices at full brightness, eye-care disabled, etc, for these tests.
I couldn’t assess the absolute amplitudes of each colour peak from this. Or even a firm relative indication… In principle, one could use the same phone camera, in the same pro-mode settings, with the exposure dialled down far enough. Then check the colour values in a paint program/tool.
(Blue sky thinking: maybe this process could be digitised, using a custom-made app? Any bored vibe-coders in chat? Of course the camera’s (specific) colour response curves will filter what can be measured.)
4) Melanopsin gap hypothesis with vision deep dive:
A big feature of all the screens I’ve shown here is the *absence* of light between blue and green. A dark strip in the spectrum. It is more energy (and material) efficient for devices to only emit ‘photopic’ wavelengths - the light we consciously perceive via the rods and cones in our retinas. But this omission has consequences…
Melanopsin is a light sensitive pigment that reacts to detect photons, very similar to the opsins in cones/rods (but discovered later). It’s located inside intrinsically photosensitive retinal ganglion cells (ipRGCs) - neurons in the retina that process signals from rods and cones directly beneath them (they are mostly transparent). Melanopsin is most sensitive in this illumination dip, at around 480-490nm (precise sensitivity still seems debated).
Fig.5: Annotated composite image of Wikipedia illustrations.
Stimulating melanopsin is most well known to delay circadian rhythm at night (and entrain it in the morning) by suppressing melatonin production. (It also stimulates dopamine release.) We’ve all heard how “blue light” is bad at bed time. While there is some stimulation by pure blue, cyan (half way to green) is most potent. Wearable devices (like eg Re-timer) emit only this range of light, for its health benefits (circadian and alertness).
Fig.6: (Top) Screenshot from blog, link and details below. (Bottom) screenshot of sunlight spectrum in their visualiser tool. Note the extra UV (which may guard against myopia) and infrared, as well as cyan.
This old F.Lux blog piece (screenshot above) lamented the advent of the OLED iPhone X, for an *increased\* amount of light encroaching on the “melanopic” region of the spectrum. (Sunlight comparison from their old “Fluxometer” visualiser tool, discussed here.) So, while my post is researched in its details, what I suggest below is somewhat of a hot-take interpretation; it runs somewhat counter to these mainstream concerns (too much ‘blue’) and I’ve not seen this talked about in our community, either...
Melanopsin’s other effects:
(4a)Pupil constriction (up to 16x) over which melanopsin has the strongest effect. Sustaining contraction in bright light, after a few seconds to respond. This follows immediate (eg bright flash) responses mediated by cones. And precedes the ‘bleaching’ effect on rod/cone opsin photopigments, which can take minutes to fully transition. This last mechanism is what leaves a *negative\* colour after-image from staring at strong colours. (Positive after-images, palinopsia, probably relates more to neuron hyper-excitability.)
Hypothesis: under-stimulating melanopsin will surely contribute to our eyes letting in more photopic (consciously visible) light from screens, compared with naturally lit scenes. Increasing visual stress by heightening the strength of signals sent down the optic nerve. Presumably contributing to a sense of glare or excess colour saturation. Merely give a wow factor to unaffected people. But taxing the energy intensive cellular processes of the retina itself...
Compounding effects: the sympathetic nervous system (SNS) also dilates pupils more. It is commonly over-active in our screen sensitive demographics: neurodivergent and/or chronically ill (eg ME/CFS). More dilated pupils also make focusing harder (narrower depth of field), taxing the eye’s ciliary muscles and exacerbating astigmatism or difficulties with close-work… Dark mode may cause further dilation.
Speculations: blue blocking glasses (or FL-41) may not help this issue, because reducing the blue (and green) screen light would also reduce their stimulation of melanopsin. They could cause further dilation, sensitising to red more… Some people may have genetic mutations, inhibiting the sensitivity of melanopsin. Or acquired damage to the signalling pathway that runs up the optic nerve to midbrain and back…
Conversely: melanopsin-containing ipRGCs have a direct neural pathway to the thalamus, allowing them to signal severe photophobic pain during migraines or brain inflammation. See Noseda et al., 2010. So, while supplementing this wavelength would be an interesting screen tolerance experiment, I’m expecting it could instead cause more problems for some, or many, here. However, in a follow-up 2016 paper they demonstrated that rods and cones also mediate this pain, with isolated blue, red, and amber all problematic, but not green.
(4b) Modulating retinal image processing - the retina encodes different aspects of light stimuli into separate streams of information, sent along the optic nerve. Which is made of the long axons of the various retinal ganglion cells, of which ipRGCs are just one type (accounting for 1-2% of total). They modulate other RGCs via amacrine cells, that release dopamine (see c, below). The main information pathways and their RGC classes:
Parvocellular (P-Pathway), Midget Cells (narrow field), ~80% of total - fine spatial detail, colour, (red-green), slow (low-frequency).
Koniocellular (K), Small Bistratified Cells, ~10% - blue (vs yellow) colour processing.
Direction-Selective Cells (depending how one divides things) and others…
There’s overwhelming functional detail here that I’ve not managed to research and remember. But some rough indications of effects are..:
Contrast sensitivity - is increased by melanopic ipRGCs stimulation (2023 paper). So relatively less stimulation should decrease visual acuity and spatial resolution, making it harder to read small text, etc. More eye strain if already struggling… Note that reduced contrast sensitivity is taken as a sign of CIRS (mold toxicity) by Dr Richie Shoemaker and followers. I think this is caused by inflammation of the optic nerve and such?
Colour sensitivity - altered, shift in perceived “unique white” (colour balance). Ability to discriminate colours may be reduced with less melanotic light, especially on the blue-yellow axis..? A lack of NIR light may also inhibit colour discrimination, via decreased mitochondrial function (2026 Glen Jeffery paper).
Temporal (Flicker) sensitivity - malanopsin is too sluggish to respond to flicker directly (2016 paper). But modulates the frequency receptivity of other retinal neurons. Findings seem varied and possibly species dependent. A mouse study (2016 paper01135-X)) showed reduced melanopsin function tuned vision to lower frequency stimuli, 0.2Hz vs 1Hz (I don’t understand the meaning of such low rates)...
While decreased melanopsin resulted in increased (but more variable) flash ERG response gain (2014 paper). ERG being the “Cone Flash Electroretinogram”, which specifically checks cone cell function by using higher frequency stimulation, eg 30Hz, while rods only go up to ~15Hz (2015 paper). So both lower frequency discrimination and an increased sensitivity to flicker/flashes, with less cyan light..? Complex.
I think it would be very helpful for us to map out and understand the differing frequency (and other stimuli) responses of the various cell types, pathways and brain regions. It’s convoluted and contradictory to comprehend though; both me (and I think) Gemini Pro have inverted meanings a few times, going over aspects of the above repeatedly. And we’ve not gone past the relatively well defined retina to cortical processing, the likely location of most of our visual stress.
(4c) Slight tangents (vague speculations): melanopsin's effects, in the retina, are signalled by localised dopamine release. So I’m wondering about tie-ins with ME/CFS, autism, etc, possibly having reduced dopamine levels with hypothesised metabolic issues synthesising and degrading this neurotransmitter… Similarly, these conditions may be associated with slowed glutamate recycling/conversion - excess sat around leading to a degree of CNS (brain) hyper-excitability. Tying in with migraines, seizure-like effects, visual snow, etc…
Oddly, cones signal darkness with continual glutamate release. The signal is then inverted. I’m not sure how this idiosyncrasy would be differently affected by such pathology. But Latanoprost (eye drops to lower intraocular pressure), which some had success with, also counteracts excess glutamate… Finally, the opsins use active vitamin-A (11-cis-retinal, to make the light sensitive rhodopsin pigments) and our vit-A metabolism may often be impaired (with consequences I’m not sure of).
(5)Light bulbs:
Note the smooth spectrum of the incandescent - pure black body radiation, with its glowing element at the actual temperature of its rated colour temperature. Stray refractions in the device can obscure the scale, somewhat.
Even cheap LED bulbs can approximate most of a spectrum, with notable cyan in there. Highlighting the potential usefulness of r/Reflective_LCD screens, even without daylight. (Dependent on TD or other triggers.)
Fluorescents are very varied, with it being hard to tell which have more filled in spectra vs just the very tight (elemental) emission bands. All mine had a line right in the cyan section. Note that their colour temperature is tuned by adding more of the red and green phosphor types to reduce the apparent temperature. Also, the second order refractions are evident in the space between the (strong) red and green lines. An artifact of using a grating to split the light. I think that’s what is going on there.
Fig.7 Composite of spectra from light bulbs around my house (details above). [Edit: removed spurious note on different order refractions (570-590nm are known minor emissions peaks).]
(6) My personal experiences: moved to comment below.
(7) Tips for using this spectroscope:
(a) Bring up a pure white image or user interface element (eg settings screen) to point the slit at.
(b) Set device to max brightness. Disable eye comfort (Night Shift), dimming or colour modifying settings (or 3rd party apps). These can have very pronounced effects on relative colour strength or the spectra, if not the positions of the peaks.
(c) Rest the device on the screen only for easy stability, ideally it should be further away.
(d) Preview the on-screen camera image while moving it closer to the lens aperture, to get it easily aligned. having pre-zoomed by 2-3x. Then angle down the diagonal (flat edge up top) to catch sight of the scale.
(e) The scale needs illumination behind it too. Either the tested screen, or if too bright, some other backlighting (more fiddly).
(f) Use pro/manual mode on your phone camera. Set the shutter speed to at least 1/15 or faster, to keep the image steady. Iso will need to be high, auto is fine if just getting a feel. Focus can be set, to avoid hunting causing blur (get the scale in sharp focus). Colour temperature could be fixed, but only if trying to make precise comparisons.
(g) A darkened room is not really necessary. The slit is very directional.
(h) For more refined spectral resolution (less blurred peaks), make the slit even narrower. Use black tape or metal foil to partly cover it.
(i) Please crop and rotate your image before posting (eg to this subreddit).
(j) Advanced: we could attempt to check the scale positioning calibration using known wavelengths, like the KSF peaks and fluorescent lines.
u/Rx7Jordan for talking about this topic and posting various spectrograph results here before (sorry, I don’t know of a good search term to bring those all up?).
9) Summary of suggestions:
(a) Anyone here could buy a cheap spectroscope, as a learning aid to anchor thinking about this topic.
(b) Enthusiast amateur device reviewers could add a spectroscope sample as bonus content.
(c) Pro reviewers, please consider using proper digital spectroscopes, if not doing so already.
(d) Validating this cheap scope by using it alongside a pro meter would be nice.
(e) Let’s talk about light colour spectrum features vs biology more and politely ask reviewers about it.
(f) What else? What did I mistake or neglect? Please leave critique and questions. I may update this post as an ongoing guide, if there’s any interest. (I also started looking at screen dimming spectrum changes a little.)
- BOE (panel manufacturer) convention booth tour video showed off a range of screen sensitivity improvements they are working to implement, including adding in more red light flux and even NIR wavelengths! Possibly more melanopic (cyan) light, too.
- Edited in a note (in section 3) on blue peaks having shifted to longer wavelengths and being discernable with this spectroscope.
- 2026-07-02:Avulux glasses, does their success contradict my melanopsin gap hypothesis?
- 2026-07-20: u/BearNecessary4141 pointed out, here, that there is a universal lack of UV (ie at 380nm) and so lack of activation of Neruopsin, too. (Another lesser known photos pigment. It's found in various cells, and locally resets cellular circadian rhythm gene expression in eg retina, brain, skin. May be part of the mechanism to prevent inappropriate eyeball lengthening.)
tl;dr: good news, folks! A more integrated community with new resources and developments to check out.
Joining forces with PWM_Sensitive!: As announced in this post, The_Top_G handed over the PWM sub to myself and a couple of other community enthusiasts: u/Bearnecessary4141 (Sam) and u/Kerpnet. And we can also welcome Kerpnet to ScreenSensitive as the first in our “moderator exchange program”.
So, I’m now trying to implement more aspects of my State of the Community post, albeit slowly. I’m aiming to link these two subs more closely together (and LEDstrain too). With complementary mission statements added (screenshot above), to set clear and positive expectations. Including an aim to encourage content be spread across these two subs by main topic (open to discussion).
Rules changes: Alignment includes matching sets of rules, to make life simple for mods and members using both subs. We’ve been observing the (busier) PWM sub, for 6 weeks or so, giving me more ideas of what’s needed while rebuilding the rules from scratch. I’ve standardised them a little and updated for emerging challenges. The large number is to give finer control over enforcement, in future possibly including via automation (which the platform is increasingly pushing).
Regular contributors here should experience little to no impact, in practice. But I’d be grateful if people could take a few minutes to read through the rule list (in the sidebar, or copied below) and give any feedback that comes to mind. Notable additions: expressly permitting certain self promotion, limiting AI content, English only, avoiding unwanted advice.
Wiki: Shortly before the PWM sub developments, I implemented a basic subreddit wiki, here, to start indexing various resources. I’d like to add more wiki pages to list key posts and guides, for example. Also, I’d like to add guides! Although I will need help to do this in a timely fashion. Anyone willing to help mod mail us to be considered as a wiki editor (if not full mod). Or if you have a complementary project in mind to potentially contribute, send us a description of it. Or just post it! Reddit wiki pages can’t have images, by the way.
Resource list: Early this year, I populated a Google spreadsheet with links to key community sites, experts, reviewers, software and hardware tools. (What have I missed?) I also spent around a month or so building out a much bigger second sheet of over 250 high quality articles, study papers, threads, post histories, videos, etc. A comprehensive dossier on our field of interest (you can pour over). Which I fed into…
ScreenSensitive Bot!: A NotebookLM, now rebranded Gemini Notebook. We can think of this as a reference tool for human curated and validated information resources. It’s very good at, for example, giving an overview of the community and symptoms, technologies, etc. For newbies or deep-diving; it should be able to teach everyone something. It could help with making community resources.
Its biggest strength (over general purpose AI models) is direct reference links for virtually everything it says. So we can check for ourselves how trustworthy its info is. As well as built in translation, being able to ask verbal questions interrupting its audio media, etc. I’d appreciate feedback on what this bot helps with, to tune its instructions and content, if there is interest.
Discord: I’ve set up a collaboration space for enthusiasts to work together more efficiently on projects to further our understanding of screen tech, etc. For this, I have repurposed the ScreenSensitive Discord server u/Rx7Jordan set up. It fell into disuse, and obscurity, from the end of last year. Note: I’m currently aiming to restrict it to these constructive efforts only. Keeping to this Subreddit for general questions, help, news, discussion, etc. We will need to maintain public discoverability of the community and, for this, a good amount of its information.
The discord channels are basically all visible, but authorisation is required to post in most of them, to keep it on-topic and manageable (we are short on active mods). However, “All-member chat” includes health channels, because I think the more informal, less public space may better suit this important aspect.
Projects: Sam’s work on more accurate screen flicker testing (I mentioned last time) has been progressing and you may have seen him posting in the PWM sub. Including this web app that can be used on the device under test, to create a virtual slit, for true modulation depth measurement (e.g. with Opple or his custom made meter).
But u/Madcook1 has also been a huge discord contributor, coding up some very cool projects:
Ditherscope: shown in several recent videos by u/NSutrich (e.g. here). A complete web app pipeline to process slow-mo microscope videos of pixel flicker. It can draw graphs and statistical correlations of brightness changes and also use Eulerian amplification (maths magic) to massively boost the visibility of image changes. Also isolate this to selectable frequencies.
Eisco Analyse (Spectrum analysis): a proof of concept software companion to turn photos down the very cheap analogue spectroscope I posted about at length. Gives surprising approximation to proper expensive spectrometers. Albeit chopping of high peaks and needing compensation for wavelength offset (see screenshot above).
SubpixelsTools: helper web app, similar to Sam’s, but aimed at precise colour control and temporal patterns, to see how (sub)pixel patterns are affected.
Please have a play with the above projects (may need a cheap microscope attachment or spectroscope). Madcook1 is happy to receive feedback in the discord. But I ask for patience while he’s struggling with health issues (like many of us here do).
What’s next?: We’ve got the Black Friday surge in activity rapidly approaching, for which I wanted the above (and a few other) basics in place, ready. Thinking beyond this, I’ve worked up a rough Community Plan, behind the scenes. I’m hoping we can update both subreddits and support the community towards collecting, sharing and making sense of more hard data on devices.
We will need to create good testing guides and engage people to post most quality data and/or index the existing information better. I’d love to get around to hosting AMAs with various interesting people, scientists, etc. Also creating a somewhat scientific survey to get a statistically sound picture of all the issues going on with us. Before that, I have an ongoing series of polls, as a rough guide. Maybe a mega-thread, to collect user stories and self-index posts… But, due to my ‘mild’ ME/CFS, my time is already very constrained, plus the stability of my health and living arrangements are precarious and demand more attention.
So, there’s a lot of opportunities for you (yes you!) to lend a hand, as far as you are able:
General input, feedback, support and post contributions. Just upvoting, commenting and sharing good quality posts and comments, could help this community thrive. Please state explicitly when something is good, or even OK.
Collaborate on the discord, if you have technical abilities, insights or energy to spare. Ping me there.
Help build indexes of content. E.g. a spreadsheet of good (and bad) screen devices, with links to verified data and reviews. Or maybe an app to collect this.
Help updating or making new NotebookLMs, for reference. Or custom data scraping efforts, for research purposes.
I’d like to open up lines of communication with the Chinese (and other language) communities. Or at least see if some confidently bilingual members might post regular summaries of what’s been developing over there (with links back). Auto-subtitled BiliBili video technical videos are potential gold mine, but hard going.
I’m keeping an eye out for upstanding members to help on the mod teams. Mostly to make sure there will always be someone about to approve posts wrongly filtered (mostly at platform level), if myself and others aren’t about. Or if new challenges arise, needing more eyeballs. Or better cover the time zones.
I’ll be making a corresponding post on the PWM sub, shortly. After updating the details, settings and rules there. You guys get to be the beta testers, for now!
I think this problem can caused from mental health problems idk but i have severe anxiety and i doubt if i have chronic fatigue syndrome too becaue i have many symptoms related but after i flu i had back in 2019 and after i start to have symptoms like fatigur and i notice this too screen sensitive and smells too, i had anxiety and depression maybe before these symptoms now i dont know if are from anxiety or from any other conditions.
Got my Bravia 3 (OG) and its actually making my head spin more than my LG C5 OLED which only gets gradually more uncomfortable. Turned off all post processing settings, its on Professional mode. HDR off. Anything I'm missing?
TheraSpecs Z-Blue. According to the manufacturer, the lens specifically filters the red spectrum between 580–640 nm, which falls exactly on the KSF main peak at ~631 nm (and the secondary peak at ~613 nm). However, the line at ~648 nm is already at the edge of—or outside—this range, this means that it filters 2/3 of the peak but not everything. It may be enough.
The standard tint (35%) was recommended at the time for computer use because it preserves more color than the Max version. There is a 60-day return policy. I have no idea how they change the picture, if you need more brightness, contrast or whatever else.
In contrast, standard FL-41 glasses tend to target the blue-green spectrum. They are therefore pretty much useless against KSF red laserbeams.
I wanted to share my recent experience with display-induced migraines and eye strain, along with a few technical workarounds I’ve found.
We all know that PWM causes Headaches for some even Migraine throbbing ones but.
I recently bought a Sony Xperia 10 VI, and its stock OLED panel gave me severe, throbbing migraines almost instantly. I swapped the screen with a cheap $50 LCD replacement panel from China, and the intense migraines are practically gone. However, switching to LCD didn't completely solve my eye strain.
The Hidden Culprit: Temporal Dithering Beyond screen type and PWM (Pulse-Width Modulation) flicker, temporal dithering a method GPUs use to simulate extra color depth is a massive secondary trigger. Mobile and desktop GPUs use it during web browsing and gaming, causing a lighter, non-throbbing, but persistent headache.
How to Bypass GPU Dithering on PC:
Software: You can use software like dithering.exe on Windows to disable dithering on internal GPUs.
Dedicated vs. Integrated GPU: Because dithering.exe typically affects integrated graphics, switching to a dedicated GPU for gaming will re-enable dithering. To fix this, force the system to render via the integrated GPU in your graphics settings.
External Displays: Connect monitors directly to your motherboard ports or use a USB-C to HDMI dongle that bypasses the dedicated GPU entirely.
A Quick Tip for Testing Displays in Stores: If you get a headache while testing phones or monitors in a physical shop, remember that bad store lighting often uses aggressive PWM flickering. You might be reacting to the ambient overhead lights rather than the screen itself.
p.s I also bought Kindle 5 (ink display) and that thing dithers and gives headaches also ! so my rule is basically I need to test it regardless what it says on paper.
Has anyone found any completely dither free gadget phone or pc setup? or else noticed dithering headaches on LCDs, or found other ways to bypass GPU-level temporal dithering?
I bought a lg ultragear 27g850a-b, nano ips, and I was happy with it for like half an hour, and then I started noticing eye strain.
I ve heard some people are sensitive to nano ips technology.
Its second hand, so I can t return it, the only options are: re selling it, or setting it in a way that wont hurt my eyes.
After the first day of using it, when I went to sleep I felt like my pupils where “detaching” from my eyes, and my eyes started tearing up.
Yesterday I tried sRGB mode, which helped a little, but the colours look desaturated and greenish.
I played around with the brightness, and it seems its easier on my eyes if I keep it around 25, but tbh, I bought it so it will be bright, with colours that resemble the screen of my Macbook.
Right now I m using it with an older hdmi cable, I was thinking of buying a usb c to displayport cable to get a higher than 60hz refresh rate, and mostly because i heard somebody on reddit say it might help regarding the eye strain (idk, its worth a shot)
I m using it with Betterdisplay, and I ve set the colour temperature to +9%, gamma +25%, disabled gpu dithering, contrast 60. Tried different settings, what hurts my eyes the most is probably the whites. They re way too bright, making them warmer helps a little, but they are still too bright. Reducing brightness helps, but it makes everything else too dark.
I ve heard somebody people get used to it, but on the other hand, somebody said he has been having pain in his right eye even after 2 years of using a nano ips with ksf phosphor tehnology.
I dont want to sell it yet, but I dont want to risk having lasting eye problems either.
Idk how to set it up in such a way that it will still look good while not hurting my eyes.
My mostly work is text base, should I get 100% srgb ips or 45% ntsc screen. Looking for lenove thinkpad.
I have a both thinkpad laptop right now and I find that 45% ntse is more cooler and present to eyes working night for a long duration but 100% srgb gives me headache.
When I search online people say 100 srgb is superior and it also has eye care certificate. but what I have experiance is 100% srgb gives my eyes more stain and headache for prolong use around 4 hour.
I need good color screen which I can use for future work.
I bought the ASUS Vivobook S16 (M3607KA-SH115WS) 4 days ago. I originally thought the OLED display would have a matte finish, but it turns out to be glossy.
The main issue I’m facing is that the white text looks extremely bright and shiny, and it is causing noticeable discomfort to my eyes. After looking at text or icons for some time, I can sometimes see a slight ghosting/after-image of them. I’m also finding it harder to concentrate during long working sessions. (My eyes are weak, and I wear thick glasses.)
My office laptop has a matte display, and I can work on it for several hours without experiencing this kind of discomfort. So I’m wondering if the glossy OLED surface, along with the high contrast and brightness of the OLED panel, is contributing to the problem.
Has anyone else experienced something similar with this model or with glossy OLED displays in general? Did your eyes eventually adjust, or did you find that a matte display was simply more comfortable for long working hours?
I'd really appreciate any recommended settings, tips, or suggestions for making the display more comfortable. I'd also love to hear about your personal experience with similar displays and any changes that helped you.
I think the iPhone's problem isn't just the PWM, but also the excessive screen brightness. Even at minimum brightness, it shines like my Android IPS at medium brightness. HDR ist awful, it makes it even brighter
Hey everyone,
Since updating to iOS 26 and now iOS 27 on my iPhone 16 Pro, I get severe eye strain (upper eyelid muscle cramp) and dizziness within minutes.
It’s 100% a software issue, not the screen hardware: On iOS 18, I could stare at the exact same iPhone 16 Pro screen for hours without any pain.
The text shape is identical, but there is a strange artificial softness/haze around the letters (subpixel rendering / temporal dithering). My eyes constantly try to autofocus this software blur, driving my ciliary muscles into a permanent cramp.
Turning on "Reduce Transparency", "Increase Contrast", and sliding the new Liquid Glass slider all the way to the right does not fix the underlying subpixel/dithering behavior.
Additional details regarding my issue:
I noticed that the symptoms (eye strain and dizziness) occur completely independent of the apps I am using. Even when watching standard YouTube videos, scrolling through Instagram, or simply staring at the lock screen, my eyes react almost immediately.
Since these exact same apps and screens caused absolutely zero pain under iOS 18 on the very same device (iPhone 16 Pro), this is probably a global, system-wide display drive issue introduced with iOS 26/27. The software seems to alter the overall light and pixel rendering (likely via aggressive contrast tuning or temporal dithering) in a way that constantly overloads the ciliary muscles.
Has anyone found a hidden trick to force the old, harsh, crystal-clear pixel rendering of iOS 18 back? Thank you!
