Forgot your password?
typodupeerror

Comment Success rate? (Score 2) 35

Anecdotes are great for swaying the mindless but how about some statistics on the rate of success this thing has. I would also want to know the rate of false identifications because who wants to have their hopes dashed?

However, what would VASTLY improve helping lost pets is directly microchip reading into the computer. I'm not joking when I say, the biggest issues with microchip'd pets is that many times, the ID code read from the chip, shown on the scanner display, and then is manually transcribed into the computer. This results in a lot of transcription errors which is something absurdly high like 7%. Sometimes the transcription error happens upon registration, sometimes it's upon lookup. Either way, if everyone simply used readers that relayed the info directly to the computer then a lot more pets would be reunited with their owners.

Comment Only 8 years late (Score 3, Interesting) 42

One has to question why Dolby would wait 8 years before making a peep. Yeah, AV1 was released in March 28th, 2018 which was exact 8 years ago, and this is the first time they have ever made any claim about it. What about Snapchat? The complaint states that Snapchat has used AV1 for video streaming "since at least November 24, 2023" but it appears that they have been using the "dav1d" AV1 decoder all the way back in Mar 21, 2019 which wasn't long after it was announced.

Their extreme delay should be enough to dismiss this case but I know it's not.

As far as I can tell, it see like Dolby was trying to wait until AV1 started getting hardware implementations in order to make alterations maximally harmful, in order to either extract the largest settlement or maximally disrupt the competition to HVEC. Either way, it seem like Dolby is acting in bad faith.

In response to Alain Williams comment, "How long before a patent troll magics up some patent relating to AV1 ?" It seems the answer is 7 years and 5 months.

Submission + - IBM quantum computer simulates real magnetic materials and matches lab data (nerds.xyz)

BrianFagioli writes: IBM says its quantum computer can now simulate real magnetic materials and match actual lab experiment results, which is something people have been waiting years to see. Instead of just theoretical output, the system reproduced neutron scattering data from a known material, meaning it lines up with real world physics. It still relies on a mix of quantum and classical computing and this is a narrow use case for now, but it is one of the first times quantum hardware has produced results that scientists can directly validate against experiments, which makes it a lot more interesting than the usual hype.

Submission + - Non-US made WiFi Routers Banned by FCC (pcmag.com)

phatrabt writes: The FCC has now banned any WiFi routers not made in the US from being sold unless granted a waiver from the Pentagon or Homeland Security. PC Mag says:

"Late on Monday afternoon, the FCC announced the order, based on a White House determination that foreign-made routers introduce “supply chain vulnerabilities” that hackers and cyberspies can exploit. Specifically, the commission updated its “covered list,” which acts as a blacklist of telecom equipment deemed to pose an unacceptable risk to US national security. It now includes “all consumer-grade routers produced in foreign countries.”

However, the FCC stresses, “This action does not affect any previously purchased consumer-grade routers. Consumers can continue to use any router they have already lawfully purchased or acquired.”

“Nor does it prevent retailers from continuing to sell, import, or market router models approved previously through the FCC’s equipment authorization process,” the commission adds.

Submission + - NetRise Provenance wants to track who writes your open source code after XZ back (nerds.xyz)

BrianFagioli writes: In the wake of the XZ Utils scare, NetRise has introduced a tool called Provenance that shifts the focus from whatâ(TM)s in your software to who put it there. The platform maps open source components back to maintainers and contributors, then traces how their code propagates through dependency chains. The goal is to give enterprises faster answers when a trusted contributor turns out to be a problem, something traditional SBOMs donâ(TM)t really address.

The idea may appeal to organizations trying to get a handle on supply chain risk, but it also raises questions about where this leads. Tracking contributors by identity, organization, or even geography could help with compliance, yet it may clash with the open nature of many projects. Itâ(TM)s not clear whether tools like this actually reduce risk or just add another layer of visibility that looks reassuring on a dashboard while the underlying trust model remains just as fragile.

Slashdot Top Deals

"A car is just a big purse on wheels." -- Johanna Reynolds

Working...