My modified fork of agnoster.zsh-theme
A ZSH theme optimized for people who use:
- Unicode-compatible fonts and terminals (I use iTerm2 + Menlo)
I've been looking for the best Linux backup system, and also reading lots of HN comments.
Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.
Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.
This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.
|// Just before switching jobs:|
|// Add one of these.|
|// Preferably into the same commit where you do a large merge.|
|// This started as a tweet with a joke of "C++ pro-tip: #define private public",|
|// and then it quickly escalated into more and more evil suggestions.|
|// I've tried to capture interesting suggestions here.|
|// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,|
|// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,|
I hereby claim:
To claim this, I am signing this object:
You should never let passwords or private data be transmitted over an untrusted network (your neighbor’s, the one at Starbucks or the company) anyway, but on a hacker congress like the #30C3, this rule is almost vital.
Hackers get bored easily, and when they’re bored, they’re starting to look for things to play with. And a network with several thousand connected users is certainly an interesting thing to play with. Some of them might start intercepting the data on the network or do other nasty things with the packets that they can get.
If these packets are encrypted, messing with them is much harder (but not impossible! – see the end of this article). So you want your packets to be always encrypted. And the best way to do that is by using a VPN.
|* Demonstrates that an RSA signature does not uniquely identify a public key.|
|* Given a signature, s, and a message m, it's possible to construct a new RSA key|
|* pair such that s is a valid signature for m under the new key pair.|
|* Requires Go version >= 1.5. Go <= 1.4 doesn't work due to a bug in the bignum|
|* package: https://github.com/golang/go/issues/9826|
|* Written in 2015 by Andrew Ayer <email@example.com>|