made you look
By claiming that you own patents on technology used by said format.
The “open royalty free” aspect applies to companies that are a part of the AOMedia group, if you’re not involved with them you’re not covered by the patent grants and restrictions in place, and can charge whatever the courts say is cool.
The best part of the article is the very end, even if the site makes it look unrelated.
Avanci’s Video pool and Access Advance’s Video Distribution Patent pool are both now seeking content royalties from streaming services for the use of HEVC, VVC, VP9, and AV1. Access Advance’s rates are capped at roughly $63 million per year, and Avanci has published rates of 1.6% to 2.0% of revenue or $0.12 to $0.15 per user per month.
$4.5 million max for H.264 is rookie numbers vs. the $63 million max for AV1
There’s BlackSky now, the first full outside server setup (Things like relays and PDSs are just smaller components of the larger required stack)
So you know, they’re at 2 total instances currently.
I remember seeing that years ago, wanted to make like a photoresist mask to etch it into metal.
These days you could probably feed it to a laser engraver, get some nice depth on a thicker sheet of e.g. aluminium, would be a nice display piece at least.
It’s not just bug reports; in the last month, AI driven development has actually gone from slop to reliably better than the average human.
Funny, I heard that same claim about 6 months ago.
And I’m sure I’ll hear it again in another 6 months or so.
Can thank Intel for that, they pressured MS to lower the documented requirements so they could sell more low-end hardware.
Of course, MS executives also gladly went along with it, not like they’re innocent in any way.
Also Nvidia and their drivers caused issues, as usual.
I agree with you, but the cash example is a bad one because there is a push to move entirely to electronic payments.
Some newer radiation hardened stuff is 10x larger than that, older gear even more so. But that just reduces the risk, not sure it’s possible to negate it entirely.
An easier way is to just include more CPUs as part of the system, run them in lockstep, then compare the results by majority rule. If 2/3 CPUs say one answer and the third says something else, you discard the result of the third and go with the other CPUs.
The ladybird devs are currently in the process of switching language again from Swift to Rust, using LLMs.
This isn’t sending your packets anywhere but their closest datacenter, not sure I’d trust MS (Or rather, Cloudflare) with your porn rather than your ISP who you’re actually paying.
The original use case for this stuff was unencrypted HTTP with a public WiFi connection, in which case your ISP is the owners of whatever shop you’re in and yeah they could see everything.
If you’re at home or whatever it offers effectively no benefits, doesn’t “block trackers” or whatever nonsense like Nord claims, but I don’t think Microsoft ever claimed that it did.
IPFS has gateways though, so you can link to the latest version of a page which can be updated by the owner, or alternatively link to a specific revision of the page that is immutable and can’t be forged.
Seems like we need to switch to URLs that contain the SHA256 of the page they’re linking to, so we can tell if anything has changed since the link was created.
IPFS says hi
It’s the same person running all of them, so yeah it is.
No, Nokia do own a bunch of patents on it, I’m pretty sure they also created (and have patents on) the HEIF format used in HEIC/AVIF as well.
Edit: search results were failing me, but here’s a couple.
https://blogs.windows.com/devices/2013/03/18/h-265hevc-high-quality-video-at-half-the-bandwidth/ https://mspoweruser.com/nokia-details-its-contribution-to-h-265hevc-hints-at-integration-in-devices/
Much in the same way that laws don’t prevent crime, a project banning AI contributions doesn’t stop people from trying to sneak in LLM slop, it instead lets the project ban them without argument.
SpaceX wrote in its July permit application — under the header Specific Testing Requirements — Table 2 for Outfall: 001 — that its mercury concentration at one outfall location was 113 micrograms per liter. Water quality criteria in the state calls for levels no higher than 2.1 micrograms per liter for acute aquatic toxicity and much lower levels for human health
Cool, you can drink the mercury water, but I’ll pass thanks.
I’ve got some numbers, took longer than I’d have liked because of ISP issues. Each period is about a day, give or take.
With the default TTL, my unbound server saw 54,087 total requests, 17,022 got a cache hit, 37,065 a cache miss. So a 31.5% cache hit rate.
With clamping it saw 56,258 requests, 30,761 were hits, 25,497 misses. A 54.7% cache hit rate.
And the important thing, and the most “unscientific”, I didn’t encounter any issues with stale DNS results. In that everything still seemed to work and I didn’t get random error pages while browsing or such.
I’m kinda surprised the total query counts were so close, I would have assumed a longer TTL would also cause clients to cache results for longer, making less requests (Though e.g. Firefox actually caps TTL to 600 seconds or so). My working idea is that for things like e.g. YouTube video, instead of using static hostnames and rotating out IPs, they’re doing the opposite and keeping the addresses fixed but changing the domain names, effectively cache-busting DNS.
To me lying implies an intent to deceive, LLMs can’t do that as they have no intentions or understanding of the output they produce.
It’s not lying, because it’s also not telling the truth either, it’s just statistically weighted noise.