Dev accidentally commits Copilot binary to FreeBSD ports repo

The FreeBSD project froze its ports repository on Wednesday. The reason turns out to be a slightly embarrassing Git-related oopsie where a version of Copilot got uploaded somewhere it should not have been. The announcement of the 2026 Ports Repository Freeze went out on July 21 and remained in effect the following day, as explained in a message on the freebsd-announce mailing list. The mail delicately skirted around exactly what happened: « The commit in question severed our ports tree mirroring to github.com due to their filesize hard limit of 100MB, and introduced a blob of questionable licensing into the repository history. » The offending commit is this one. It’s not a disaster; the problem is that the Ports repository is automatically mirrored to various places, including a read-only Github mirror – and as Github’s docs say, “GitHub blocks files larger than 100 MiB.” There is already an official FreeBSD port of Copilot, but FreeBSD terminology is slightly confusing here: the “port” is effectively a sort of package that allows the Linux binary to run inside FreeBSD’s Linux emulation, called the Linuxulator. It isn't a native FreeBSD version of Copilot, and the package is not meant to include the actual Copilot CLI binary – partly because that is under its own custom license. That’s what FreeBSD’s Kyle Evans meant by “questionable licensing”. We don’t blame anyone for using any available resources to help with using GitHub. Navigating Linux, FreeBSD, and worst of all Git is hard, especially the last one. Git is aptly named – it’s not an acronym, it’s a real word: someone annoying or unpleasant. It is, however, now more or less the de facto standard version control system of the FOSS world. Despite not being a developer, the Reg FOSS desk worked with Git on a daily basis for over four years – blame the Docs as Code philosophy – and developed a deep and abiding dislike for it. It’s not just us: it’s in an XKCD comic, so it must be true. (This vulture has directly lived the experience described in that comic.) Personally, we always found Git much harder work than the tar command. It should come as no surprise that multiple teams are working on compatible alternatives. A Game of Thrones Trees Just the day before some FreeBSD developer’s regrettably public mishap, a new version of one of those alternatives appeared: Game of Trees version 0.127. Game of Trees, known as Got for short, is a Git-compatible version control system (VCS) developed by contributors to the OpenBSD Project. It’s been in development since 2019, and we feel that the project has a nice line in self-deprecation – starting with the homepage’s project description: “a version control system which prioritizes ease of use and simplicity over flexibility.” This is, we suspect, in response to Git’s self-description, which says that it is “designed to handle everything from small to very large projects with speed and efficiency.” We also like the Got project goals and especially the FAQ, which really does not beat about the bush: « Does Got aim to replace Git? No. Got does not aim to replace Git. Got can be used instead of Git (for some tasks), or in addition to Git. If you are already using Git and are happy with it, you don’t need Got. » And even more succinctly, under the anchor “pointless”: « What’s the point of all this? Why not just use Git? If you are wondering why Got even exists, you can just ignore it. » Got isn’t the only tool that aims to remain compatible with Git, but simplify the experience. Gitless is another, which describes itself as “a simple version control system built on top of Git,” and says that it’s “easy to learn and use.” Unfortunately, development seems to have gone quiet: the last release appeared the same year that Got appeared. Another (and even younger) Git-compatible VCS is Jujutsu, often called just “Jj”, and not to be confused with the traditional Japanese martial art Jiu Jitsu. Jujutsu the VCS has lots of documentation, but if it has a weakness, it's that it rather assumes that you already know your way around VCS use in general and Git in particular. If that’s not the case for you, you might find Jujutsu for Everyone by Remo Senekowitsch more helpful. ®

source https://www.theregister.com/os-platforms/2026/07/24/dev-accidentally-commits-copilot-binary-to-freebsd-ports-repo/5278458

Read More

Hackers hijack hotel Wi-Fi DNS to steal Microsoft 365 accounts

Hackers are changing the DNS settings on Wi-Fi devices at hotels and conference centers to redirect users to fake Microsoft 365 login pages. [...]

source https://www.bleepingcomputer.com/news/security/hackers-hijack-hotel-wi-fi-dns-to-steal-microsoft-365-accounts/

Read More

New Dolphin X malware uses AI to rank high-value targets

A new Dolphin X remote access trojan claims to use an AI-powered profiling feature to score and rank infected users, helping cybercriminals identify which victims should be targeted first. [...]

source https://www.bleepingcomputer.com/news/security/new-dolphin-x-malware-uses-ai-to-rank-high-value-targets/

