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.
ITT people who don't understand that generative ML models for imagery take up TB of active memory and TFLOPs of compute to process.
Somewhere south of "man flu" but north of "the sniffles"
Promises to recover all fraud, is unable to prove any fraud...everyone wins!
The issue here is that Lemmy is federating out it's content with the pre blocks containing rendered code fit for some sort of code display plugin/CSS - which KBin doesn't have.
It would ideally send out the blocks html encoded and would let downstream implementations like KBin or others figure out how to display it themselves. I don't know how we would fix this.
As a vegan, and a pirate, I approve this message.
This is actually due to the way these platforms work. When a user comments on a comment or post on their instance it will be shown on their instance. It's then sent on to the owning instance of that comment or post. That owning instance then forwards it on to all interested parties (magazine instance, commenters instance).
Any instance in that chain can refuse to forward or broadcast that message due to a block, but the users own instance will likely always show that post. Ideally they would not do that and would be made aware of a block but that is a bit of a grey area in ActivityPub implementations.
Read the "The Punch Escrow". Not star trek but well worth it if you're into this sort of thought experiment.
For me that can be answered with 90% of the feature set for 50% of the cost.
It runs the KBin instance I'm using to reply to you :)
Also Adguard home.
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).
When was that update?
Guess I'm missing some lore. Where can I find out more about Q's involvement (also, why was the footage so... different)
Lately (last few weeks or so) my Pixel 6 Pro has developed an incredibly frustrating contactless payments problem.
Out of the blue it will become really, really slow to respond to tapping for a payment, taking 5 -20 seconds to actually open the Google Wallet/Pay app and do it's thing. If I tap and it's not immediately opened I've tried to open the app via the quick tile but the button is non-responsive. Eventually it'll open and then I can pay.
Once it's acting like this it'll do it indefinitely, but I can fix it by restarting the phone. Then payments (and opening the app) are near instant as they should be.
Anyone else seen anything like this? Any solutions?
A #PHP developer who, in his spare time, plays #Tabletop and #VideoGames; if the weathers nice I #Climb rocks, but mostly fall off of indoor #Bouldering ones.
Pronouns He/Him Blog https://realmenweardress.es Photos https://pixelfed.social/pieceofthepie Keyoxide https://keyoxide.org/606B2E3C103A443663DA82716B37390F365AADAA