skuzz

There are cheap Chinese ODMs that make trackers for companies. Used to be a "cube" branded tracker that was for keys, not sure there still is. Never used the app, just used LightBlue explorer (free app) to scan for BLE devices and noted its MAC address. The app shows signal strength.

If you have to find your thing, you just point your phone around and watch the signal until it gets stronger. Same process the fancy apps use without the creeper crap. This app also let's you find any of your devices broadcasting a beacon. Fitbit, watch, whatever.

I only decided to set up a personal AWS for some minor things after having worked on it at employers for many years, after watching employers accidentally spend $3000 a day or $1 million a month or $35,000 in error. Cloud is the devil, bring back servers. One flat piece of hardware you can do whatever with...but even that's not sacred. If you use hosted servers, the hosts often still charge for ingress/egress and other things now, so you still fall into traps if not careful. Simpler though.

So I guess, storing your own server in your office is the way to go, but then the ISP issues...

Let us all just go back to paper, actually.

While it does vaguely link to the Consumer Reports link, most sites just auto-link to the home page or some redirect.

Media should just show the list, and first, always.

I say vaguely because on mobile one has to hold their finger on the link and in some cases copy-paste it elsewhere to see what the contents is. That's just malicious publishing.

With the advertisement culture constantly pushing "Total T" (which isn't actually Testosterone) and whatever, it's a profitable market selling to men that they are inadequate and some magic pill will make them a "man" again. Not to completely disregard the actual real medical use for it, however.

The advertisements (especially on linear TV these days like cable) are almost non-stop to push mail order prescription Testosterone and supplements that don't do anything, as well, which suggests the male ego is a very profitable market.

Some info on this from the past:

A recent market analysis reports that prescription sales of testosterone have increased from US$150 million in 2000 to US$1.8 billion in 2011 worldwide, with US and Canada driving the growth in sales numbers. Interestingly, a significant portion of men prescribed testosterone replacement therapy did not meet laboratory criteria for hypogonadism, according to a market analysis.

a recent study revealed that out of seven online-only clinics, six prescribed testosterone to an undercover urologist who had normal testosterone levels and did not meet the treatment criteria set by the American Urological Association (AUA) and the Endocrine Society.

Windows ME had the same fixed 64KB user resources and 64KB GDI resources memory limits as Windows 95 and Windows 98 for system resource allocation regardless of how much actual RAM you had. Since ME was more resource-intensive than the previous versions, you could run out of these resource allocations while still having very much free RAM much faster.

The end-result was the computer becoming unusable even though you had resources available that the OS could have otherwise used. Certain inefficient applications like I believe Quicken could snarf up all of the system resources so you had to restart with everything you could disabled to run that one application. Same computer on Win2K would run circles around WinME.

Apparently a lot of older men are on supplements or prescriptions for testosterone. Any surprise they’re all so aggro?

Palm Pre did it first. Apple copied.

To be fair, the crops didn't exist when the native pollinators were alpha, so the argument is semi-irrelevant. Again, the bigger problem is just that insect populations are failing. The focus should be fixing that, with that comes the bees. Although, that means fixing climate change. Soooo....

You're under-thinking it.

In pseudo-correct but probably not order:

• Step 1: Collect underpants
• Step 2: Keep receiving Google security updates but stop updating Google mainline
• Step 3: Start replacing the underbelly to just raw Linux (or BSD or whatever) and slowly shift the "Android" portion to a VM/container
• Step 4: RIL and other stuff (probably should happen first) have to be packaged up and become their new entity on the modem side (also probably the biggest challenge, but manufacturers and ODMs provide dev kits)
• Step 5: ???
• Step 6: Once the Android side is safely firewalled away from the core OS, start embracing something like PostmarketOS
• Step 7: GUI/graphics are built out with the Android pieces still running in a container
• Step 8: Start writing applications that replace the Android applications, go one by one, remove dependence on each Android application as you go while still maintaining compatibility (I mean the core OS ones that make the device at least basically functional, the F/OSS devs will have to each rewrite/change their apps, or some other magic can be inserted here that isn't really magic.)
• Step 9: Once the OS itself is beefed up enough, retain Android container for the needs of some for some uncomfortably long frustrating time to maintain, but not too long
• Step 10: Have Obtainium/F-Droid/etc. all simultaneously pivot and start providing apps for the native OS as well as maintaining backwards compatibility with the Android apps in the container
• Step 11: Once some magic point, forced or otherwise happens, sunset the Android portion of the app stores. Keep the containerized Android around a little longer
• Step 12: Sunset the Android container, at this point the phone should be running 100% "native" OS and apps and store
• Step 14: Profit!

There are industry blueprints for this. Apple is probably the best example of how to implement these shifts, from OS 9 (co-op MT proprietary OS)->OS X (BSD-NextStep-based Unix OS), 68k->PPC, Replacing Unix underpinnings with Apple Frameworks, PPC->Intel, OS X->iOS, Mac from Intel->ARM, etc. etc. They frequently used containerization to keep the old running while the new was built up around it and replaced. It is a solid proven design pattern.

And edit72: I'm not just saying "hey magic people do this" - I've done this shit. I'm down to help, and I will. But the project owners need to step up for some actual work instead of just putting potpourri on something someone else built. Annoying side-story, I figured out how to cross-compile/rebuild/fix dependencies on a CPAP app called Oscar so it would be ARM-native on ARM Macs. Couldn't figure out how to contact the devs after much digging to let them know, so. I have 1 of 1 copy of that app running ARM-MacOS native. Would be neat to help them replicate it though.

There are so many little cuts that are surfacing in the US weather forecasting system this year. Daily forecasts wrong, weekly forecasts wrong. Storms that shouldn't have happened or moved on just sit and spin. Flights are getting randomly more turbulent, as they don't have the jet stream forecasts to plot daily routes and have to rely more on the first plane to hit it to report it back. The systems had enough failsafes that are slightly holding them together, but it is extremely apparent the damage is already present and becoming worse.

Graphene would be better off cutting themselves off from Google's OS future entirely and pivot the fork as quickly as possible to remove all dependencies. Probably too arrogant to consider it, though. Also becomes much more work.

Qualcomm isn't exactly the best vendor to choose either. They're US-based, closely-aligned with the US government as a military contractor, and the baseband/processor are heavily integrated on many chipsets, even sharing memory. That means a compromised carrier network could twiddle bits that the operating system sees, if they so wanted. Among many other issues.

There's something about a Samsung Exynos designed to spec by Google that is actually more desirable even with the lack of compute performance. More fingers in the pot, less chance of some sneakiness working its way in.