ACTCD
ACTCD
https://wiki.greasespot.net/Metadata_Block#@require > The URL specified may be relative to the URL the script is being installed from. But we don't actually support this, and since the current architecture does not...
https://github.com/quoid/userscripts/issues/248#issuecomment-1421925648 The order of checking for updates should be: - `@updateURL` (`optional-metadata`/`.meta.js`) - `@downloadurl` (`optional-metadata`/`.user.js`) - `installURL` (`optional`/`NOT-metadata`/`.user.js`) `installURL` is not metadata, but the real URL when installed from a...
- https://github.com/quoid/userscripts/issues/224 > Revisiting this feature, I think we should deprecate it instead of implementing it. > > The starting point for considering this issue has never been to maximize...
https://wiki.greasespot.net/Metadata_Block#Description > The metadata block appears in JavaScript line comments and may appear anywhere in the top level Greasemonkey code scope of the script, but is usually near the top...
Recent CI deployments often fail, on the one hand due to the premature adoption of Xcode 26 beta, and because we made a [new App Icon](https://github.com/quoid/userscripts/pull/829) that require this version....
I had the idea very early on that we should cancel the use of modal window and instead use the editor area directly. - This reduces complexity (wrapper/mask). - Takes...
- https://github.com/quoid/userscripts/issues/821 Once I have the above issue, I have to think, why can't we do the same thing in `UserScript`? I think this makes a lot of things easier,...
`https://developer.chrome.google.cn/` is redirecting to `https://developer.chrome.google.com/` (`NXDOMAIN`) The actual common domain name is: `https://developer.chrome.com/` I'm not sure there are many similar situations out there.