cr3ative

I can imagine this just fine. I can also imagine the same thing, but a dragon is there, if that helps.

Right. This unfortunately reads like a human process has been set up where automation should have been set up, and now that hand is being forced.

The hand-waving away of certbot/ACME at the very end of the article only really goes to show that it hasn't been looked in to properly for whatever reason.

Probably just scanned in with classic OCR.

I feel rug pulled by the fact this turned out to be external mods to the game.

“My installation is non standard” should probably be disclosed early.

I’ll look to do so, and appreciate your pointers. Thank you for being kind!

This is in such a thick academic style that it is difficult to follow what the problem actually might be and how it would impact someone. This style of writing serves mostly to remind me that I am not a part of the world that writes like this, which makes me a little sad.

Grids are widely interconnected. Problems on one grid can and do cascade to another.

No? You just fill in a form. https://www.gov.uk/guidance/register-as-a-keeper-of-less-tha...

I think in this case it’s shelf life. Very little discharge for a very long time.

The transcript was a good read, I also don’t prefer audio.

Admittedly I can skim read quite well though.

Causing annoyance by posting AI slop then having to justify it should not be mistaken for entertainment, it’s closer to trolling.

I feel like some conclusions of the intent here are born from being very well versed in the actual outcomes, including what I can only assume was a very painful end to someone's life.

But on the surface level of it, it's a scientist doing something knowingly incredibly dangerous and dumb for no particularly justifiable reason.

We've all felt a bit like that at some point. We just probably didn't have a core and a screwdriver.

Yeah, it’s blocked by NextDNS too

This is only part of your post, but VueScan is very good for older scanners on newer OSes. It’s paid software but I like it, avoids the landfill.

Nothing wrong with an older scanner after all - the tech was already impressive 10 years ago!

And how many times has this worked?

I’m not overly surprised that in a startup, there was no mechanism built to split off a small defined portion of their fleet to a different, independent cloud.

Bit different to changing the whole infrastructure out for every car in a disaster recovery situation.

I think this is the kind interpretation; he doesn’t seem to have anyone around him who he trusts to tell him he’s incredibly off base. He’s in an accidental echo chamber.

The theme here with “leave if you disagree”, though with decent terms, correlates.

Yes, but unfortunately they are all Matt

The seller is revk (AJK) who came up with the Faikin - it's his github :)

It's really pleasing to me how the "analogue loophole" continues to work. Previously, recording music through the Line Out, or what have you. Now, using a robot to press the supplied remote. It's delightful.

That sounds like a lot of work which could lead to people complaining that their money didn’t go where they wanted it to go. This is simpler.

The font hinting(?) causing merged arrow characters on this article made me think Wordpress themes had started using entirely new characters to represent template steps.

Not what I'd expect in a formatted code block.

I don't like how this feels - kind of like Product Hunt, Digg, Reddit, etc, and the implications of the "power users" there too. I'm not sure this is something to encourage.

Just after I upgraded 105 microservices to 1.21, naturally. Ah well, it was a glorious few hours being up to date!

I feel silly saying it, but they’re not designed to run without a controller. He has been fighting this for two blog posts now.

These aren't meters (in that sense) - generally they're reading from CT clamps placed on the tails from your meter.

They're generally airport codes, so Philadelphia and Amsterdam... unsure about FRE.

This is a very neat visualisation. Even if a little CPU intensive expanding areas! I'd hope the Chrome team has something similar internally, it looks really useful to understand the attack surface, as it were.

This reminds me of a service I recently found that was routinely crashing out and being restarted automatically. I fixed the crash, but it turns out it had ALWAYS been crashing on a reliable schedule - and keeping the service alive longer created a plethora of other issues, memory leaks being just one of them.

That was a structural crash and I should not have addressed it.

"on error resume next" never died, it just became serverless!