And this is in Firefox, which renders fonts more bold than other browsers.
Original: working on a standard DPI Mac, but it still looks fine - see http://imgur.com/WRWYzBx. Trying to figure it out now...
Cause that looks like a printer that ran out of ink.
It's painfully thin, and the eyestrain factor is pretty high.
But you don’t notice it until you open a font selection menu.
But seriously, I had to use Gtk3's font selection menu today, and it was impossible to work with it.
I've made some changes to Typekit to thicken things up. Is it better? If not, can you provide details of your OS?
Original:
I'll investigate and fix that now. What OS are you on so I can reproduce it?
It looks this this here in Firefox (http://imgur.com/WRWYzBx) and this in Chrome (http://imgur.com/6dFeQhG) on OS X, testing across multiple Macs here. I'd really like to fix it though! Thanks for the heads up!
We moved from Google Fonts to TypeKit recently, so I suspect it may have happened then.
Not just the weight, the size combined with the weight: 12px in a thin font is too light for a screen, especially done in grey. Going to 16px could really make a difference.
Going with a bigger size gives the scope to use a different, contrasting (perhaps thicker, perhaps thicker and smaller for double-contrast?) font for the headings currently in green.
* Getting older happens to different people at different ages, one of the effects of this means eyes get more temperamental, and this doesn't happen 50+, it happens a lot earlier for a lot of people.
I'll be changing the base font to 14px and darkening the grey to #222 quite soon.
I'll also look at 16px but this needs some additional design work.
I can't wait until letsencrypt is done.
> I'd actually pay more than I do now for SSL certs to get that kind of simplicity.
Text needs to be legible, please try and stick to normal and bold weights.
I for one had never heard of these guys and appreciate the mention. Besides, as far as I can recall, it's never been considered problematic to promote your own service on HN as long as the mention is topical and done tastefully.
There's also the guideline specifically asking you not to go on about being downvoted.
It's not hard to see what kind of discourse we're going for here. What's hard is to stick to it when you're feeling that someone is subpar. On the internet, human biases yield a strong tendency to feel that way about others, and we all need to be disciplined about counteracting it. If you can't or won't take up the task, you're not welcome to comment here.
That doesn't mean you have to abide by it perfectly. I can't, and doubt anyone can. It means that when we slip we need to recognize our error and correct it, not defensively dismiss the information.
When people can't or won't be civil on HN, we ban their accounts. There's no exception for getting downvoted—on the contrary.
I'm asking because I'm wondering if it should be made more obvious that he is when he is posting in his moderation role.
I actually had never heard of this and think it's pretty cool.
(No affiliation, I just saw their HN post some time before)
Does anyone know if there's an undo command for `$ letsencrypt run`?
I would love to try this, but too scared to do it and mess up with my nginx configs.
I still haven't figured out how that interacts with the automated renewal features (probably not well right now!) but the ability to revert configurations exists.
Also, please don't try the client with a live site right now, because we don't have general public availability (nobody outside of Let's Encrypt can get a cert issued from the Let's Encrypt intermediate -- you'll get one from "happy hacker fake CA" instead), and we don't have the cross-signature. We're not even quite at the beta-test stage yet, let alone the "please use our certificates on your popular public services" stage. :-)
The main exception would be if you currently don't have HTTPS enabled at all and you're in the mood to experiment to learn more about Let's Encrypt.
A recently released Ruby gem also looks promising, in that it's a much better codebase with a tonne of tests.[1].
[0] https://github.com/diafygi/letsencrypt-nosudo [1] https://github.com/unixcharles/acme-client
https://letsencrypt.org/howitworks/
I'd actually pay more than I do now for SSL certs to get that kind of simplicity.