That shoddy code rots when you update the compiler. (And occasionally good code, depending on what rules the compiler wants to start enforcing)

Well, that diagram brings up an interesting point. In fediverse if the host dies the federated content can still live on (theoretically, I haven’t checked to see if they cull content from dead hosts) but ATProto would dictate that the host is missing and therefore all content associated with the host is now immediately 404.

I could appreciate a client certification that is optional, like a list of approved clients on their website or something along those lines.

It should not be enforced by killing the client. I like security, but I enjoy software freedom more.

Llvmpipe is enabled in mesa at compilation time and actually modifies the swrast_*.so the last time I checked. Not runtime configurable. Also, I know at one point it had issues running on 32 bit machines. Not sure if that’s still the case.

Just add a new user

Not sure about the Eco tank line, but the smart tank line botched the IPP interface. Ink level reporting is always wrong and printer status is regularly wrong. Exposed settings are limited to push people to the app.

I’m currently use RiMusic, but I wish something would automatically sort through my ListenBrainz recommendations

We’ll have a timeline for the plan to make the plan by next quarter

Was actually considering buying premium now that I use YouTube for music more than Spotify, but then the ad stuff happened and now this. Going to avoid it out of principle now.

Sounds like it would specifically be APRS if they were. Neat protocol. Unfortunately no encrypted traffic was allowed last time I looked into it.

Wordpress

Ah, so the kernel actually uses mailing lists. You need to use the get maintainers Perl script to get the people you need to send the email TO and then send it to them with the dri-devel list CC’d.

That wouldn’t be accepted as is, but those sound like tunables. They could be exposed as kernel parameters. May be worth submitting the patch as an RFC just to call attention to it.

What modifications were required? The good part of a rolling release is that upstreaming things means you only have to deal with manual fixes for like 2 or 3 updates.

Dude tried doing that at the Dallas airport recently as well. I do believe they should be getting a larger cut but it’s sketchy as hell to not have anything backing the ride.

They’d update it, but they are afraid it would no longer work as well

I want the statistic on how many Google employees use ad blockers now. It’s basically a necessity.

Because ARM was built to be cheap.

BIOS nowadays is basically a bootloader shim in EEPROM. The majority of the ARM ecosystem wanted flexible and cheap devices. This promoted the use of a small ROM loader burned into the device and a removal of basically all EEPROM from the SoC.

The flexibility came back through the use of a secondary bootloader layer normally stored in the devices primary storage. Most manufacturers use u-boot or coreboot on an SD card or eMMC. Android standardized this as part of their partitioning scheme. All devices have a dedicated bootloader partition housing the secondary bootloader and any additional boot artifacts.

Then phones became wildly expensive and invalidated most of this.

Also, do you think it’s possible that this way of doing things will come to the computer, with ARM hoping to gain a good share of the market and all?

It already has. Most of what ARM is doing to be cheap was already pioneered by PowerPC.

ARM EBBR specifications attempt to standardize this boot flow somewhat, introducing a standard EFI shell in u-boot. This does not solve the dependency on the secondary bootloader, and it doesn’t prevent people from shooting themselves in the foot. It just makes distro interactions with the secondary bootloader more standardized.

This is a short term loss for a potential long term improvement. By eliminating dependency on translation APIs they can force the use of more open solutions like oneAPI which is even getting buy-in from companies like Imagination.

Keeping cuda alive is a bad idea.

The bot avoids roasting torvalds but will roast maintainers. That’s a little odd, but I guess it keeps it out of the news.