Actually, I wouldn’t be surprised if screenshots are disabled in that app considering the rest, to “stop leaking sensitive information”.
Actually, I wouldn’t be surprised if screenshots are disabled in that app considering the rest, to “stop leaking sensitive information”.
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.
There are pros to this:
If the person you blocked can’t see your posts, they can intuit that you’ve blocked them. Then, they might try and find you on other social media to harass you even further, or shift targets to someone else.
If they can see your posts, they have no idea they’ve been blocked, similar to Reddit’s shadow bans. This might make them think you’re just annoyed or rarely look at your DMs, making them invest even more time to uselessly try to contact you.
Of course, I can see the other side too, that you don’t want them to know about any (new) posts you’ve made; but it isn’t as one-sided as you seem to think it is.
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.
Danke für den Tipp, muss ich mir mal gerade einen Bericht mit Namen “niemand” erstellen und Maimais pfostieren, damit er in Betracht gezogen wird…
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.”
Depending on the stuffing, I might actually rather take the seat, just because it’s got armrests.
Gotcha, I didn’t catch that on my first read-through.
This seems wrong…
10^17 milligrams
-> 10^14 grams
-> 10^11 kilograms
-> 10^8 tons
So it should actually be 553 402 322 tons, which means that we can do it only using the rice produced in 2022.
But you just completely ignored everything I said in that comment.
Mathematically, that is precisely how O notation works, only (as I’ve mentioned) we don’t use it like that to get meaningful results. Plus, when looking at time, we can actually use O notation like normal, since computers can indeed calculate something for infinity.
Still, you’re wrong saying that isn’t how it works in general, which is really easy to see if you look at the actual definition of O(g(n)).
Oh, and your computer crashing is a thing that could happen, sure, but that actually isn’t taken into account for runtime analysis, because it only happens with a certain chance. If it would happen after precisely three days every time, then you’d be correct and all algorithms would indeed have an upper bound for time too. However it doesn’t, so we can’t define that upper bound as there will always be calculations breaking it.
It’s very pedantic, but he does have a point. Similar to how you could view memory usage as O(1) regardless of the algorithm used, just because a computer doesn’t have infinite memory, so it’s always got an upper bound on that.
Only that’s not helpful at all when comparing algorithms, so we disregard that quirk and assume we’re working with infinite memory.
That may be true for smaller cities, but in bigger cities it becomes impossible, because there just isn’t enough space to house all the people near areas of interest. Cars don’t factor in there at all. Give me a subway for the major areas, and perhaps a tram or bus system so you don’t need that many subway stations in the residential areas, and you can have car-free city centers.
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.
That’s something I would disagree with though. “Sticking with plain HTML and CSS” is way more work, and often has significantly less functionality, than building a website with a framework.
Well, what problems are you trying to solve by having the classes all access each other’s data members? Why is that necessary?