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 !programminghumor@lemmy.world and not technology?

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

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.

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…

Yet another example of why we need privacy laws with real teeth.

Do you mean Computer Fraud and Abuse Act (CFAA)?

Yeah, the first 2/3rds of the article covering Naomi Wu was worth a read, but that last 1/3rd… I get her argument, but she should have left that out to focus just on Naomi.

Found the article where the screenshot came from, and wow it’s even more infuriating! The VideoLAN folks tried to work with them for months, and Unity seems to have cranial rectal inversion.

I honestly see this being a continued expectation to be a bigger issue. Two communities with the same name on different servers could be very different spaces. Giving users the ability to group them together homogenizes them in a way that is likely bad for the ecosystem overall.

I see the issue, but I still see the tradeoff as being worth it. Right now, if I want to browse technology commies I have to click into each one I’m subbed to. This means I’m going to go the to biggest one first, then second biggest, and so forth. This pretty much favors the big commies over the small ones because this is just annoying to the end user. Grouping gives those smaller ones a better chance of appearing in someone’s feed thus spreading out activity over a larger part of the lemmy fediverse.

There’s going to be ups and downs. I wouldn’t be too concerned right now.

I see the bigger problems being community discoverability, not being able to group communities together, and moderation tools.

Microsoft really needs an antitrust smackdown with their repeated behavior.

Given that the 70’s was 50 years ago, most people don’t know the details of what happened. Other than a metric conversion was attempted.

It’s both surprising and not that it was killed by republicans. And given the current nationalist furor in the party, it doesn’t have a snow ball’s chance in hell of happening in the next decade. If it was proposed, again.

It’s the difference of saying hey and HHHEEEEEEEEEEEEEEEEYYYYY! @#$@!#$!@@$@#$!