HN user

section_me

76 karma

$argon2id$v=19$m=8192,t=2,p=4$9ZkXRhw89+aLS9A/Bb9eEw$H212a4HKLPGJ9ABnlBrLTvTrUvrAVk13

Posts7
Comments34
View on HN

I got an LLM to analyse all of my messages and e-mails from the launch of gmail to work out my writing style, it says I heavily favour em-dash's. I used to work in the industry of type settings and press and publishing. I even use — in HTML when I have to write it nowadays. em-dash is not a LLM thing. It's just most people don't know how to use it. It also said I'm wry. Go figure.

As someone with the ID 1653, I've totally given up on the thing. I've even created my own rust based forge, ironically, hosted on github at the moment.

Same can be said for people using LLM agents to complete jobs faster than humans ever possibly can. It's not like they just fluked it. They've learned how to harness the capabilities of the tech. Now companies are introducing this stuff as a normal workflow but they are clueless as to how it actually works and expecting 10x output from people.

Matter turned into a cluster fuck of devices. Use you're android phone to provision a device and connect it to your setup, most people use Google Home or homeassistant, smartthings is also an option, maybe others. But it's only to onboard the device for the most part. It'll still connect to your WiFi, give you next to no visibility as to what's going on in a failure and no interface to control it should your controller go down.

It's also not very well supported in things like homeassistant, despite what they say.

A big thank you to the creator. Was one of my goto sites to debug IPv6 issues on random devices over the years.

The post man always bent our magazine and pushed it in the cat flap making the included disk useless (even though it was clearly marked "DO NOT BEND!"), so I remember having to type everything out and sometimes correct the typos introduced into the print version. Fun times.

Or the mitigation of someone running unsigned code on your product using an embedded pi.

Stop some ways supply chain attacks can happen.

Probably some other use cases I've not considered too.

Yes. If you have physical access, as this requires you to pull a GPIO pin down to enter the mode required for the setting on the one time programmable memory.

Documentation states: WARNING: Modifications to OTP are irreversible. Once revoke_devkey has been set it is not possible to unlock secure-boot mode or use a different private key.

Possibly off topic,

I actually registered the org oci-base (https://github.com/oci-base), when Docker Inc. announced the registry fees.

In part as I've been annoyed with multiarch and docker/registry in the past.

Then to top it off the official registry has/is taking ages to support signing/attestation.

Plan is for it to be contributor driven, and RFC style requirements following best practices.

Not had much time to work on it lately, kids, Easter, etc.