Linus has repeatedly pointed out that, unfortunately, it works. They make way more money from videos that follow this shitty trend.

41 here. Getting drunk on a Friday wipes me out for a long weekend. It’s touch and go whether I’ll be capable of work on Tuesday.

Finally got around to playing Carrion. It’s a great game for the deck and is a massive amount of fun.

Stella Maru off the north west coast of Mauritius.

It was all rental gear so I just took what they gave me.

I was in a BCD but I guess they preferred to do the weights the old way.

Deck is at about 20 meters. Something like 27 to the sand.

I’d give my left nut for a Pebble T(ime)2.

Was going to be an absolute GOAT smart watch.

The holosuites

Splitters

Somewhere south of “man flu” but north of “the sniffles”

Promises to recover all fraud, is unable to prove any fraud…everyone wins!

As a vegan, and a pirate, I approve this message.

Read the “The Punch Escrow”. Not star trek but well worth it if you’re into this sort of thought experiment.

The issue with orchestration is that you still need a way to share those small databases and config files.

Docker has ok NFS support so you’d want to move the files to NAS shares and have them mount those. Without some way to centralise or spread the files out you won’t be covering your SSD failure case. Once you’ve got that going docker swarm will probably cover your needs just fine.

You could go with K8S but based on you setup that’s a bit overkill (unless you’re doing it as a learning exercise, in which case go nuts).

Guess I’m missing some lore. Where can I find out more about Q’s involvement (also, why was the footage so… different)

One of the first things my base ansible role does is disable password logins. All keys, all the time.

This morning I walked the dog in my full autumnal boots, jeans and a Rab padded jacket.

It be cold.

Mmm. Looks like you’ve stumbled across (or at least highlighted) a bug in the way kbin federates out links in it’s content. I thought I’d covered the various cases but apparently didnt.

When a post is made to kbin (or federated into it) that contains !magazineName@instance it does a best effort to make links that will work for users on that instance, but it appears that best effort applies to the outgoing federated content too - and it shouldnt, or at least, it should do something different.

I’ll get a bug ticket in.

EDIT. For now I’d recommend that where possible you use fully explict links i.e. [{@|!}community@instance](https://instance/{m|c}/community)

No, I won’t, it demonstrably is.

Dessert places. Ice cream, waffles, all that kind of thing. There are a few around here that are always busy 10-12pm.