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.
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.
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).
Linus has repeatedly pointed out that, unfortunately, it works. They make way more money from videos that follow this shitty trend.
On the left is the DNS server that DHCP sets first. On the right is one it sets second.
This is a mixed machine network (Windows, MacOS, iOS, Android etc).
My clients will mostly pick option number one, but as you can see it's not a guarantee at all.
EDIT. Since lemmy doesn't show kbin images attached to comments https://media.kbin.pieho.me/81/1e/811e8f6bf8aa5e8ea9219ff52d1e61aec8624107ffd11f2a13631d0a1ac29abc.jpg
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.
Been using Mastodon a while. Once you hit critical mass of people you follow you just sort of find new ones.
If someone you enjoy reading boosts something someone else has said you go off and probably end up following them too.
With Mastodon you have to be a bit more pro active about building (and pruning) your social network but I've found it worthwhile.
ITT people who don't understand that generative ML models for imagery take up TB of active memory and TFLOPs of compute to process.
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!
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.
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?