geerlingguy

Quick, rename it to "HackerDiscussed"!

I know my older APC UPSes do weekly self tests, but I guess newer equipment does more frequent self testing? And of course they're all internet-connected meaning clocks are within a few hundred ms of each other.

It also made me think about how many GitHub Actions I have that kick off on Sunday morning at a specific time. I try to vary the time/day for those jobs but I'm guessing there are enough things that kick off at specific time intervals to make an impact at the top of an hour, or at :15, :30, :45...

This particular fan is a high quality / high CFM fan meant for servers and industrial gear.

Usually these boxes are at remote sites or in already-loud test racks, so the noise isn't a concern.

The Noctua is rated for lower CFM, so if you are already at a slim margin for thermals, switching to a quieter fan is not necessarily a good idea.

I do wish more manufacturers would go to 60 or 80mm fans instead of the 40mm ones common in this gear. Power supplies especially!

Used, AFAICT. New is a bit more.

The best way is to measure temps before (ideally over at least 1-2 hours), then to measure temps the same amount of time after and compare.

In the case of this Rb oscillator, it is temperature sensitive, but also built for pretty extreme environments.

I'm not too worried about this particular application, because the clock will be in an air conditioned environment, and I'm monitoring the clock accuracy to +/- 2ns from another GPSDO / rubidium clock. The performance before and after the fan swap is within my measurement noise for 24H, though I haven't done 30+ day measurements and ADEV comparison. Still working on a consistent test setup.

I don't even think they're driving hype, they just have a problem common in the hardware world, they are far too optimistic in their shipping timeline.

Versus a company like Bambu who seems to ramp up production now, in advance of selling the product.

> Formlabs will happily upsell the "Form Wash" for this for another 699

(A separate aside, since the main ones were addressed: Formlabs also launched a new "Wash+Cure" station that does wash and cure for $199, instead of their standalone (but better, of course) units that cost something like $1000 together.)

I have a blog post up for those who don't like extracting the relevant info from a video :)

https://www.jeffgeerling.com/blog/2026/formlabs-form-studio-...

You need to buy a tank anyway, which is $50 or so — that works with their new Alpha resins. The slightly more expensive tank is necessary only for their engineering-grade resins (only a couple are certified for the Studio 1 so far) and 'OMM' (Open Material Mode), which as mentioned above, comes out of the box on the Studio 1.

(Not replying to you directly, but generally to this thread)

Scrappy builds aren't "affordable" but are more so than running Nvidia + optimized builds. You could put together a machine for $5000 or less that competes with frontier models from less than a year ago, albeit a little slower.

And cards like the $1600 (sheesh) R9700 have actually gotten more capable through community efforts at optimization, since their launch.

I think if the bubble can ever deflate/pop, and GPUs and RAM back off a bit, we'll see the dam burst for local AI.

Right now it's only accessible to people who can justify the costs.

Once you do get measurement down to nanoseconds, you quickly realize how 'bad' so many clocks you thought were good actually are. Lots of GPS modules with massive sawtooth behavior. Over a day they may be within tens of ns. But over a minute, a lot worse!

Similarly Remi for the RedHat-derivative side of things: https://blog.remirepo.net (he's on vacation, but apparently is pushing updates now).

Ah, indeed... I thought the GA push was the final step but there's another manual process between that and updating the Docker Hub image tags: https://github.com/docker-library/official-images/pull/22541

It should definitely have a 'high impact' workflow that bypasses some of those manual steps.

A PR was posted within a minute or two of PHP's source code update. Then within a minute of the PR's CI job completing, it was merged, and the build took a while but is now complete: https://github.com/docker-library/php/actions/runs/396158697...

It would not be easy (or reasonable) to take a public build like that private to build a 'secret' image version, and I'm not sure GitHub even has the capability to do that. I would not trust a build pushed to Docker Hub separate from the established / public / auditable process they have in place.

Even some smaller vulnerabilities are spread through hosting companies pretty quickly within a day or two prior to public release, to give teams time to make sure staff will be ready to patch immediately.

The wider the pre-release news spreads, the more chance you get someone who will spill the beans (intentionally or not).

One pattern of AI-assisted writing I hate is that technical articles now read as Atlantic journalistic tech-noir stories, which require scrolling through 20+ pages of content to get to the meat of a post.

I'm using Remark42; some downsides but somehow, spam has not been a big issue for me. https://remark42.com

I thought they were down earlier, but apparently they were just pre-announcing being down in about 30 minutes, until they finish patching their servers.

I've seen a number of notifications on X and Bluesky of people taking their sites offline, though. Supposedly Cloudflare is providing all customers a WAF rule that will mitigate the exploits they've been able to see so far (though they mention, this is not full protection—patching is still required).

Only 'parts' of their website are down currently (e.g. download pages, linked from the home page: https://obsproject.com/welcome-redirect returns a 502).

Tons of sites are currently offline to hopefully prevent an attack until they can update PHP; just the things I've run into this morning: OBS, TicketTailor, tons of wikis...

That was how a cluster of Java servers at a former employer avoided the Log4j vulnerability. Though I think they'd be on at least PHP 5 by now (maybe even PHP 7!), so they can't dodge two bullets.

There are some vulns that warrant a pre-release announcement (in the Drupal community, this happened for a few of the more serious fixes). And prior to the public pre-announcement, there is often informal coordination between some of the larger hosting providers or giant companies who can help roll out the patch more quickly.

This should definitely be opt-in.

I thought of the National Institute of Standards and Technology... acronym/naming overload, like using "STL"!

As a noob to chip design, I've always wondered; why can't chip packages integrate filter caps at the outputs directly? Instead of having boards put a ton of them on the PCB as close to the chip connections as possible?

Is it a matter of current handling? Or repairability (easier to replace one external smoked cap than a whole IC...)?

(I know the filtering here is a little different in purpose, but it just made me wonder).

This is a more interesting one, though; some people might dislike Adobe's practices enough to be okay with an AI reimplementation of their suite.

I just wish I could still buy a 'Creative Suite' one off and keep using it instead of having to subscribe to these apps.

I assume any computer connected to my LAN is also a dedicated attack vector for everything on my LAN in case of compromise.

Exposing any port directly to the Internet is a huge risk these days—at minimum I'd put a very strong firewall in front, and unless it's serving the general public, switch to a non standard port. It's not much but would prevent the dumb automated scripts that operate on standard ports.

A fun little easter egg - I had read it earlier on my iPad, so didn't notice the mouse interaction. I love it, reminds me of acko.net and how each page would have a unique little animated feature to play with.

This is like the perfect clock demo opposite of the classic Bartosz Ciechandowski blog post on mechanical clock movements: https://ciechanow.ski/mechanical-watch/ (I love both, just opposite in the color vs dryness, jank vs precision, "build first, principles later" approach).

But in terms of rearranging the stack vertically; is that a possibility?