Looking at the supported platforms, it looks like the only one is Linux. The README has this to say about it though: "This will run on Linux; however YOU SHOULD NOT RUN THIS ON LINUX. Instead use the kernel module; see the installation page for instructions."
Is rust stable enough from 20-24 that the project would likely remain in a state to compile on a new rust tool chain? Do "Editions" completely solve this?
Pretty much. I've had a great deal of luck rebuilding older projects. You can lock your toolchain as an added protection, but `cargo clippy --fix` is often enough to fix 90% of those.
I think the only time I really struggled with a toolchain upgrade was with one of the crypto libraries that was bringing in a broken version of some SIMD code (cannot remember the exact details).
For kicks I cloned and build this with Rust 1.80 and it built just fine (a few reasonable warnings), and even bumped the edition up to 2021. The README suggests you need nightly but that's clearly not the case.
EDIT: the Rust code is actually unsoundly using MaybeUnit in a few places.
So the "tcp: fix incorrect undo caused by DSACK of TLP retransmit" done five weeks ago for the Linux kernel didn't need to happen for the Rust implementation?
I don't think this commit has anything to do with wireguard. It's a fix of a bug in the kernel TCP stack, which wireguard doesn't use. (Beware, the wireguard-linux repo is a "fork" of the complete linux kernel)
And even if it did, a userland TUN implementation of the wireguard protocol probably doesn't have the same bugs as the linux kernel one.
Sure, the standard is relatively straightforward, but the implementations have to keep up with their environment. Wireguard in Linux has to keep up with changes in the kernel to a degree, for example.
Sadly, once you get far enough in (the end of Day 6 is entirely missing), a lot of the links are broken. Kind of fitting, but it does make it harder to read.
Now for a phone that has a battery that will last that long. That would really be news. I find that I don't replace a phone because it can't function or is no longer secure. I replace it because it can't hold a charge long enough for regular daily use.
That's an inherent limitation of modern lithium batteries with a smartphone's constraints of density, size, packaging, charge current, and a bunch of other requirements. Replacing a battery every 18-24 months costs ~$75 (or 1 hour and $35 if you're comfortable with DIY), which is a reasonable maintenance cost considering smartphones cost $300-$1300. Many car owners don't sell/scrap their car until repairs exceed the value of the car, we should apply the same philosophy to smartphones.
I've replaced the batteries on several phones (at authorized places) and, while I like the idea, they all started displaying weird behavior. I guess they are glued so hard that the heating needed to open them up must cause some tiny damage. Just a guess.
I haven't had any issues with a Samsung S7, Samsung S9 (although I broke HDMI output), and Sony Xperia 5 Mark II (very pleasant to repair). iPhones have been much more troublesome for me, as I have destroyed three during repair attempts. All the issues were from damage to ribbon cables, as they are fragile and easily damaged from being bent. So I'd advise avoiding devices with tight tolerances like iPhones, and minimizing interaction with ribbon cables.
I usually use Chinese knockoffs. Brands like Cameron Sino and Nohon are growing brands who accurately state capacity, make good batteries, and don't pretend to be OEMs.
As for official batteries, California's Right to Repair law compels manufacturers to sell parts like batteries for as long as they sell battery replacement services, up to 7 years. Apple still replaces batteries for the iPhone 5S, a 10-year-old phone, so they 2022+ phones should have official batteries available for a long while (and the prices seem quite fair). Google also sells genuine batteries for the Pixel 2, a 6-year-old phone, through iFixit. Samsung only offers batteries attached to a midframe and display assembly, for the S20 and newer, through iFixit for $200+. So the former 2 brands seem like good options.
Correct me if I’m wrong but limiting my charging to 80% (and minimum to say 20%) can increase the charge cycles of a battery by about 5x. This exists on laptops (Thinkpads and Franeworks at least), phones should also offer it.
I would love if this was "fine-tunable" on iOS. On macOS there are various ways to cap the maximum charge percentage. On iOS (and macOS by default) it tries to learn your charging habits and do various things based on that, but it never actually caps you to 80%. For example, it knows I plug my phone in over night, so it charges to 80%, pauses, then does the remaining 20% right before I wake up.
This exists on Samsung. I've used it on my S10 Lite since day one and I am not sure if it's directly related but my battery is fine approaching 4 years now. All my previous phones had issues with the batter around the 2 years mark. (It might just be improved battery tech too)
