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.

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

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.

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.

TFIDF and some light rules should work well and be significantly faster.

Everything loops back to steam in the end. Solid state thermoelectric devices have been around forever, and before that we had the idea of using thermal energy to augment magnetic fields and jump to kinetic energy without any intermediary conversion. All very low yield results, but we’ve tried it anyway.

Keep thinking about it, we need all the brains we can get, but don’t write it off as a novel idea that the other egg heads just haven’t gotten around to solving yet.

Data centers will probably be the only practical application. Consumer electronics will probably barely produce enough energy to power the regulator and tie-in circuit just to feed back into the pwm driver for fans nowadays.

Some internet funeral aesthetics

Lol, changing the country of origin doesn’t constitute innovation from a consumer standpoint…

Now if this was using 5nm or chiplit or any of the other buzzwords of the day it could be marketed as innovative in the modern sense of the word.

Realistically there is no innovation left for ARM platforms. They all use the same core schematics. They only control data flow and peripheral IP as a manufacturer, unless they feel like building their own core from the spec (nobody really does that anymore as ARM has been desperately trying to standardize everything). The most “innovation” I’ve seen has come from stubbornness around keeping legacy bus architecture around instead of adopting AXI (even when all the IP they are trying to use already uses AXI and they keep having to make translation hardware).

Fuck it. Gun it at the brick wall. Jerry’s rigging up an emergency break as we speak. Don’t mind that the last piece to said break may be missing.

- Man who will probably die before we hit the wall

I was working at a company at one point that got a contract to build something I viewed equivalent to malware. Immediately I brought it up to several higher-ups that this was not something I was willing to do. One of them brought up the argument “If we don’t do it someone else will.”

This mentality scares the shit out of me, but it explains a lot of horrible things in the industry.

Believing in that mentality is worse than the reality of the situation. At least if you say no there’s a chance it doesn’t happen or it gets passed to someone worse than you. If you say yes then not only are you complicit, you are actively enforcing that gloomy mentality for other engineers. Just say no.