Wouldn’t surprise me if even Unicode advices against using Roman numerals depending on meaning.

It was mostly a joke (though frankly if you try any implementation more complicated than that joke you’re going to have a bad time).

It’s simple ⅯⅯⅩⅩⅣis a number, MMXXIV is not.

I mean Fibonacci did more or less the same thing to his work a few centuries later, so fair play I guess.

You can stick your tongue in it. Wouldn’t recommend actually trying to get anything in your mouth.

You’re protected by the thin layer of nitrogen that immediately sublimates, this lasts until the nitrogen heats up so the liquid can touch you directly, which you want to avoid.

For mostly the same reason you can stick a finger into molten lead (without losing said finger), provided you do it fast enough and your finger is wet enough.

If someone’s licking any of the transuranic elements I’m not sticking around to watch.

Some stuff should simply not exist in a lickable quantity.

O(1)

They definitely didn’t just stop tracking you because this option exists.

Cookies are a non-issue. They store data only locally and can be edited and removed at will. With third party isolation on by default there’s really no reason to worry about them much anymore. And if you do just install cookie auto-delete to clean things up.

This variant is definitely worse because the data is no longer just local.

One of the better uses I’ve seen involved using this perspective to turn what was effectively a maximum likelihood fit into a full Gaussian model to make the predicted probabilities more meaningful.

Not that it really matters much how the perspective is used, what’s important is that it’s there.

Just because you don’t know what the uncertainties are doesn’t mean they’re not there.

Most optimization problems can trivially be turned into a statistics problem.

So what you’re saying is that if you put a burrito inside a burrito it’s still a burrito?

I am, no worries.

Using reverse proxies is common enough now that quite a few apps can deal with subpaths, and for the ones that can’t you can generally get nginx to rewrite the paths for you to make things work.

The extra syntax is just to add some features that aren’t in CSS. Not quite sure where this came from, I think it’s from the Adblock Plus era, but Gorhill perfected it for uBlock origin, which makes it a very powerful tool.

It’s not limited to just hiding the elements either, if you want you can simply restyle them (I’ve used this to redact sports results until I hovered over them).

Fair. It’s not too hard, but most lemmy UIs make it a bit harder than it needs to be because they want to be a fancy JavaScript-ridden mess of html tags.

On old.lemmy.world it is supremely easy, you just use the element picker tool of uBlock to select all posts, add the ‘magic’ command :contains(reddit) to filter out the word you don’t want (in this case reddit), and you’ve got your filter. This would result in old.lemmy.world##.post:contains(reddit).

On lemmy.world it is trickier because it is the kind of HTML no sane person would write. Doing the above you end up with lemmy.world##div.mt-2.post-listing:contains(reddit) which is messy, and misses a line that is used to divide the posts. With some manual tuning you can first simplify the first part to ##.post-listing:contains(reddit) and then add :xpath(.|following::hr[1]) to get rid of the annoying line. This results in ##.post-listing:contains(reddit):xpath(.|following::hr[1]).

Word filtering is fairly easy to do if you know your way around uBlock filters.