I tried to hand-solder a Hirose .35-pitch connector onto a custom OSHPark board once. Let’s just say it was a humbling experience. Thanks to a generous friend, I learned the value of solder masks and owning a home reflow oven.

Respect to whoever can do this sort of thing, but life is too damn short and my eyesight and hands don’t need the abuse.

How you solder those without dropping a blob and causing a short is a mystery.

Good to see proliferation of presence detectors. Good for turning things off when nobody is around.

In my last job I got to play a bit with the SeeedStudio mmWave presence box. What was interesting (and a little confusing) was that it took multiple add-on boards for things like on-device fall detection (for elderly). For the time I had with it, it worked fine with HA: https://wiki.seeedstudio.com/mmwave_radar_Intro/

There’s also: https://www.modular.com/max/mojo

All 418 error codes. We good.

Remembering ActiveX Controls, the Web’s Biggest Mistake: https://www.howtogeek.com/717016/remembering-activex-controls-the-webs-biggest-mistake/

If using pyenv to support multiple python versions, when creating venvs, make sure to pass --copies to it.

% python3 -m venv venv --copies

Ordinarily, venv uses symbolic links back to the current version of the python binary. A lot of tools and IDEs don’t traverse symbolic links. That flag actually copies the real binaries over to the venv.

This avoids a metric ton of hard-to-diagnose misery later on.

“It also includes optimized support for Raspberry Pi SBCs to deliver enhanced performance and compatibility.”

Have you looked into the suid bit? You can set it on the file, then change the script owner to root and it runs in elevated mode: https://linuxhandbook.com/suid-sgid-sticky-bit/

If you liked Apollo, you’ll really like Voyager for Lemmy: https://apps.apple.com/us/app/voyager-for-lemmy/id6451429762

Let’s not forget… the reason this type of licensing exists is because large cloud providers were taking a large code base and selling them as services . Often, the main path for the creators to make any money from their code is to offer a paid, managed tier, along with professional services. They would end up competing, and losing, against those cloud providers.

Not saying this kind of license is good or bad, but the reason is often not to stop self-hosting or screw contributors, but to maintain couple of the only pathways FOSS can bring in revenue.

A lot of tech people are getting laid off and looking for jobs. This makes them susceptible to social engineering efforts like this.

In the last two weeks I’ve been getting multiple unsolicited text messages saying they have reviewed my resume and have a job that would be perfect. Of course, there’s a link to follow.

If I sent someone a message like that, if they DID click on it, that would be an automatic disqualification on grounds of infosec dumbassery.

Be careful out there.

Ignore them. Send a pull request with the full source of Arch Linux.

Oh man, you would have loved a project I was working on ~15 years ago.

Sorry, I don’t have enough certifications to answer that question.

The argument in the blog post sounds like one of those technologies that says “it works great once you have a billion users! Just wait and see.”

Tried it once. It was a testing nightmare, trying to catch all the varying edge cases. Gave up and never looked back.

Wait till they find out what software ‘architects’ really do.

Anyone tempted to write a custom database should ask if they’re prepared to be in the database maintenance business.

Because that’s where they’re heading, for a really long time.

Little Bobby Tables says hi.

Thanks. On the plus side, I got to try ‘soup dumpling’ – still the best I’ve ever had. And Kaoliang, the most gut-busting distilled beverage known to mankind. OTOH, the product shipped, won lots of awards, and got national coverage for the company.

Nothing to do with timezones, but still, fun times.