Hacker News new | past | comments | ask | show | jobs | submit
Just fyi, Dark Reader (Firefox extension) completely broke the more interesting experiments and I had to disable it to see them. Only the 'square color gradient' experiments survived, for some reason.
The appropriate place to report this is dark reader's issue tracker.

What is a website maker to do with this info? An extension made to deface sites defaced my site? Expected behaviour.

It is a widely used plugin. By me as well. And usually allmost all sites work.

So technically the developer of dark reader is the place to go. But if I would use svader - then I would have to be prepared to loose all that audience. (or at least use a sign to warn)

So giving that feedback is still valuable.

People don't care who is to blame. They care if it is working or not. (maybe there is something simple the dev of svader can do)

It works wonderfully until it fails miserably. At least, a couple years back that was the case. Someday, my local vision model will prefecth, take screenshots to check for my desired contrast, and iterate. Then the 3-5% of sites (perceived) that ruin rule based tools like DarkReader can finally perform reliably and not ruin our sleep or give us headaches.
> widely

Bullshit.

Your overall comment might apply to a consumer facing website, but your feedback is rubbish for some developer providing a proof-of-concept. mckirk made a perfectly good "fyi" comment because it didn't pressure the dev, while giving the dev a heads up _if_ they are interested and happen to read HN.

Firefox on a laptop is now a niche browser (3.35%) and is trending to be less popular than Opera (2.86%) and Samsung Internet (2.6%). Obviously HN selects for abnormal users: I actually like mckirk's comment because it is a beautiful reminder that there are niche users with interesting configurations and maybe I should have a look at that plugin. Nobody wants to be an entitled open source user.

>> widely

>

> Bullshit.

Dark Reader has >9 million total users across browsers as reported by the Chrome, Edge, Firefox, and Mac app stores [1][2][3][4]. That is definitely a very small percentage of total web browser users - with some estimates putting chrome users at 3.2 billion(!)[5], but 9 million users isn't something to scoff at either.

FWIW - I completely agree that mckirk's comment was a great passing "fyi" that doesn't put pressure on the dev. I also think it relevant to the original post (not some tangential common complaint, nor against the HN guidelines).

[1]: https://chromewebstore.google.com/detail/dark-reader/eimadpb...

[2]: https://microsoftedge.microsoft.com/addons/detail/dark-reade...

[3]: https://addons.mozilla.org/en-US/firefox/addon/darkreader/

[4]: https://apps.apple.com/us/app/dark-reader-for-safari/id14382...

[5]: https://www.statista.com/statistics/543218/worldwide-interne...

"Your overall comment might apply to a consumer facing website"

Svader is for making consumer facing websites. At least potentially.

"mckirk made a perfectly good "fyi" comment"

And was still downvoted for it. Hence my reaction.

"Firefox on a laptop is now a niche browser"

And I use dark reader on firefox as well as on chrome.

> downvoted

Correctly downvoted: 1. guidelines "Please don't complain about tangential annoyances", 2. HN site norms are enforced by downvotes - downvoting is correct by definition

Plus another important guideline is "Please don't comment about the voting on comments". I'm trying to help you moderate yourself - of course the next escalation is for this inane subthread (including my comments) to be flagged.

https://news.ycombinator.com/newsguidelines.html (edited: added more details)

You might as well quote the rule in full, if you are going to throw the guidelines around.

> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.

I think this makes it pretty clear that this guideline wasn't talking about people trying to provide helpful feedback for a developer, letting them know about a strange edge-case (i.e., why should an extension injecting CSS even mess with WebGL content?) that they might want to look into.

"Correctly downvoted: 1. guidelines "Please don't complain about tangential annoyances""

We disagree on "tangential annoyances". And that's it from my side.

Usually, the Dark Reader failure mode is that things look a bit off and you can tell that something is not working, which tells you as a user that you might have to disable it.

In this case, there simply was nothing shown for the affected experiments, which is somewhat unusual, and it took me a second to even realize it might be Dark Reader. I thought that could be useful feedback for the developer.

{"deleted":true,"id":42416983,"parent":42416643,"time":1734182836,"type":"comment"}