Jedd

You're right, and as someone north of that age, and who self-assess as mildly competent with technology, I didn't mean to imply a linear correlated.

I'm aware our (AU) representatives & senate average age is relatively low compared to US / UK, and I think that figure (52 ish) is probably relatively healthy in terms of a spread of younger + experienced minds.

But OTOH, our government has form on this front (of doing as our friends over the pond instruct, and of not really understanding the technology around which they are formulating laws) and I should probably have pointed at that aspect, but it's harder to succinctly convey that track record.

You're conflating - 'Do we understand that Holmes did these things?' - with 'Were those specific charges brought against her and were they successfully prosecuted?'.

Reading John Carreyrou's book, it's pretty clear she was guilty of (lots of bad) things beyond the lone 'defrauding investor' charge that was successfully carried.

The _other_ option is to shift, perhaps in two x half-hour stages over a month or longer, but around the equinoxes - the 'standard operating hours' for services and businesses.

This is often overlooked as an alternative to shifting everyone's timepiece at the same instant -- I've never understood why there's so much much emotion and/or inertia around clock changes.

Sure, but that's quite a fanciful universe you're imagining there - the feasibility of a corporation obtaining insurance to cover that offer of liability ownership has got to be close to zero.

People - usually suit-wearers - have been making this spurious claim for decades, but it doesn't hold water.

The largest of the finest print reminding you that it's 'sold as is' (or more encompassing variants that might continue '... with no warranty for fitness of purpose') means that liability remains in the lap of the purchaser / consumer / operator.

(This has been a source of immense frustration over my career - where such people have assured me that they have 'recourse' (it's always vaguely described) by spending money on proprietary products & services, rather than opting for functionally equivalent or superior free options.)

I think your third paragraph is implying a distinction (or conflating the difference?) between LLMaaS's and self-hosting publicly available models.

If it's just where it's hosted that provides the legal insulation then things like OpenRouter would give you that. (But again, I suggest that it would not.)

A weird target, the author has.

The title is 'for single node local S3' but what they actually mean is 'for minio-compatibility', which is an entirely different question.

When I abandoned minio a year or so ago, I also surveyed the options, and settled on Garage. It lacked the GUI, but felt about the same complexity as minio. Perhaps a smidge more complexity, as I moved to 3-node and 5-node separate instances of garage, running as containers under Nomad.

I don't recall it being onerous, but I was looking for some basic S3-alike capabilities, not just minio-alike.

(How many people set out to build an object storage system with some number of AWS S3 primitives, but primarily try to match a third-party proprietary system's foibles?)

> So, Garage does work, but gosh…it is not just a drop-in replacement in terms of code changes.

I think in terms of actual code that uses local S3, it pretty much was a drop-in replacement. (I have multiple distribution/registry, Grafana Loki / Mimir, influx3 - all backing onto my object storage system, and the config changes there were modest - key+secret, and url - just as you'd expect.)

> collecting different coloured stuff to convert into other different coloured stuff.

You are loosely describing almost every computer and board game ever made.

I say this as someone who has a few hundred hours in NMS, and also appreciates people spelling colour properly.

From TFA

> VMware to Proxmox migrations are not affected ...

Amusingly - and acknowledging tiny scale and modest automation requirements of home lab compared to enterprise - as I started migrating to Proxmox a year or two ago, the process of shuffling VMs off my ESXi servers and onto Proxmox was surprisingly painless. Effectively mount the ESXi as storage systems, and then 'copy to here'.

IIRC the only small challenges were a conservative choice on target VM's CPU type (Proxmox seems to dislike defaulting to 'host' CPU) and the network / SCSI controller defaults. I assume designed to prioritise robustness over performance.

All automatable, I'm sure.

Pavers for $40-45 - are going to be pretty unattractive grey concrete (well, cement) ones, right?

Even Bunnings (albeit marketplace) has 100mm geogrid for $20 / square metre.

Most local vendors have 'call us for pricing', but I've found a few others in the $10-20 range. Obviously, yes, in-fill on top of that - say $250 a cube depending on your tastes, so add $12-25 per square metre.

As per sibling comment - with some fabric underneath, and a modest amount of ground prep, installation of this stuff sounds fast and easy.

I saw some examples of this while travelling in Japan last year, and am keen to replicate. I suspect, like a lot of things, the local product there is superior to what I could find back home here in AU.

At some castle courtyard, we were walking around on a smooth-white-gravel surface, and I didn't immediately register how different it felt.

Stare at the ground for a few moments, and notice some of the small (15-20mm) off-white pebbles are perfectly aligned on a grid pattern.

Squat down to investigate, and they've got these corners of the plastic mesh geogrid topped off with little white caps that are almost indiscernible from the rounded white aggregate they're using as infill. It was almost like seeing a random dot stereogram, except completely regular (and no dinosaurs) of course.

The math is pretty interesting, and TFA didn't touch on this aspect I don't think. I'm looking to use 10-20mm irregular shaped scoria on a large-ish area, and the heuristic evidently is that your maximum aggregate size should not exceed one third of the geocell depth - so I'd want 50mm depth at most there, sitting on solid-ish sub-layer.

(I believe that heuristic goes out the window if you've got regular shaped gravel.)

The other ratio to consider is aggregate size to cell size, and that, in turn, is dependent on load and slope. Then there's the mechanical attributes of your in-fill (will it slowly crush over time, with expected loads - for softer rocks you'll definitely need a geotextile above your sub-base and below your geo-cell.) All tremendously more complicated than the 'few wheelbarrows of blue metal' I grew up with.

I don't use gcc directly - not in a long while - but almost everything I rely on uses it, and it's hugely encouraging to have the stewards of this project contemplate, and then determine to have this policy.

Meanwhile, I don't know who quotemstr is, but they don't sound sane in any of the exchanges in this thread.

I was sure that pre-2020 - going back 40y or so prior - VLP's were also generally regarded as coming under the umbrella term 'vaccine'.

In what way are they not a vaccine?