Read More

Codeberg gives vibe-coded projects the toss, promotes human FLOSS

You can take your vibe-coded project elsewhere. Codeberg, a volunteer-run code hosting community, has decided that AI-authored software is no longer welcome. On Thursday, Codeberg announced that the members of Codeberg e.V., the Berlin-based non-profit overseeing the code hosting service, had voted to ban "vibe-coded projects" and declared that Codeberg would not use users’ code or data for AI training due to its impact on Free, Libre and Open Source Software (FLOSS). The vote follows ongoing efforts by Codeberg to prevent automated software (bots) from taxing its infrastructure with excessive network requests. Authors Bastian Greshake Tzovaras, Otto Richter, and William Zijl argue that AI companies are shifting costs to others and damaging online communities in the process. "LLMs are so costly that companies externalize the costs on a massive scale – on those who don't use them and society at large," they wrote in a blog post. "Increased hardware prices, energy use and environmental damage – we all pay for it!" They point to the cost of Codeberg's SSD and memory hardware as an example, noting that a drive that only a few years ago cost €700 (~$800) now costs €3,700 (~$4,200) – if it's even in stock. The result is that Codeberg has been forced to raise prices. The authors also call out the proliferation of projects that often involve a solo developer "working with a statistical machine that turns energy into code." They fault these folks for not having any community and argue it's unreasonable for Codeberg to spend its limited CI/CD and storage resources on ghost projects. But the vote isn't simply about unfair resource consumption. It reflects broader unease among Codeberg members about the damage AI coding models are doing to the FLOSS community. AI-driven price hikes, they contend, are broadening the digital divide by making personal computers less affordable, forcing more people toward corporate-owned cloud services. And beyond the environmental harm of increased water and energy use, the Codeberg authors argue that LLM use is undermining the foundation of trust and community that makes FLOSS work. "The widespread use of LLMs in FLOSS is instead becoming a multidimensional attack on the trust between contributors and the very idea of convivial collaboration itself," they state. LLMs magnify maintainers' workloads, create confusion around whether projects will be maintained, and "lead to 'license laundering', where copyleft code is stripped of its reciprocity requirements by 'generating' it out of the training data." "As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons," the authors conclude. As a consequence of the community vote, projects developed and maintained mostly by an AI agent are no longer welcome at Codeberg and are urged to move to other hosting options. This is reflected in amended Terms of Use language: "You must not share projects that mostly consist of code written by 'generative AI'-tools (including services such as Claude, OpenAI Codex). Such projects having an unclear copyright status … and furthermore have little safeguards to ensure that they do not include harmful code." Enforcement of the ban seems unlikely, however, unless a project draws attention to itself, given Codeberg's statements about limited resources and its overburdened workforce. Support for the vibe-coding ban was substantial but not overwhelming, with some celebrating the decision and others condemning it. Among Codeberg members, 358 voted in favor, 144 voted against, and 14 abstained. About half the active members voted. "I think this is a very bad move, and the people behind Codeberg should re-consider their stance," said Armin Ronacher, creator of Flask and one of the co-founders of AI agent biz Earendil. On its way toward Free, Libre, and Open Source Software equilibrium, Codeberg also decided to ban cryptocurrency projects, citing a similar move by SourceHut in 2023. A proposed amendment to make it Codeberg's stated purpose "to oppose discrimination and promote a diverse FOSS community" passed with a two-thirds vote but is not yet merged. The protection extended to philosophical outlook does not cover belief in AI. ®

source https://www.theregister.com/ai-and-ml/2026/07/23/codeberg-gives-vibe-coded-projects-the-toss-promotes-human-floss/5277717

Read More

Australian energy provider Origin says data breach exposes client data

Origin Energy has confirmed that an unauthorized party accessed and subsequently leaked customer data online, exposing sensitive personally identifiable information (PII), among others. [...]

source https://www.bleepingcomputer.com/news/security/australian-energy-provider-origin-says-data-breach-exposes-client-data/

Read More

Fake Claude app promoted by Bing ads pushes SectopRAT malware

A malvertising campaign on the Bing search service is pushing a fake Claude desktop app installer hosted on a legitimate Claude.ai domain to deliver the SectopRAT malware. [...]

source https://www.bleepingcomputer.com/news/security/fake-claude-app-promoted-by-bing-ads-pushes-sectoprat-malware/

Read More

South Korea discloses data breach impacting diplomats worldwide

