Congress quietly removed provisions that would have let the U.S. military fix its own equipment without relying on contractors, despite bipartisan and Pentagon support. The Register reports: The House and Senate versions of the NDAA passed earlier both included provisions that would have extended common right-to-repair rules to US military branches, requiring defense contractors to provide access to technical data, information, and components that enabled military customers to quickly repair essential equipment. Both of those provisions were stripped from the final joint-chamber reconciled version of the bill, published Monday, right-to-repair advocates at the US Public Interest Research Group (PIRG) pointed out in a press release. [...] According to PIRG's press release on the matter, elected officials have been targeted by an "intensive lobbying push" in recent weeks against the provisions. House Armed Services Committee chair Mike Rogers (R-AL) and ranking Democrat Adam Smith (D-WA), responsible for much of the final version of the bill, have received significant contributions from defense contractors in recent years, and while correlation doesn't equal causation, it sure looks fishy. [Isaac Bowers, PIRG's federal legislative director] did tell us that he was glad that the defense sector's preferred solution to the military right to repair fight -- a "data as a service" solution -- was also excluded, so the 2026 NDAA isn't a total loss for the repairability fight. "That provision would have mandated the Pentagon access repair data through separate vendor contracts rather than receiving it upfront at the time of procurement, maintaining the defense industry's near monopoly over essential repair information and keeping troops waiting for repairs they could do quicker and cheaper themselves," Bowers said in an email. An aide to the Democratic side of the Committee told The Register the House and Senate committees did negotiate a degree of right-to-repair permissions in the NDAA. According to the aide and a review of the final version of the bill, measures were included that require the Defense Department to identify any instances where a lack of technical data hinders operation or maintenance of weapon systems, as well as aviation systems. The bill also includes a provision that would establish a "technical data system" that would "track, manage, and enable the assessment" of data related to system maintenance and repair. Unfortunately, the technical data system portion of the NDAA mentions "authorized repair contractors" as the parties carrying out repair work, and there's also no mention of parts availability or other repairability provisions in the sections the staffer flagged -- just access to technical data. That means the provisions are unlikely to move the armed forces toward a new repairability paradigm.

Read more of this story at Slashdot.

On a recent immigration raid, a Border Patrol agent wore a pair of Meta’s Ray-Ban smart glasses, with the privacy light clearly on signaling he was recording the encounter, which agents are not permitted to do, according to photos and videos of the incident shared with 404 Media.

Previously when 404 Media covered Customs and Border Protection (CBP) officials’ use of Meta’s Ray-Bans, it wasn’t clear if the officials were using them to record raids because the recording lights were not on in any of the photos seen by 404 Media. In the new material from Charlotte, North Carolina, during the recent wave of immigration enforcement, the recording light is visibly illuminated.

That is significant because CBP says it does not allow employees to use personal recording devices. CBP told 404 Media it does not have an arrangement with Meta, indicating this official was wearing personally-sourced glasses.

An activist in Charlotte provided the photos and videos to 404 Media. 404 Media granted them anonymity to protect them from retaliation.

They said the encounter happened at a busy intersection surrounded by a forest where a flower seller usually sets up shop. “By the time we showed up, the flower vendor had apparently seen Border Patrol agents approaching, and he ran into the woods,” the activist said. “They then deployed agents that were wearing these bucket hats into the woods.”

One of those agents was wearing the Meta Ray-Ban glasses, the material shows.

When we initially wrote about CBP agents wearing Meta Ray-Bans in Los Angeles, privacy experts told 404 Media that Department of Homeland Security (DHS) policies ban agents from wearing personal recording devices and also explicitly ban agents from taking their own recordings.

CBP’s policy on recording devices states that “no personally owned devices may be used in lieu of IDVRS [Incident Driven Video Recording Systems] to record law enforcement encounters.” It adds that “recorded data shall not be downloaded or recorded for personal use or posted onto a personally owned device.” The broader DHS policy says that “the use of personally owned [Body Worn Cameras] or other video, audio, or digital recording devices to record official law enforcement activities is prohibited.”

In a statement to 404 Media, a CBP spokesperson reaffirmed that the agency does not have any contract with Meta, and said that agents cannot use personal recording devices, but can bring “personally purchased sunglasses.” The statement did not say anything about what happens if the sunglasses happen to have a camera and microphone inside of them.

“CBP does not have an arrangement with Meta. The use of personal recording devices is not authorized; however, Border Patrol agents may wear personally purchased sunglasses,” the CBP spokesperson told 404 Media. “CBP utilize Go Pros mounted to helmets or body armor at times, as well as traditional DSLR handheld cameras.” 

Meta did not respond to a request for comment.

In November, DHS launched an operation it called “Charlotte’s Web,” focused on the North Carolina city. In its announcement, DHS pointed to several criminals it said it detained. Data recently obtained by the CATO Institute showed that 73 percent of people detained by ICE since October had no criminal convictions, and five percent had a violent criminal conviction.

Tech giants including Meta, Alphabet, Microsoft and Amazon have all extended the estimated useful lives of their servers and AI equipment over the past five years, sparking a debate among investors about whether these accounting changes are artificially inflating profits. Meta this year increased its depreciation timeline for most servers and network assets to 5.5 years, up from four to five years previously and as little as three years in 2020. The company said the change reduced its depreciation expense by $2.3 billion for the first nine months of 2025. Alphabet and Microsoft now use six-year periods, up from three in 2020. Amazon extended to six years by 2024 but cut back to five years this year for some servers and networking equipment. Michael Burry, the investor portrayed in "The Big Short," called extending useful lives "one of the more common frauds of the modern era" in an article last month. Meta's total depreciation expense for the nine-month period was almost $13 billion against pretax profit exceeding $60 billion.

Read more of this story at Slashdot.

Paramount Skydance is launching a hostile bid to buy Warner Bros. Discovery after it lost out to Netflix in a months-long bidding war for the legacy assets, the company said Monday. CNBC: Paramount will go straight to WBD shareholders with an all-cash, $30-per-share offer. That's the same bid WBD rejected last week, according to people familiar with the bid who asked not to be named because the details were private. The offer is backstopped with equity financing from the Ellison family and the private-equity firm RedBird Capital and $54 billion of debt commitments from Bank of America, Citi and Apollo Global Management. "We're really here to finish what we started," Ellison told CNBC's "Squawk on the Street" Monday. "We put the company in play." On Friday, Netflix announced a deal to acquire WBD's studio and streaming assets for $72 billion. David Ellison-run Paramount had been bidding for the entirety of Warner Bros. Discovery, including those assets and the company's TV networks like CNN and TNT Sports.

Read more of this story at Slashdot.

A Republican call to give Americans cash instead of health insurance subsidies revives an old idea that has left millions with medical debt.

(Image credit: Kevin Dietsch)

It runs locally, a free/open source home automation platform connecting all your devices together, regardless of brand. And GitHub's senior developer calls it "one of the most active, culturally important, and technically demanding open source ecosystems on the planet," with tens of thousands of contributors and millions of installations. That's confirmed by this year's "Octoverse" developer survey... Home Assistant was one of the fastest-growing open source projects by contributors, ranking alongside AI infrastructure giants like vLLM, Ollama, and Transformers. It also appeared in the top projects attracting first-time contributors, sitting beside massive developer platforms such as VS Code... Home Assistant is now running in more than 2 million households, orchestrating everything from thermostats and door locks to motion sensors and lighting. All on users' own hardware, not the cloud. The contributor base behind that growth is just as remarkable: 21,000 contributors in a single year... At its core, Home Assistant's problem is combinatorial explosion. The platform supports "hundreds, thousands of devices... over 3,000 brands," as [maintainer Franck Nijhof] notes. Each one behaves differently, and the only way to normalize them is to build a general-purpose abstraction layer that can survive vendor churn, bad APIs, and inconsistent firmware. Instead of treating devices as isolated objects behind cloud accounts, everything is represented locally as entities with states and events. A garage door is not just a vendor-specific API; it's a structured device that exposes capabilities to the automation engine. A thermostat is not a cloud endpoint; it's a sensor/actuator pair with metadata that can be reasoned about. That consistency is why people can build wildly advanced automations. Frenck describes one particularly inventive example: "Some people install weight sensors into their couches so they actually know if you're sitting down or standing up again. You're watching a movie, you stand up, and it will pause and then turn on the lights a bit brighter so you can actually see when you get your drink. You get back, sit down, the lights dim, and the movie continues." A system that can orchestrate these interactions is fundamentally a distributed event-driven runtime for physical spaces. Home Assistant may look like a dashboard, but under the hood it behaves more like a real-time OS for the home... The local-first architecture means Home Assistant can run on hardware as small as a Raspberry Pi but must handle workloads that commercial systems offload to the cloud: device discovery, event dispatch, state persistence, automation scheduling, voice pipeline inference (if local), real-time sensor reading, integration updates, and security constraints. This architecture forces optimizations few consumer systems attempt. "If any of this were offloaded to a vendor cloud, the system would be easier to build," the article points out. "But Home Assistant's philosophy reverses the paradigm: the home is the data center..." As Nijhof says of other vendor solutions, "It's crazy that we need the internet nowadays to change your thermostat."

Read more of this story at Slashdot.