“If Paul McCartney comes to my store and wants it, I’ll give it to him for free.”

Who wouldn‘t.

That‘s about the only things it can do accident free indeed.

I‘m using Al Dente on my MBA that I bought in jan 2023 and it gives me some peace of mind whenever I use it plugged in for longer hours. Have it set to keep the battery to 90% charged, which for me is enough juice to use my machine unplugged when I need to. Every once in a while I disable Al Dente to charge to 100% for calibration purposes. If this whole process really does something good for long term battery health I don‘t know, it should at least do no harm.

It helps to keep a backup account on another instance, in case there is an issue with your main server. You can export your settings and subscriptions from your main account and import to another Lemmy instance.

Each instance of Lemmy has their own list, like so: https://feddit.org/instances https://feddit.nl/instances

This seems to be fixed indeed, can confirm! Good job 💪

Without an installed desktop environment on your Pi, you will not be able to use GUI apps, not even remotely. You would have to install it on the Pi first.

Thank you so much 💪 😄

After all, a stubborn oil filter will be the least of your concerns then 😅

Interestingly enough - I checked again. The message is different when trying to edit a comment. I tried for testing purposes with my comment here: https://feddit.org/post/7542299/4550121

Mlem gives error message when pressing the copy button “The operation couldn’t be completed. (MlemMiddleware.ApiClientError error 2.)” In the message itself, it says "response error: ApiErrorResponse(error:“language_not_allowed”) with status 400

I finally edited the comment with the feddit.org default web interface, and it worked fine.

Version info of the instance: BE: 0.19.5 Mlem app: 2.0 (222) (weekly beta Testflight)

Editing a post or comment sometimes currently fails for me with the following message:

The operation couldn’t be completed. (MlemMiddleware.ApiClientError error 2.)

Is this something that is already on the roadmap to be fixed?

Hell seems like a good comparison, indeed

Yes, especially with macOS, we need a Snow Leopard 2.0 moment.

Hello world!

You could setup a new, empty VM and use it as a download only machine for packages, although it makes the process a bit more complicated.

I found this, maybe it is a suitable solution? https://unix.stackexchange.com/a/408348

Summon the poop knife

Did you try to reboot the watch? I assume this would fix it.

Don‘t stop believing, we are the champions of another brick in the wall on the highway to hell

iirc the display engines are built into the AXX chipsets. As only pro phones get a pro chip, Apple probably does not add the capabilities to drive displays at higher refresh rates to the non-pro silicon. So even if the display itself could go higher, the hardware to drive it is missing, not locked in software.