South Korea disclosed that hackers breached the National Diplomatic Academy's online education system for ten months and stole personal information belonging to current and former employees of the Ministry of Foreign Affairs (MFA), including overseas diplomats. [...]

source https://www.bleepingcomputer.com/news/security/south-korea-discloses-data-breach-impacting-diplomats-worldwide/

Read More

Codeberg’s programmer user base overwhelmingly votes to ban slopcoded projects from its platform

What happens when programmers get to vote on a complete ban on slopcoded software on their code platform? Members of Codeberg were asked to vote on a proposal to completely ban slopcoded projects from Codeberg, and in what should not be a surprising outcome to anyone not overcome with “AI” hysteria, the vast majority voted in favour of the complete ban: over 70% of Codeberg members voted to ban slopcoded projects entirely (358 in favour, 144 against, 14 abstentions).

Of course, this is not a surprising outcome. Stripped down, programming is a form of artistic expression, and programming is no different than writing, painting, composing, or any other artistic endeavour. I think it’s safe to say writers, painters, composers, and similar creatives are against “AI”, so it’s only natural programmers feel the same; poll after poll shows the overwhelming majority of respondents – usually well over 70-80% – are against “AI”.

The pro-“AI” accounts on OSNews often try to paint my anti-“AI” position as extremist, but in reality, I’m just voicing how 70-80% of people clearly state they feel. I have zero skin in this game, zero outside pressure to please any bosses to get that promotion, zero pressure to conform to avoid getting laid off, zero pressure to not contradict upper-management. I can speak freely, openly, and without fear of retaliation. And as Nikhil Suresh explains in his harrowing from-the-trenches article AI Mania Is Eviscerating Global Decision-Making, that’s a massive asset.

The vast majority of people – including your friends, family, and co-workers – really hate “AI”. You can either accept this, or be left behind.

source https://www.osnews.com/story/145583/codebergs-programmer-user-base-overwhelmingly-votes-to-ban-slopcoded-projects-form-its-platform/

Read More

Fresh off AI layoffs, Block now wants to whack Slack with agent-human collab tool

After cutting over 4,000 jobs due to AI, fintech biz Block is back with Buzz, a shared workspace where humans and bots can collaborate in ways that are more auditable, sovereign, and secure than what you can do in chat tools such as Slack. Block's human-bot co-op is built upon a turducken of tech jargon: The platform is free and open source. It's based on the decentralized Nostr protocol, so there's cryptographic identity. It's "sovereign," a naively optimistic term readers of Neal Stephenson's Snow Crash should recognize, which in this context means self-hostable. And it's intended as a replacement for Slack, GitHub, and various other communication and collaboration tools. If "Buzz" sounds familiar, that's because Google used that name in a social media faceplant more than 15 years ago. For those who missed the first go-around, Google Buzz, a failed social media service, gave rise to Google+, also a failed social media service. Block appears to believe that a decade and a half is sufficient for a brand cleanse. The project's GitHub repo offers a more apologetic assessment: "Yes, it's another AI-adjacent developer tool. We're sorry. The difference is what agents can actually do once they're inside: open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels, and pull in whoever needs to see it. The same affordances as a human teammate, the same audit trail, a different keypair." You can already sic software agents on collaborative workspaces. Block's main insight is that it would be useful to link AI agents with cryptographic identities. Others have already arrived at that conclusion. Hence OWASP's Agent Name Service, DNS for AI Discovery, Estonia's digital IDs for agents, and so on. But Buzz's badging of humans and bots with cryptographic key pairs is bound to tick governance boxes. "Every company is going to need a place where humans and agents work together," said Bradley Axen, head of AI capabilities at Block, in a statement. "The question is whether that place is proprietary or open. We built Buzz because we believe it should be open." Moat-seeking tech incumbents would probably disagree about the need for openness, even though they're fond of using the word without applying it. We note that OpenAI sells closed AI. And Anthropic's decision to disallow third-party tools from using Claude subscriptions highlights the seemingly inevitable path from openness to barriers when revenue is at stake. What's more, it's not obvious that every company will need people and bots in the same space. There's a strong case for keeping humans and agents apart because they work at different speeds. Git at least was built for handling many distributed code edits, pull requests, and merges. It's hard to see how people and bots can share a text-based communication space unless the bots are rate-limited or just talk among themselves. "The bet is that one community can do what teams currently fake with chat, forges, bots, CI dashboards, release tools, search indexes, and a pile of glue code," Block's Buzz developers state. "Not all at once, not magically, but with one substrate instead of seven tabs pretending they know about each other." If tools for these sorts of things didn't already exist, and no large tech companies had designs on this space, Buzz might face less daunting odds. But it's worth a shot. ®

