konradzikusek

DDG without JS - https://duckduckgo.com/html/ Even lighter DDG - https://duckduckgo.com/lite/

Those are still around, and are being used for fingerprinting devices.

Every media query can be checked using JS - `matchMedia('(prefers-color-scheme: dark)').matches` => true/false

No, there are not. http://jsbin.com/bewinalezu/1/edit?html,js,output

Here are all 90 nude images: http://jsbin.com/hufulewaji/2/edit?html,js,output . Truly professional take on the topic.

I really hope you haven’t picked a dataset that features only women nudity, but sample images suggest otherwise: https://dataturks.com/projects/Mohan/NSFW(Nudity%20Detection...

It looks like Ryan Dahl predicted it: "It would be nice to download the massive codebase that ESLint is and run it without it taking over my computer - which it could."

https://www.youtube.com/watch?v=M3BM9TB-8yA&feature=youtu.be...

> I didn't notice a single typo

JavaScript is spelled incorrect all over the place.

Awesome feature and post!

Ability to pause iframes, which Transfer Size Policy depends on, is already on Chrome's radar: https://www.chromestatus.com/feature/5141555102875648

<iframe max-transfer-size="300KB" src="...">

Proposed Transfer Size Policy will allow site owners and ad networks to block abusive ads - https://github.com/WICG/transfer-size

We were looking for an easy way to share our style guide between front-end and design teams. `react-sketchapp` by airbnb didn't really work for us (because it requires you to use React, only generic components (no HTML tags) and inline styles), so we build html-sketchapp. Video showing how it works: https://twitter.com/kdzwinel/status/893242605009612801

Chrome will officially support headless mode: http://crbug.com/546953

Glad you like it! You can track request/response modification feature here: https://github.com/kdzwinel/betwixt/issues/10

Thanks! You can track HTTPS support here: https://github.com/kdzwinel/betwixt/issues/3

Two days ago my team was doing a global change in our style guide and we needed a visual regression tool to help us avoid unexpected issues. Unfortunately, PhantomCSS setup is complicated and we quickly got frustrated. That's why I crated Look-alike. It's convenient for ad hoc usage. (Note that it's not meant for cases where frequent, repetitive and multi-page tests are needed!) Oh, and BTW - the whole thing is open source and available on github: https://github.com/kdzwinel/Look-alike

I'm not sure what do you mean. Only code that I wrote for this demo is in index.html and main.js. These two files are not minified. Ocrad.js, jquery, modernizr, bootstrap are minified because these are libraries that I'm importing. Everything is explained under the app, please read the description.

Thanks! It doesn't have to be 'huge' image, I just recommended it as it gives better results. Small text tends to be more distorted.

That's strange, I never got that bad results. Check out my video where I'm demonstrating the app ( https://www.youtube.com/watch?v=ttn437BlEbo ), you'll see what texts I've worked on.

Recognition algorithm is provided by ocrad.js which is a JavaScript version of the OCRAD project ( http://www.gnu.org/software/ocrad/ ). It's not perfect, but IMO it's very good - just make sure to use huge, printed, black-on-white text.

Using simple text correction algorithm should work just fine. However, this goes beyond this simple experiment. I just wanted to demonstrate capabilities of ocrad.js . Feel free to implement it yourself! It seems that there are multiple JS auto-correction libs, e.g. https://code.google.com/p/careti/ .

It should probably work on Chrome for iPhone. It won't work on Safari since it doesn't support getUserMedia and WebGL.

That would be great! Any idea how to locate the text on the image? Since face recognition can be done "online" ( http://auduno.github.io/clmtrackr/examples/facesubstitution.... ), finding text should also be possible.