Is there a specific reason you’re taking the services down before bringing them back up? Just docker compose pull && docker compose up -d recreates all services that had a new image pulled, but leaves the others running.

That’s painful to look at. You can do markdown code blocks with triple-backticks `

+1

I like this perspective of yours, and while I don’t think I’ll join you on your instance (I take it this was an open invitation, yes?), I’ll look into ways to hide votes on my client.

Although I do wonder, would you prefer everyone to return to long strings of “+1” and “agreed” posts?

Love the outside the box thinking though. Really inspirational!

I would totally do that. Only problem is that the third yacht really is my favourite, so I’m gonna pass if that’s okay. Thanks!

… and enhanced by a sentence or two why it is worthwhile. Getting really tired of the no-effort link drops around here. Better yet, the same no-effort link drop to multiple similar communities on various instances.

Is there a block function for link-only posts?

Are there filters to prevent seeing duplicate content?

But boy, if he does…

I recommend installing calibre web on a home server, installing koreader on the Kobo, and accessing your eBook library over your WiFi and OPDS.

Koreader is such a good reading experience, I never want to go back to stock firmware (well, except for the dictionaries maybe, those are better.)

I have done a similar thing in the past, but to flash firmware onto any device with a certain USB descriptor that gets plugged in. It was a mess of USB hubs and cables, but it worked.

What I did was write a udev rule that checks for the vendor and product id of a newly plugged in device and calls a script when there’s a match. The script then performs the flashing and logs the output.

In your case:

1. dd the source USB to a file (make sure the partition you’re dding is smalled than any target drive
2. Udev rule according to your needs (all the same product or different drives?)
3. Script that dds the file you created earlier back to the newly plugged in drive.

Edit. Did this on a rpi3

This looks promising, but I can’t get it to work.

Wireguard, even though they explicitly mention it in their tutorials, doesn’t have an allow/block list for me, so I can’t allow the proxy network bridge. Curious those settings are gone. Too bad!

Thanks, but not an option.

Much obliged.

I agree, it’s a good solution. Just not worth the downsides for my situation currently.

Really? How does that work? Maybe it’s time to look into Tailscale after all…

Thanks for the ideas. I’ll consider it, although my use case doesn’t really warrant carrying a router around.

Having strong opinions is what Graphene does. 😅

And they do seem to be an authority on all things security, so most of the time I like that about them.

Thanks for the link. I am on Graphene, and if a fellow poster in here is correct that doesn’t help. Bummer.

Dang, also on Graphene…

here’s a thread with official Graphene voices saying it won’t happen (and why)

Right, thanks.