It's fine to point out that the colors are troublesome. It's bad to complain about how you can't read it and your eyes still hurt, as if there's no way to avoid it.
I suspect most people are up-voting this story because of the link-bait title.
The author's blog posts don't really give much in the way of a substantial explanation of what's going on here. The impression I get is similar to other comments here: he comes off as raving and kind of irrational? He's mad about something on Wikipedia and he says he's been blocked, but then doesn't say why?
As far as I can tell, none of the journalists who wrote stories about this read that page, and none of them talked to any of the members of the Wikipedia ArbCom committee. Seriously. Check out Wikipedia ArbCom member Molly White's twitter over here:
She's pretty angry about the press' interpretation of the events here, wherein many of the articles basically flat-out said that "feminists have been carte-blanche blocked from Wikipedia!" The press loves to feed off controversy on Wikipedia, and also loves to not do their homework.
That said, Wikipedia does have an editor gender gap, but I'm not sure there's a lot that can be said based on these blog posts here.
This looks really great, and has some big names endorsing it. Has anyone here read the book and could provide some additional insight on what the book did for you?
I read a draft version of it through my employer, and I have to say it is the best book on Web security I've ever seen. It is basically an encyclopedia of attack vectors, organized by the technologies that enabled them. The author discusses both inherent problems with the protocol, as well as nuances in different implementations, which makes it extra valuable. Reading the book through was an eye-opener, and there were countless oh-crap-I-didn't-know-it-could-work-that-way moments.
Two warnings about the book: first, it is really an encyclopedia, so the author skims the part on how to prevent the attacks. There's a security cheatsheet at the end of each chapter, which is helpful but a bit too succinct. You have to understand the book fully to really make use of it. If you're more into a cookbook style book, look elsewhere. Second, the browser information is not quite up-to-date and thorough. I can't blame the author, as security is an ever-changing landscape. But just standard warning: Do your experiments. Test the attack vectors in all browsers. I once shipped a vulnerability because I blindly trusted the information in the book (thankfully it was disclosed responsibly)
we're actually reading it collectively in our inaugural engineering book club. I'm about a third the way through, it's full of insights on weaknesses and exploits for web based applications.
It contains some seriously in-depth analysis of both current and historic nuclear weapons development, with a strong bend toward the diplomatic and political side of things.
This is really cool! What I'm wondering is how well the "compiling Python code to a highly optimized Dart code" step works. For instance, does the standard Python test suite mostly pass? I imagine this is a monumentous task, and so a bit more detail on the status of the effort would be helpful!
