There is way less bandwidth involved since the amount of data transferred for a shared coding exercise does not surpass the data (pixels) involved in screen sharing.
Helps with remote interviews/candidates with slow connections.
Every time LetsEncrypt is brought up I am reminded of "if it's for free, You are the product". In this case it is one's servers. A single company has a hand on the pulse and runs software on your server in exchange for continuous "convenience". I am still NOT buying in, diversifying SSL certs from reputable companies with 12 (or sometimes 13) months validity are still ok for me in 2017.
I don't really understand what you're implying but here's some information that might help.
Let's Encrypt is a non-profit service and we don't use your data for our benefit. We work hard to collect and retain as little of your data as possible.
We do not require you to run software from us on your server. You can use any client you want. In fact, we don't even produce client software -- all Let's Encrypt clients are built and maintained by our community (the client we often recommend, Certbot, is an EFF project).
This seems a little tin-foil-hatty. The only information which Let's Encrypt receives is the domain name that the certificate is for (which is public anyways for any CA implementing certificate transparency). The Certbot software is open-source and easily verifiable, and there's multiple independently developed alternatives available if you don't like it.
Some of these are much lighter weight than Certbot and have many fewer dependencies. You can also take your pick of what language they are written in and how they are installed on your system.
You're also welcome to write your own client that speaks the ACME protocol. Let's Encrypt is near to rolling out an API endpoint that will speak the IETF-standardized version of ACME, developed through an open standards process and in consultation with other implementers.
I know that some people have said they don't like running a large new application as root, even when it's open source. So, please have a look at some of the other clients and see if one of them strikes your fancy!
Let's Encrypt's operational funding is thanks to these entities
which view the service as worthwhile and important and have chosen to donate funds to support its operation. The organization is overseen by these people
In this model there is no need to charge users for certificates or try to indirectly monetize the use of the service, although users are very welcome to donate if they find the service useful, and Let's Encrypt may be more sustainable if some users choose to do so.
I agree, but you could say that any of major issuers was reputable 2, 5, ... years into issuing certificates. Being new doesn't mean you're better long term.
But I personally like the fact there's much less commercial pressure on LE - for the time being at least.
Got a bunch of servers with Linode: personal GitLab, self-hosted Zimbra, Pgsql database, personal/family/fun x2 (python, some PHP, some go behind nginx), couldn't be happier, have been paying $120-$160/m for almost 3 years now. Now also behind free cloud flare account getting free SSL and http2.
