Looks like you edited but kept the “th” suffix instead of “nd” :)

For a while Intel’s QuickSync was I think one of the better for transcoding (e.g., for Jellyfin). Didn’t see mention of this in the article, I wonder if AMD is on par now?

My carrier is Google Fi — one perk is that they will give you free data-only sims (up to 10 I think?) and you just pay for the data you use like any other data. I have used old Android phones in USB tether mode this way, and it works just fine. So, rpi+old/cheap phone should do the trick.

One fun bonus is that if you tether over USB it will work as a WiFi dongle, too — the failover from WiFi to cell should happen on the phone, transparently iirc. Not sure if that affects you.

Caveat is that I did this a while ago, and their pricing structure may have changed. Finished to be a great deal but has slowly become another carrier with not much to differentiate it…

Lol, comment removed. It ended with, “…support for the Chinese Communist party” as a way of finding out someone is a child.

Which was then removed in a, dare I say, childish act of moderation.

(Which is fine, the folks at .ml are welcome to censor as they see fit, of course, and I’m sure this comment isn’t long for this world.)

I have a Mikrotik router, 2x VLAN-enabled switches, and 3x VLAN-enabled APs. My Internet access broke every day for a month while I figured out what I was doing.

deleted by creator

Completely agree.

The Wikipedia article itself has this to say:

Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors who are unable to support the new extensions.

By that logic Lemmy/Mastodon/fediverse are already extinguished. Those of us in the fediverse are already “marginalized” wrt Twitter/Threads/Facebook/whatever.

There are very good reasons to hate Meta, but personally, I think EEE isn’t the biggest issue.

Slack killed IRC integration mid 2018.

What exactly did Slack “allow” though? The continued existence of an ancient protocol with a niche but dedicated following of predominantly “old school” tech people?

Absolutely.

Maybe. Or this will play out like Slack and IRC.

Initially, Slack integrated with IRC. Which was great! It meant I could use xchat to talk with folks, and could set up simple bots using standard IRC tools.

And then Slack killed that feature…but it absolutely didn’t kill IRC, because die hard IRC users never cared about Slack in the first place.

My prediction is it’ll be the same — what sort of people will be attracted to Threads vs a smaller “proper” instance? Probably the sort of people who would never consider a federated platform in the first place.

Just speculation and I could certainly be wrong…

IIRC mine (as an employee, not HR) verified some stuff on my CV (education details I think).

Other comment says there is a way from inside, just not outside (which doesn’t help with a young kid/toddler/baby is the inside passenger of course).

Either way, glad this is “only” a huge embarrassment, and not a dead kid.

AFAIK in the USA you can’t have the main batteries be replaceable (I think an aux battery for wireless functions is allowed…).

EDIT: I seem to be thinking of California, maybe not all of US.

What country? AFAIK in the US you can’t make the batteries replaceable. If they are wirelessly linked they can have auxiliary batteries for that, but (I believe) that’s different than the main battery…

EDIT: I seem to be thinking of California, maybe not all of US.

with the ever present threat of hurricanes

That may be true for Florida, but that’s not really relevant for northern California/PNW/many, many other parts of the world…

My company did it the right way — they gave us the day off.

We really need to see info from the BIOS — exact CPU model, RAM speed, etc.

As others have pointed out, this is a pretty anachronistic build — i586 with DDR1 is just weird, so it’s possible there’s some really niche hardware and you may need an exotic kernel (or kernel options) to get anything to boot.

That said: have you just tried running a standard live or install CD from that time period? You could try booting a 2001 Slackware installer to see what happens.

Is that for sure what happened? IIRC there was speculation about mechanical failure (lights we not out on ship, large plume of smoke…).

Though perhaps that doesn’t really matter as far as how much it sucks for the crew.

Can you post the CPU info? I think it should be available from the BIOS.

Basically sounds like the Tesla game plan, which was super effective: roadster (which is purely a toy for the rich) and a little later the Model S (practical EV), and then introduce an affordable model.

This implies that eventually people will strap rusty boxes to their head though, so grain of salt with the analogy…