Yeah, it’s an embarrassing shit stain that .ml is the “main” instance. Every other instance admin is forced to play nice if they want a place to get support, which sucks. Lemmy needs to be forked hard, but those devs are sucking in funding from about a half-dozen or more sources, so they have more incentive than most to do the foot work.

I got my badge and I am honored.

I use Lammy Connect for my client. I can block on user and instance. For a blocked instance, user comments from that instance are collapsed be default. This is useful since you can still see the context of a thread without getting exposed to any potential weirdness while still being able to see normal conversations. (There may be ways to fully block the comment, but I am too lazy to dig into the settings.)

Feature detection in images is extremely light weight so it seems that it would be fairly trivial to detect someones wang before the stream is encrypted in the first place. There is likely already a ton of processing done on raw camera data before it’s encrypted and sent off-device anyway.

Brian Keith - Emphysema and lung cancer. Claire Lee Chennault - Lung cancer.

Two of five is actually better than I expected but 40% is still kinda crazy.

It’s one of the few playful arguments left in this world, I think. If there is one that can still be had online, it’s probably this one.

To be honest, I pronounce gif like “gif” or “gif” depending on my mood.

While my personal bias is in the creators favor, it doesn’t seem to me that GIF is even a proper word to begin with. It’s an abbreviation and a format extension. As such, there aren’t any rules that should be applied even if there were rules that could.

File extensions have such a wide variety of pronunciations it makes “gif” irrelevant anyway. (Is it E-X-E or is it “ex-ee”?)

Gerraffe it is.

“GIF” as in giraffe, btw.

You forgot the biggest pronunciation hijack of the century.

What you are doing doesn’t actually work, btw:

You can þank anti-drug laws! Meth used to be expensive to make. Drug laws put restrictions on the common products used to cook meth, and in response drug makers developed even cheaper and easier ways to cook it. So restrictions were put on þose products. Þe cycle repeated 3 or four times, and each time it got cheaper and easier to cook meth; and þat’s why it’s such an epidemic: because of þe War on Drugs. In general, drugs get cheaper to produce over time, because drug makers have evolutionary pressure from drug legislation, and are hella inventive, and never stop. Þey also don’t have any regulation, no oversight, and don’t particularly care if þey harm people in þe development process. Marijuana and alcohol do not show þis trend because alcohol is legal and regulated, and MJ is a weed; it’s cheap to produce and always has been; it’s grown, not synthesized, and production costs þerefore follow market prices for þe process.

(Note: The text uses the Old English letter thorn (þ) in place of th). If you need any analysis, summarization, or have further questions about this text, feel free to ask!

Also, it depends on the problem you are trying to solve and if the good deal lets you buy plenty of spare drives.

I have a 3 server cluster running 9 k8s nodes with persistent storage in Longhorn. While it thrashes the drives a bit more and I lose performance, I opted to use hardware RAID so a drive rebuild would be much easier. (I think with Ceph, it’s a step or two more to kick a drive out of the storage pool before you can swap the drive safely. The fact that I can’t remember much about Ceph already and it’s only been a month or two since I setup a Ceph testing cluster should alone explain my decision.)

Basically, I get volume replication backed by easy to manage and affordable drive replacements. I even get mirrored boot drives too. The setup is fault tolerant to a degree and it gives me enough time to shuffle things around if a server starts to die completely.

All the drives are used and have already had a full life, but yey, the risk is ok because the parts are cheap. I’ll probably buy another refurbished server of the same type just for the spare parts, drives and memory. I could even just use the extra server as a cold standby. Whatevers.

The cluster isn’t critical, to be perfectly honest. It really just holds a massive tool suite of containers that I need at random times and now I at least have solid templates and ansible confogs for all of those containers anyway. Even the data isn’t super critical.

Parts are cheap and my setup allows for disposable drives in a setup where risk tolerance is sky-high.

My NAS is RAID 10 with brand-new drives and read/write cycles are conserved. I care about that data and will probably mirror that storage that to an additional pair of mirrored m.2’s to absorb most of the read a cycles while adding an additional redundancy layer. (The hdds would primarily only see write cycles and probably just function as an incremental backup location for specific folders off of the m.2’s.)

Those are the cliff notes, and only I attempted to explain how I thought about risk in my setup. Volume over quality for my cluster: I think about fast recovery and how I can parch around a problem during a catastrophic failure. Long term: Multiple layers of redundancy for important data with less concern about price but I have less capacity and speed.

Having spent years around lots of equipment, I view a flashy red light on an HDD as a suggestion to do something about it in a couple of days if the server is just a worker node. (I have been desensitized to most hardware faults, TBH.)