203 karma · joined September 11, 2019
The managed hosts and/or their tools probably helped negate damage/resolve issues quicker. However I think that the idea that "all you need is a couple of dozen lines of yaml and a managed provider" is exactly why it's headed down a similar path.
For a real world examples just look at every improperly configured S3 bucket leaking data. Every private key accidentally posted to github from a careless 'git add -a'. Every API that doesn't properly check auth. None of these are within the purview of a managed hosts responsibility.
I'm not even against K8 in any of this. Just making the observation that - like PHP - it is empowering entire groups of people to do things they otherwise wouldn't be able to do.
And like PHP, it will be criticised with the power of hind sight but will continue to be used and power vast swaths of the internet.
“The law, in its majestic equality, forbids rich and poor alike to sleep under bridges, to beg in the streets, and to steal their bread.”
Youtube et al certainly encourage the free and public flow of traffic. Their business model depends on it. So their responsibility to the public would seem to obviously overshadow the perceived protections as a "private company".
I was also a child of the 80's
https://www.cl.cam.ac.uk/~mgk25/pet2004-fpd.pdf
tl;dr The signal from a DVI cable can be detected but at much more reduced ranges. See also; RAGEMASTER (Snowden leak) a range extending implant for video cables.
I noticed you said "meaningful" impact and not "no impact". If your optimizing this seems like the best of both worlds in the slight increase of conversion and the security of verified email?
Revenue driven design will win every time.
Now look at this app I can write in 30 lines of code with this framework! Oh and 500 lines of yaml across 2 dozen files but look the "code" is so sleek and sexy.
Joking aside I think he could have at least mentioned the difference between required complexity and unneeded complexity. Ironically it seems to spawn from attempts to reduce the first type of required complexity in a lot of cases.
I can verify the OS install media with trusted publishes using signing keys and PKI. I can't do a god damn thing about the cheap, back-doored PCI controller from China.
What protection does secure boot really offer the end user at that point? The PCI controller is in place to just pass the right signatures to secure boot or just wait until after the secure boot checks so it's not helping with bad hardware. I already verified the OS media at install, so its not super useful there either. Did my boot code change? How would I know? Did the bad PCI controller fake it? Do I have any additional trust in my system? I can't go probing the system to try to find out.
A black box with zero control told you you were safe and there is no way to look at or modify the system now so you can trust it. Your hardware was never on a TAO workbench. Who doesn't feel safer?
That "very small set of primitives" is enough to build the cloud vendors themselves so how exactly is that a limiting factor?
If I seem overtly hostile I don't mean it that way. I am just genuinely curious for an extended explanation. In it's current form it sounds down right marketing tautology to my ears.
A cheap phone or tablet hardly represent best of breed for the technology as a whole.
What exactly is irrational about a kid with 300k in debt and no job hoping that a collapse could lead to a real future for himself and/or his kids?
Eh? Code can be just as generalized and "deep". The code may (probably) not be usefully executable, but it could describe any concept. At that point it's just "math" again, albeit with different format and symbols.
So I guess your point stands, but its a very thin distinction of common usage.
Use with any standard SIP client. It can be stand alone or part of a PBX... It can be crabby to build and as others have pointed out it's gonna need a bit of horse power but by no means do you need a super high end 48 core monster but your not gonna host this thing on a AWS micro instance either.
It's dead simple to poison some website, insert a thumb drive, or just flat out lie and put it on a device after the fact and make any target an instant socially repugnant felon. The ROI on that is fantastic
"Look at the wage rate between the foreman and the worker in Iussia" - I have, a foreman in the US today makes twice the hourly rate of the worker and that's before benefits packages and other compensations low level hourly workers do not get. So it can be more than double.
In fact, the OECD's own data the US is now has a wider inequality gap than Russia.
https://data.oecd.org/inequality/income-inequality.htm
Only in economics could someone be so provably wrong yet considered a luminary...
What does China tell us about Republics, given that it is the Peoples Republic of China? What does North Korea tell us about democracy and repulbics, given that it is "The Democratic Peoples Republic of Korea"?
No? But we are willing to take at face value oppressive regimes using "socialist" language?
"This is my brothers Ritalin, It's great for staying up and studying just don't try to write an English paper on it"
a) Shared data source; each service writes pid/state to a file in the shared data store. It could be a single directory in a single server setup or a dedicated NFS/SMB server for hundreds/thousands of nodes.
b) Pub/Sub service; Kafka, et al, in which services simply subscribe to and publish to a central channel to see everyone else.
c) Determinism; You use predictable naming/addressing and simply infer. This is tricky to scale but not impossible.
d) Any number of stand alone discovery services ala Zookeeper or Eureka. They all end up being effectively the same pub/sub model as B, just prepackaged.
e) You don't discover shit, you have a single load balanced endpoints that can scale out instances as needed behind balancer with zero knowledge required by the rest of the system.
Pick one to suit your needs. Service Discovery is not that hard and has been way over engineered.
It's more about chain of custody/location and time verification. Video authentication can't be used to tell if a video is real because it may just be a "real" recording of faked content. But you can say with some certainty that a video came from DVR X at Y time.
I think you may have inadvertently bolstered OPs claim.
Everyone claiming tooling or funding or this or that is missing the forest for the detail of trees in the client spec.