NO NO NO NO NO NO NO NO NO

I see, interesting. Do you know if there’s a way to completely prohibit an app from running in the background other than just using the “restricted” battery mode for it, which doesn’t stop it completely?

I only have 1 app active in the background and it’s a custom DNS. I’m very good about keeping all my apps closed when I’m not using them and notifications are disabled for most apps.

Phone batteries still do that

I can see why you’d prefer braces in that case. I actually personally prefer {} over indentation as a matter of opinion, I just see them both as working fine 99% of the time. I’d also definitely take indentation over some shenanigans like start/end to define scopes.

I don’t understand why people complain about their Python code breaking because it relies on indentation instead of explicit {} syntax. I’ve never had an issue with it and it’s not just because I’m used to it because Python is the only language I use that relies on whitespace like that. I think the complainers just don’t know how to indent properly, which makes me really glad they’re writing in a language that forces them to instead of pushing unreadable garbage in other languages.

I have chronic pain and can confirm that this is NOT the case.

You don’t suffer after you’re dead. Being reincarnated and killed infinite times is infinitely worse than being killed once. If each trolley kills at the same rate, the actual amount of created suffering should be comparable, but I’d argue that since the infinite people don’t revive, we can assume that the trolley is replacing their normal deaths. This means that the suffering they would experience from dying normally never happens and the infinite people option actually creates less suffering overall.

Yep. Not always larger necessarily, but close to the same size on average, or maybe a little smaller if the domain is limited and compression can be applied. Not really useful.

I don’t really get why people use any time other than ms/seconds since the epoch for anything other than displaying that time to the end user. Having time just be a single number with no time zone shenanigans makes writing logic like that so much easier.

If they can prove you got a bunch of gold with a loan and then your descendants suddenly have a bunch of gold, but they can’t prove it’s the same gold, is that enough to make the descendants pay back the loan?

What if you did it with Monero to make it impossible to prove it’s the same money?

Put it on 90% “sale” all the time.

I know that’s illegal, but when have laws mattered to pharmaceutical companies?

Holy hell. So I guess cloaking technology already exists, it’s just that the octopuses got to it first.

I only tried one example, so the sample size is pretty small, but that search engine seems pretty bad. I tried looking up “rust bevy points” in both Google and Yep. The first Google result is a library to draw points in Bevy and the rest are pretty relevant. Yep simply doesn’t have that result at all and all of their results are just generic results about Bevy.

I tried DDG for the sake of comparison and it’s somewhere in-between. The results are mostly relevant and the “correct” result is still on the first page.

Oh ok, makes sense.

That’s sad to hear.

What about the irreparable harm caused by outlandish fees, or will they be forced to pay those back?

I think that you’re right that this wouldn’t count as a meme in most situations, but it still fits the sub because it’s political. The downvote situation would seem to imply that the majority disagree with us, but I don’t care and neither should you. The majority can be wrong.

You need to make sure to remove excess whitespace from the JSON to speed up parsing. Have an AI read the JSON as plaintext and convert it to a handwriting-style image, then another one to use OCR to convert it back to text. Trailing whitespace will be removed.

I don’t even like tankies, but this one didn’t say anything wrong.