narc0tic_bird

I have several components in my network that are at least 6 years old. Is that a problem..?

full mirrors of YT

Yeah...not going to happen.

Sounds cool, I just fail to understand how this takes Cinnamon "out to the real world".

What's Ullr?

Sounds about right. There are some valid and good use cases for "AI", but the majority is just buzzword marketing.

The main thing (by far) degrading a battery is charging cycles. After 7 years with say 1,500 cycles most batteries will have degraded far beyond "80%" (which is always just an estimate from the electronics anyway). Yes, you can help it a bit by limiting charging rate, heat and limit the min/max %, but it's not going to be a night and day difference. After 7 years with daily use, you're going to want to swap the battery, if not for capacity reduction then for safety issues.

Technically, wired charging degrades the battery less than wireless charging, mainly because of the excessive heat generated by the latter. The same way slower wired charging generates less heat. Lower and upper charging limits also help (the tighter the better).

But I personally don't bother with it. In my experience, battery degradation and longevity mostly comes down to the "battery lottery", comparable to the "silicon lottery" where some CPUs overclock/undervolt better than others. I've had phone batteries mostly charged with a slow wired charger degrade earlier and more compared to almost exclusively wireless charging others. No battery is an exact verbatim copy of another one. Heck, I had a 2 month old battery die on me after just ~20 cycles once. It happens.

Sure, on average you might get a bit more life out of your batteries, but in my opinion it's not worth it.

The way I see it with charging limits is that sure, your battery might degrade 5% more over the span of 2 years when always charging it to 100% (all numbers here are just wild estimates and, again, depend on your individual battery). But when you limit charging to 80% for example, you get 20% less capacity from the get go. Unless of course you know exactly on what days you need 100% charge and plan your charging ahead of time that way.

Something I personally could never be bothered with. I want to use my device without having to think about it. If that means having to swap out the battery one year earlier, then so be it.

The article links an article from March '24 talking about the introduction of these devices that contains this part:

The scanner that Adams and police officials introduced during Thursday’s news conference in a lower Manhattan station came from Evolv, a publicly traded company that has been accused of doctoring the results of software testing to make its scanners appear more effective than they are.

So they could never be trusted but were still allowed to proceed.

I expected something more shocking when I read "working with Russia".

Kagi uses multiple search backends, and of course it needs to forward search terms to these backends. These backends probably can't trace the searches back to the individual Kagi user though, but Yandex could still analyze search trends for example.

What's worse is that - unless they use Yandex' API for free - customers indirectly (and likely unknowingly) support a Russian company with their paid Kagi subscription.

Kagi should at the very least release a statement about this claim.

Happy cake day!

Bitwarden keeps working just fine.

I'm no expert here, but I'm pretty sure branch prediction logic is not part of the instruction set, so I don't see how RISC alone would "fix" these types of issues.

I think you have to go back 20-30 years to get CPUs without branch prediction logic. And VSCodium is quite the resource hog (as is the modern web), so good luck with that.