The right to repair. It’s going to require the ability to make changes to the software on the vehicle. At a minimum the ability to replace the public encryption keys used to communicate with the servers. The bootloader and software is probably locked behind signing keys; so you need to be able to disable or add your own keys. I doubt anyone has access to the full protocols used to communicate with the servers. So, the full technical standard need to be released (which is never going to happen) or reversed engineered through unencrypted traffic analysis and reverse engineering the software.

A good right to repair law could require some of that be releasable while the company is still active or all if the company goes belly up. IIRC there was a smaller EV company that went bankrupt and there was a concern that once the servers were shutdown the vehicles would be bricked. Not sure what happened in the end. In any case, cars as IOT is the stupidest idea ever created.

Neat buuUUUuuut.

Does Revolt have federation?

As of right now, Revolt does not feature any federation and it is not in our feature roadmap.

[…]

What can I do with Revolt and how do I self-host?

[…]

You can self-host Revolt by:

• Using Docker Compose and our recommended guide.
• Building individual components yourself from the source code.

It’s basically a bunch of islands.

Fukin hell, I’m in this meme. At least all my customers are engineers. So, less orcs that need slaying.

Yes, that’s in the post title.

“I decided to donate the equipment I acquired with my own resources to the chamber,” she said in statement on X, following a social media backlash.

“Obviously, neither I nor my advisers need a toilet.”

I think she really needs it because she is full of shit.

Do these designers not have children?

Their children are furry and meow. But in all seriousness, I would consider it an engineering oversight for not considering how their product is being used in real households.

Even I have to clean up when I miss; which happens max, max, 95% of the time.

You miss a max of 95% of the time? 🙃 On a related note, most people are bad with percentages.

Devin will finally learn the identity of the cow that kept mocking him.

Apple has a long history of working against right to repair and third party repair shops. This includes making it difficult for third parties to source the parts needed and changing the designs to requiring part pairing in the name of security. It got to the point where repair shops were buying broken Apple products so they could hopefully source the parts needed.

Looking through what they provided now, it’s basic stuff any third party repair shop could do if they could source the parts. It’s useful. However good electronic technicians can go beyond that and do board level repairs. But that requires schematics and diagrams. A lot of times they would have to get those through other parties who in turn got them through less than official means or violated NDAs.

Guess what Apple isn’t providing? Board level information. This is just doing the minimum the law requires them to do.

Bonus: Louis Rossmann talks about Apple’s history of right to repair [10 minute video]

And just like Taco Bell when something goes bad you get to deal with all the diarrhea.

But seriously, shouldn’t this be in [email protected] and not technology?

Robot raptors

My guess: turn failing big companies into failing little ones.

Looks like someone tried to archive an archived page. You can see https://web.archive.org/... is listed twice in the url. I just trimmed off the first one then it works: https://web.archive.org/web/20240229113710/https://github.com/polyfillpolyfill/polyfill-service/issues/2834

I’ve never made one with Sunny D, but a screwdriver is pretty tasty.

That depends. Are you looking at preserving the music without loss of information? Then you need to use a lossless format like flac. Formats like aac, mp3, opus can throw away information you’re less likely to hear to achieve better compression ratios. Flac can’t, so it needs more storage space to preserve the exact waveform.

You can use a lossy format if you want. On most consumer level equipment, you probably won’t notice a difference. However, if you start to notice artifacting in songs, you’ll need to go back to the originals to re-rip and encode.

Do you remember lycos or ask jeeves?

Yeeeaaah, that makes more sense. 😅 That would be a giant gaping vulnerability if everything was in kernel space.

Bluetooth has one of the largest network stacks. It’s bigger than Wifi. This means some parts of the stack probably aren’t tested and may have bugs or vulnerabilities. It has duplicate functionality in it. This opens up the possibility that flaws in how different parts interact could lead to vulnerabilities or exploits.

A number of years ago some security researchers did an analysis of the Windows and Linux stacks. They found multiple exploitable vulnerabilities in both stacks. They called their attack blue borne, but it was really a series of attacks that could be used depending on which OS you wanted to target. Some what ironically, Linux was more vulnerable because the Linux kernel implemented more of the protocol than Windows.

There’s talk on the Linux kernel mailing list. The same person made recent contributions there.

Andrew (and anyone else), please do not take this code right now.

Until the backdooring of upstream xz[1] is fully understood, we should not accept any code from Jia Tan, Lasse Collin, or any other folks associated with tukaani.org. It appears the domain, or at least credentials associated with Jia Tan, have been used to create an obfuscated ssh server backdoor via the xz upstream releases since at least 5.6.0. Without extensive analysis, we should not take any associated code. It may be worth doing some retrospective analysis of past contributions as well…