True, but at that point, every website I’ll ever visit and have visited in the past might be a threat, so that doesn’t really matter too much to me.

I’ve got several hits, but none of them have permission to request my location. If I understand the README correctly, that should mean I’m safe, right?

If you want the magic explained, here’s a start: https://en.wikipedia.org/wiki/Lempel%E2%80%93Ziv%E2%80%93Welch

Hardly a surprise, since Windows 10 didn’t need new hardware to run. You could install it on anything.

Cookies required for the website to work (like that one) are totally fine and, in fact, they don’t even have to ask you about them - if they’re not used for tracking. So no, asking each time is definitely avoidable.

Because you don’t need to have significant experience or rent a VPS in order to do that, and I can respect that. We don’t need to force FOSS developers to become proficient in everything.

What needs to happen is some kind of tool (ideally FOSS) that lets you spin up an actual forum with the same difficulty to set it up as Discord.

Huh, TIL.

Regarding your edit, that amount wasn’t the cumulated cost of whatever Limewire were distributing, that would be idiotic indeed; rather the RIAA tried to call for a ruling that somehow those guys were causing $150,000 in damages - per instance. Now the article unfortunately doesn’t state how they possibly tried to justify that number, and I can’t be bothered to research that myself. Another thing that would interest me is how the plaintiff expected them to pay with almost every dollar on Earth.

So while I don’t think this had anything to do with “lost sales”, I do agree with the possible fines and damage calculations not being fit for any sort of realistic purpose at all.

Late reply, but for me personally, I started doing it because my Keepass database is already accessed using two factors (password and key file). Therefore, I’d gain very little by keeping the second factor of those sites external - essentially, those second factors are compounded into the second factor for the database.