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 have a Moto G 1st generation and put LineageOS [0] on it. Far better experience and much more free space.
Unfortunately won't help with making the camera better.
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.
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.
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.
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.
I'm just going to comment on the first aspect of this, the "Merge Tabs and Apps" option.
The first thing I do with the "Merge Tabs and Apps" is to disable it and use the in browser tab switcher.
I usually have many tabs open and I usually have many apps open. Merging the two lists just creates more noise in the app switcher. Imagine if they did this on desktop and suddenly alt-tab gave me (right now) an extra 26 things to switch through! I don't even think I am a heavy open-tabber.
My non-techie spouse wanted me to change it back immediately after the update with no prompting from me. I'm sure some people must prefer it but I find it way too busy in the switcher.
That's not entirely true. Go allows you to tag with the Go version you are aiming for and imports will use that. You do not have to keep your master clean. If you clone explicitly into your GOPATH then you can develop on any branch you like. Similarly, if you use git for version control and so does your library then you can always submodule your dep into your GOPATH and submodules allow you to specific the exact commit you wish to use.