mianosm
Might be smart in many instances to do cross training, and on the job perspective expanding, but at the end of the day: it's usually better to let the animous live...and the spice flow.
Until nation-states fund and invest in the infrastructure, finding your confidence in cryptocurrency with little to no regulation is a massive risk.
It will be interesting to see over the next few decades if sustainable power sources (arguably Nuclear, especially under the recent Advance Act) won't just be a lagging situation.
Something that I don't think is available at the source that would be a nice addition would be a per capita (looking at the population and using it as a basic sortable column for quick reference).
It's a very cool tool and resource, though.
https://www.vox.com/2015/5/23/8647095/kool-aid-jonestown-fla...
They really do appear to be all in on avoiding memory leaks from C/CPP:
> Over the next few years we plan to continue replacing C or C++ software with memory safe alternatives in the Let’s Encrypt infrastructure: OpenSSL and its derivatives with Rustls, our DNS software with Hickory, Nginx with River, and sudo with sudo-rs. Memory safety is just part of the overall security equation, but it’s an important part and we’re glad to be able to make these improvements.
It seems like a really challenging endeavor, but I appreciate their desire to maintain uptime and a public service like they do.
Sometimes the person who says "I'm really smart, like mensa level", does some really ignorant and stupid things.
I've seen a few attempts to leverage certificates, or GPG; and keys nearly always are an 'easier' process with less burden to teach (which smart(er) people at times hate to do).
Also: better to save a life and either average down whatever PFA count they have, or bolster their blood volume so they can start producing their own lower PFA infested hemoglobin.
Lesser of evils, and kind of a win win: if everyone was blood letting for the safety and humanity of others.
Coming up with a uniform, concise, and easily decipherable scheme is really the best for naming nodes on a network (be it at your home, or in a data center with 10s of thousands of machines (virtual and physical)).
GUID is a bit extreme, but leveraging DDNS, and having a plan is always the best (and not naming things after a finite index like: planets, cartoon characters, mythological objects, or models).
* Idle Load Balancers
* Underutilization of EBS volumes
* Unassociated Elastic IP addresses
* Idle RDS intsances
* R53 latency resource record sets
* etc...
It stinks of dynamic demand, or elastic compute...
...hopefully it helps in their quest to continue serving the drooling masses and being the 'front page' of the Internet.
Source code or GTFO was the response, and seemingly its all theory so far....
Here the countdown hits zero well before the lights shift to yellow and finally red. Perhaps Toronto needs to readjust if there is a high number of rear-ends occurring due to drivers going off of the pedestrian control devices instead of vehicle control devices.
https://www.usenix.org/sites/default/files/conference/protec...
https://www.usenix.org/system/files/conference/nsdi13/nsdi13...
Pinging your loopback address just shows that your localhost is still there.
If you were to write a script that instead pulled the local IPv4 address you are getting - that might be a little more sensical?