source https://www.theregister.com/ai-and-ml/2026/07/22/fresh-off-ai-layoffs-block-now-wants-to-whack-slack-with-agent-human-collab-tool/5276529

Read More

US Marines' latest anti-drone toy is an AI turret that uses regular machine guns

The US military is adding autonomous gun-based counter-drone systems intended to reduce its reliance on expensive interceptor missiles. They also have the potential to kill humans. Defense robotics firm Allen Control Systems (ACS) announced a deal with the US Marine Corps on Monday to get its Bullfrog autonomous weapon system attached to the Light Marine Air Defense Integrated System (L-MADIS) expeditionary counter-drone platform. L-MADIS consists of pairs of off-road vehicles, one carrying a suite of sensors and the other slated to be outfitted with a Bullfrog autonomous weapon station. Videos on ACS’ YouTube page demonstrate the Bullfrog in action, taking down a number of small drones in demonstrations over the past couple of years. While we didn't hear back from ACS about the Bullfrog's capabilities to target manned vehicles and troops, a short video on the company's channel also shows a Bullfrog unit switching from targeting aerial drones to ground targets with ease. This suggests that Bullfrog systems aren't just capable of knocking drones out of the sky. They are also fully capable of - and lack any software protections against - the fully autonomous targeting and killing of humans with complete autonomy. Bullfrog systems are a little different from your typical AI-controlled counter-drone systems in that they’re not built with an attached weapon, but are designed to slot in “any legacy or modern firearm” in order to turn them into systems able to “detect, track, and defeat incoming threats at a fraction of the cost of even the least expensive kinetic interceptors.” In other words, ACS claims it's cheaper to build a system that can adapt existing military firearms than to invest in a purpose-built counter-drone weapon system. Bullfrog units provide the AI, computer vision, and precision aiming robotics to take out drones, while the military only has to plug in its own hardware. There are several variants of the Bullfrog available from ACS, with units designed for everything from the M240 machine gun to the M2 50-caliber machine gun. The company is currently working on M230 chain gun and M134 minigun variants as well. In the case of the Marine Corps contract, it appears the service is taking on some M240 variants based on a link in ACS’s press release to the M240-variant’s page. The M240, the smallest of the weapons designed for the Bullfrog, fires up to 850 7.62×51 mm NATO rounds per minute and is effective up to 800 meters in the Bullfrog. The Bullfrog M240 is capable of taking down drones up to DoD Group 3, meaning anything with a max gross takeoff weight less than 1,320 lbs, able to operate as high as 18,000 feet above sea level, and with an airspeed of less than 250 knots. The DoD grouping goes up to Group 5, which includes some of the military's largest drones, such as the RQ-4 Global Hawk. The US Army and US Navy are both already fielding Bullfrog units, making the Marines the third branch to get their hands on the system. ACS cited the proliferation of cheap drones in the Russia/Ukraine conflict and in the Middle East as a need for comparable cheap counter drone tech. ®

source https://www.theregister.com/offbeat/2026/07/21/us-marines-latest-anti-drone-toy-is-an-ai-turret-that-uses-regular-machine-guns/5275691

Read More

Anubis ransomware claims Coca-Cola Fairlife attack, threatens data leak

The Anubis ransomware gang has claimed responsibility for the cyberattack on Coca-Cola's Fairlife dairy subsidiary, threatening to publish allegedly stolen corporate data unless the company pays a ransom. [...]

source https://www.bleepingcomputer.com/news/security/anubis-ransomware-claims-coca-cola-fairlife-attack-threatens-data-leak/

Read More

Iran says it's struck offline AWS facility in Bahrain ... again

