Well, what problems are you trying to solve by having the classes all access each other’s data members? Why is that necessary?

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.

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.

Because I didn’t know absurdism, I read the second one differently at first:

[The] Nothing matters.

And I immediately had to think of this gem:

“But it doesn’t do anything!” - “No, it does nothing.”

I don’t really like including pedestrians in there. Like sure, you can fit a bunch of people in a small area, but another point you shouldn’t ignore is the throughput over time, and pedestrians are by their nature rather slow. Obviously if you’re looking at shopping in a street lined by shops left and right, then that street becomes tailor-made for pedestrian traffic (and nothing else except perhaps bicycles). But public transport is much better suited for travelling any further distances, and that should be the main focus when deciding to ditch cars.

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.