US Citizen Faces Federal Charges After GrapheneOS Phone Auto-Wiped at Airport

·1 views

A US citizen was federally charged with obstruction of justice and destruction of evidence after their GrapheneOS-powered smartphone automatically wiped itself during a Customs and Border Protection search at a US airport in early 2026. CBP agents were attempting to access the device during a secondary inspection when the phone erased all its data, which prosecutors claim was a deliberate act to obstruct a lawful search. The defense argues the wipe was an automated security feature built into GrapheneOS, not a manual action by the traveler. The case is being closely monitored by digital rights groups including the EFF and ACLU, as it raises unresolved Fourth and Fifth Amendment questions about border search authority and encrypted devices. Legal experts believe this is among the first federal cases where a US citizen has been charged specifically in connection with a GrapheneOS auto-wipe at a border checkpoint.

Read the full story at DEV Community

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

Discussion (0)

Moonshot AI Releases Kimi-K3 Technical Report

Moonshot AI has published the technical report for its Kimi-K3 model, made available via the company's GitHub repository. The report details the architecture and capabilities of the K3 system, representing the latest release in the Kimi model series. The document was shared on Hacker News, where it drew early attention from the developer community. Kimi-K3 appears to be Moonshot AI's continued effort to advance its large language model research and development.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Missing Database Index Crashed a Live Launch With 400,000 Records Loaded

In 2021, a first-time startup developer in India helped build a full-stack app that was set to launch with over 400,000 pre-loaded user records in a MongoDB database. During the live launch event, the server began crashing after just 50 mid-level users signed up, largely because the database was running on an AWS free-tier EC2 instance with no room to scale. The root cause turned out to be a missing index on a key collection, forcing the CPU to scan all 400,000 records for every single query and pushing it to 100% utilization. The team quickly scaled up the server and added the missing index, rescuing the event in real time. Five years later, the same platform serves over 5 million users and runs at roughly 0.05 rupees per user per month after ongoing optimizations including Redis integration.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Minecraft Java Edition bumps recommended RAM to 16GB before Vulkan switch

Minecraft Java Edition has raised its recommended system memory requirement to 16GB, up from previous lower thresholds. The change comes ahead of a planned transition to the Vulkan graphics API, which is expected to significantly alter how the game handles rendering. Vulkan is a modern, low-level graphics API known for improved performance and better utilization of system resources. The higher memory recommendation suggests the upcoming engine changes will be more resource-intensive than the current implementation.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Developer finds hidden 'ip_reminder' tag in Claude Code session logs, raises cost concerns

A developer using Anthropic's Claude Code discovered an undisclosed system-prompt tag called 'ip_reminder' appearing repeatedly in local session logs stored under ~/.claude/projects/. By grepping the JSONL log files, the developer found 151 lines referencing the tag and 17 opening tags with zero corresponding closing tags in a single session. Several similar findings had previously been reported by other users on Anthropic's GitHub, with one claim citing over 10,000 hidden injections and another estimating roughly $133 in extra token costs at Opus 4 API rates. All related GitHub issues — totalling at least four — were closed by Anthropic with a status of 'not planned', without a public explanation. The episode has prompted questions about transparency around hidden context injected into user sessions and whether such overhead is reflected in cost reporting tools.

0 comments Read more at DEV Community