SShortSingh.
Back to feed

Court Rules Fourth Amendment Does Not Cover AI-Generated Probable Cause

0
·3 views

A court has reportedly ruled that the Fourth Amendment's protections do not extend to probable cause determinations generated by artificial intelligence. The decision was highlighted in a Techdirt report published on November 19, 2026. The source material offers limited detail beyond the headline and linked discussion, so specifics about the case and its parties are not available. The ruling raises questions about how constitutional search and seizure standards apply when law enforcement relies on AI tools.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

The 21-Day Habit Myth Traces to a 1960 Preface; Research Points to About 66 Days

The popular claim that habits form in 21 days originated in a 1960 book by plastic surgeon Maxwell Maltz, who described it as a minimum time for a mental image to change, not a rule for behaviour. A 2010 University College London study tracked 96 volunteers over 12 weeks and found automaticity rose along a curve that plateaued, with a median of 66 days to reach 95% of the plateau and a range of 18 to 254 days. A 2024 systematic review of 20 studies reported similar medians of 59 to 66 days. Neuroscience work from MIT in 1999 found that rats' striatal neurons came to encode well-learned routes as single chunks, supporting the idea that habits are gradually consolidated rather than switched on.

0
ProgrammingDEV Community ·

IETF 127 hackathon shows independent verifiers disagreeing on identical evidence data

At the IETF 127 Hackathon in San Francisco in November 2026, several teams building verifiable records of AI agent actions had outside developers write verifiers from their documents alone. Each implementation passed its own tests, but the verifiers diverged when run against one another. One project's two reference verifiers gave different serializations of the same number and reached conflicting ALLOW and DENY verdicts. A separate comparison of four JSON canonicalization implementations produced differing bytes on a small share of test cases, mainly involving very large integers, byte order marks, duplicate members, and deep nesting. Operators comparing receipts from two transparency logs also found the same statement yielded different leaf hashes, because the specifications do not fix the entry serialization. The authors say these results point to the need for explicit rules, such as refusing ambiguous inputs, to keep verification consistent across implementations.

0
ProgrammingDEV Community ·

pdfjs-dist Font Files Can Go Missing From Next.js Standalone Builds

A developer found that the standard_fonts directory bundled with pdfjs-dist can be left out of Next.js standalone output because file tracing cannot detect how it is loaded at runtime. The omission fails silently, since missing fonts raise no error and only text extraction from PDFs using standard fonts such as Helvetica breaks. In pdfjs-dist v6, an unresolvable font path makes getTextContent() throw, which a surrounding try/catch can hide, leaving near-empty extracted text. The team addressed this by explicitly including the directory in configuration via outputFileTracingIncludes. They also added a fail-fast check at production startup to catch the directory if it goes missing again.

0
ProgrammingDEV Community ·

Browser cat extension's CPU cost cut by moving walk animation to Web Animations API

The developer of Tabloaf, a pixel cat that walks across Chrome and Firefox pages, found that a clip-path on its moving canvas roughly doubled Chrome's GPU process CPU use while the cat walked. Earlier, the cat's walk ran on requestAnimationFrame, and switching straight walks and runs to Element.animate() reduced load further. To keep clicks accurate, the developer split the cat into a non-interactive canvas and a separate hit element shaped by a clip-path, both moving on the same animation clock. In Chrome, this brought the GPU process down from about 14% to about 6% of a core during a walk, while in Firefox the page process fell to roughly 2%. The post also explains that the hit outline was simplified during walks, trading some precision for lower overhead.