skilltheamps

How does this part (which is what the headline refers to and presumably the most outrageous inspection finding)

At one point during the examination, the air-safety agency observed mechanics at Spirit using a hotel key card to check a door seal [...]. In another instance, the F.A.A. saw Spirit mechanics apply liquid Dawn soap to a door seal “as lubricant in the fit-up process,” according to the document. The door seal was then cleaned with a wet cheesecloth

have anything to do with the opening of the article

Just last week, a wheel came loose and smashed through a car, and earlier this year the door from a 737 Max aircraft broke off mid-flight

???

The article misses the whole point, which is that the audit did not uncover the sources of these incidents.

Those are symptoms of sitting at that operation point permanently, and they are a of course a concern. What I'm after is that people think that energy gets put in to the battery, i.e. it gets charged, as long as a "charger" is connected to the device (hence terms like "overcharged"). But that is not true, because what is commonly referred to as "charger" is no charger. It is just a power supply and has literally zero say in if, how and when the battery gets charged. It only gets charged if the charge controller in the device decides to do that now, and if the protection circuit allows it. And that is designed to only happen if the battery is not full. When it is full, nothing more happens, no currents flow in+out of the battery anymore. There's no damage due to being charged all the time, because no device keeps on pumping energy into the cell if it is full.

There is however damage from sitting (!) at 100% charge with medium to high heat. That happens indipendently from a power supply being connected to the device or not. You can just as well damage your cells by charging them to 100% and storing them in a warm place while topping them of once in a while. This is why you want to have them at lower room temperature and at ~60%, no matter if a device/"charger" is connected or not.

(Of course keeping a battery at 60% all the time defeats the purpose of the battery. So just try to keep it cool, charged to >20% and <80% most of the time, and you're fine)

"overcharging" doesn't exist. There are two circuits preventing the battery from being charged beyond 100%: the usual battery controller, and normally another protection circuit in the battery cell. Sitting at 100% and being warm all the time is enough for a significant hit on the cell's longetivity though. An easy measure that is possible on many laptops (like thinkpads) is to set a threshold where to stop charging at. Ideal for longetivity is around 60%. Also ensure good cooling.

Sorry for being pedantic, but as an electricial engineer it annoys me that there's more wrong information about li-po/-ion batteries, chargers and even usb wall warts and usb power delivery than there's correct information.

It is not that easy to understand what you want, to me it reads like you want something like Nextcloud - i.e. your own little cloud, where you can put all your stuff, and view it through the webbrowser or the nextcloud apps, and also keep selected parts of your stuff in sync with your devices (or automatically upload photos take with your smartphone for example).

Backup of Nextcloud (or whatever you want to use) is a seperate topic. Any incremental backup tool would apply though, so there's much to choose from. I personally use btrbk which uses Btrfs Send+Receive to push incremental snapshots to an offsite server.

that doesn't require I keep a full local copy of all the data

If you don't do that, the place that you call "backup" is the only place where it is stored - that is not a Backup. A backup is an additional place where it is stored, for the case when your primary storage gets destroyed.

It is not a fork aiming to replace it. It is rather a spin with saner defaults to cater to companies as customers. The product which shall carry ondsel financially is their freecad compatible cloud offering, and the hope is to use that for elevating freecad itself too. They need their spin to be able to ship an ootb experience fitting their motive and brand. So if you would like a less confusing experience it might be something for you. Currently there's a lot of borderline deprecated and also redundant functionality in freecad, so I hope that ondsel's cleanup mantra will make it to the ootp upstream experience as well.

As far as I remember ondsel is working on upstreaming realthunder's approach to freecad, but it is a lot of work to polish up because it touches so many parts of the application.

Here is a nice interview with one cofounder of ondsel where I have this information from: https://shows.acast.com/ohm-podcast/episodes/ep-12-brad-cto-of-ondsel

Just recently I listened to a very interesting interview of Brad Collette, the founder of ondsel. You can find it here https://open.spotify.com/episode/2TwCcFWC8VwQ4ctjBTZ0Xd?si=pNjFQOI0RCe0v1MU47mwpg

and here https://shows.acast.com/ohm-podcast/episodes/ep-12-brad-cto-of-ondsel

The second statement is not true, the standardization is flatpak portals and they by now cover almost every aspect of the system. The screenshot api is this: https://docs.flatpak.org/en/latest/portal-api-reference.html#gdbus-org.freedesktop.portal.Screenshot

In terms of helluvalot less critical - is it really though? Remember that the app on your phone is also witten by them, closed source and does whatever they want with your clear-text messages. If the trustworthyness of a messaging vendor is part of the critical-ness question, e2e encryption does not add anything: Either you trust them and could also do so when they process your message on their server, or your don't and they could indeed spy on you on the proprietary client app.

End 2 end encryption is only a real benefit when the ends actually belong to the user, i.e. theres transparency about the ends being clean, which can only be shown for open source ends. If the ends are potentially compromised, there's so security / privacy guarantee.

But why?