Sacre bleu

By how the protocol is structured, it’s impossible for the address a downloader sees to know what the packet they forward actually contains, so they’re just taking the role of an ISP. Also, they don’t know the original source IP.

Chicken Game!

Rules: don’t look at the chicken.

🐔

Game Over

(I stole this from a shirt that did this better due to the layout)

This would also be fairly unintrusive, but could add a few false positives.

If this was the case, we’d have a whole bigger problem on our hands.

Even considering the birthday problem, the chance for such collisions is astronomically small. Especially if you combine it with the file size that you always have anyways.

In fact I’d guess that sites like these already do exactly that in order to avoid hosting duplicates (if not handled at the file system level).

Not with that attitude

You can measure anything in nanograms, but a typical LSD dose starts at about 100ug with the threshold at about 25ug or so. Still not much, but not what you’d usually measure in nanograms.

It’s still rough around the edges, but at least it seems to understand what LaTeX did well, and what people didn’t like about it.

It’s the most reachable thing. Markdown feels like a toy for many (not me)

Oh yeah. Markdown. While it does have a place, the limitations on top of my head as to why I wouldn’t use it in bigger projects:

1. There is no standard in that sense, but multiple dialects / flavors
2. No support for stuff you might want, e.g. alphabetical ordered lists.

It’s fine for when you know what output you produce, like for Lemmy or in a wiki or whatever. But once you want more control, you lack options or need to rely on non-“standard” (is there was one) solutions to somehow achieve it.

I think, as an easy, yet powerful solution, AsciiDoc is better-suited.

Nothing is better than LaTeX/XeTeX + BiBTeX to my knowledge.

LuaLaTeX + Biber

Talking about tables, if you’re not using tabularray in 2024, you’re doing yourself a disservice IMHO. I almost use it exclusively except for text formatting as only tabularx supports page footnotes easily.

It has turned LaTeX tables from absolutely annoying to something that actually makes sense and looks nice and comes with most tools you want from tables. Except booktabs which it supports with an option. For example, it supports cells with line breaks, variable width columns, multiline and multi row cells - and even manages to align the text in them correctly. I don’t know how Jianrui Lyu did this, but he did.

So yeah. Tables in LaTeX don’t have to be pain.

In general, I don’t think the concept of a configuration database is bad - at least not inherently moreso than every application putting its own configuration file(s) in whichever format it wants somewhere on the filesystem.

Whether the window registry is a good implementation of this concept is surely debatable.

Nice until you’re at a hotspot that blocks most ports but the most common ones.

I use HTTPS for all stuff, that has given me the best results overall. But of course, you can offer multiple options simultaneously

Also game servers because they’re generally very easy to host at home, and due to generally high RAM and storage needs paying for hosting can be quite pricey.

Really?

I thought this was more the case with flexible providers like DigitalOcean. My current provider charges 5,36€ per month for 4 cores (though I assume this corresponds rather to 2 SMT-enabled cores), 6 GB of RAM and a 400 GB SSD. It offers better latency for most players (obviously not for myself) and in most cases has been sufficient regarding performance.

“how would I know”

Ah, ACLs, had the pleasure of working with these again last weeks.

It gets really curious when even the Arch wiki doesn’t really know what’s going on (talking about mask and effective permissions):

The factual accuracy of this article or section is disputed.

Reason: The original note about the --mask option (which was taken from setfacl(1)) was determined as inaccurate, but the new note does not seem correct either. See the talk page for details.

From trying, I can confirm that the info presented further down is wrong.

Once you read what it actually does and why it’s the way it is, it makes more sense - not that I remember it now - but at least there was a coherent design decision behind it

You’re not supposed to “sudo everything” though. It’s mostly for changing the system configuration (editing config files in /etc/, running your system package manager etc.). It shouldn’t be a “oh, I got a permission error, better sudo the same command again olol”

Maybe not the best acronym, with Node Package Manager around

Hence the comment about “bias automation”