-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stylish #455
Comments
😧 |
I've already turned off auto-update for the Addon, but I'm also pretty certain that such an addition wouldn't get approved on the Firefox addon review process, not sure about Chrome. |
It's already approved on Chrome... I got the update today. |
Thanks for the heads up. It's unfortunate that I have to uninstall Stylish, since the tampermonkey script always takes a moment to apply... |
There is an opt-out available from what I read, but not sure how effective it is. |
It looks like nobody's touched the Firefox extension… yet anyway. The diff for stylish-userstyles/stylish-chrome@78bb18f is extremely unreadable, and in some parts, disturbing… For example, why have JSON files been marked as executable in that commit? It almost looks like the new management don't actually know what they doing. |
Maybe its time to make a custom extension to apply changes to the site without the tampermonkey delay but with all of tampermonkey's github-dark features? |
Is it still there? I thought I fixed this in StylishThemes/GitHub-Dark-Script@2ab740f ;) |
(Using Chrome Version 55.0.2883.87 m) Has the script url changed so I'm out of update or something? It is pointing to https://raw.githubusercontent.com/StylishThemes/GitHub-Dark-Script/master/github-dark-script.user.js so it does not seem like it would... |
The URL is okay. If it shows 2.0.18, you're up to date. Guess I have to actually test in Chrome, but I suspect it might just be a Tampermonkey-specific issue. |
Yes it does show as 2.0.18. Tampermonkey itself is at 4.2.7, which chrome is saying is the latest as well. |
It doesn't sound like the TamperMonkey extension is all that much better from a privacy standpoint...I could be missing something glaring, however.... |
Yeah, I still notice the white flash once in a while. We should be able to get the userscript to get around that problem. I'll look into it when I get this other project I'm working on done. And I'm not against converting the GitHub-Dark script into an extension, but I don't own any Apple products so I would not be able to make the extension for Safari. |
@Mottie I set this up as an extension for Edge that I side load (Stylish isn't available and Tampermonkey doesn't work because of some api issues). It's the bare minimum to make it work, but it's been serving me just fine for 6+ months now. https://github.com/xt0rted/edge-github-dark |
I'd love a Chrome extension (or any other means) as well, I just installed Stylish due to these changes. It's unfortunate, because whatever resource benefits the company could bring in a partnership, it will never outweigh the tracking. And more importantly, trust is broken in a way that can't be restored. That company bought an extension that had the read/write all permissions already agreed to by many users...that's what they're after, not Stylish. |
For anyone interested the Edge plugin I linked to above can be side loaded in Chrome as well. If you're looking for something to hold you over this should work. |
I think I'll start working on a browser extension/addon that'll apply themes and allow customization for all of our active StylishThemes. I opened a new issue so enable discussion... #458. |
In the mean time, you can install a style from userstyles.org if you have Tampermonkey installed on Chrome... It doesn't work for our Stackoverflow-Dark style because the userscript doesn't appear to include the // @include /https?:\/\/((.+)\.)*stackoverflow.com.*$/
// @include /https?:\/\/((.+)\.)*stackexchange.com.*$/
// @include /https?:\/\/serverfault.com.*$/
// @include /https?:\/\/superuser.com.*$/
// @include /https?:\/\/stackapps.com.*$/
// @include /https?:\/\/mathoverflow.net.*$/
// @include /https?:\/\/askubuntu.com.*$/ Result: // ==UserScript==
// @name Stackoverflow Dark
// @namespace http://userstyles.org
// @description Dark style for Stack Overflow (& many Stack Exchange sites)
// @author StylishThemes
// @include /https?:\/\/((.+)\.)*stackoverflow.com.*$/
// @include /https?:\/\/((.+)\.)*stackexchange.com.*$/
// @include /https?:\/\/serverfault.com.*$/
// @include /https?:\/\/superuser.com.*$/
// @include /https?:\/\/stackapps.com.*$/
// @include /https?:\/\/mathoverflow.net.*$/
// @include /https?:\/\/askubuntu.com.*$/
// @homepage https://userstyles.org/styles/35345
// @run-at document-start
// @version 0.20170203012237
// ==/UserScript== |
A fork of the previous version of Stylish with all analytics removed and a compatible backup feature here. |
Awesome work @narcolepticinsomniac! Thanks! I've opened an issue with some of my suggestions and concerns - openstyles/stylus#20. |
It appears that Stylish is under new ownership...
This post is disturbing.
And I don't think I will continue to use the Stylish addon. I will try to find a nice alternative, or maybe install an older version of Stylish, or maybe even create a userscript to apply the styles we have available here.
Either way, I think changing the links to Stylish in the read me might be advisable. Or, at least add a warning and link to the above post.
The text was updated successfully, but these errors were encountered: