Even if you’re poking at a black box and are reporting that “it acts funny when I poke it this way.” I’m my opinion, a reporter should send along a script or at least explicit instructions on how to repro.

I take the report more serious since it demonstrates you have an understanding of the issue or exploit. It will also save my time and it’s likely a trivial effort for the reporter since they’ve the context and knowledge of the issue loaded up and ready to go.

Agree that people like to fluff the severity of bugs they report. It’s better for prestige and bounty payouts. But this is a little more nuanced.

“While I didn’t really intend the module to be used for any security related checks, I’m very curious how an untrusted input could end up being passed into ip.isPrivate or ip.isPublic [functions] and then used for verifying where the network connection came from.”

It’s interesting, that it would be hard to make a case that there was a “vulnerability” in the ip package. But it seems like this package’s entire purpose is input validation so it’s kind of weird the dev thinks otherwise.

Recurring incidents like these raise the question, how does one strike a balance? Relentlessly reporting theoretical vulnerabilities can leave open-source developers, many of who are volunteers, exhausted from triaging noise.

The researchers need to provide proofs of concept. Actual functional exploits.

BAT is trash but I’d love to see more quick crypto donation options.

They went bankrupt in 2018 and are but a shell of what they once were.

On new install without logging in a Microsoft account?

They do, and did. Perhaps this reaction with the ozone layer just hasn’t been considered until now.

One of the better blunt rotations.

Just put up a free charging station or an outlet with a USB port in a hotel and you got yourself free USB connections to phones.

I can never bring myself to connect to those things.

For those unaware: https://en.wikipedia.org/wiki/Mobile_virtual_network_operator

“Bitcoin mining may be our last line of defense against a CBDC [Central Bank Digital Currency],” Trump said in a Truth Social post Tuesday.

lol, no shot he wrote this.

I’d still own one if they were just banned on highways. The risk is probably pretty low on low speed city streets, where these would be most useful.

Their 2x spicy is great. Now I really want to find and try the 3x.

No clue what that means. I was thinking more along the lines of how there’s 3+ techniques for async functions. Or that there’s a handful of syntax implementations, versions, and supersets of the language. Or that there are many interpreters all with different standard libraries and quirks.

It’s an annoyingly flexible language.

Oh, and there’s at last 2 other ways to do it too.

You say that like this shit is hard to use.

Oh yeah, I agree it’s super inefficient currently. But if the theoretical 100% efficient process is 5% of our current yearly energy expenditure, that sounds promising and suggests we shouldn’t just write off the idea.

Looks like a specially modified SyncThing was just used for exfil.

Just click this link bro. Just one more link man. Just click it I need it.

Can’t imagine “shutting down completely for just two weeks” would exactly be reasonable, but yeah I wonder if the article had a typo in it. I’m not sure. As of right now, the numbers are still the same in the article.

If the numbers are correct, expending like 5-10% of our energy expenditure for a single year on carbon capture sounds a lot more reasonable than the article suggests. Even if it were half of our yearly energy usage, that sounds pretty reasonable if you draw that out over a few decades.

By stealing its photons!

(it’s a joke)