yoavweiss_

4 ms·

1.
by yoavweiss_ 3y ago
> I don't believe in attacking individuals for what is a systemic issue. I appreciate that! > From what I can see, the webpage needs to return the token to the server before it decides to respond [1]. True that proposal doesn&#x2
2.
by yoavweiss_ 3y ago
> Do you know why this proposal is over a public repo which is not a part of any official open web group discussion? A typical workflow for standard proposals is: personal repo => incubation venue => official working group This pro
3.
by yoavweiss_ 3y ago
> Nobody is missing this; you're defending this work. You can't both defend the work itself and place yourself outside of the process as a "chair." I'm not defending the work. I'm defending the venue, to ena
4.
by yoavweiss_ 3y ago
Blog post author here. A few clarifications: * I am not a contributor to the repo, and stepped in as chair on the repo after writing this, to help the engineers contributing to it deal with clear spam & abuse cases. I wrote this post
5.
by yoavweiss_ 10y ago
The spec has been split into smaller pieces. The first one that made the most progress is https://wicg.github.io/feature-policy/
6.
by yoavweiss_ 12y ago
The canonical link in that aspect is http://wiki.whatwg.org/wiki/Why_not_conneg There are various people in various vendors (Mostly Mozilla and Apple) that oppose conneg based solutions. I didn't mean to be vague,
7.
by yoavweiss_ 12y ago
I looked into that in http://blog.yoav.ws/2012/05/Responsive-image-format But image formats are hard, since they require an eco system, investment from large cos, etc. Maybe in a few years...
8.
by yoavweiss_ 12y ago
The browser can do whatever it wants (read: whatever's best for users) in this case. Current Blink (Chrome/Opera) code wouldn't download the higher res image for 'x' descriptors, but that may change in future versio