BearOfaTime

Ooh, thanks, that sounds Intriguiging! Will try them next cycle (I have a couple small hydroponic setups).

And honey is sugar.

The difference between it and table sugar is negligible from a glycemic response perspective.

There's a number of tags that could be useful, like politics, sports (or specific sports, though I'd filter all of them, just not my thing), or pick something.

It would also be a useful way to setup different collections, like right now I want to see posts about cooking - I could have a view with just "cooking" tags (a category that could have further tags, eg "Cooking, veggies" or "Cooking, Pork", etc).

Of course this would require voluntary and consistent use of the tagging system, but I think over time most posters would embrace such a thing.

A couple days ago I decided to just start blocking people who post political crap, especially where it doesn't belong (particularly political tirades or rants). Such people provide no value, so no need to have them in my feed.

The databases at my company nearly 30 years ago were staggering at the time. I can only imagine.

Thank you. Brilliant, wonderful.

So tired of politics, there are communities for that stuff.

I think you could make this a Dad joke

Hell, The tools have always been there for business, where in-house expertise is the norm (or contracted, especially for SMB).

The people who pushed for cloud were bean counters, senior IT management, etc, because those costs are an expenditure for services (reduces your tax liability also while offloading risk to the vendor). While keeping it in-house means buying equipment and owning it, which increases tax liability and keeps risk in-house. (They also thought they could reduce staff, haha, nope!)

There's a place for doing this, for sure. Things like email hosting, especially for small business where they just aren't going to have the staff to manage the spam, etc. But that's paying an email vendor to manage the service. Bit of a different animal.

Or for enterprise, having the flexibility to quickly spin up new resources for expansion. Or redundancy. Or for a new small business, you can spin up resources as needed until you've determined what you actually need, then migrate to local (or not, if the venture isn't successful).

For home, yea, there's lots of stuff available these days, more than you can shake a stick at. Some of the simpler things like CasaOS and FreedomBox are simple enough for moderately technical people.

But generally it's not a good choice to go cloud.

But the Android API isn't Linux.

Android runs on a Linux kernel, not the same as Linux.

Wine isn't Linux. Wine runs on a Linux kernel giving us a Windows API on Linux.

I'd even go so far to say Android is an API/shell on a Linux kernel.

Just like Mac is it's own API on a Linux kernel.

There's probably a better term for this today.

Even Windows is an API on the Windows kernel. At one time there was a Posix API for Windows. Today there's both an Android Subsystem for Windows, and a Linux Subsystem for Windows. Which are little more than APIs that run on the Windows kernel (though quite a hit more involved).

There was a really good explanation by a rando about how it happened. Seems a dev made a mistake when publishing a change.

Apparently bitwarden immediately changed internal procedure for publishing changes.

Isn't the pixel intended to serve as a model/benchmark Android phone?

That's what the Nexus was.

I suspect for Google it's about demonstrating what Android can do, so more about marketing than direct profit.

Hell, I prefer that UI. It works, it's info dense. Unlike newer stuff where there's less and less info on a screen with a lot more white space (I'm looking at you FolderSync).