daxterspeed

14 ms·

1. 91.▲
   by daxterspeed 8y ago

   gorhill, the developer of uBlock Origin, has already fixed the issues affecting uBlock Origin (AppCache and SW). "Regarding [who left open the cookie jar] I was contacted in March by one of the researcher regarding the "behind-the
2. 92.▲
   by daxterspeed 8y ago

   I suppose the author meant that the illusion of proper encryption is worse than simply storing the password as plaintext - especially when the encryption is presented as an opaque string instead of clearly stating that it's using MD5.
3. 93.▲
   by daxterspeed 8y ago

   I understand your sentiment but I do wonder what the extent would actually be. The largest website are more than capable of adapting, and older sites are more likely to either not use any JavaScript or only accept http traffic (which is alr
4. 94.▲
   by daxterspeed 8y ago

   All these security headers seem like a terrible idea to me, shouldn't security be the default - especially if it breaks insecure websites?
5. 95.▲
   by daxterspeed 8y ago

   uBlock Origin is the uBlock. A few years ago, back when uBlock Origin was just uBlock, gorhill (it's sole developer at the time) entrusted the uBlock development to what was supposed to be a community effort. Instead a single develop
6. 96.▲
   by daxterspeed 8y ago

   There's many amazing things only possible in canvas because you can read the pixels directly (especially in displaying complex pixel art), so removing that capability out-right would be highly disappointing. I suppose a better solution
7. 97.▲
   by daxterspeed 8y ago

   I really wish the browser vendors would come together to establish a plan to clean up User-Agent. It's one of the worst offenders in header legacy[1] and fingerprinting. Exposing what browser I am using and it's major version is f
8. 98.▲
   by daxterspeed 8y ago

   While there's a few gotchas, rolling your own JSON parser isn't necessarily a ton of work. Or perhaps a proposal could be written to give numbers emitted by JSON.parse a "raw" property, so they could be decoded using Big
9. 99.▲
   by daxterspeed 9y ago

   Not having numeric types is a real issue - but on the plus side BigInt is advancing quickly https://github.com/tc39/proposal-bigint
10. 100.▲
    by daxterspeed 9y ago

    It was announced in V8 6.1 that asm.js could be validated and compiled to WebAssembly. https://v8project.blogspot.se/2017/08/v8-release-61.html To be fair I don't think this announcement ever spread that fa
11. 101.▲
    by daxterspeed 9y ago

    I love it! I've been working on a brainfuck to asm.js compiler myself and it's a great learning experience, even if asm.js will be going away in favor of wasm (though I believe Chrome compiles asm.js into wasm). I'm excited t
12. 102.▲
    by daxterspeed 9y ago

    When you install an extension in chrome it's by default set to be disabled in incognito mode (supposedly since some extensions don't respect privacy). From the extensions page you can easily set UO, or any other extensions for tha
13. 103.▲
    by daxterspeed 9y ago

    This result is by itself amazing, but if you want to make it behave a bit more like the bug you can set the transform-origin to "center bottom".
14. 104.▲
    by daxterspeed 11y ago

    I believe this is caused by .clip() being "wonky" in Chrome. I think the better alternative to .clip() is: context.closePath(); context.fill(); context.globalCompositeOperation = "source-atop"; In action: htt