The difference between "read only" and "state updating write" is not nearly as clean cut as people like to pretend, even without regarding the technical differences between GET and POST requests. E.g. sites can have visit counters that update when someone visits, and that's a GET.
If you had a small black hole in a lab you could generate power from the hawking radiation, likely enough to power the entire world. A 1,000,000 ton black hole would last over a thousand years without feeding it more mass and produce about 300 TW of energy (increasing over time, so you better keep feeding it). You'd also need some pretty good sunglasses to be able to watch things being thrown into it. Also I'm not sure how you could throw anything into it given the amount of radiation pressure... Maybe a dedicated particle accelerator could do it.
Anything smaller while also lasting long enough to do an experiment on and you'd likely end up producing too much energy and destroying the planet.
Unfortunately when your power source black hole got smaller it would get hotter, finally reaching runaway at the end and detonating with hundreds of times the power of the Tsar Bomba.
Do note that that's a bit speculative. We haven't actually observed hawking radiation. And Hawking radiation definitely isn't what slows feeding in astronomical black holes, but radiation from the gas heating up as it falls.
The M87 supermassive blackhole is thousands of times as massive as Sagittarius A*, but since Sagittarius A* is a lot closer their emission rings appear roughly the same size in the sky (42 μas vs 51 μas). Both have already been imaged by the Event Horizon Telescope. https://en.wikipedia.org/wiki/Event_Horizon_Telescope
>it’s buried in the tags as grey on light grey on white.
if you happened to miss the tags, reading approximately any of the article should make it pretty clear.
"This report was reviewed by Legal, who have asked us to clarify that the fox was depicted as over eighteen and that the sunglasses remained on throughout."
it was just my favorite part. i can copy/paste all of the outlandish parts, if you want, but i would be copy/pasting the entire article.
ignoring the satire tag at the top of the page, some examples from the first ~20%:
- its on a personal blog, with no mention of what the actual product is
- resolving an incident "by treaty"
- "Severity: Informational → Critical → Withdrawn → Critical → Negotiated"
- incident *duration* measured in "billable tokens"
- link to a CVE named "YIKES"
- an incident being resolved by the attacker reading a file
- no dates provided, just "Day 1, 02:51 UTC"
- creats.io doesn't exist
Even if you remove a watermark, the companies still have a record of which images they have generated and for whom. Even if you remove the obvious watermarks, all major image generators are using steganography to embed hidden information that you can't be sure were removed. This is a type of one-sided arms race where one player gets to be invisible if they want to.
Yes usually, since an important aspect of steganography is error correction. For example we know that SynthID is robust enough to survive resizing and small blurs.
Thanks, tried it, but it's crashes on clicking the microphone icon. Default `make install` for some reason tries to install it to /usr, I changed that and after torturing more mature coding LLMs for 20 minutes, made it running with mic/sound.
The mic button requires clicking to transcribe and start listening again, and default voice is low-quality (I assume it can be configured).
In general I'm looking for a way to try the on-device hands-free voice mode.
It has been my experience that this is currently the case. I haven't had to even open protondb or search for a workaround in over a year. The only titles I know that don't work are a handful of multiplayer games that have intentionally disabled linux support.
It's not a database, it's just files. And they are hosted by Cloudflare so they can cope with a lot of downloads.
I think he should make the files smaller my removing the second half of the hashes, i.e. reduce it from 40 hex digits to 20. This increases the change of a false positive (i.e. I enter my password, it says it was compromised but it wasn't, it just has the same hash as one that did) from 1 in 10^48 to 1 in 10^24 (per password), but that's still a huge number. (There's less than 10^10 people in the world, they only have a few passwords each). This will approximately halve the download, maybe more because the first half of each hash is more compressible (when sorted) the second half is totally random.
> You are being purposefully obtuse here. HIBP is a very, very well established site with a long history of operating in good faith.
Allowing people to query and someone downloading the entire dataset is normally considered abuse, so being blocked is the expectation here. You're so dense you're bending light around you.
reply