The nice thing about some battery backup is not keeping it running during an outage, but safely shutting it all down.

I agree on the laptop battery, I’m just disagreeing on battery backup. It serves a purpose, as does decent surge elimination.

Considering our use is not to the general public, we’d be better off with an entirely different strategy.

Yeah… I didn’t choose it, but some of the services from my employer run there. May be a good time to make some moves, we’ll see.

Not really going to be an issue I can fix obviously, but I’ll be making even more backups than normal…

I have a feeling the big impact is going to be in other services, namely AWS. Makes me wonder if some new global outages are coming, which are always fun to deal with.

There is nothing native (though a few options have been played with, AFAIK never completed because…), but there are a ton of integrations. You can use webhooks to teams, there are python wrappers for the API, even a google docs integration.

Probably the lowest code option would be to find someone else’s tool for snipe-it (sorry I’ve never looked), or do something like snipe it to google sheets to be imported as a CSV or something.

Or take a peek at some others in the same territory, or maybe ticketing systems with simple asset management.

But i think something like snipe-it, if not exactly, is going to be the right territory of what you’re looking for

Its about $2.6 billion per week in revenue, even by the weekly numbers its not an impact

(based on ~$135b in revenue for 2023, according to financial disclosure reports)

What about asset management software, like snipe-it? Or are you trying for payment in there too?

Because the separate installation means you can actually end up with both an apt installed and a snap installed.

My comment about docker was a specific example of such a case, where vulnerabilities were introduced. It was actually a commonly used attack a few years ago to burn up other CPU and GPU to generate crypto.

Yes, canonical provides both. Guess what? They screwed up, and introduced several vulnerabilities, and you ended up with both a snap and apt installed docker.

The fact that they are both packaged by Canonical is both irrelevant and a perfect example of the problem.

One selects a different package, same source repo.

The other completely changes the installation, invisibly to the user, potentially introducing vulnerabilities.

Such as what they did with Docker, which I found less than hilarious when I had to clean up after someone entirely because of this idiocy.

The differences seem quite clear.

Well, that’s your problem for not understanding the massive difference, not mine.

Russia was bombing civilian targets from the start.

Yeah, I just glanced at the top few drives I’ve pulled from my three NAS (bigger drive in there now) - two 500gb and a 4tb.

I’ve also got a ps3 sitting around, so maybe some weekend fun since I haven’t touched it in years.

That is about the most generic statement possible, with nearly zero knowledge of what I’m doing on yours.

So… What problem? Feel free to enlighten me.

Eh, I’d say mostly.

I have one right now that looks at data and says “Hey, this is weird, here are related things that are different when this weird thing happened. Seems like that may be the cause.”

Which is pretty well within what they are good at, especially if you are doing the training yourself.

Yup, debian is where I was before Ubuntu, and where I went back to. Still what I run mostly, plus a few different flavors of it (proxmox for example).

Though I’m also running an arch desktop on one of my play machines, kind of reminds me of having to write my x conf out in the 90s! Not bad overall.

(Never giving up my deb stable servers though!)

Yes, and I don’t consider that an “easy to disable” option for regular users, but that’s just my opinion.

“Easy to disable” is also the wrong approach, IMO. It should have been “easy to enable” - stuff like this should always be opt-in, not opt-out. Opt-out, to me, demonstrates a company’s motivations more than anything else.

Ehh… not at first. That was a later release.

A dumb phone and a feature phone are not the same thing, and a feature phone may connect to the internet.

Which is why dumb phones and feature phones aren’t common anymore, and the people choosing them are specifically choosing it to avoid being available via WhatsApp/Signal/Slack/Discord/Teams/whatever else.

My FIL for example has a clamshell feature phone, because he doesn’t want to be reached except by phone or SMS. He doesn’t want to read email or get messages on his phone, he wants to restrict that to when he’s in front of his computer.

So yes, you would not be able to use messaging clients on a dumb phone, that’s the idea behind their use today.

…so you just made it up then.

No, the phone industry made up these terms.

No one has done that. The only comments I’m downvoting are the ones spreading disinformation.

So how I read that is “Anything that isn’t what I want it to say is disinformation”.

Well, enjoy your day buddy, my participation in this thread is over. Its a neat feature phone, and that’s where I’ll be leaving that.