26 karma · joined February 3, 2020
ISO8601 won't scale to universe-level applications!
:)
I once had the (mis)pleasure of dealing with some novice DBAs. There were instances in the data model where things were so recursively linked that one query would fan out to 200+ to actually return the set of meaningful data. As you might of imagined, this caused scaling issues when you started dealing with significant amount of data (hundreds of GB of data in the DB).
Eventually we brought in some pros and one of the first things they did was eliminate a number of overly recursive queries and duplicated some (not all) fields of data to speed up performance. We went from 1->200+ fanout in a typical query to 1->25-ish. The performance gains were insane.
Of course it violates the "don't repeat yourself" and to abstract linked (repetitive) data in a relational way. But sometimes this best practice can really be counter-productive in edge performance scenarios. But in general yeah, don't be repetitive, abstract your stuff, and keep it clean and easy to change globally if/when needed.
I'm glad I'm not the only one who feels like this.
I nearly got fired by digging my heels in on a privacy/infosec flawed design... until CTO/CIO layer gleaned what I was freaking out about and the energy (angry, "wtf", etc) suddenly pivoted to the original architect and engineers who cooked up some half-baked stuff.
You don't want your name attached to bad stuff in life. You only have one reputation. Don't mis-spend your social (political) capital by letting dummies bully you into ignoring tangible security issues.
I will check it out now that you have stated it is a bug.
Thanks!
The demo page does that annoying crap where it tries to prevent you from navigating to your prior site.
I thought that trend peaked in like 2001.
You're off base.
DNSSEC is not any more nebulous than the existing structure and control mechanism with regards to domain names. It (mostly) is adding cryptographic under-pinnings to the responses. The control remains the same (registrar level).
Care to share more (as much as you feel comfortable)? That's a very unconventional childhood experience! Thanks!
Yes.
Nah. We have these things called elections (and representational democracy). In general that mechanism decides how society will progress forward from a political perspective.
The United States Government (USG) enjoys a monopoly of violence (consent of the governed). However, a citizen (or group of them -- org/corp) does not enjoy such rights. Your comparison is invalidated.
This is a fairly standard infosec method already in use for a long time (defense in depth, enclave-based security architectures, etc).
Not knocking them - JPL are wonderful people. If I had to guess they did not have funding for this prior, got caught (embarrassed) and now are correctly allocating resources to deal with the issue. Good news!
This guy was not just a "dark web tycoon", he was a child porn hosting empire owner. Much higher severity in terms of moral heinousness than say selling drugs on The Silk Road.
Userland packet processing (in network context) is much more flexible and less brittle than forcing certain functionality to exist solely in the Kernel layer. However things do exist that allow you to (mostly) transparently re-jigger a standard app's TCP/IP calls. One such example is using LD_PRELOAD to "hijack" the sys-calls for certain things and snake it to your (super high performance) userspace app!
There's a lot of exciting stuff happening in the open source networking world (DPDK, VPP/FDio, Network Service Mesh, etc). I really recommend digging into it!
But I understand your point and agree with you. I prefer direct communication. If you don't want to hang out just say so - I like clarity.
I do all of my VPC peering and route-table manipulation via terraform repos today, so I am curious what the benefit of using this would be over what I have today (if there is).
Thanks.