

My thought exactly. OTOH, I feel like the anti-Musk ball only really got rolling in March, and this report can’t possibly cover March - it’s got to be Dec24-Feb25, so probably just a hint of things to come.
My thought exactly. OTOH, I feel like the anti-Musk ball only really got rolling in March, and this report can’t possibly cover March - it’s got to be Dec24-Feb25, so probably just a hint of things to come.
It kind of amazes me that, in this day and age, email has turned out to be the lynchpin of security. Email as a 2FA endpoint. Email password reset systems. If email is compromised, everything else falls. They used to tell us not to put anything in email that you wouldn’t put on a postcard…how did this happen?
Wonder if there’s an opportunity there. Some way to archive one’s self-hosted, public-facing content, either as a static VM or, like archive.org, just the static content of URLs. I’m imagining a service one’s heirs could contract to crawl the site, save it all somewhere, and take care of permanent maintenance, renewing domains, etc. Ought to be cheap enough to maintain the content; presumably low traffic in most cases. Set up an endowment-type fee structure to pay for perpetual domain reg.
At least my descendants will own all my comments and posts.
If you self-host, how much of that content disappear when your descendants shut down your instance?
I used to host a bunch of academic data, but when I stopped working, there was no institutional support. Turned off the server and it all went away (still Wayback Machine archives). I mean, I don’t really care whether my social media presence outlives me, the experience just made me aware that personal pet projects are pretty sensitive to that person.
Imagine the CEO of Browning or American Rifles helping Joe Biden pick out a new gun from a display in the state dining room.
Back in the day, I set up a little cluster to run compute jobs. Configured some spare boxes to netboot off the head-node, figured out PBS (dunno what the trendy scheduler is these days), etc. Worked well enough for my use case - a bunch of individually light simulations with a wide array of starting conditions - and I didn’t even have to have HDs for every system.
These days, with some smart switches, you could probably work up a system to power nodes on/off based on the scheduler demand.
I bit the bullet this month & bought a domain so I can assign mail handling and change providers without changing my email address. Currently using https://purelymail.com/ because they’re $10/year for as many addresses & domains as you want “within reason.” It’s apparently just one guy with some AWS instances, but it was very straightforward to set up.
There are still “favors” to be done.