alexanderby

I have to publish a bug fix for a version, that is Pending Review, and it is not possible to submit the new update before the previous one was removed.

Chromium team fixed this issue by showing theme background color by default. So you should install some dark theme, e.g. this one https://chrome.google.com/webstore/detail/material-incognito...

Also if you download Chrome Canary and launch it with --force-dark-mode flag, you will get early access to built-in dark mode.

No. You can locate the files of the extension and ensure that it doesn't make anything severe, the code is not obfuscated.

Unfortunately Chrome and Firefox API has no this feature yet. Time Settings (ability to set active hours) were implemented recently and soon will be published.

Of course it will be cheaper. When you take some code from the original Dark Reader, obfuscate it, add some features, then you can put a $2 label.

When the amount of donations will be enough, then I would be able to publish the source code of the Safari app. But currently it is the major source of revenue and it lets me continuing the development and spend as much time as possible.

Stylus already does it well, so I think you could use Stylus for such websites. UserStyles.org is still owned by SimilarWeb, so I would stay away from it. What is planned is to add some static themes for popular websites.

The newest Opera has some changes, to make the extension work on Google Search you have to open Extensions page and click "Allow access to search page results".

Just checked, it works on Canary too.

Yes, it works in Firefox for Android and in Yandex browser. The only issue with Firefox is white user interface and white default color.

You can already use per-site settings https://darkreader.org/blog/custom-site-settings/

I'm an author of both Dark Reader and Dark Reader for Safari.

Then you should try switching to Filter or Static mode.

The browser doesn't separate what injected script can do and what it can't. Regarding Dark Reader, it needs to know page URL to determine if it is blacklisted by your settings or not.

CSS filters can cause heating of your phone.

Sorry, I'm not sure that publishing a paid app source code would be a good idea. There is a chance that somebody will publish the same app under different name. Somebody has already published a crack for it. And another Safari app already reuses some code from Dark Reader for Chrome.

There was a long discussion regarding this review https://www.reddit.com/r/apple/comments/9y0s2a/dark_reader_d...

You know, some Apple developer can also put some malicious code into Safari, but for some reason you trust them and use their browser, even though they used to slow down older iPhones without a warning, forcing users upgrade to newer devices. Who knows what they will do the next time.

If you prefer dark text on dimmed background try Dark Reader's light (dimmed) mode https://i.imgur.com/H38tpIS.png

Firefox add-ons pass full source code review before the submission after the Stylish incident. Safari extensions also pass manual review, Apple asks developer to send an ID card photo. Not sure about Chrome, you have to simply trust me, the code is not obfuscated and you can always locate the files and see what the extension does in your browser. Google recently announced some security changes https://blog.chromium.org/2018/10/trustworthy-chrome-extensi...

Your code is based on CSS filters. Dark Reader provides this mode too, but also allows users to fix and share wrongly inverted parts https://github.com/darkreader/darkreader/blob/master/src/con...

Dynamic mode is slower at start, but has no impact on performance after all the stylesheets were analyzed.

Dark Reader provides all 3 possible modes: - Static: simple and fast. - Filter: simple, but uses GPU very much and usually inverts already dark parts. - Dynamic: complex, but tries to achieve the best visual results. There are some known issues and the work on it is in progress.

Here are some more details https://darkreader.org/help/en/#theme-generation-modes

Dark Reader also offers static CSS support https://darkreader.org/blog/stylish/

Global CSS will work well on text websites. For many others it will break up the coloring and make page parts hardly distinguishable.

Bad performance in Firefox is a known issue and I'm working on improving it. It's not an issue in Chrome and Safari. Low performance can be noticeable in new GMail design, but the reason is their heavy stylesheets full of unused code and images, that Dark Reader tries to analyze. Some day it will be fixed by adding some static themes for popular websites.

I'm trying different approaches. The crowdfunding was not very successful, so I decided to try making the app paid for Safari, since the platform is technically different and users count is low. App Store makes its best in selling the apps.

At the same time Chrome Web Store is not suitable for paid apps, today it looks like a big dump: it is filled with outdated and poor made extensions. Raking system makes good apps hardly discoverable. Also paid Chrome extensions work only in 36 countries. Dark Reader owes its popularity to Hacker Vision extension that became paid some day. Maybe that's the reason why some developers prefer monetizing their extensions by selling users browsing history.

The quick answer is: it makes it possible to work on project full-time. Only 1 of 2000 makes a donation https://darkreader.org/blog/500k-users/

This is XML, Dark Reader works for HTML only.

Dark Reader (which generates dark themes dynamically) added support for static CSS so that style sheets can be migrated http://darkreader.org/blog/stylish/

Dark Reader (which generates dark themes dynamically) added support for static CSS so that style sheets could be migrated http://darkreader.org/blog/stylish/