careful there buddy

Gosh I knew they were dumb but this is embarrassing

Never trust a fart they say

Crisis averted

Isn’t fitgirl a repacker?

Also, did recent denuvo games get cracked?

Dang

Absolute bonkers

Maybe 100 DLCs will fix it

Even earlier with Pokemon Stadium’s Gameboy emulator.

I worked in software certification under Common Criteria, and while I do know that it creates a lot of work, there were cases where security has been improved measurably - in the hardware department, it even happened that a developer / manufacturer had a breach that affected almost the whole company really badly (design files etc stolen by a probably state sponsored attacker), but not the CC certified part because the attackers used a vector of attack that was caught there and rectified.

It seemingly was not fixed everywhere for whatever reason… but it’s not that CC certification is just some academic exercise that gives you nothing but a lot of work.

Is it the right approach for every product? Probably not because of the huge overhead power certified version. But for important pillars of a security model, it makes sense in my opinion.

Though it needs to be said that the scheme under which I certified is very thorough and strict, so YMMV.

I was also with a provider that didn’t offer API access for the longest time. When they then increased prices, I switched, now paying a third of their asking price per year at a very good provider.

I guess migrating is difficult if the provider doesn’t offer a mechanism to either dump the DNS to a file or perform a zone transfer (the later being part of the standard).

Can only recommend INWX for domains, though my personal requirements aren’t the highest.

A lot of paid cert providers were not so great before LE put the spotlight on the issue; it was more of a scheme to extract money from operators who couldn’t afford to not offer TLS / SSL. https://bugzilla.mozilla.org/show_bug.cgi?id=647959 was a famous post that made fun of / criticized the system before LE. This hurt security, and if not free, LE wouldn’t have worked.

Also wildcard certificates are more difficult to do automated with let’s encrypt.

They are trivial with a non-garbage domain provider.

If you want EV certificates (where the cert company actually calls you up and verifies you’re the company you claim to be) you also need to go the paid route

The process however isn’t as secure as one might think: https://cyberscoop.com/easy-fake-extended-validation-certificates-research-shows/

In my experience trustworthyness of certs is not an issue with LE. I sometimes check websites certs and of I see they’re LE I’m more like “Good for them”

Basically, am LE cert says “we were able to verify that the operator of this service you’re attempting to use controls (parts of) the domain it claims to be part of”. Nothing more or less. Which in most cases is enough so that you can secure the connection. It’s possibly even a stronger guarantee than some sketchy cert providers provided in the past which was like “we were able to verify that someone sent us money”.

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.

The R in LLM stand for Return on Investment

True commitment to the craft

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).

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.