191–199 of 199 posts
Earlier quoted context omitted.
We need a more efficient way to eliminate bullshit patents or bullshit patent infringement claims than "violate them then spend millions on lawyers to fight them in court".
Sure, and at the same time we need a more efficient way to ensure big companies can’t just take what they want and bury anyone who complains. It’s not an easy problem.
Not on topic, but wow the internet has very quickly devolved into: click -> "making sure you're not a bot", click -> "making sure you're a human", click -> "COOKIES COOKIES COOKIES", click -> "cloudflare something something"
We had to set it up on the parts of VideoLAN infra so the service would remain usable. Otherwise it was under a constant DDoS by the AI bots.
Earlier quoted context omitted.
The "can't" comes from the fact that VLC is not going to rewrite their forum software or software forge. Software written in PHP is in most cases frankly still abysmally slow and inefficient. Wordpress runs like 70% of the web and you can really feel it from the 1500ms+ TFFB most sites have. PhpBB is not much better. Pathetic throughput at best and it has not gotten better in decades now. I don't know how GitLab beca…
> Wordpress runs like 70% of the web and you can really feel it from the 1500ms+ TFFB most sites have. PhpBB is not much better. At least phpBB died 15 years ago with most communities migrating to Xenforo. I'm not quite sure how or why WP is still around with so many SSGs and SaaS site builders floating around these days.
Earlier quoted context omitted.
I think there's a few things at play here - AI scrapers will pull a bunch of docs from many sites in parallel (so instead of a human request where someone picks a single Google result, it hits a bunch of sites) - AI will crawl the site looking for the correct answer which may hit a handful of pages - AI sends requests in quick succession (big bursts instead of small trickle over longer time) - Personal assistants may…
Also, relevant for forges: AI doesn't understand what it's clicking on. Git forges tend to e.g. have a lot of links like “download a tarball at this revision” which are super-expensive as far as resources go, and AI crawlers will click on those because they click on every link that looks shiny. (And there are a lot of revisions in a project like VLC!) Much, much more often than humans do.
It's simply bad, inefficient software and we shouldn't keep making excuses for it.
is there any understanding of how big of an improvment av2 will be over av1?
About 30% better compression than AV1 at equivalent quality. But it'll be a while before it's a good idea to use AV2 in your home media server. (AV1 is still not that broadly supported)
Claimed by the authors or actually based on anything more than "trust me bro"?
Earlier quoted context omitted.
Also, relevant for forges: AI doesn't understand what it's clicking on. Git forges tend to e.g. have a lot of links like “download a tarball at this revision” which are super-expensive as far as resources go, and AI crawlers will click on those because they click on every link that looks shiny. (And there are a lot of revisions in a project like VLC!) Much, much more often than humans do.
This is also irrelevant to the original comment which is complaining about bot checks for looking at the root of the repositiory - which is probably the highest requested resource and should be 100% served from cache with a cost much less than running the bot checks. It's simply bad, inefficient software and we shouldn't keep making excuses for it.
The only issues I found amounted to "here's how to use Anubis to block everything"
There's also some new but poorly supported standards around agents setting `Accept: text/markdown` and https://github.com/cloudflare/web-bot-auth
Earlier quoted context omitted.
riscv is primarily used in microcontroller or peripheral cores on an soc. It'll be a while yet until it is competitive on application cores that applications people run on such that we adopt it in mass. Arm and x86 are also not legacy or going away. The choice to focus on them is rational at this time.
I hear you, I disagree. We do not need to argue over this, but rather, we can see what happens over the next couple years.
Earlier quoted context omitted.
> AV2 is the next-generation video coding specification from the Alliance for Open Media Oh no. Not another one. I presume this one makes lossy better, or faster or both.
Why do you not want another one? We're approaching a decade since AV1 released. There's plenty of improvement to put into a new format.
Like what ? Lossy compression has nothing to offer since about 10 years ago.
Is there a flac for video ? Is there a codec able to "guarantee" DVD quality on today's internet ? Those "up to" really sound like "up your's".
Earlier quoted context omitted.
Why do you not want another one? We're approaching a decade since AV1 released. There's plenty of improvement to put into a new format.
> There's plenty of improvement to put into a new format Like what ? Lossy compression has nothing to offer since about 10 years ago. Is there a flac for video ? Is there a codec able to "guarantee" DVD quality on today's internet ? Those "up to" really sound like "up your's".
h.266 is about 1/3 smaller than AV1, so it fits about 50% more video per megabyte at the same quality. AV2 will almost certainly be better than h.266
> Is there a flac for video ?
ProRes is a close equivalent.
> Is there a codec able to "guarantee" DVD quality on today's internet ? Those "up to" really sound like "up your's".
Basically no. You won't find a video distribution codec that guarantees any level of quality because they're all configurable. And youtube in particular is always tweaking the quality dial as low as they can. But if you can get a bitrate that would be passable with h.264, then AV1 will look good and AV2 will look great at the same bitrate.
And they can all beat a DVD with a fraction of the bitrate. You just have to not get greedy.