151–160 of 173 posts
Earlier quoted context omitted.
Probably because I was a mod of a moderately popular local sub. I started losing my shit at people posting anti trans hysteria. Part of me wants to send spez a bill for 14 years of deleting dick pics and local kkk posting. And then there was COVID...
you should have collected all those dicks in bag and mailed them to spez
Earlier quoted context omitted.
This is such a blatant rewrite of history; as an example live migrations were a thing in Xen: https://docs.redhat.com/en/documentation/red_hat_enterprise_... .
I didn’t realize Xen migrations were made available from a uniform web API accessible from remote tools and fully abstracted/automated at the cluster level. You are focused on the details and missing entirely the point of my post.
https://web.archive.org/web/20011204195446/http://www.sw-sof...
https://web.archive.org/web/20011224040032/http://www.sw-sof...
That's 2001, and Virtuozzo was already advertised supporting migrations.
OpenVZ remained super popular for at least like 10 years after it was open-sourced as OpenVZ in 2005, well into 2015, at least. Primarily because it allowed over-provisioning of RAM and all the other resources, which wasn't possible in other environments without the memory balloon drivers and other issues.
I imagine the major reason OpenVZ has declined in popularity is because nowadays memory is cheap enough that over-provisioning of RAM isn't that much of a selling point, and not being able to run your own kernel with processor-guaranteed virtualisation, is deemed too old-fashioned and less secure for true multitenancy than Linux-KVM, which has basically taken over the entire market, from both Xen and OpenVZ, and VMware, and everybody else. Even Amazon EC2 is based on Linux-KVM now, whereas previously it was based on Xen.
Earlier quoted context omitted.
I didn't get an AI vibe from this post. Grammar checkers add em dashes, too. If anything, an AI tool would have written a shorter, less rambling post.
It’s easy to be fooled, myself included it seems :) For context, here’s a handful of the ChatGPT cues I see. - “wasn’t just my backup—it was my clean room for open‑source development” - “wasn’t standard AWS incompetence; this was something else entirely” - “you’re not being targeted; you’re being algorithmically categorized” - “isn’t a system failure; the architecture and promises are sound” - “This isn’t just about…
Dude, plenty of people write with em-dashes and semicolons; I personally use them constantly (and I don't use LLMs at all). Em-dashes are trivial to type on MacOS (Alt+Shift+Dash) and even on Windows—I used to have the alt code muscle memorized (Alt+0151) but now I just use the Mac version with an AutoHotkey script. I get being wary of LLM spam now that it's pretty much everywhere, but this is not the "tell" you think it is.
To be clear, you're free to dislike this writing style, but I'm 100% confident that it has been common since long before LLMs were in widespread usage.
> his real writing style when you read his actual written work is great.
You're doubling down on this not being "his real writing style" despite acknowledging you were wrong about this being written by ChatGPT?
Earlier quoted context omitted.
And the people using it multiple times a year delete it afterwards?
> And the people using it multiple times a year delete it afterwards? The people wouldn't, but in the environments I'm thinking of, security policies might. What you're leaning into is a high-risk backup strategy that would rely mostly on luck to get something remotely close to the current version back online. It's pretty reckless.
In environments that go so far (deleting local checkouts of code out of security concerns), I bet they do have a mirror/copy of the version controlled code.
Earlier quoted context omitted.
Yeah, at some point the article says: > I’d done everything right. Vault encryption keys stored separately from my main infrastructure. Defense in depth. Zero trust architecture. The works. Did you? Is putting all your eggs in one basket "defense in depth"? Is total trust in AWS "zero trust architecture"? I'm not defending AWS here; they fully deserve all the fallout they can get from this, and I do feel for the dev…
I dont disagree with your broader point—centralizing everything in one provider is a systemic risk. The architecture was built assuming infrastructure within AWS might fail. What I didn’t plan for was the provider itself turning hostile, skipping their own retention policy, and treating verification as a deletion trigger.
And if you have a similar horror story with a tens/hundred of thousands of dollars (or more) monthly AWS invoice, please speak, I'm very curious to learn what happened.
Earlier quoted context omitted.
OK, so, you're saying migration and remote drives over IP is the secret sauce of AWS / EC2? Per Wikipedia, live migration was added to OpenVZ in April 2006, one year after OpenVZ was open-sourced in 2005, five years after Virtuozzo was first released as a commercial product in 2000, 3 years after the company was started in 1997. Straight from Wikipedia. I would guess that prior to April 2006, live migration was alrea…
You are failing to understand that the product is not the technology. The product is the interface. One of the products you listed had the “cloud” interface we are familiar with today.
Earlier quoted context omitted.
But it's github ...... it can't be lost. Unless github closes the account, or a hacker gets access, or a rogue employee gets mad and deletes all, or some development accident results in repo deletion, or etc etc.
Or if the one employee who created the account and was paying for it on his personal credit card and then got laid off. And no one else in the company knew what GitHub was.