Iran's Islamic Revolutionary Guard Corps (IRGC) claims it hit an AWS datacenter in Bahrain months after taking it offline for the first time, in a move it claimed as retaliation for a US attack on a nuclear plant that was under construction. The IRGC said in a statement on Tuesday that it had struck back at what it called the "child-killing US Army" by attacking Amazon infrastructure in Bahrain, claiming AWS's "central data infrastructure" had been "destroyed" after being hit by "several cruise missiles," according to Google Translate. The IRGC said the claimed strike was retaliation for what Iran described as a US attack on the under-construction Darkhovin nuclear facility. A look at the AWS Health Dashboard shows that there are definitely issues in Bahrain and the UAE, with issues in both regions being blamed on the US-Iranian conflict. While the status of AWS me-central-1 (UAE) is just “unable to reliably support customer applications,” me-south-1 (Bahrain) is said to be “currently unavailable.” The last update to the state of AWS services in Bahrain and the UAE in the open issues area of the Dashboard was on April 30, and the Service History tab shows that every single AWS service in Bahrain has been offline for months. Per our previous reporting, Iranian state-affiliated media claimed that strikes on AWS infrastructure in Bahrain and the UAE were deliberate, after US and Israeli attacks on Iran in late February. AWS-hosted providers including Snowflake and Red Hat subsequently urged affected customers to fail over or move workloads to other regions after the facilities were damaged. AWS waived all usage-related charges for March 2026 in its me-central-1 region in the UAE following the attacks on its infrastructure. Iran has also reportedly designated facilities associated with Google, IBM, Microsoft, Nvidia, Oracle, and Palantir as legitimate targets for retaliatory strikes, citing their alleged support for US military operations. The fact that services in Bahrain have been unavailable for months, and continue to be offline, makes it challenging for El Reg to confirm the legitimacy of Iranian claims it hit the site again. We’ve reached out to AWS to learn more, but didn’t hear back. ®

source https://www.theregister.com/off-prem/2026/07/21/iran-says-its-struck-offline-aws-facility-in-bahrain-again/5275762

Read More

Full Volleyball Match 4K 🏐 Weekend Warriors vs Spike Squad | Shreewoods, Dhanori, Pune | 18 July 2026

Weekend Warriors vs Spike Squad — Shreewoods Weekend Volleyball, 18 July 2026 (4K)

Weekend Warriors vs Spike Squad — spike at the net, Shree Woods, Siddartha Nagar, Dhanori, Pune (18 July 2026)

Another cracking weekend of local volleyball at Shree Woods, Siddartha Nagar, Dhanori, Pune. On 18 July 2026, Weekend Warriors squared off against Spike Squad in a full, end-to-end match — big spikes, stubborn blocks, scrambling digs and some genuinely long rallies on the red-clay court. We filmed it all in 4K and cut it into the full set below so you can relive the game however you like.

The story of the match

This one had everything grassroots volleyball does best — no officials, no timeouts, just two sides going all out. The attackers went up hard at the net, the back line kept balls alive that had no business staying up, and the rallies kept building until someone finally put the ball down. Watch the Best Plays Montage for the highlights, then the Full Match for the complete flow of the game, and drop into Slow-Motion to see the spikes frame by frame.

Weekend Warriors vs Spike Squad — airborne attack, Shree Woods, Siddartha Nagar, Dhanori, Pune (18 July 2026)

The players and the community spirit

What keeps this going is the crowd of regulars — friends, neighbours and passers-by from Dhanori who turn up every weekend to play or cheer. No club fees, no gatekeeping: just show up, rotate in, and play. The photos below are pulled straight from the 4K footage.

Community weekend volleyball — Shree Woods, Siddartha Nagar, Dhanori, Pune

How we film and produce every match

Every match is shot in 4K, then cut into a full edit, a slow-motion breakdown, a best-plays montage and a highlights reel — with the spikes, blocks and long rallies pulled out frame by frame for the gallery.

Weekend Warriors vs Spike Squad — rally in full swing

Watch every version (4K)

📺 Raw Combined (LIVE)

🔥 Best Plays Edit (9 min)

🎯 Match Highlights

🏐 Best Plays Montage

🐢 Slow-Motion Best Plays

📱 Slow-Motion (Mobile)

📸 Every best play — the full gallery (226 shots)

Tap any photo to open the full-resolution 4K still.

Reel-format stills (9:16)

Playlists

• 📺 Full Volleyball Matches: Watch the playlist
• 🎥 Raw LiveStreams: Watch the playlist
• 🩳 Best-of Shorts (a new one daily): Watch the playlist

Come play with us 🏐

We play every Saturday & Sunday — mornings 8:00 AM and evenings 4:30 PM — at Shree Woods, Siddartha Nagar, Dhanori, Pune (Google Maps). All levels welcome. Subscribe to Explore NY Stream for a fresh local volleyball match every weekend, plus daily Shorts of the best spikes and rallies.

Read More