I wonder how many people here that advise against minification, keep
their compiled binaries "readable". Please start shipping your
makefiles with "-Og" instead of "-Os" then.
On 19 May 2018 at 11:16, Hiltjo Posthuma wrote:
> On Fri, May 18, 2018 at 07:32:49PM +0100, Martin Tournoij wrote:
>> On
The terminal is still the lowest common denominator in user
interfaces. Which is Good, because while it restrains you from doing a
few useful things, it also stops everyone else from doing some
extremely harmful things. Sadly that also means there's little
incentive for fixing the awful stuff (like
> Isn't that what [axfrdns](https://cr.yp.to/djbdns/axfrdns.html ) from
> djbdns is made for?
It's the "S" in "HTTPS". The whole point of the exercise is to have
end-to-end encryption and server authentication between you and the
DNS server. Otherwise it's dumb, it just adds overhead. If you trust
offer
similar services, this would be a way of ensuring no single provider
sees all of your DNS traffic.
On 3 April 2018 at 22:30, Calvin Morrison wrote:
> On 3 April 2018 at 16:22, harry666t wrote:
>>> There is a small bug on line 34: if the statuscode isn't 200 then the
>
If I can't get a small program right, who would
ever trust me to write a big one correctly?
<3!K.
On 3 April 2018 at 22:17, Martin Tournoij wrote:
> On Tue, Apr 3, 2018, at 21:12, harry666t wrote:
>> My take - if you don't mind Go...
>> https://github.com/rollcat/g
My take - if you don't mind Go...
https://github.com/rollcat/gdoh
No forking, no dependencies outside of stdlib, async
queries/responses, allows using multiple providers, 78 loc.
> I'm pretty sure DNS over HTTPS runs on top of a TCP stream and not a UDP
> stream.
In Calvin's sdohd, it's curl doi
> So yes, the entire password store should be kept in one encrypted file
> and so it can be opened and closed.
And then merges become a total pain. You might as well use Keepass.
