Thanks for providing this perspective.

It’s good to separate the architectural/system management approaches from the content differences.

You sound like me - my 20 year old “toy truck” has been offroad lots more that most of those garage queens (and looks it).

I don’t look to go off road, sometimes it’s just necessary to get somewhere like a neat campsite, and it can do it.

Por que no los dos? 🤣

(We’ve all had crappy teachers).

This is already covered by existing laws

It protects everyone

Or are you OK with someone yelling “I’m going to kill you” and you have no legal recourse?

So is the backlash against minimalism or against anti-minimalism? 😁

(Just thought it funny that it could be read either way, if you choose to).

I run a 2019 Dell OptiPlex SFF desktop as my ESXi box - it idles under 20w with multiple Linux and Windows VM’s (4 are standard, besides the ad-hoc ones for testing stuff).

Hard to beat the idle combined with performance when needed. Pi really doesn’t compare.

What are you trying to do?

In the business world, this would be your business requirements. Once you have those then you can spec the technical requirements.

Without having a target, you’ll just be all over the place.

Start with one thing, get that setup, get management for it in place, backup processes, etc.

Then do the next thing.

Iceberg made a great rec - start with Jellyfin. It’s pretty easy, but touches on all sorts of stuff like storage, backups (which media is worth backing up?), etc. Plus it has a high reward - watching what you want, when you want, from almost any device.

Read up on cortisone - related cartilage/tendon concerns.

Your doc probably overstates the risk a great deal. Check NLM for studies, it looks like there’s a risk, but all the studies are of patients with injury and on-going degeneration. By the time you get to injections you’ve exhausted other treatments.

And being the southwest wearing a hat outside isn’t really a choice, unless you like a sunburned scalp.

I wear a hat because I don’t like a sunburned scalp

Yes

1. Use proper capitalization

2. Don’t attack people when they state they’re trying to understand what you’re saying, like you just did here with HikingVet.

You’re the issue here, as you demonstrated the exact same behaviour here with HikingVet, and are looking to blame others.

This isn’t about restrictiveness - it’s a problem of RCS being ass-backwards garbage.

This isn’t a an Android issue, it’s a Google and cell provider issue. And that RCS (like SMS), are based on ancient technology/concepts, and both need to just die.

SMS is based on the physical architecture of cellular networks, and has no error handling whatsoever - it’s a Best Effort transmission.

RCS uses a hardware-bound ID, something we decided was a Bad Idea 40 years ago, and is wholly dependent on cell provider support.

We have a protocol, TCP-IP, that eliminates all these issues. It’s been the networking standard since the mid-90’s when even Netware decided it was a superior solution to IPX/SPX. It’s wholly hardware independent (it’s not tied to a physical device’s ID), so you can transmit/receive from any device without having to update everyone else that this is your new device.

We have numerous IP-based instant messaging systems today, with one in particular (XMPP) being open, flexible, extensible.

There’s no use for an archaic solution like RCS, except keeping your messaging in a system controlled by Google and carriers.

What’s a “Google”? 😝

There’s essentially Lineage (formerly Cyanogen, or a fork of it) and Graphene.

Ignore /e/ OS - it’s Lineage with their crap on it.

Go read about those two.

RCS is so backwards it’s not a step in the right direction.

It’s hardware bound - which tells me they want definite tracking capability.

Wow, that page has so much crap on it that it crashes because I block the crap.

Hahahaha, thanks for that.

A brilliant joke that will last forever!

My pronouns are fuck you AI