you're not gonna brute force an AES256 key

if you have a bad password that's a user issue

You're not gonna remember a AES256 key either (or at least not many of them), not to mention the ergonomics associated with entering a AES256 key. The whole point of security chips like google's titan m2 or apple's secure enclave is to strengthen weak passwords (eg. 6 digit pins) so they offer comparable security to 256 bit keys, without having to enter 256 bit keys.

why is it so slow? it's around 50x slower than I would have expected for numbers https://github.com/ConstexprCore/perfect_hash

you can easily record lossless h264 via obs and any ffmpeg-backed player will play it just fine

the days where the OS matters for video playback are long gone

prores is not lossless. It's also an intraframe codec so compression is not great.

It depends what you mean by "not great". Prores's compression is far better than say H.264, if you actually want usable footage for editing.

not even for editing https://www.eoshd.com/comments/topic/46562-prores-vs-h264-vs...

I'm not sure what that graph is meant to be showing.

ssim by bitrate for prores, h264 with IPB frame types, and h264 with only i-frame types (which is a direct prores alternative) (the last one is for some reason not visible on this plot, only one post up)

pure text search (the deterministic kind you're talking about) is medieval technology that's useless in a web search engine

Yes, I'm aware. I meant that deteministic systems should be at the core (PageRank was deterministic), alongside other contextual clues and knowledge graphs -- things Google did before this AI overview crap.

What pisses me off is that you can't turn it off. Like, fine, you may bury and dark pattern the crap out of the disable toggle, but at least give users the choice to opt-out. And no, UDM=14 is not a toggle.

Is this related to the fact that I'm regularly unable to find many github repos via google?

I think github hides repos from indexing by default.

that never happened before. and kagi still shows them

Kagi might be (intentionally or accidentally) working around GitHub's attempt to prevent indexing of repos.

> did not respect our robots.txt

I don't see a problem

> ignored our Terms of Service

ban them from the service then and case closed?

> and defied the creators' licenses: 423 of the 712 projects are licensed for non-commercial use only

because it's been proven they have been used commercially?

I do. It's wrong to ignore a robots.txt.

The fact someone else may have licenced content for commercial use doesn't entitle someone else to do the same without paying for it. That's the whole point of copyright law.

title says DNS, article says access, so which is it?

All DNS servers operating in France are required to cooperate with the censorship regime, this is why Quad9 exited France. Presumably part of this new measure will be ISPs redirecting all port 53 traffic to their own resolvers.