Looks like they did well. All of the attacks required physical access and glitching the chip. That should be good enough for a lot of use cases.

Yes and no. A lot of the projects I work on the majority of the engineers are funded by companies which have very real commercial drivers to do so. However the fact the code itself is free (as in freedom) means that everyone benefits from the commons and as a result interesting contributions come up which aren’t on the commercial roadmap. Look at git, a source control system Linus built because he needed something to maintain Linux in and he didn’t like any of the alternatives. It solved his itch but is now the basis for a large industry of code forges with git at their heart.

While we have roadmaps for features we want they still don’t get merged until they are ready and acceptable to the upstream which makes for much more sustainable projects in the long run.

Interestingly while we have had academic contributions there are a lot more research projects that use the public code as a base but the work is never upstreamed because the focus is on getting the paper/thesis done. Code can work and prove the thing they investigating but still need significant effort to get it merged.

It’s one of the reasons I enjoy working on open source. Sure the companies that pay the bills for that maintenance might not be the ones you would work for directly but I satisfy myself that we are improving a commons that everyone can take advantage of.

So this is like extending mastodon replies into your blog post, but with more syndication options?

I don’t quite follow what this is. Is it a from scratch implementation of the vscode experience or a fork which has removed propriety bits and telemetry?

I work for a company that makes money supporting FLOSS. Our members pay fairly hefty membership fees because they have a vested interest in their chips being well supported by Linux and the wider ecosystem. That money funds common projects they all benefit from all well as numerous maintainers in projects keeping those projects ticking.

The engineers on the project I mostly work on are predominantly paid to work on it. We value our hobbyist itch scratchers (~10% off contributors) but it’s commercial money that keeps those patches reviewed and flowing.

Magic Wormhole - it’s been around awhile but it’s super useful for moving files from your internet connected server to your phone without going through multiple hops copying stuff to you local machine and finding a cable.

That’s how it starts. Before you know it you’ll be buying no-name smart bulbs from Ali Baba and investigating custom firmware for full local only control.

Other way around. Loyalty cards have always been about getting that sweet sweet data about customer habits.

Something like this: https://apt.izzysoft.de/fdroid/index/apk/de.westnordost.streetmeasure

ETA: oops, I didn’t realise this uses a non-free component.

Why do the $20 subscription when the API pricing is much cheaper, especially if you are trying different models out. I’m currently playing about with Gemini and that’s free (albeit rate limited).

I wrote a bit of BASIC on my Spectrum but there was a reason they had keyword shortcuts on that keyboard. It wasn’t until I got my Dragon 32 which had I proper keyboard that I really got into coding.

My dad failed his 11+ so was sent to a technical school so he actually learnt how to lay a row of bricks or how to beat out lead flashing. He did end up doing a PhD in Physics but I suspect his early school years explain why he’s always been much more practical than me. My wife was a stage tech during uni so I’ll happily defer to her for joinery. I can just about solder a copper pipe or big pads on a PCB.

Buy games from indie developers on platforms like itch.io. You may have a negative view of the other people involved in funding and marketing a triple AAA game but they all contribute and get a share of the retail price. You don’t get to pick and choose who deserves to get their slice.

It’s interesting they’ve gone from a simple reskin to a downstream fork. I’m guessing there won’t be much of value to find though.

Basically your only other option is to find the keys for each BluRay you own yourself. I did go through the hoops a while ago and wrote it up: https://www.bennee.com/~alex/blog/2011/04/18/playing-blu-ray-under-linux/#playing-blu-ray-under-linux

However it’s a pain sourcing the encryption keys you need for each disk. While I work hard to prefer FLOSS apps over their propriety equivalents in this case I’m happy to pay the small fee for a perpetual licence of MakeMKV.

It works well enough with the rasbian OS derived from Debian. However pure Debian currently doesn’t have all the user space components to take advantage of the video decoder needed to play things smoothly. Currently I have Bookworm installed on the system but I run Kodi out of a docker image: https://github.com/stsquad/dockerfiles/blob/master/distros/raspios-bullseye/Dockerfile

Is the hardware support for Raspberry Pi still out of tree or can I use an upstream build now on my Pi 4?

curl --upload-file thefile.tgz https://transfer.sh/somename

Then paste the resulting URL to the person who wants the file. Another useful app is the magic wormhole and I think there are some web front-ends for it.

Alcohol isn’t that great as an organic solvent. Are you using the air fryer to evaporate? That must be a fair fire risk!

Butane on the other hand is a good organic solvent and will evaporate at room temperature (just don’t evaporate it in a room or near any heat source).