That’s fair, there’s other angles of observation made available already.

Seeing as you like speculating about cyberpunk, how about if observation is just the initial way to way to sell the drone cloud? Depending on how cheap you can make them, there’s an argument to made for reducing time-to-intercept for low-speed aerial objects.

If you’ve got a bunch of drones overhead already, you could run one in to the path of a kamikaze drone, or if your swarm is even lightly armed, you can extend engagement range and reduce required accuracy with a single buckshot shell to shoot an offending drone down.

If you’re content to prioritize executive safety over public saftey, there’s a lot that can be done.

Drone displays terrify me.

Not to mention, the minute it happens, the government will carpet the skies with observation drones in the name of safety

Just a little piece

That’s what I was thinking, I know the pain of watching something run for ages, only to finally get past where it failed last time and run straight in to another stumbling block.

I don’t envy you having to work in an SELinux environment with less than stellar developer understanding of policies and contexts.

Is it not possible to run it in audit mode in dev and have it tell you what the would have blocked?

Devils on horseback!

User on both platforms checking in, it’s great!

You’re a monster. My scps would go nowhere

It’s the right move.

I tell you, the first time you’re sat in front of a CEO and an auditor and you have to explain why the big list of servers has a highlighted one called C-NT-PRIK-5 is when the fun stops.

Explaining that it’s short for ‘customer network tester Mr. Prickles 5’, and is actually a cacti server never really seems to help the situation.

At least a few of the customers got a laugh out of it being on the reports!

Username checks out

You had me digging through old hosts files and ssh configs to find some of these.

I try to name them something that resembles what they do or has something to do with what their purpose is.

Short is good, and if it can match more than one of the machine’s purpose/os/software/look, the better.

If it’s some sort of personal machine, it gets a personal name

Phones

• traveller
• pawn
• rook
• bishop

Virtual Workstations

• boxy

• moxy

• sandbox

• cloud

• ship lxc container host

• dock docker host

Laptops

• ciel Razer blade stealth with a rainbow LED keyboard
• arc runs arch.
• lled is a dell

Desktops

• bench
• citadel
• bastion

They’ve stuck it under its own app entry. Both K-9 and Thunderbird end at 8.2 for suggested releases.

I just installed Thunderbird, looks identical, just a rebrand. They’re so identical the import function is seamless mostly seamless.

Not sure if it’s a quirk of GrapheneOS or just the way things are now, but for gmail accounts, you’ll need to go in to something like Settings > Account > fetching mail > incoming server and then hit next.

This will dump you back in to the google web login auth page, so you can approve the app for each account.

Otherwise, the sync and alert settings are copied just fine, so it’s good enough.

Unless you run your own davmail server and connected to that instead, probably not.

I would trade meticulous handover notes fit in to the working week if it meant I could work one week on, one week off.

I go to pornhub for the definite article

I played splinter cell chaos theory coop with some random on my steamdeck on a transatlantic flight a few months ago. Can highly recommend!

Assuming this hasn’t been adjusted for, possibly because it was bundled with the ps2 in a lot of places

I bought the dbrand grip for the last 3 phones I’ve had, and it’s always been a great choice for me, highly recommend; but I shouldn’t have to spend $60 and increase the thickness of the phone by nealy 20% just to be able to hold on to the damn thing.

Lots of people have been talking about products and tools. It’s docker, tailscale, cloudflare proxmox etc. These are important, but will likely come and go on a long enough timescale.

In terms of actual skills, there’s two that will dramatically decrease your headaches. Documention and backup planning. The problem with developing those skills is, to my knowledge, they’ve only ever been obtained through suffering. Trying to remember how to rebuild something when you built it 6 months ago is futile. Trying to recover borked data is brutal. There’s no fail-safe that you haven’t created, and there’s no history that you haven’t written. Fortunately, these are also the most transferable skills.

My advice is, jump in. Don’t hesitate. The chops in docker/linux/networking will come with use and familiarity. If it looks cool, do it. Make mistakes. You will rapidly realise what the problems with your set up are. You will gain knowledge in leaps and bounds from breaking a thing vs learning by rote or lesson. Reframe the headaches as a feature, not a bug - they’re highlighting holes in your understanding. They signpost the way to being a better tech, and a more stable production environment.

The greatest bit about self hosting for me is planning the next great leap forward, making it better, cleaner, more robust. Growing the confidence in your abilities to create a system you can trust. Honing your skills and toolset is the entirety of the excercise, so jump in, and don’t focus on any one thing to master or practice before hand!

Buying their 1 tb drives has been my prefered way to to do backup sync and distro hopping for a while now, with a $20 cradle, and a wallet of these things, you never have to leave anything behind.