Adam

allows it to make its tokamaks at only two percent of the volume of conventional tokamaks

Strap that into a tank, with - hear me out - legs, and we’re golden.

Easily doable in docker using the network_mode: "service:VPN_CONTAINER" configuration (assuming your VPN is running as a container)

It’s unfortunate that (at least on the Bluesky side) an attempt at following a person doesn’t result in them getting a DM asking for that to be ok.

Which means following a person on Bluesky is not possible unless they’ve already opted in.

All I want to do is follow a couple of authors or content creators but none of them know what bridgy.fed is :(

I’ve not used dockge so it may be great but at least for this case portainer puts all the stack (docker-compose) files on disk. It’s very easy to grab them if the app is unavailable.

I use a single Portainer service to manage 5 servers, 3 local and 2 VPS. I didn’t have to relearn anything beyond my management tool of choice (compose, swarm, k8s etc)

Yes. On older generation/cheaper ANC this is perceived as increased “pressure”. It doesn’t seem louder but the physical sensation of loudness is there.

“…prohibits repair stores from repairing components on the mainboard. Instead, the entire component must be replaced…”

A flagrant disregard for the costs of e-waste on the environment. What a surprise.

The sound produced by ANC is the exact 180 degree inverse (or as near as possible) of the incoming bad noise.

It’s produced in realtime by dedicated signal processors and requires mic arrays feeding in the sound. The quicker your processing pipeline the better the match is and the more powerful the effect is.

There’s no prerecorded sound that would work.

Aside from everyone who’s using flutter?

Long story short the MRI showed no impinging of the cord so we were told to just monitor it. It’s slowly fading.

The long story is that the next day the GP repeated 111’s advice so we bundled up pillows and painkillers and, still very upset, we went back. After an hour the triage nurse told us that all the GP needed to do was a referral by email and we would have been admitted straight to the spinal unit.

She then rang the GP and actually tore them a new one. It was highly satisfying.

We spent the rest of the day in spinal, her on a bed, and got seen by excellent staff who did more explaining about the injury and what to expect than anyone else had done to that point. We were in limbo about the whole thing till then.

Fuck.

My wife and I were in this A&E 3 days later. She’d new lower body numbness appear some months into a broken back recovery. 101 said go straight there, this is a no fuck around situation.

We get there and are advised it’s a 12 hour wait, the place is rammed, ambulances are queuing and the corridors are full of gurneys and paramedics.

My wife at this point is in tears. The broken back means sitting for an hour on a shit waiting room chair is hard work. 12 literally can’t happen.

So we leave. What else can we do.

The situation was fucking awful, but I don’t blame the staff. I felt genuinely bad for all of them - there was just a complete lack of hope on any of their faces.

If only k/mbin federated better - I’d be all over it :(

Privately operated ICBM’s. I can’t see how that’ll fly but I look forward to finding out.

Main page of dashboard

If you long press on a tile (this is kitchen)

The news article/statement I read has it related to major abdominal surgery from back in January. So none of the good kinds. Not that any cancer is good.

Didn’t even think 4k80 was generally available yet?

There’s a couple of caveats with it, but I think neither are worse than your proposed flow.

1. After putting things in an album you’ll need to manually run the migration job to have immich reorganise into album folders.
2. Images in multiple albums will only be migrated to the path of the newest album.

Immich does support folders?

https://immich.app/docs/administration/storage-template/

With this you can store your photos in whatever structure you want.

Yes.

Docker will have only exposed container ports if you told it to.

If you used -p 8080:80 (cli) or - 8080:80 (docker-compose) then docker will have dutifully NAT’d those ports through your firewall. You can either not do either of those if it’s a port you don’t want exposed or as @moonpiedumplings@programming.dev says below you can ensure it’s only mapped to localhost (or an otherwise non-public) IP.

Documentation people don’t read

Too bad people don’t read that advice

Sure, I get it, this stuff should be accessible for all. Easy to use with sane defaults and all that. But at the end of the day anyone wanting to using this stuff is exposing potential/actual vulnerabilites to the internet (via the OS, the software stack, the configuration, … ad nauseum), and the management and ultimate responsibility for that falls on their shoulders.

If they’re not doing the absolute minimum of R’ingTFM for something as complex as Docker then what else has been missed?

People expect, that, like most other services, docker binds to ports/addresses behind the firewall

Unless you tell it otherwise that’s exactly what it does. If you don’t bind ports good luck accessing your NAT’d 172.17.0.x:3001 service from the internet. Podman has the exact same functionality.