No worries. That’s interesting, I haven’t heard of the increased number of nail infection cases during and after the pandemic. Actually, I haven’t been vaccinated for COVID, because I didn’t have to go somewhere that required the vaccination, and I opted for remaining inside at home most of the time during the pandemic.
Frankly, the PinePhone is far from being obsolete. First of all, there are already many PinePhones in the hands of their owners, and we simply must make sure that, from the software side, they will work just fine in 10 or 15 years from now. Next, I think it’s important to differentiate the obsolescence on different levels, i.e. on the software level, on the hardware level, and on the platform level, to be precise. Modern Android phones quickly become obsolete on both software and platform levels, unfortunately, because they’re pretty much throwaway devices intentionally treated by their manufacturers as short-lived projects whose sole purpose is to make money for them. Those Android phones are far from being obsolete on the hardware level, but their closed nature makes it pretty much impossible to do anything to prevent the overall obsolescence from happening. It’s also an incredibly massive waste of the natural resources and a huge source of global pollution, if you agree.
On the other hand, the PinePhone may easily be considered obsolete on the hardware level by modern standards, but the open nature of both hardware and software, combined with the current state of open-source software support for the Allwinner A64 SoC in the upstream projects, is what makes it nearly impossible for the PinePhone to become obsolete on the software and platform levels. The only missing piece to the puzzle is to make the PinePhone supported at the same level as the A64 in the upstream projects, together with implementing a number of missing features.
As an example of avoided obsolescence, we could take very old i486 or Pentium PCs from the early 1990s that can still run modern mainline Linux kernel just fine. Yes, they’re very slow by the modern standards, but the key is that even very old PCs can still work, and an old Pentium III or Athlon XP may still be usable for some purposes. Actually, old PCs from the Athlon64 X2 era are still very usable, for example.
The PinePhone is still a very nice piece of hardware, despite its rather underpowered SoC and modest amounts of RAM and eMMC storage, according to the modern standards. It’s all generally usable, but many more software optimizations and improvements are still needed to make the overall user experience much better. Let’s also remember that standard PC hardware and even server hardware from 15 or 20 years ago was much, much weaker than the PinePhone, yet people used it just fine and did many incredible things on it. These days we have much more powerful hardware, but modern software tends to be bloated and inefficient, with many layers of abstraction that allow hyperproduction of even more bloated software. 
In other words, I intend to fulfill the promise you described, by eventually upstreaming all that hasn’t been ustreamed yet. I’ll also implement some of the missing features for the PinePhone, such as the charge-only mode, which I already got implemented to about 50%. Here’s a short video that shows the charge-only mode in action, running under simulated conditions, of course.
Just to clarify, charge-only mode isn’t the “mysterious” new feature I mentioned in my earlier posts.