734 karma · joined March 3, 2010
I'm a fan of 16px + for body copy. I think the browsers have it right most of the time with the default font size of 1em == 16px. You've got me thinking of experimenting with 18px now though.
Where does the 65 chars per line come from? I've heard 2 to 3 English alphabets length but I don't know the original source of that guideline.
This is a question I asked yesterday that was down voted at impressive speed. Thankfully a couple of the commenters helped me out with information that benefits the community. Their comments would have made acceptable answers but they were unfortunately closed.
http://stackoverflow.com/questions/23998391/how-to-identify-...
Or perhaps I did just ask a bad question, it wouldn't be the first time.
As the article shows it's pretty straightforward to setup; if you can add a response header to your app then you'll be able to figure out how to harden your app with HSTS.
For my fellow web developers who like to learn by video, I've tried to make an easily digested screencast and a page of sketch notes to help get the word out about HSTS and explain what it protects against [2].
But I might be missing the full picture, and perhaps I'm just not the target audience.
Good luck to Snip.ly, but for developers who would want to stop this kind of thing from happening on their own sites, OWASP has a clickjacking defense cheat sheet:
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_S...
When I've worked on news sites in the past, many of the journalists preferred writing in their desktop word processor of choice and cutting and pasting into the CMS as the final step before publishing.
The CMS was probably viewed as a necessary evil and I don't remember there being much love for it from the people who had to spend hours in it everyday.
Partly this was due to the CMS not working offline and it just wasn't as pleasant to use as the software the writers have used for years, which is understandable.
Enhancement request: Fullscreen mode