I feel like excluding IPv4 folks is a large reason why IPv6 continues to fail. I feel like this is a pretty good compromise between pushing IPv6 and not being an IPv6 hermit in the IPv6 desert.
178 karma · joined September 10, 2013
I am an Infrastructure Engineer at Braintree
I feel like excluding IPv4 folks is a large reason why IPv6 continues to fail. I feel like this is a pretty good compromise between pushing IPv6 and not being an IPv6 hermit in the IPv6 desert.
https://en.m.wikibooks.org/wiki/OpenSSH/Cookbook/Multiplexin...
It creates a control socket that lasts up to x minutes after your last session closes, so for me, all day + 15 minutes, which then new connections go over instead of re-athenticating.
Many places disable it for "security" reasons.
Does the transpiling step take as long as Ruby doing the parsing?
(I know this is more about ergonomics than performance, but just curious if you've tested these things.)
I would much prefer a terminal that still provided interactivity when text was scrolling in other parts than raw speed. Open up two panes in tmux or your favorite split screen with text scrolling in one and measure latency in the other pane with typometer and I will use whatever comes up to the top.
The attack works against both WPA1 and WPA2, against personal and enterprise networks, and against any cipher suite being used (WPA-TKIP, AES-CCMP, and GCMP).
I would like to see what it is like for a small sliding scale. Give me the same data with the ability to slide it over a 10 year or 10 month period. Do the smaller population areas flip back and forth between "mobile" and "immobile"?