Ah sh*t

That’s a clever approach, thanks for the explanation

Interesting, though what if the receiver fails to scan the codes quicly enough?

What happened to Nova? I use it and seems to work fine?

Me grabs a cable: “F*ck, it’s a charging only cable!”

Me grabs another cable: “F*ck, it’s USB 2 only!”

Me grabs another cable: “F*ck, the connection is dropping/flakey!”

Second that! It does have issues on Windows, but it’s Windows so what would you expect? And it doesn’t matter to the OP anyway.

For what it’s worth I’ve been on Lemmy for barely over a month, so I’m still pretty new to this. I was not at all expecting to be talking to people from Mastodon or mbin here 🤔

My understanding was that federation allowed many independent Lemmy instances to interact, but nit that it even included other platforms. Looks like I’ll have to do some reading into this whole thing.

Thanks for trying to explain!

What are you talking about? I don’t know what you use to browse Lemmy, but I use Voyager and it shows clearly that this was posted on the programmerhumor lemmy community/world/instance 😂

It’s literally in the programmerhumor community 😂

I deleted the whole /usr/bin to be sur

Having its own data connection would just drain the battery faster. In theory, a Pebble has an open SDK, even the firmware is open, so you could hack whatever you want into it (as long as the resources suffice)

How is crashing on an unhandled path in a security context not better?!

However, Vaultwarden only implements the webvault, the client apps are still only supplied by Bitwarden, which they could make incompatible with Vaultwarden at some point.

I’ve also seen some sites use POWBlock, though, don’t know anything about it.

WireGuard is stateless, so running it “on” 24/7 is cheap, set it up once for them and leave it on, ideally they wouldn’t notice a thing.

The crux of the issue, at least as I understand it, is that traditionally you’d build the system components in a way that they were interchangeable by defining some standard-ish API. While you can interchange some Systemd components, since “ststemd-xyz” is just the umbrella name of the project as a whole, so some components are completely independent, the core ones can’t really easily be swapped, and it’s only getting worse, especially as systemd is starting to become a hard requirement, a lot of people are rightfully feeling peeved. There’s a great talk made by a BSD developer that admits the virtues of Systemd while bringing the downsides, so no blind hate, you can google for the video “The tragedy of systemd”.

Amazing talk, was hoping somebody would’ve linked it and was not disappointed

Proxmox VM snapshots and backups, plus proxsave I assume?

I actually did that. Or well, I was planning to upgrade the Debian version and instead of doing it in place I replaced the drive (kept the old around for a while just in case) and did a clean install. I didn’t make any new backups or moved configs or anything outside what I already had, the system was back to operations faily quickly. The main reason, I have a markdown file describing every configuration and recovery step needed to get a fresh system to a fully working state in case of a disaster, and my test showed that it worked great. It does take a bit of effort to keep it up-to-date, but as shown, really worth it, and it douples as a small wiki for accumulated knowledge. I do wish to play with Ansible at some point if I have the time, but this works for now.

Did you restart the browser/phone in between? Maybe the old cached list was being used? Heard some recommend restarting the phone just to be sure.