thechriswalker

The Final Empire is a good start, or maybe one of the more standalone books - Warbreaker is one of my favourites.

That's what I use, Caddy webserver with Gandi DNS (also used Route53 in the past) handling the ACME challenge and a `*.l.mydomain.tld` pointing to 127.0.0.1.

Adding reverse proxies for different local services becomes a piece of cake, but mkcert allows you to use `localhost` directly if needed. Personally I never have and like not having to make any changes to the trust store.

I don't think it does. That quote is from the section explaining how to configure "Password" authentication. i.e. to use Password authentication, you must enable it on the target server.

It then goes on to list how to use Kerberos or Public Key methods.

I think the use cases there is more accurately, if the user doesn't paste into the first box AND copies the content, don't let them paste into the second.

I would paste into both boxes and resort to developer tools if I am not allowed.

from css/main.scss `$monoFont: 'Courier New', Monaco;`

I think it's caused be the missing fallback `monospace` in that list.

I did not like the feature and did not use it.

That doesn't make it OK to remove a feature that people did use and like.

That feels like a bit of a slap - what if they decide to remove some other feature I like but other people don't use (e.g. the always allow zoom feature which I would not like to go without)

I have been watching the bazil project for a while - it's exactly the system I want. Still very alpha right now, so I don't (and one shouldn't) trust it with irreplaceable data.

Less complex way to get public ip.

`dig +short myip.opendns.com @resolver1.opendns.com`

From what I just read, the "shun" method means that you can rewrite history by adding a shun, rebuilding a copy, then switching copies.

Not db rewrite, but the same end result.

edit: bad english

Firstly this is super cool and much simpler than other SSGs, but whilst I applaud the stand against "convention over configuration", I read the docs and find all the magic. Files starting with underscore are ignored? Where was the configuration for that? Oh yeah, that's just a convention. Then there's the magic for "_inherit.yaml", which -- by convention of this tool -- is treated specially. You can't have it both ways.

Surely it's because it looks like a flux capacitor. Seems reasonable to me.

Actually, IIRC it's the exact same reason as the io.js split. The maintainer of jsdom had changes that weren't being merged into node's VM module.

So jsdom 3.x used a lib called "contextify". When io.js was released and the changes included, node support was dropped. Now node 4.0.0 is out and has those changes, jsdom now works on node again.