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.
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.
The Punch Escrow is a great pulpy book along the same lines.
Company comes up with foolproof way to ensure zero transporter accidents. Don’t tell everyone that they’ve just invented a suicide booth that triggers when receipt of the copy has been verified - till that part fails and the original walks out after the copy has. Cue corporate thriller coverup story.
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)
Without a pet-tax image I’m not sure I can upvote.
With a small amount of effort and the use of https://github.com/nanos/FediFetcher and https://github.com/g3rv4/GetMoarFediverse you can mitigate basically all those issues. It’s still not perfect by any means but it results in a perfectly usable single user instance.
The first populates the replies of the home timeline posts you see (as well as profiles of people it finds in those replies) and the second pulls down all the content from instances you select for your followed hashtags (choose mastodon.social and you can guarantee you’ll see most all posts with those tags)
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.
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.
But… You literally have ports rules in there. Rules that expose ports.
You don’t get to grumble that docker is doing something when you’re telling it to do it
Dockers manipulation of nftables is pretty well defined in their documentation. If you dig deep everything is tagged and natted through to the docker internal networks.
As to the usage of the docker socket that is widely advised against unless you really know what you’re doing.
There’s a huge amount of it on the fediverse right now. People are working very hard at getting rid, all of them volunteers, and in their own time.
It seems the majority of the torrents with poor seeder count are in the 1.5TB+ range. I just simply don’t have the storage for that. Most everything in the 0-300GB range is pretty well covered.
Very first line of the GitHub readme. As a support tool it’s mostly useless, endless similar or identical questions answered differently or not at all and none of it indexed by search engines for use on the web.
It’s an awful data silo / black hole that increases volunteer load.