Sopel

you're not gonna brute force an AES256 key

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

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)

because crypto is just an excuse to speculate in an unregulated market

that's like asking "should I use an audi or a tesla"

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.

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

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

> 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?

well it kinda worked? over on reddit r/gaming thinks the data has been stolen

more radicalization towards AI

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

yes, you would have to allocate space for up to 100 file paths, but the article says

> it’s more efficient because it reduces the amount of calls into the file system, which is where the bottleneck is

Upon reading it a few times I think the article is alluding to a crappy two-pass solution where you don't store a filename but instead an index into a directory, which is flawed anyway due to being racy.