The project, contributed by Databricks and now hosted under Linux Foundation governance, extends the Delta Sharing protocol beyond structured data into AI-era assets such as agent skills, machine-learning models and unstructured data volumes. Its backers say the goal is to reduce reliance on proprietary marketplaces, one-off integrations and duplicated data pipelines that have slowed cross-platform AI deployment.

OpenSharing arrives as companies seek to build AI systems that can operate across clouds, data lakes, private infrastructure and business partners without locking sensitive information into a single vendor stack. The protocol is designed to let organisations publish data and AI assets once, with standard mechanisms for discovery, authorisation and access, while allowing recipients to consume them through different platforms.

The Linux Foundation said the project is intended to provide community-governed infrastructure for secure AI collaboration at scale. Jim Zemlin, its chief executive, said OpenSharing addresses “a critical need” for a common framework that lets organisations exchange AI assets securely and interoperably across platforms and ecosystems.

Databricks has positioned the move as the next stage of Delta Sharing, which it introduced in 2021 for secure data exchange. Delta Sharing has been used across analytics and business intelligence tools including Apache Spark, Oracle, Power BI, Tableau and Snowflake, and by enterprises including Amadeus, Atlassian, LSEG, SAP, Stripe and The Trade Desk. OpenSharing broadens that base by adding support for Apache Iceberg recipients and by covering AI assets that were not part of traditional data-sharing workflows.

Matei Zaharia, Databricks co-founder and chief technology officer, said Delta Sharing had shown that the industry would choose “open over locked-in”. He said OpenSharing extends that principle to the full AI stack, including Iceberg recipients and on-premises providers.

A central selling point is the ability to connect on-premises and private-cloud data sources to cloud-based AI and analytics systems without moving the underlying data. Storage partners including Everpure, MinIO and Qumulo are listed among early providers, with Cohesity, Commvault, HPE, NetApp, Nutanix, Rubrik and VAST Data named as additional partners. That architecture could be significant for financial services, healthcare, telecoms and public-sector users that face data residency, audit and security requirements.

The announcement reflects a wider shift in enterprise AI from model selection towards infrastructure control. Companies deploying autonomous or semi-autonomous agents increasingly need standard ways for systems to discover capabilities, use data, call tools and exchange outputs across organisational boundaries. Without common protocols, agents can remain trapped in isolated software environments, limiting their usefulness in procurement, compliance, customer operations, logistics and software development.

OpenSharing is not the only standardisation effort gaining ground. The Agent-to-Agent protocol, originally developed by Google and now hosted by the Linux Foundation, focuses on how AI agents discover, communicate and transact across frameworks and vendors. The Model Context Protocol has also become an important part of the integration debate by standardising how agents connect to tools and enterprise systems. OpenSharing’s narrower role is to address the exchange of data and AI assets rather than agent communication alone.

The launch also comes amid evidence that AI adoption is creating as many organisational bottlenecks as technical breakthroughs. A European technology talent study found employers expect AI to have a positive net hiring effect of 27% in 2026 and 17% in 2027, with demand particularly strong for AI-specific roles. Yet security concerns affect 51% of organisations and privacy concerns 44%, while gaps in cybersecurity, AI operations, cloud computing and data engineering are limiting deployment.

Europe’s challenge is especially acute. AI talent in the EU more than doubled between 2016 and 2023, but still represents only 0.41% of the workforce. Women account for less than a quarter of AI engineers across Europe, and in some cities the share is as low as 11%. Germany issued nearly 78% of all EU Blue Cards in 2023, highlighting how skilled migration remains concentrated in a few markets rather than evenly spread across the bloc.

Enterprises are responding by prioritising internal training. Upskilling existing staff is now favoured over external hiring because it preserves institutional knowledge, lowers recruitment costs and improves team cohesion. Open source has also become a core strategy for AI implementation, particularly for organisations seeking sovereignty, lower licensing costs and reduced dependence on dominant technology suppliers.

The article OpenSharing pushes enterprise AI beyond vendor silos appeared first on Arabian Post.

The migration gives JPL a unified platform for running traditional virtual machines alongside containerised applications, allowing teams to modernise core workloads without forcing an abrupt break from legacy systems that support highly specialised mission environments. The decision positions OpenShift as part of a broader operational shift inside space agencies and research organisations, where hybrid cloud architecture is being used to support scientific computing, secure application delivery and long-duration spacecraft operations.

JPL selected Red Hat OpenShift with built-in virtualisation capability to support a high-performance environment designed for complex mission workloads. The platform enables virtual machine migration and management while providing a consistent foundation for future cloud-native applications. That combination is significant for a laboratory whose systems must support mission planning, spacecraft data processing, telemetry handling, software development and operational continuity across projects that can run for years or decades.

The laboratory, federally funded by NASA and managed by the California Institute of Technology, is central to the United States’ robotic exploration programme. Spacecraft developed at JPL have flown to every planet in the solar system and beyond, while its teams support missions spanning Mars, Jupiter, Earth science, asteroid exploration and deep-space communications. Its operational environment is therefore unusually sensitive to downtime, software fragmentation and infrastructure complexity.

A key part of that workload is the Deep Space Network, the global communications system managed and operated by JPL’s Interplanetary Network Directorate. Its complexes in California, Spain and Australia provide continuous communications coverage with spacecraft as Earth rotates. The network supports interplanetary missions, radio astronomy, radar astronomy and selected Earth-orbiting missions, making reliability and scheduling efficiency central to mission success.

The OpenShift deployment comes as deep-space operations are being reshaped by heavier data flows and more demanding spacecraft instruments. Missions such as Europa Clipper, launched in 2024 and due to reach Jupiter in 2030, require long-term operational planning, radiation-tolerant hardware, repeated flybys and extensive science data management. JPL also supports missions such as Psyche, Mars rover operations and Earth observation programmes that add to the pressure on mission systems.

OpenShift Virtualization allows organisations to run virtual machines on Kubernetes-based infrastructure, reducing the divide between established applications and newer container-based services. For JPL, that means existing workloads can remain operational while development teams gain a path to automation, microservices and AI-ready application patterns. The model is designed to avoid the operational risk of replacing mature systems too quickly, particularly in environments where software certification, security reviews and mission continuity impose strict constraints.

Security is a major element of the platform choice. OpenShift includes role-based access control, network policy controls and SELinux security contexts, while related tools support compliance monitoring and runtime security across clusters. Such controls are important for agencies handling sensitive mission systems, scientific data and operational pipelines connected to spacecraft communications.

The move also reflects a broader enterprise technology trend. Organisations with large virtual machine estates are reassessing infrastructure strategies as they seek alternatives that can support both legacy workloads and application modernisation. Open-source platforms have gained ground where institutions want portability across data centres, private cloud and public cloud environments while retaining control over security and operations.

For Red Hat, the JPL deployment reinforces OpenShift Virtualization as more than a migration tool. The company is positioning the platform as a bridge between traditional virtualisation and cloud-native computing, particularly for organisations that cannot simply abandon established workloads. The JPL case gives that message a high-profile reference point in one of the most demanding technical environments in government science.

JPL’s operational needs are distinct from standard enterprise computing. Spacecraft missions often involve customised software, long service lives, rigorous validation requirements and interfaces with ground systems that must function across vast distances. Signals from deep-space spacecraft may take minutes or hours to travel, leaving little room for unreliable support systems on the ground. Infrastructure modernisation must therefore be incremental, secure and carefully controlled.

The migration is also aligned with the growing role of automation in mission support. Deep-space operations involve complex scheduling, telemetry processing, instrument planning and cross-team coordination. A platform that can simplify workload management, automate repeatable tasks and support consistent deployment practices offers potential efficiency gains across technical teams managing multiple spacecraft and science programmes.

The article JPL shifts mission systems to OpenShift platform appeared first on Arabian Post.

The project, initially developed at Infoblox, is being positioned as a neutral discovery layer for the emerging agentic web, where software agents are expected to act across websites, enterprise systems, cloud platforms and developer tools with limited human intervention. Its backers argue that agent-to-agent communication will require the same kind of open, scalable naming infrastructure that allowed the public internet to grow beyond closed networks.

DNS-AID, short for DNS AI agent Discovery, uses DNS as a global directory for publishing and finding metadata linked to autonomous agents and Model Context Protocol servers. The approach is intended to allow organisations to advertise agent capabilities inside their own DNS namespace, while giving other systems a standard way to locate the relevant endpoint, access protocol and supporting metadata.

The project comes under Linux Foundation governance with support from Cloudflare, CSC, Equinix, GoDaddy, Indeed, Infoblox, Internet Systems Consortium and WWT. That coalition places DNS-AID at the intersection of internet infrastructure, enterprise networking, domain management and AI application development, reflecting a wider industry push to prevent agent discovery from becoming controlled by a small number of platform operators.

The technical foundation is tied to work advancing through the Internet Engineering Task Force, where a DNS-AID draft was published in March 2026 as a standards-track proposal. The draft describes a method for using DNS to support scalable and interoperable discovery between AI agents, including a structured namespace and record usage model for metadata exchange and capability advertisement. It does not propose changes to DNS message structure, new operation codes, new response codes or new resource record types.

That design choice is central to the project’s appeal. By relying on DNS infrastructure already deployed across public and private networks, DNS-AID seeks to avoid the operational burden and governance risks associated with building a new global registry for agents. Developers can use existing DNS providers and internal DNS systems, while enterprises retain control over their own agent naming and publication policies.

The reference implementation includes a Python software development kit, a command-line interface and an MCP server, giving developers a way to test publication and discovery workflows without waiting for a full standards process to conclude. The project repository describes the implementation as separate from the protocol specification, with protocol-level changes expected to be handled through the IETF process.

Security is one of the main drivers behind the initiative. As agents begin to call tools, trigger workflows, exchange data and act on behalf of users or organisations, weak discovery mechanisms could allow malicious systems to impersonate trusted services or insert themselves into sensitive processes. A compromised discovery path can widen the attack surface even where application-level safeguards and model controls are in place.

DNS-AID’s supporters see DNSSEC, DNS-based Authentication of Named Entities, service binding records and service discovery mechanisms as part of the trust framework needed for agent identity and verification. The aim is not merely to help agents find each other, but to give systems a consistent method for evaluating where an agent is published, who controls its namespace and what metadata is being presented.

The project also fits into a broader Linux Foundation strategy around multi-agent infrastructure. The foundation has already brought agent-focused initiatives such as AGNTCY under its governance, with work covering discovery, identity, messaging and observability across agent systems. DNS-AID is narrower in scope, focusing specifically on DNS-based discovery, but its arrival strengthens the foundation’s role as a neutral venue for agent interoperability projects.

Competition and overlap remain likely. Other proposals, including Agent Name Service and academic work around agent directories, are exploring identity, verification, routing and capability registries for autonomous systems. Some approaches rely more heavily on new directory layers, public key infrastructure or specialised schemas. DNS-AID’s advantage lies in its use of the internet’s existing naming fabric, though that also means it inherits DNS’s complexity, governance debates and security limitations.

Enterprise adoption will depend on whether vendors and developers see DNS-based discovery as practical for real deployments. Large organisations already rely on DNS for service discovery, traffic routing and security policy enforcement, but AI agents introduce faster-changing metadata, fine-grained capability descriptions and policy questions around who may discover or invoke a given agent. Public discovery may suit some use cases, while regulated sectors may prefer internal namespaces and restricted visibility.

The article Linux Foundation anchors AI agents in DNS appeared first on Arabian Post.

Mozilla has released Firefox 150 with a broad security update that fixes 41 vulnerabilities, including multiple high-impact flaws tied to memory handling, browser components and privilege controls, prompting renewed calls for users and enterprise administrators to move quickly on patching. Mozilla’s advisory for the release was published on April 21, 2026, and classed the overall impact as high.

The most serious issues include CVE-2026-6746, a use-after-free flaw in Firefox’s DOM Core and HTML component, and CVE-2026-6747, another use-after-free bug in the WebRTC component. Mozilla rated both as high impact. Such flaws matter because use-after-free weaknesses can allow attackers to manipulate memory after it has been released, a class of bug long associated with browser crashes, data corruption and, in worst cases, remote code execution if successfully chained and exploited. The same advisory also lists high-impact problems in Web Codecs, Canvas2D, WebRender and the JavaScript engine, underlining how widely the patched weaknesses were spread across the browser stack.

Mozilla’s advisory also includes memory-safety entries that state some bugs showed evidence of memory corruption and were presumed capable, with enough effort, of being exploited to run arbitrary code. Those bundled entries, covering Firefox 150 as well as supported ESR branches and Thunderbird builds, reinforce the severity of the release even where individual exploit chains were not publicly described. Alongside the main Firefox 150 release, fixes were also shipped for Firefox ESR 140.10 and Firefox ESR 115.35, helping cover enterprise and legacy deployments that do not move on the rapid release cadence.

For users, the practical message is simple: updating is the main safeguard. Browsers sit on the front line of everyday exposure, handling untrusted web content, real-time communications, scripts, media streams and extensions. That makes them a frequent target for attackers looking to turn a single corrupted memory state or bounds-checking error into broader system compromise. Firefox 150’s patch list reflects that familiar attack surface, with high-severity or notable flaws touching WebRTC, DOM processing, WebAssembly, networking, graphics and media playback. Several moderate-impact vulnerabilities also involved mitigation bypasses, privilege escalation and information disclosure, which can become more dangerous when combined with another bug rather than exploited in isolation.

The release also arrives amid a wider shift in how software flaws are being discovered. Mozilla said this week that Firefox 150 includes fixes for 271 vulnerabilities identified during an initial evaluation using Anthropic’s Claude Mythos Preview, an early AI-assisted security testing effort. That figure is larger than the 41 CVE entries described in the public Firefox 150 advisory because a single CVE can cover multiple underlying bugs and not every defect necessarily appears as a separately listed public vulnerability record. Even so, the disclosure points to a new phase in browser security, where automated reasoning and fuzzing-assisted methods may sharply increase the volume of weaknesses defenders can find before attackers do.

That shift carries both promise and pressure. Mozilla’s public remarks suggest the organisation sees AI-assisted vulnerability discovery as a force multiplier for defenders, but also as a warning that attackers will not ignore the same tools. For browser vendors and open-source maintainers, the challenge is no longer only fixing isolated bugs quickly; it is building enough engineering capacity to absorb a much larger stream of credible findings without breaking release discipline. Firefox’s long history with memory-safety defects shows why that matters. Academic work examining Mozilla vulnerabilities has found that regression weaknesses and tool limitations can persist even in mature projects, especially when developers are working under complexity and time pressure.

Firefox 150’s non-security release notes are comparatively light, mentioning a macOS Lockdown Mode display fix and tab-group handling changes, which leaves the security update as the defining feature of this release. That makes the patch cycle less about new consumer-facing features and more about closing off exploitable pathways before they can be abused in the wild. Mozilla has not said in the advisory that the listed Firefox 150 flaws were under active exploitation, but the high-impact ratings and repeated references to memory corruption are enough to put this update in the urgent category for most users and organisations.

The article Firefox 150 closes code execution risks appeared first on Arabian Post.

For publishers, streaming platforms and site operators, the practical effect is straightforward: pages carrying multiple embedded clips, podcasts or promotional reels no longer need to start pulling those assets immediately on page load if they sit farther down the screen. MDN’s documentation for says lazy-loaded media will only begin applying preload behaviour once the element is near or within the viewport, and that poster images for video are also deferred. Its documentation for says bandwidth and storage use can be avoided until playback is more likely, improving performance in typical use cases.

That matters because media files are often among the heaviest objects on a web page. Even when developers use preload=”metadata” rather than full preloading, browsers may still establish connections, fetch headers or download poster images long before a reader decides to press play. By letting Chrome postpone those steps, Google is giving developers a native option to reduce initial page weight without relying on JavaScript workarounds or custom lazy-load libraries. MDN’s broader performance guidance continues to frame lazy loading as a standard way to defer non-critical resources and improve page speed.

Security and privacy specialists are also likely to note the narrower, but still meaningful, side effect of delaying contact with third-party hosts. Many media embeds call resources from content delivery networks, analytics systems or outside platforms the moment a page opens. Deferring off-screen audio and video can therefore postpone those requests until the user scrolls near the content. Chrome and MDN material stop short of presenting this as a broad security fix, but the documentation does make clear that deferred loading alters when external requests are made, and that JavaScript must be enabled for the feature to work because browsers treat lazy loading as a potential anti-tracking issue.

There are limits. The new attribute is a hint, not a command. MDN notes that browser behaviour is not absolutely mandated by specification, and autoplay still takes precedence over preload settings. For video, a lazy-loaded element set to autoplay will still need data when playback is required. For audio, the feature is more constrained: MDN says lazy loading depends on visible controls, meaning an off-screen audio element without the controls attribute will not load lazily at all. Developers trying to treat the change as a universal optimisation will need to test carefully across use cases.

Another caveat is cross-browser support. MDN labels the HTMLMediaElement. loading` property as not yet part of its Baseline set because it does not work in some widely used browsers. That means developers building for a mixed browser environment may still need fallbacks or selective deployment strategies, especially on sites where media delivery is central to revenue or audience retention. Chrome may have moved the feature into stable territory, but the wider web platform has not fully caught up.

The move fits a broader Chrome pattern. Google has spent years turning performance techniques that once required scripts or specialist tooling into native browser attributes. Images and iframes received lazy-loading support earlier; media files are the next logical target because they combine high transfer costs with uneven user engagement. Pages with multiple clips, tutorial libraries, long-form articles with supporting video, education portals and audio-heavy product pages stand to benefit most, particularly on slower connections and mobile hardware where every deferred request can improve perceived speed. MDN’s guidance on multimedia optimisation reinforces that oversized media remains a persistent drag on load quality, and Chrome’s new implementation gives developers a simpler way to address that at the markup level.

The article Chrome widens lazy loading to media appeared first on Arabian Post.

That framing drew a sharp rebuttal from WordPress co-founder and Automattic chief executive Matt Mullenweg, who argued that EmDash is not truly in WordPress’s tradition because WordPress can run almost anywhere, while EmDash, in his view, works best inside Cloudflare’s own infrastructure. Mullenweg also rejected the idea that Cloudflare had solved WordPress’s plugin problem, saying the openness and deep reach of plugins are central to WordPress rather than a flaw to be engineered away.

Beneath that exchange lies a deeper industry argument about security, openness and control. Cloudflare says EmDash tackles a structural weakness in the WordPress model by isolating plugins in separate runtime environments, reducing the damage a compromised extension can do. That message is likely to resonate because WordPress’s plugin ecosystem has long been both its biggest strength and its biggest vulnerability. Patchstack’s 2025 security report said 7,966 new vulnerabilities were identified across the WordPress ecosystem in 2024, with 96 per cent found in plugins and only a tiny share in core software.

Yet WordPress remains dominant on a scale that makes any challenger look small at the outset. W3Techs data updated on 5 April 2026 shows WordPress is used by 59.8 per cent of websites with a known content management system, representing 42.5 per cent of all websites. That reach gives WordPress a community, plugin library and installed base that no new entrant can match quickly, even one backed by Cloudflare’s engineering reputation and distribution power. The size of that footprint is also why disputes inside the WordPress world now spill well beyond a niche developer audience and into broader business and publishing concerns.

Those concerns have been building since the confrontation between Automattic and hosting company WP Engine erupted into open litigation in late 2024. WP Engine accused Automattic and Mullenweg of defamation and business interference after access to WordPress.org resources was blocked. In December 2024, a federal judge ordered Automattic to restore WP Engine’s access to WordPress. org, a significant early setback for Automattic. The case did not end there. In September 2025, the court allowed several of WP Engine’s major claims, including defamation, trade libel and interference claims, to proceed, while dismissing antitrust, attempted extortion and some other claims, partly with leave to amend.

Automattic then escalated matters with counterclaims filed in October 2025, arguing that WP Engine had abused the WordPress trademark, misled customers and failed to give enough back to the open-source community. This year, the dispute intensified again after WP Engine filed an amended complaint containing new allegations uncovered during discovery, including claims that Automattic had contemplated pursuing royalty demands against multiple competitors. Automattic has dismissed those claims as recycled narrative, but the filings show that the conflict is not cooling.

For users, developers and publishers, the combined effect of the lawsuit and the EmDash debate is to expose a tension that has existed for years. WordPress built its influence on openness, portability and a huge community of contributors. Critics say that very openness has also produced governance ambiguity, uneven plugin quality and a security burden that falls heavily on site owners and hosting providers. Cloudflare is trying to turn those frustrations into an opening, offering a system that promises stricter guardrails without abandoning open-source licensing. Mullenweg, for his part, is defending a model that prizes freedom to run code anywhere and warns against exchanging one problem for another in the form of platform dependency.

The article Cloudflare’s EmDash sharpens WordPress fault lines appeared first on Arabian Post.

Mozilla has released Firefox 149, introducing a suite of features aimed at strengthening privacy protections and improving user productivity, as competition intensifies across the browser market.

The update, issued on 24 March, combines new browsing tools with expanded security layers, signalling a broader strategic shift by Mozilla to differentiate its flagship product from rivals such as Google Chrome and Microsoft Edge.

Central to the release is a Split View browsing feature that allows users to display two web pages side by side within a single window. The capability, long requested by users, is designed to streamline workflows such as research, comparison shopping and multitasking. Analysts note that while similar functionality exists through extensions or operating system features, integrating it directly into the browser reduces friction and could appeal to productivity-focused users.

Mozilla has also introduced a built-in virtual private network offering up to 50 gigabytes of free monthly data. The move places Firefox among a limited group of browsers embedding privacy tools natively rather than relying on third-party services. The VPN is intended to encrypt traffic and mask user locations, addressing growing concerns over surveillance, data tracking and unsecured public networks. Industry observers say the inclusion of a free tier could attract users who have been reluctant to pay for standalone VPN subscriptions, though questions remain over long-term sustainability and potential upselling strategies.

Security enhancements form another pillar of the update. Firefox 149 expands its tracking protection systems, tightening controls on cross-site cookies and fingerprinting techniques that advertisers and data brokers often use to identify users. Mozilla has also strengthened sandboxing and isolation mechanisms to limit the impact of malicious code. These changes come amid a broader industry push to reduce reliance on third-party cookies, a shift that has prompted ongoing debate between privacy advocates and digital advertising stakeholders.

Performance improvements are also highlighted in the release, with Mozilla claiming faster page load times and reduced memory consumption under heavy workloads. Engineers have focused on optimising rendering processes and improving resource allocation across tabs, an area where Firefox has historically faced scrutiny when compared with Chromium-based browsers. Early user feedback suggests incremental gains rather than a dramatic overhaul, but the direction aligns with Mozilla’s effort to close performance gaps without compromising privacy features.

User interface refinements accompany the technical upgrades. The update introduces more intuitive tab management, enhanced customisation options and subtle design changes aimed at simplifying navigation. These adjustments reflect Mozilla’s attempt to balance functionality with accessibility, particularly as browser interfaces grow increasingly complex.

Beyond mainstream features, Firefox Labs continues to serve as a testing ground for experimental tools. Version 149 expands access to several early-stage capabilities, allowing users to opt into features that may later become permanent. This approach mirrors strategies adopted by competitors, offering a controlled environment for innovation while gathering user feedback.

Developers are another key audience for the update. Mozilla has introduced new debugging tools, improved support for modern web standards and refinements to its developer console. These changes are intended to maintain Firefox’s reputation as a developer-friendly browser, even as the ecosystem becomes more fragmented. Enhanced compatibility with emerging frameworks and APIs is expected to reduce friction for web developers working across multiple platforms.

Platform-specific updates further broaden the release. On desktop systems, Firefox 149 delivers improved integration with operating system features, while mobile versions focus on efficiency and battery optimisation. The cross-platform consistency underscores Mozilla’s strategy of maintaining a unified experience across devices, a critical factor as users increasingly switch between desktops and smartphones.

The update arrives at a time when browser competition is shaped by diverging priorities. Chromium-based browsers dominate global market share, driven by tight integration with services and aggressive performance tuning. Mozilla, by contrast, has positioned Firefox as an alternative centred on privacy, transparency and open standards. The inclusion of a built-in VPN and stronger anti-tracking measures reinforces that identity, though it may limit certain advertising-driven functionalities.

Risks and trade-offs accompany the changes. Integrating a VPN directly into the browser raises questions about data handling and user trust, even for a company with Mozilla’s privacy-focused reputation. There are also potential performance overheads associated with encryption and additional security layers. Some users may find the new features unnecessary or prefer specialised third-party tools that offer more advanced configurations.

The article Firefox 149 pushes privacy and productivity gains appeared first on Arabian Post.

Huawei is set to announce an open-source project centred on its A2A-T software, a move designed to accelerate the adoption of agent-to-agent communication standards across enterprise and industrial ecosystems.

The Shenzhen-based technology group has indicated that the A2A-T framework will be made available to developers and research institutions under an open governance model, allowing external contributors to refine and extend the protocol stack. The initiative is positioned as part of Huawei’s broader push to strengthen interoperability between autonomous software agents, particularly in artificial intelligence, edge computing and industrial internet scenarios.

A2A-T, short for Agent-to-Agent-Transmission, is understood to focus on secure, low-latency exchanges between distributed intelligent agents operating across heterogeneous systems. Huawei executives have described it as a modular architecture intended to standardise how digital agents discover, authenticate and collaborate with one another. By releasing the core codebase, the company aims to encourage alignment with emerging global standards bodies and industry alliances working on multi-agent frameworks.

The announcement comes at a time when enterprises are deploying AI agents to manage workflows, customer interactions and predictive maintenance. Analysts say that without common communication standards, fragmented systems risk creating inefficiencies and security vulnerabilities. Interoperability has become a central theme in AI governance discussions, particularly as organisations experiment with autonomous decision-making systems that operate across cloud, edge and on-premises environments.

Huawei’s open-source strategy mirrors earlier moves in its technology portfolio. The company has previously supported projects such as OpenEuler, its open-source operating system distribution, and MindSpore, an AI computing framework designed to reduce reliance on proprietary ecosystems. By expanding into agent communication protocols, Huawei appears to be seeking influence in a layer of the AI stack that is still evolving.

Industry observers note that agent-to-agent standards are gaining traction among global technology firms and research consortia. Multi-agent systems are increasingly used in logistics optimisation, smart grid management and advanced robotics. In such environments, digital agents must exchange structured information, negotiate tasks and resolve conflicts without human intervention. Standardised transmission layers can reduce integration costs and enhance reliability.

Company representatives have indicated that A2A-T incorporates encryption and identity management features intended to address data security concerns. Secure communication between agents has become a policy focus in multiple jurisdictions, particularly where critical infrastructure and sensitive industrial data are involved. By embedding authentication and traceability mechanisms, Huawei is seeking to align with regulatory expectations around AI transparency and accountability.

The open-source release is also likely to serve strategic objectives. Huawei continues to navigate restrictions in several Western markets, particularly in telecommunications infrastructure. Expanding participation in open developer communities allows the company to demonstrate technical credibility and foster partnerships beyond hardware. Analysts say that open-source engagement can help mitigate perceptions of closed ecosystems while broadening adoption in Asia, Africa and parts of Europe.

Technical documentation shared in advance of the announcement suggests that A2A-T is designed to operate across 5G and 5.5G networks, as well as Wi-Fi 7 environments. Huawei has been a prominent advocate of advanced connectivity standards, arguing that high-bandwidth, low-latency networks are essential for large-scale AI deployment. Integrating agent communication frameworks with network infrastructure could provide performance advantages in latency-sensitive applications such as autonomous vehicles and industrial automation.

Academic researchers have welcomed moves towards standardisation in multi-agent systems. Studies published in peer-reviewed journals highlight that interoperability frameworks can accelerate innovation by allowing developers to focus on higher-level intelligence models rather than bespoke communication protocols. Open-source governance structures also enable peer review, which can strengthen security and reliability.

At the same time, questions remain about global alignment. International standards organisations including the International Organization for Standardization and the Institute of Electrical and Electronics Engineers have been exploring frameworks for AI interoperability. Whether Huawei’s A2A-T initiative converges with these efforts will depend on technical compatibility and collaborative engagement. Competing technology vendors are also advancing proprietary or semi-open protocols, creating a fragmented landscape.

Market analysts suggest that enterprise demand for AI agents is expanding rapidly. Consulting firms project that multi-agent systems will underpin digital transformation in manufacturing, finance and public services over the next decade. As deployments scale, pressure is mounting for common protocols to ensure seamless integration across vendors and platforms.

Huawei’s move is likely to resonate strongly in markets where the company maintains significant network infrastructure footprints. Governments in parts of the Middle East and Southeast Asia have partnered with Huawei on smart city and digital government initiatives. A standardised agent communication layer could enhance such programmes by enabling cross-departmental automation and data exchange.

The article Huawei unveils open A2A-T agent framework appeared first on Arabian Post.

Open-source game engine Godot is facing mounting strain as a surge of AI-generated code submissions overwhelms volunteer maintainers, raising concerns about quality control, contributor accountability and the long-term sustainability of community-driven software projects.

Core developers behind the free and open-source engine say they are grappling with a wave of pull requests that appear to have been produced with the help of generative artificial intelligence tools. While such tools can accelerate coding, maintainers argue that many submissions show limited understanding of the engine’s architecture, introducing errors, redundancies and security risks that require extensive review and correction.

Godot, widely used by independent developers and small studios as an alternative to proprietary engines such as Unity and Unreal Engine, operates under an open governance model. Its source code is publicly available, and contributions from volunteers form a central part of its development process. That openness, long regarded as a strength, is now creating new pressures.

Developers involved in reviewing contributions have described a noticeable shift in the pattern of submissions over the past year. Instead of carefully scoped improvements or bug fixes from contributors familiar with the codebase, maintainers report receiving large patches filled with boilerplate-style changes, inconsistent naming conventions and logic that fails to integrate cleanly with existing systems. Some submissions replicate functionality that already exists or propose sweeping refactors without a clear rationale.

Concerns have been voiced publicly by senior contributors who say the review burden has grown sharply. They argue that reviewing poorly understood AI-assisted code can take longer than writing the fix from scratch. Volunteer time, already limited, is being diverted to filtering out low-quality contributions rather than advancing planned features and stability improvements.

Godot’s popularity has risen following turbulence in the game development ecosystem. When Unity announced controversial pricing changes tied to game installs in 2023, many developers began exploring alternatives. Godot saw a surge in downloads, community engagement and financial backing through donations and sponsorships. That influx of interest also expanded its contributor base, bringing both experienced programmers and newcomers eager to participate.

Generative AI coding assistants, powered by large language models, have become commonplace during the same period. Tools integrated into code editors can produce entire functions or suggest architectural changes based on natural language prompts. Technology companies promoting these tools argue they enhance productivity and lower barriers to entry for aspiring developers. Yet open-source communities are discovering unintended consequences.

Experts in software engineering note that AI-generated code often reflects patterns present in training data without full contextual awareness. While such output may appear syntactically correct, it can misalign with a project’s specific style guidelines, performance constraints or security standards. For complex systems like a game engine, subtle inconsistencies can cascade into significant bugs.

Godot’s maintainers have not banned AI-assisted contributions outright. Instead, discussions within the community have centred on reinforcing contribution guidelines and encouraging submitters to demonstrate understanding of their changes. Some contributors have suggested requiring more detailed explanations in pull requests, comprehensive testing and stricter adherence to coding standards before code is considered for merging.

The debate also touches on broader philosophical questions about open-source collaboration. Projects like Godot depend on goodwill, transparency and distributed responsibility. If contributors rely heavily on automated tools without engaging deeply with the codebase, maintainers worry that the culture of shared learning and mentorship could erode. At the same time, excluding newcomers or dismissing AI tools entirely risks alienating developers who see such technologies as integral to modern workflows.

Industry observers point out that the challenge is not unique to Godot. Maintainers across popular open-source repositories on platforms such as GitHub have reported spikes in AI-influenced submissions. Some projects have introduced labelling systems to flag AI-generated patches, while others have tightened review processes or implemented contribution quotas to manage workload.

Financial support, though improved for Godot compared with earlier years, does not eliminate the bottleneck. The engine is backed by the Godot Foundation, which coordinates fundraising and strategic direction, but much of the day-to-day code review remains volunteer-driven. Expanding the pool of trusted maintainers is one option under discussion, though onboarding new reviewers requires time and careful vetting.

For developers who rely on Godot to build commercial titles, stability and reliability are paramount. Studios evaluating engines weigh not only features but also governance and long-term viability. Persistent friction in the contribution pipeline could slow feature rollouts or delay critical fixes, affecting user confidence.

Some community members argue that the current turbulence reflects growing pains rather than systemic decline. They note that every widely adopted open-source project must evolve its processes as scale increases. Clearer documentation, automated testing pipelines and stronger mentorship for first-time contributors could help filter out superficial submissions while preserving openness.

The article Godot maintainers struggle with AI code flood appeared first on Arabian Post.

At its core, PocketBlue combines large language model orchestration with structured data ingestion, enabling users to run intelligence workflows on their own infrastructure. The platform’s developers describe it as privacy-first, with an emphasis on transparency and auditability. That approach arrives at a time when concerns over data sovereignty, security and algorithmic bias are shaping debates across both the public and private sectors.

Open-source AI tooling has accelerated over the past two years, fuelled by the release of foundation models and a broader movement towards reproducible research practices. Enterprises, academic institutions and independent developers have increasingly questioned whether centralised AI services expose sensitive data to third parties. High-profile data breaches and regulatory scrutiny in the United States and Europe have intensified those concerns, prompting a shift towards self-hosted or hybrid systems.

PocketBlue enters this environment with a clear design philosophy: intelligence analysis should be modular, inspectable and deployable on local machines or private servers. Rather than offering a monolithic interface, the platform allows developers to plug in models of their choice, integrate open datasets and construct bespoke workflows for tasks such as document analysis, network mapping and pattern detection. By separating the orchestration layer from the underlying models, it enables users to experiment without locking themselves into a single provider.

The local-first model is particularly significant. Many AI-powered research tools operate primarily through remote APIs, sending user queries and data to cloud servers for processing. While this allows for scalability, it also creates dependencies on external infrastructure and raises compliance issues in regulated industries such as finance, healthcare and defence. PocketBlue’s architecture enables processing to occur on local hardware, provided sufficient computational resources are available. That feature appeals to organisations with strict confidentiality requirements or those operating in jurisdictions with stringent data protection laws.

Developers familiar with open-source ecosystems note that PocketBlue reflects a broader push towards sovereign AI systems. Governments across Europe and parts of Asia have articulated ambitions to reduce reliance on foreign technology providers. Within this context, tools that can be deployed independently and audited at code level are viewed as strategically valuable. The platform’s open licence allows contributors to inspect, modify and extend its capabilities, aligning with principles of transparency long championed by the free software movement.

Industry analysts say the timing is notable. As generative AI becomes embedded in research workflows, questions have arisen about reproducibility and verification. Intelligence analysis, whether in journalism, corporate investigations or policy research, depends on traceability of sources and clarity of reasoning. Proprietary AI systems often provide limited visibility into how outputs are generated. By contrast, PocketBlue’s modular framework is intended to expose intermediate steps, enabling users to review how data is processed and how conclusions are formed.

The project’s GitHub activity suggests steady engagement from developers experimenting with integrations and feature enhancements. Documentation emphasises extensibility, with support for connecting to different model backends and data connectors. That flexibility mirrors trends seen in other open-source AI frameworks, where communities iterate rapidly and adapt tools for niche applications.

Privacy advocates argue that decentralised AI research platforms could mitigate risks associated with mass data aggregation. Centralised services concentrate large volumes of user data in a small number of corporate repositories, creating attractive targets for cyberattacks. Local-first tools distribute that risk, though they also place responsibility on users to maintain security practices.

Critics caution that open-source intelligence platforms can be misused if not governed carefully. The ability to aggregate and analyse large datasets, even from publicly available sources, raises ethical questions around surveillance and profiling. Developers of PocketBlue have indicated that the software is intended for lawful and responsible research purposes, but as with many dual-use technologies, safeguards depend largely on the communities that adopt them.

Competition in the AI research tooling space is intensifying. Commercial platforms offer polished interfaces and integrated cloud resources, appealing to users who prioritise convenience and scalability. Open-source alternatives such as PocketBlue, by contrast, target technically proficient users willing to manage deployments in exchange for greater autonomy. The divergence reflects a wider tension in the AI ecosystem between managed services and self-hosted infrastructures.

The article PocketBlue signals shift in open intelligence tools appeared first on Arabian Post.

PocketBook has unveiled the InkPad One, a 10.3-inch e-ink tablet built on an open Linux architecture, positioning it as a direct challenger to Amazon’s Kindle Scribe and signalling a push to loosen the grip of closed digital reading ecosystems. The device combines stylus support with broad file compatibility, underscoring the Swiss-based company’s attempt to appeal to readers and professionals seeking greater control over their digital libraries.

The InkPad One enters a premium e-reader segment that has grown steadily since Amazon introduced the Kindle Scribe in 2022, adding note-taking functionality to its established Kindle range. While Amazon’s hardware has benefited from tight integration with the Kindle Store and Audible, critics have long argued that its ecosystem limits flexibility by prioritising proprietary formats and services. PocketBook’s strategy is to lean into openness, supporting a wide array of formats including EPUB, PDF, MOBI and several comic and document standards without mandatory conversion.

At the heart of the InkPad One is a 10.3-inch E Ink Carta display designed to mimic paper while reducing eye strain. The larger screen size mirrors that of the Kindle Scribe, targeting students, researchers and business users who require annotation tools. Stylus input allows handwriting, margin notes and document mark-ups, functions that have become central to the appeal of large-format e-ink devices. PocketBook has emphasised that notes can be exported in multiple formats, a feature aimed at users who prefer not to remain tied to a single cloud service.

Industry analysts note that openness has become a selling point in a market increasingly shaped by concerns over digital ownership. Consumers who purchase e-books through major platforms typically license, rather than own, content, and transfers between ecosystems can be cumbersome. By contrast, PocketBook’s Linux foundation allows users to sideload content more freely and manage files directly through USB or third-party cloud services. The company has stated that its devices avoid aggressive digital rights management where possible, although content restrictions ultimately depend on publishers.

Amazon, for its part, has strengthened its hardware portfolio with incremental updates to the Kindle Scribe, improving note-taking tools and synchronisation with its broader Kindle ecosystem. The Scribe’s seamless integration with Kindle Unlimited and Audible remains a powerful draw, particularly in markets where Amazon’s content catalogue is extensive. However, its reliance on Amazon’s file structure and services has led some users to seek alternatives that do not require ongoing platform dependency.

PocketBook’s move reflects a broader shift in the e-ink sector, where competitors such as Kobo, reMarkable and Onyx have experimented with open systems and Android-based devices. The reMarkable tablet has carved out a niche among productivity-focused users, while Kobo has maintained a loyal base through EPUB compatibility and library partnerships. Onyx’s Boox line, built on Android, offers app flexibility but has faced scrutiny over software updates and security transparency. PocketBook’s Linux approach attempts to balance openness with stability, avoiding the complexities of a full Android environment.

The premium e-reader category has benefited from rising demand for distraction-free devices. As tablets and smartphones become more multifunctional, a segment of consumers has sought dedicated reading and writing tools that minimise notifications and glare. E-ink displays, which consume power only when refreshing the screen, also offer extended battery life measured in weeks rather than days. Market data from research firms tracking digital publishing trends indicate steady global growth in e-reader shipments, driven partly by educational institutions and remote working patterns.

Pricing will play a critical role in the InkPad One’s reception. The Kindle Scribe has typically retailed at the higher end of the market, with costs varying by storage configuration and stylus options. PocketBook has indicated that its device will be competitively positioned, though final pricing may differ by region. Distribution partnerships across Europe and parts of Asia have historically been strengths for the company, though Amazon’s logistical network gives it a formidable advantage in scale.

Beyond hardware, software longevity and support will shape buyer confidence. Amazon’s vertically integrated model allows it to roll out firmware updates and content synchronisation across millions of devices. PocketBook must demonstrate comparable reliability while maintaining the flexibility promised by its open framework. Cybersecurity experts have observed that open systems can offer transparency benefits but require consistent patch management to protect user data.

Publishers and authors are watching these developments closely. While open file support expands reader choice, it may complicate digital rights management strategies that underpin revenue models. At the same time, broader compatibility can increase the reach of independent authors who distribute works outside dominant platforms. Educational institutions, in particular, may view open devices favourably if they enable easier distribution of academic materials without proprietary barriers.

The article PocketBook targets Kindle Scribe with open design appeared first on Arabian Post.

Open-source compiler infrastructure project LLVM has formally clarified how contributors may use artificial intelligence tools when submitting code, allowing AI-assisted contributions while placing clear responsibility on human reviewers to understand, verify and stand behind every line. The policy, adopted after months of internal discussion, reflects a wider reckoning across open-source communities grappling with the growing presence of generative coding systems.

LLVM’s leadership has made it clear that the project is not banning AI-generated code. Instead, it is drawing a line around accountability. Contributors who rely on large language models or other automated tools must treat those systems as assistants rather than authors, ensuring that submissions meet LLVM’s quality, licensing and security standards before they reach the codebase.

The approach is framed around a “human in the loop” requirement, meaning that any code influenced by AI must be reviewed by a contributor who fully understands how it works and is prepared to take responsibility for its behaviour over time. Project maintainers say this is essential for a codebase that underpins widely used compilers such as Clang and influences software across operating systems, cloud infrastructure and embedded systems.

At the heart of the policy is a simple principle: LLVM already expects contributors to understand and vouch for their code, and AI assistance does not change that obligation. What does change, according to maintainers, is the risk profile. AI-generated output can appear plausible while containing subtle errors, inefficient constructs or security flaws. Without careful human scrutiny, those weaknesses could be propagated across dependent projects.

The policy also addresses licensing concerns, a sensitive topic in open-source development. Contributors are expected to ensure that AI tools used in the development process do not introduce code that violates LLVM’s licensing requirements. Because many generative systems are trained on vast corpora of publicly available code, questions have emerged across the industry about provenance and copyright. LLVM’s stance places the burden squarely on contributors to ensure compliance, regardless of the tools involved.

In practice, the guidance means that patches submitted to LLVM should be no different in quality or clarity than those written entirely by hand. Code reviewers may ask contributors to explain design choices or implementation details, and inability to do so could lead to rejection. Maintainers have emphasised that citing an AI tool as the origin of a patch will not excuse shortcomings or errors.

The move comes as generative coding tools become increasingly embedded in software development workflows. Products such as GitHub Copilot, ChatGPT-based coding assistants and enterprise-focused AI development platforms are now widely used by programmers to draft functions, refactor legacy code and explore alternative implementations. While many developers report productivity gains, open-source projects have faced questions about whether such tools align with long-standing norms of transparency and shared responsibility.

LLVM’s decision echoes debates playing out in other major projects. The Linux kernel community, for example, has seen high-profile discussions about AI-generated patches after maintainers flagged submissions that showed signs of automated origin without adequate understanding. Python and other language communities have also issued guidance urging caution, particularly around licensing and maintainability.

Supporters of LLVM’s approach argue that it strikes a pragmatic balance. By neither banning AI tools nor embracing them uncritically, the project acknowledges how development practices are evolving while protecting the integrity of its codebase. They note that compilers are foundational infrastructure, where subtle defects can have far-reaching consequences across entire software ecosystems.

Critics, however, warn that enforcement may prove challenging. Determining whether a contributor truly understands AI-assisted code can be subjective, and reviewers already face heavy workloads. There are also concerns that smaller contributors or newcomers, who may rely more heavily on AI tools, could be discouraged by stricter scrutiny. LLVM maintainers respond that the expectations apply equally to all contributors and mirror standards that have long existed, even before AI entered the picture.

Beyond LLVM, the policy is being watched closely as a potential model for other open-source projects. As AI systems continue to improve, communities are under pressure to articulate norms that preserve trust, collaboration and legal clarity. LLVM’s emphasis on accountability rather than prohibition suggests one path forward.

The article LLVM sets guardrails for AI-assisted code submissions appeared first on Arabian Post.

Daniel Stenberg, the creator and lead maintainer of curl, said the volume of submissions claiming security flaws had grown to a level that could no longer be handled responsibly. Many of the reports, he explained, were produced using large language models that generated plausible-sounding but incorrect analyses of the curl codebase, forcing maintainers to spend significant time verifying issues that turned out to be baseless.

The decision marks a notable moment in the wider open-source ecosystem, where bug bounty programmes are increasingly strained by automated or semi-automated submissions. Curl, which is embedded in operating systems, networking equipment, smartphones and countless applications, has long been regarded as a critical piece of internet infrastructure. Its security disclosures are closely watched because flaws can have far-reaching consequences.

Stenberg said the project’s bug bounty system had initially been introduced to encourage responsible disclosure and reward researchers who invested real effort into finding genuine vulnerabilities. Over time, however, the incentives began to attract a different kind of participation. Submissions grew sharply in number but not in quality, with many reports recycling generic vulnerability patterns or misinterpreting perfectly safe code paths as exploitable weaknesses.

According to Stenberg, a growing share of these reports showed clear signs of having been generated or heavily assisted by AI tools. They often included confident language, references to well-known classes of vulnerabilities and long explanations that collapsed under scrutiny. Each submission still required manual review, code inspection and testing, creating a workload disproportionate to the benefits of the programme.

The curl security team is small and largely volunteer-driven. Unlike large technology companies that run bug bounties with dedicated staff and automated triage systems, curl relies on maintainers who balance security work with development, documentation and community support. Stenberg said the time spent filtering out invalid reports had begun to interfere with addressing real issues and improving the software.

The move has sparked debate across the security research community. Bug bounties have become a standard mechanism for identifying vulnerabilities, particularly in high-profile projects. Supporters argue that financial incentives widen participation and uncover flaws that internal audits may miss. Critics counter that bounties can distort behaviour, encouraging quantity over quality and rewarding superficial analysis.

AI has intensified these tensions. Large language models can scan code, flag potential issues and draft vulnerability reports in seconds. Used carefully by experienced researchers, such tools can improve productivity. Used indiscriminately, they can flood maintainers with false positives. Several open-source projects have reported similar pressures, though few as prominent as curl have taken the step of ending a bounty outright.

Stenberg emphasised that curl is not closing the door on security reports themselves. The project continues to accept vulnerability disclosures through established channels and remains committed to responsible handling and timely fixes. What has changed is the removal of a financial reward that, in the project’s assessment, no longer aligned with sustainable security practices.

The decision also highlights the uneven impact of AI across the software supply chain. While large organisations can absorb the cost of noisy inputs, smaller projects that underpin much of the internet often lack the resources to do so. Security experts warn that if maintainers burn out or disengage, the overall risk to the ecosystem increases.

Some researchers have suggested reforms rather than abandonment, such as stricter submission requirements, proof-of-concept mandates or higher bars for eligibility. Others argue that community norms must evolve, with clearer expectations around the ethical use of AI in security research and greater emphasis on validation before disclosure.

The article Curl drops bug bounty after AI-driven report surge appeared first on Arabian Post.

Microsoft has unveiled WinApp CLI, an open-source command-line tool released in public preview, aimed at simplifying how developers build and package applications for Windows. The tool brings together tasks that are typically spread across multiple utilities, allowing teams to initialise projects, manage software development kits, configure app manifests, handle certificates and generate MSIX packages from a single workflow.

The launch reflects a broader push by Microsoft to lower the friction involved in Windows app development, particularly as developers increasingly work across diverse frameworks and languages. WinApp CLI is designed to support projects built with Electron,. NET and Rust, among others, providing a common interface regardless of the underlying stack. By standardising these steps, the company says it can reduce setup time and minimise configuration errors that often slow down delivery.

At its core, WinApp CLI automates tasks that have long been seen as repetitive or error-prone. Developers can scaffold a Windows application with predefined templates, ensure that the correct Windows App SDK components are installed, and maintain consistent project settings across teams. The tool also generates and validates app manifests, a process that has historically required manual edits and deep familiarity with platform requirements.

Packaging and distribution form a central part of the offering. WinApp CLI integrates MSIX packaging into the development cycle, enabling developers to produce installable packages that meet Windows security and deployment standards without relying on separate build scripts. Certificate creation and signing are handled within the same environment, addressing a common pain point for smaller teams and independent developers.

The public preview status signals that Microsoft is seeking early feedback from the developer community. By releasing the tool as open source, the company is encouraging external contributions and scrutiny, with the aim of refining features and expanding framework support. Engineers familiar with the Windows ecosystem note that this approach mirrors earlier efforts such as the Windows App SDK, where community input helped shape tooling priorities.

Industry analysts view the move as part of a competitive response to cross-platform development trends. Tools like Electron and Rust have gained popularity for their portability, but Windows-specific deployment steps have remained complex. A unified command-line interface could make Windows a more attractive target for teams that want to maintain a single codebase while still delivering native-quality experiences.

The introduction of WinApp CLI also aligns with Microsoft’s broader strategy of investing in developer productivity. Recent updates across its tooling portfolio have focused on automation, reproducibility and integration with modern continuous integration pipelines. A single CLI that handles setup and packaging fits neatly into automated build environments, reducing the need for bespoke scripts.

Developers who have tested early builds say the promise lies in consistency. By codifying best practices into commands, WinApp CLI can help ensure that applications meet platform guidelines from the outset, rather than requiring late-stage fixes. This is particularly relevant for organisations managing multiple Windows apps with shared infrastructure.

The article Microsoft rolls out WinApp CLI for developers appeared first on Arabian Post.

Microsoft has released XAML Studio as open-source software, opening up a Windows app design tool that had remained proprietary since its launch eight years ago, in a move aimed at rebuilding trust and momentum among developers working on modern Windows interfaces.

The company confirmed that the source code for XAML Studio has been published under a permissive licence, allowing developers to inspect, modify and contribute to the tool that is widely used to preview, test and refine XAML-based user interfaces for Windows applications. The decision places XAML Studio alongside a growing list of Microsoft development tools that have transitioned to open development models as the company seeks deeper engagement with external contributors.

XAML Studio was introduced as a lightweight environment for designers and developers to experiment with XAML layouts without the overhead of a full integrated development environment. Over the years, it became a familiar companion tool for teams building applications with Universal Windows Platform and later WinUI frameworks, offering live previews, rapid iteration and a bridge between design concepts and production code.

By making the tool open source, Microsoft is signalling a willingness to let the wider community influence its direction at a time when Windows application development faces stiff competition from web-based and cross-platform frameworks. Developers have increasingly favoured tools that evolve in public, respond quickly to feedback and integrate with a diverse ecosystem of libraries and workflows.

Company engineers involved in the project said the transition followed sustained internal discussions about the future of XAML tooling. Contributions from outside Microsoft had long been limited to feedback and feature requests, but the open-source release now enables direct collaboration on performance improvements, bug fixes and new capabilities. The codebase is being made available with documentation and contribution guidelines to lower the barrier for first-time contributors.

The move also reflects a broader recalibration of Microsoft’s Windows developer strategy. While the company has invested heavily in cross-platform technologies such as. NET and web-centric tooling, it has also faced criticism that native Windows development lacked transparency and pace. Opening XAML Studio allows developers to see how design-time rendering, layout parsing and live preview mechanisms work under the hood, offering educational value as well as practical benefits.

Industry observers note that XAML itself has undergone shifts in relevance, with some developers questioning its long-term role amid the rise of web technologies and multi-platform UI frameworks. Microsoft has maintained that XAML remains central to high-performance, native Windows experiences, particularly for applications that require tight integration with the operating system. An open XAML Studio may help reinforce that position by encouraging experimentation and modernisation driven by the community.

The release comes at a point when Microsoft has already open-sourced significant parts of its UI stack, including WinUI components and related tooling. Developers familiar with those projects are expected to recognise architectural patterns in XAML Studio, making it easier to contribute across repositories. Microsoft has indicated that it will continue to steward the project, reviewing external submissions and setting a public roadmap informed by community priorities.

Early reaction from developers has focused on the potential for faster feature delivery and better alignment with real-world workflows. Requests that previously took months to surface internally can now be addressed directly by contributors who depend on the tool in daily work. There is also interest in extending XAML Studio beyond its original scope, including support for newer UI controls, improved accessibility visualisation and tighter integration with design systems.

From a governance perspective, Microsoft said it will manage the project with an open issue tracker and regular updates, while retaining responsibility for major architectural decisions. This hybrid approach mirrors how the company oversees other high-profile open-source projects, balancing stability with community innovation.

The article Microsoft opens XAML Studio to developers appeared first on Arabian Post.

Control over personal photo archives stored in Apple’s iCloud has taken on sharper relevance as users look for greater autonomy over their data, and a small open-source project has emerged as a practical response to that demand. icloudpd, a Python-based command-line utility, allows users to download and synchronise photos and videos from iCloud to local storage, offering an alternative to Apple’s tightly integrated ecosystem.

Developed originally in 2016, the tool was designed to address a straightforward problem: iCloud Photos works seamlessly across Apple devices but offers limited, manual options for bulk export or automated backups outside the platform. icloudpd fills that gap by enabling users to pull their media libraries onto local machines, external drives or network-attached storage systems without relying on proprietary software.

At its core, icloudpd authenticates a user’s Apple account and mirrors the iCloud Photos library locally. The software supports incremental updates, meaning only new or modified items are downloaded after the initial sync, reducing bandwidth use and storage duplication. It also preserves metadata such as creation dates, geolocation data and album structure, which is critical for photographers and archivists who depend on accurate cataloguing.

The project has gained attention within privacy-focused and self-hosting communities because it aligns with a broader movement to reduce dependence on single-vendor cloud platforms. Users who back up their photos using icloudpd often combine it with local redundancy strategies, including offline hard drives or private servers, creating layers of resilience beyond Apple’s cloud infrastructure.

One of the factors behind the tool’s steady adoption is its flexibility. icloudpd can run on Windows, macOS and Linux, and it integrates cleanly with Docker containers, making it suitable for automation. Many users schedule it to run at fixed intervals on home servers or NAS devices, ensuring that their local photo archive stays in sync with iCloud without manual intervention. This automation has proven attractive to technically inclined users managing large libraries that would be impractical to export manually.

Community-driven development has shaped much of icloudpd’s evolution. Contributors have added features to handle Apple’s two-factor authentication, cope with changes to iCloud’s web APIs and improve error handling during long downloads. As Apple periodically adjusts its backend systems, maintaining compatibility has required ongoing updates, underscoring both the fragility and resilience of open-source tools that depend on closed platforms.

The project’s maintainers have been careful to position icloudpd as a client-side utility that respects user credentials rather than a workaround for security controls. Authentication occurs through Apple’s standard mechanisms, and the tool does not attempt to bypass access restrictions. That distinction has helped sustain trust among users wary of sharing account details with third-party software.

icloudpd’s rise also reflects changing attitudes towards digital ownership. Photos increasingly represent personal history, professional assets and even legal records. Relying exclusively on a single cloud provider, even one with Apple’s scale and reputation, is viewed by some as an unnecessary risk. Local copies, managed independently, offer reassurance against account lockouts, service disruptions or policy changes that could affect access.

There are limitations. As a command-line tool, icloudpd is not aimed at casual users unfamiliar with terminal environments. Installation requires Python and a basic level of technical confidence. Large libraries can take days to download, depending on connection speeds, and occasional interruptions may require restarts. Apple’s rate-limiting measures can also slow transfers during peak periods.

Despite these constraints, the tool’s impact lies less in mass adoption and more in its symbolic value. It demonstrates how open-source software can restore a degree of balance between users and dominant platforms by offering choice rather than replacement. Apple’s ecosystem remains central for millions, but icloudpd shows that participation does not have to mean surrendering control entirely.

The article Open-source tool reshapes iCloud photo control appeared first on Arabian Post.

Photon HQ has released an open-source iMessage Kit that allows developers to automate Apple’s messaging system on macOS, a move that broadens access to a platform long guarded by Apple’s tightly controlled ecosystem. The toolkit enables programmatic interaction with iMessage through local databases and system scripting, opening the door to AI-driven assistants, workflow automation and experimental messaging tools that previously sat beyond the reach of independent developers.

At its core, the kit provides structured access to the SQLite databases used by iMessage on macOS, paired with AppleScript hooks that let software read, send and manage messages under user control. This approach avoids reverse-engineering network protocols and instead works within the confines of data already stored on a user’s machine. Developers can query conversations, detect message states and trigger actions based on content or metadata, while maintaining compatibility with Apple’s desktop environment.

Photon HQ says the project was built to reduce friction for builders exploring AI agents and automation on personal devices. The company has also introduced a more advanced TypeScript implementation designed for real-time processing. That version supports event-driven workflows, allowing agents to react instantly to incoming messages, classify content, or coordinate actions across other macOS applications. For developers building local AI systems, the ability to treat iMessage as an addressable interface is seen as a significant step.

The release arrives at a moment when interest in on-device AI is accelerating. Privacy-focused developers are increasingly wary of routing personal communications through cloud services, favouring local processing instead. By keeping operations on macOS, the iMessage Kit aligns with that trend, enabling tools such as personal scheduling agents, customer-support prototypes for small teams, and accessibility features that operate without exporting message data.

Industry observers note that Apple has historically limited third-party access to iMessage, positioning it as a differentiator for its hardware ecosystem. While Apple provides APIs for notifications and limited messaging integrations, full automation has remained out of bounds. Photon HQ’s approach challenges that status quo by demonstrating how macOS-level access can be leveraged without modifying Apple’s servers or bypassing user consent mechanisms.

The project has already drawn attention within developer communities experimenting with agent-based software. Early adopters have showcased prototypes that summarise conversations, flag urgent messages, and integrate messaging with task managers and calendars. The TypeScript version, in particular, has been highlighted for making it easier to build maintainable, event-driven systems rather than brittle scripts.

Ethical and security considerations sit alongside the enthusiasm. Direct access to message databases raises concerns about misuse, especially if tools are deployed without transparent user understanding. Photon HQ has emphasised that the kit is intended for personal or consensual use on devices where the user has full control, and that it does not circumvent platform safeguards such as device encryption or account authentication. Still, experts caution that open-source availability lowers the barrier for experimentation in ways Apple may view as problematic.

There is also the question of platform stability. Apple routinely updates macOS and its applications, and undocumented database structures can change without notice. Developers adopting the kit must accept the risk of breakage after system updates, a trade-off familiar to anyone working close to the operating system layer. Photon HQ has acknowledged this limitation, framing the project as a foundation for exploration rather than a guaranteed long-term interface.

From a competitive perspective, the release underscores growing pressure on large platform owners to balance control with developer innovation. Messaging has become a critical interface for AI agents, from customer engagement to personal productivity. By enabling iMessage automation on macOS, Photon HQ is effectively inviting developers to treat Apple’s messaging client as another programmable surface, even if unofficially.

The article Photon HQ opens iMessage automation to developers appeared first on Arabian Post.

Cocos, the long-running developer of cross-platform game technology, has moved its Cocos 4 game engine from a proprietary model to full open source, a step that reshapes its relationship with developers and signals a strategic shift in the competitive middleware market.

The company confirmed that the entire Cocos 4 engine codebase is now available under an open-source licence, allowing studios and independent developers to inspect, modify and redistribute the technology without the restrictions that applied under earlier commercial terms. The change applies to the core runtime, editor integrations and platform abstraction layers that previously sat behind licensing agreements.

Cocos has been widely used for mobile and web games for more than a decade, particularly in Asia, where it became popular for 2D and lightweight 3D titles that needed to scale across Android, iOS, browsers and mini-game platforms. Earlier iterations, including Cocos2d-x and later Cocos Creator releases, blended open components with closed tooling. Cocos 4 marks the first time the company has removed proprietary barriers across the entire engine stack.

Executives at Cocos said the decision was driven by changes in developer expectations and by the growing importance of transparent, community-maintained infrastructure in game development. In a statement accompanying the release, the company described open source as a way to “accelerate innovation, deepen trust and reduce long-term risk” for studios building live services that must be maintained for years.

Industry analysts note that the move comes amid rising concern about vendor lock-in and pricing volatility in game middleware. Over the past two years, licensing disputes and pricing changes at rival engines have prompted studios to reassess their technology dependencies. By contrast, open-source engines give developers legal certainty over access to source code and the freedom to maintain forks if a vendor’s priorities change.

Cocos 4 is positioned as a modernised engine with a reworked rendering pipeline, improved performance on low-end devices and expanded support for 3D workflows alongside its traditional 2D strengths. Developers familiar with earlier Cocos versions can migrate projects while retaining scripting approaches based on JavaScript and TypeScript, which remain central to the engine’s design.

For smaller studios, the open-source transition lowers barriers to experimentation. Teams can now profile performance bottlenecks directly in the engine code, adapt platform integrations for emerging devices and contribute fixes upstream rather than waiting for official patches. Larger publishers, meanwhile, gain the option to audit the engine for security and compliance purposes, an increasingly common requirement for games distributed across multiple jurisdictions.

The decision also reflects a broader trend in game technology toward community-driven development. Godot, another open-source engine, has expanded its footprint in both indie and professional circles, supported by a foundation model and external sponsorships. By opening Cocos 4, Cocos enters a more direct comparison with such projects, while differentiating itself through its mobile-first heritage and established user base.

Revenue considerations remain central. Cocos has indicated that it will continue to monetise through enterprise services, cloud tooling, technical support and optional extensions rather than engine licensing fees. This mirrors approaches used by other open-source software companies that rely on services and ecosystem partnerships to sustain development.

Developers have broadly welcomed the announcement on technical forums, highlighting the potential for faster bug fixes and greater transparency around engine roadmaps. Some have cautioned that success will depend on governance: clear contribution guidelines, responsive maintainers and predictable release cycles will be critical to sustaining trust within the open-source community.

The article Cocos game engine opens its full codebase appeared first on Arabian Post.

Launched as a framework-agnostic alternative to popular UI kits tied to React, Vue, or Angular, Web Awesome is built on native web technologies such as HTML, CSS, and JavaScript, with a strong emphasis on Web Components. Its creators argue that this approach allows components to work consistently across projects, regardless of whether teams are using modern JavaScript frameworks, server-rendered applications, or simpler static sites.

At the core of Web Awesome’s proposition is a library of meticulously designed components that aim to balance aesthetics, accessibility, and performance. Buttons, forms, modals, navigation elements, and data display components are presented as building blocks rather than opinionated templates. Each component can be themed and extended, allowing teams to adapt designs to brand requirements without rewriting underlying logic. The maintainers say this modularity is intended to reduce technical debt over time, a concern increasingly voiced by engineering leaders managing large and long-lived codebases.

The project’s emphasis on web standards reflects a broader shift in front-end development. After years in which frameworks abstracted away the browser, browser APIs have matured significantly, making native capabilities more powerful and predictable. Web Awesome leans into this trend by relying on standardised features that are supported across modern browsers, reducing the need for heavy runtime dependencies. This approach also lowers the barrier for adoption, as developers familiar with core web technologies can integrate components without learning framework-specific patterns.

Another distinguishing feature is the library’s focus on accessibility from the outset. Components are designed to meet established accessibility guidelines, with keyboard navigation, screen-reader support, and sensible defaults built in. While many UI libraries offer accessibility as an optional layer, Web Awesome treats it as a baseline requirement. Advocates within the accessibility community have long argued that retrofitting accessibility is both costly and unreliable, and the project’s maintainers position this design choice as a response to that reality.

Customisation is handled through a combination of CSS variables, design tokens, and clear extension points. Rather than forcing developers to override deeply nested styles, Web Awesome exposes theming controls intended to be predictable and maintainable. This is particularly relevant for organisations that support multiple products or white-label platforms, where consistency and scalability are critical.

Community governance is another area where the project seeks to differentiate itself. Developed openly, with contributions encouraged from designers and developers alike, Web Awesome positions itself as a collaborative effort rather than a vendor-driven initiative. Its roadmap is shaped by community feedback, and discussions around new components or changes are conducted in public. This openness is designed to foster trust and long-term sustainability, addressing concerns that have arisen when popular open-source tools become tightly coupled to commercial interests.

Early adoption has been driven largely by developers working across heterogeneous stacks, including teams migrating between frameworks or maintaining legacy systems alongside newer applications. For these users, the promise of a single, consistent component library that can span multiple environments is particularly attractive. Analysts note that this use case has grown as organisations seek to rationalise tooling and reduce the cost of maintaining parallel front-end implementations.

Despite the enthusiasm, challenges remain. Competing with established framework-specific libraries means convincing developers that a standards-first approach can match the convenience and ecosystem support of entrenched tools. Performance expectations are also high, and any perception of overhead in Web Components could slow adoption among performance-sensitive teams. The maintainers acknowledge these concerns and say ongoing optimisation and benchmarking are central to the project’s development priorities.

The article Web Awesome aims to reshape open-source UI development appeared first on Arabian Post.

Google has continued to expand the reach and capabilities of Copybara, its open-source tool designed to automate code migration and synchronisation across repositories, positioning it as a critical utility for organisations grappling with large, distributed codebases and complex development workflows. Originating from the company’s own need to manage code movement out of its vast internal monorepo, Copybara has evolved into a mature project used well beyond its original environment, reflecting wider industry pressures around collaboration, compliance and continuous delivery.

Copybara addresses a common but difficult problem in modern software development: keeping code consistent and up to date across multiple repositories without resorting to brittle scripts or error-prone manual processes. Many enterprises now operate hybrid models, combining internal repositories with external platforms such as GitHub, while also maintaining open-source mirrors, vendor forks or downstream customer branches. Copybara automates these flows by defining repeatable, auditable transformations that move code from one location to another while applying rules that adapt it to the target environment.

At the core of the tool is a domain-specific language based on Skylark, the configuration language also used by Bazel. This allows teams to describe migration workflows declaratively, specifying where code should be read from, how it should be transformed and where it should be written. Transformations can include refactoring paths, rewriting file headers, adjusting build metadata or filtering sensitive content, all of which are frequent requirements when code crosses organisational or licensing boundaries. By encoding these steps in configuration rather than ad-hoc scripts, Copybara reduces the risk of drift and makes migrations reproducible.

Integration has been a central focus of Copybara’s ongoing development. The tool supports Git as a primary version control system and works seamlessly with hosted platforms such as GitHub, enabling automated synchronisation between internal repositories and public open-source projects. This has made it particularly attractive to organisations that develop software in private but publish selected components openly, or that need to regularly pull upstream changes from external dependencies while preserving internal customisations. Support for pull request workflows and automated commits allows Copybara to fit into established review and governance processes.

Another area of growing importance is the role Copybara plays in continuous integration and delivery pipelines. As CI/CD systems become more sophisticated, the ability to reliably propagate code changes across repositories has become essential. Copybara can be run as part of automated pipelines, ensuring that updates triggered by a commit in one repository are reflected elsewhere in a controlled manner. This reduces manual coordination between teams and shortens the time between development and deployment, particularly in large organisations with multiple product lines sharing common code.

The tool’s design reflects lessons learned from Google’s internal development model, where thousands of engineers work in a single monolithic repository but still need to exchange code with external partners and open-source communities. While most companies do not operate at that scale, the underlying challenges are increasingly familiar as codebases grow and teams become more distributed. Industry analysts note that tools like Copybara are gaining attention as enterprises seek to balance the flexibility of multi-repo strategies with the consistency benefits traditionally associated with monorepos.

Copybara’s open-source status has also shaped its trajectory. Google maintains the project and continues to publish updates, but external contributors have influenced its feature set by adapting it to different organisational contexts. This has included enhancements around error handling, logging and dry-run capabilities, which are essential for teams that need confidence before applying large-scale changes. The project’s public issue tracker and documentation have matured alongside the code, lowering the barrier for adoption outside Google’s ecosystem.

Despite its strengths, Copybara is not positioned as a general-purpose version control replacement. It assumes a certain level of engineering discipline and familiarity with configuration-driven tooling, and its Skylark-based syntax can present a learning curve for teams without prior exposure. There are also limits to how far automated transformations can go before human review becomes necessary, particularly when semantic changes to code are involved. As a result, Copybara is often deployed as part of a broader toolchain rather than as a standalone solution.

The article Google’s Copybara reshapes large-scale code movement appeared first on Arabian Post.

Docker has made its enterprise-grade hardened container images freely available to the global developer community, marking a significant shift in how secure software supply chains are built and maintained. The company confirmed that images once restricted to paid enterprise customers are now open source and released under the Apache License 2.0, allowing unrestricted use, modification and redistribution.

The move centres on Docker Hardened Images, a curated set of container base images designed to reduce attack surfaces, address known vulnerabilities and align with modern compliance expectations. By opening access, Docker is seeking to respond to growing concerns around software security, as organisations face mounting pressure from regulators, customers and insurers to demonstrate stronger controls across development pipelines.

Docker executives said the decision reflects changes in how software is built and deployed, with containers now foundational across cloud, on-premise and hybrid environments. Hardened images typically include minimal packages, strict dependency management and regular security updates, helping developers avoid common pitfalls such as bloated images and outdated libraries that can expose systems to exploitation.

The newly opened images include hardened variants of widely used bases such as Alpine, Debian and Ubuntu, as well as language-specific images for runtimes like Java, Python, Node. js and Go. These images are scanned continuously, rebuilt when vulnerabilities are disclosed and maintained with reproducibility in mind, enabling teams to trace builds back to known states.

Docker’s decision arrives against the backdrop of intensifying scrutiny on open-source software following high-profile supply-chain incidents in recent years. Governments and large enterprises have increasingly demanded software bills of materials and clearer provenance for components used in production systems. Hardened images address part of that challenge by offering trusted starting points for application containers.

Until now, Docker Hardened Images were bundled into enterprise subscriptions, limiting adoption largely to larger organisations with the budgets and governance frameworks to justify paid offerings. By making them free and open source, Docker is aiming to broaden uptake among startups, independent developers and small teams that may lack dedicated security staff but still deploy software at scale.

Industry analysts say the shift could alter competitive dynamics in the container ecosystem. Several cloud providers and security vendors offer hardened or “distroless” images, often tied to proprietary tooling or platform-specific services. Docker’s approach, anchored in open licensing, lowers barriers and reinforces its position as a neutral layer in an increasingly fragmented landscape.

The Apache License 2.0 grants developers broad rights while offering legal protections around patents, a point that resonates with enterprises wary of ambiguous licensing. For corporate users, the change simplifies internal approvals, since teams can adopt hardened images without navigating procurement cycles or subscription constraints.

Security professionals caution that hardened images are not a complete solution. Application code, configuration and runtime practices remain critical, and vulnerabilities can still be introduced through dependencies added on top of base images. However, starting from a hardened foundation reduces baseline risk and can ease compliance efforts when paired with scanning and monitoring tools.

Docker has indicated that enterprise customers will continue to receive additional assurances, including service-level commitments, priority support and deeper integrations with policy and governance features. The open release does not eliminate the commercial tier but repositions security basics as a shared public good rather than a premium add-on.

The announcement also underscores Docker’s broader strategy to reassert relevance as container tooling matures. While container orchestration and cloud platforms have absorbed much of the operational complexity, Docker retains strong influence at the developer workstation level. Providing secure, production-ready images strengthens that connection and encourages developers to stay within Docker’s ecosystem from local builds to deployment.

Open-source contributors are expected to play a role in refining the images over time, proposing improvements, reporting issues and extending support to additional stacks. Docker said it will continue to steward the project, balancing community input with internal security processes to maintain consistency and trust.

The article Docker opens hardened container images to all developers appeared first on Arabian Post.

Denmark has begun a phased retreat from Microsoft software across parts of its public administration, signalling a broader reassessment of how governments manage dependence on dominant technology suppliers and safeguard digital sovereignty. The shift, confirmed by officials overseeing state IT procurement, starts with the transport and traffic administration but is framed as a test case for wider adoption across ministries and agencies.

At the centre of the move is a plan to replace Microsoft Office with open-source alternatives such as LibreOffice and to reassess cloud services tied to US-based providers. Senior officials involved in the transition describe it as a pragmatic step rather than a wholesale rupture, designed to give public bodies greater control over data, costs and long-term interoperability while reducing exposure to licensing changes dictated by a single vendor.

The transport authority has already begun migrating internal workflows, document management and collaboration tools away from Microsoft’s ecosystem. Staff training and parallel systems are being used to limit disruption, and legacy formats are being retained during the transition to ensure compatibility with external partners. The government has acknowledged that Microsoft products will continue to be used where replacements prove impractical, particularly in specialised systems.

Denmark’s decision reflects a wider debate across Europe about digital autonomy, sharpened by concerns over data protection, geopolitical risk and the escalating cost of enterprise software subscriptions. Public administrations have faced repeated price increases for cloud and productivity suites, alongside tighter contractual terms that critics say lock customers into long-term dependence. Open-source platforms, while not cost-free, are viewed by advocates as offering greater transparency and flexibility.

Officials involved in the Danish review argue that the move is not anti-American or anti-Microsoft but a recalibration of risk. They point to the country’s obligations under European data protection rules and the need to ensure that sensitive public data can be managed under national legal frameworks without ambiguity. The use of software governed by foreign jurisdictions has long been debated, but heightened regulatory scrutiny has brought the issue into sharper focus.

The Danish Agency for Digital Government has previously outlined principles encouraging public bodies to consider open standards and interoperability when procuring IT systems. Those principles are now being operationalised, with ministries asked to evaluate whether existing software contracts align with long-term strategic goals. The traffic department’s transition is intended to generate practical evidence on costs, productivity and security before decisions are taken elsewhere.

Technology analysts note that Microsoft remains deeply embedded in European public sectors, making a clean break unlikely. Email systems, identity management and specialised applications are often tightly integrated with Microsoft infrastructure, and replacing them can require years of planning. Denmark’s approach, which emphasises gradual change rather than abrupt termination, is seen as a realistic attempt to rebalance rather than disengage entirely.

Similar discussions have emerged in other European states and municipalities. Authorities in Germany, France and the Netherlands have at various times experimented with open-source office software or sovereign cloud initiatives, with mixed results. Some projects were scaled back due to usability challenges or compatibility issues, while others delivered savings and reduced reliance on proprietary platforms. Denmark’s effort is being closely watched for lessons on execution rather than ideology.

Microsoft, for its part, has invested heavily in compliance with European regulations and operates data centres within the region. The company has argued that its cloud services meet stringent security and privacy standards and that economies of scale deliver value for public clients. Industry observers say that Denmark’s move may prompt renewed engagement from Microsoft on pricing, contract flexibility and localisation assurances.

Civil servants involved in the pilot stress that user acceptance will be critical. Early feedback has highlighted differences in document formatting and collaboration features when switching away from familiar tools. Training programmes and technical support are being expanded to address these issues, and officials concede that productivity gains will not be immediate. The objective, they say, is resilience and choice rather than short-term efficiency.

The article Denmark starts unwinding its reliance on Microsoft appeared first on Arabian Post.

Nvidia has unveiled Nemotron 3 Open, a new family of large language models designed for agentic artificial intelligence, marking a shift in how the company is addressing enterprise demand for systems that can plan, reason and act across multiple tools and agents rather than respond with single-turn answers. The release underscores Nvidia’s push to balance scale with efficiency as businesses seek AI that can operate reliably within defined workflows.

The Nemotron 3 Open models are positioned for multi-agent environments in which specialised agents collaborate, delegate tasks and verify outcomes. Nvidia says the models are optimised for instruction following, tool use and structured reasoning, reflecting a growing emphasis among enterprises on predictable behaviour, auditability and cost control. By making the models openly available under a permissive licence, the company aims to accelerate adoption across regulated sectors such as finance, healthcare and industrial operations, where proprietary black-box systems face resistance.

This launch arrives as enterprises increasingly deploy agentic AI to automate complex processes such as customer service orchestration, supply chain optimisation and software operations. Traditional large models, while powerful, can be expensive to run and difficult to constrain. Nemotron 3 addresses this by offering multiple parameter sizes tuned for deployment efficiency, allowing organisations to choose models that fit latency, throughput and budget requirements without sacrificing reasoning capability.

Nvidia’s move reflects broader industry trends. Model developers are rethinking the assumption that bigger is always better, focusing instead on task-specific optimisation and composability. Agentic systems typically rely on several models working in concert, including planners, retrievers and executors. In such setups, inference costs multiply quickly, making efficiency a commercial imperative. Nemotron 3 is designed to slot into these architectures, supporting function calling and structured outputs that simplify integration with enterprise software.

The models have been trained using a mix of curated datasets and reinforcement learning techniques aimed at improving reliability in multi-step tasks. Nvidia has emphasised safety alignment and controllability, areas that have drawn scrutiny as AI systems gain autonomy. Enterprises deploying agentic AI often require clear guardrails to ensure systems act within policy and regulatory constraints, and Nvidia says Nemotron 3 has been evaluated for consistency and reduced hallucination rates in operational contexts.

Beyond the models themselves, Nvidia is positioning Nemotron 3 within its broader AI ecosystem, which includes frameworks for orchestration, deployment and monitoring. The company’s strategy leverages its dominance in accelerated computing, pairing software with hardware optimisations to deliver end-to-end platforms. This integrated approach has become a competitive differentiator as rivals offer standalone models without comparable infrastructure support.

Competition in the open-model space has intensified, with technology firms and research labs releasing increasingly capable systems to attract developer mindshare. By opening Nemotron 3, Nvidia signals that openness can coexist with commercial ambition. The company continues to monetise through enterprise support, cloud partnerships and hardware sales, while benefiting from community-driven innovation and faster iteration cycles.

Early feedback from developers highlights the appeal of models tailored for agentic workflows rather than general chat. Use cases cited include automated incident response, document processing pipelines and collaborative coding agents. These applications prioritise determinism and tool integration over conversational flair, aligning with Nemotron 3’s design goals.

The release also has implications for AI governance. Open models allow organisations to inspect, fine-tune and deploy systems within their own environments, addressing concerns around data sovereignty and compliance. This is particularly relevant in regions with stringent data protection rules, where sending sensitive information to external APIs is problematic. By enabling on-premises and private cloud deployments, Nvidia broadens its reach into sectors that have been cautious about adopting generative AI.

While the models promise efficiency gains, challenges remain. Agentic systems are complex to design and maintain, requiring careful orchestration and monitoring to avoid cascading errors. Enterprises adopting Nemotron 3 will still need expertise in prompt engineering, evaluation and lifecycle management. Nvidia’s tooling aims to lower these barriers, but successful deployment depends on organisational readiness as much as model capability.

The article Nvidia opens Nemotron 3 models for agentic AI appeared first on Arabian Post.

Zerobyte has entered the crowded data protection market with a proposition aimed at individuals, small businesses and early-stage teams seeking simple backup automation without licensing costs. Marketed as a free and easy-to-use tool, Zerobyte supports a wide range of backup needs at a time when data loss incidents, ransomware attacks and accidental deletions continue to disrupt organisations with limited technical resources.

The tool is designed to automate routine backups across local devices and selected storage environments, reducing dependence on manual processes that remain common among freelancers, start-ups and small offices. Developers behind Zerobyte say the software focuses on lowering the technical barrier that often prevents users from adopting structured backup practices, particularly outside large enterprises where dedicated IT staff are absent.

Zerobyte’s release comes amid growing concern over data resilience. Industry surveys have consistently shown that a significant share of small firms still operate without verified backups or rely on irregular copying of files to external drives. This vulnerability has been amplified by the rise of ransomware, which increasingly targets smaller organisations perceived as easier entry points. Against this backdrop, free automation tools have gained attention as a first line of defence rather than a comprehensive disaster-recovery solution.

According to product documentation and early user feedback, Zerobyte allows scheduled backups, incremental updates and basic restore functions, features that until a few years ago were typically bundled into paid software. The platform supports common file systems and standard storage locations, making it compatible with widely used operating systems and hardware setups. Its developers emphasise that installation and configuration can be completed without command-line interaction, a deliberate choice to appeal to non-technical users.

Analysts tracking the backup and recovery sector note that Zerobyte fits into a broader trend of “good-enough resilience” tools. These products are not designed to replace enterprise-grade systems used by banks, governments or large cloud providers, but to close a persistent protection gap at the lower end of the market. By offering automation at no cost, such tools can encourage better data hygiene while also serving as entry points to paid upgrades or complementary services.

Competition in this space is intense. Established vendors already offer freemium versions of backup software with storage limits or reduced functionality, while open-source projects provide flexibility for advanced users willing to manage configurations themselves. Zerobyte differentiates itself by positioning simplicity as its core feature, with minimal setup screens and default settings intended to work “out of the box”. This approach mirrors successful adoption strategies seen in password managers and personal encryption tools over the past decade.

Security specialists caution, however, that free tools still require careful evaluation. Backup software can access sensitive files and system resources, making trust, transparency and update practices critical. While Zerobyte’s creators highlight regular updates and clear documentation, experts advise users to verify restore processes and understand where backups are stored, particularly if external or network locations are involved. Automation reduces human error, but it does not eliminate the need for periodic checks.

From a market perspective, Zerobyte’s launch reflects a shift in how backup solutions are consumed. Cloud storage costs have fallen, operating systems have improved native recovery features, and users increasingly expect automation as a baseline rather than a premium add-on. Tools that fail to meet these expectations risk irrelevance, especially among younger businesses accustomed to subscription-free utilities supported by community development or optional paid features.

There is also a regulatory dimension. Data protection rules in several jurisdictions place responsibility on organisations to safeguard personal and business information against loss. While Zerobyte does not position itself as a compliance solution, its availability may help smaller entities demonstrate basic due diligence in data handling, provided backups are configured securely and tested.

The article Zerobyte positions itself as accessible backup automation tool appeared first on Arabian Post.

Ubuntu is set to expand support for AMD’s data-centre GPUs after Canonical confirmed that it is working with the chipmaker to deliver a streamlined, fully integrated version of the ROCm software stack in upcoming releases of the operating system. The decision marks one of the most significant efforts yet to improve deployment of AMD accelerators across enterprise servers, cloud environments, and developer workstations as demand for AI workloads continues to rise.

Canonical said the partnership would give Ubuntu users a more consistent and predictable way to install and maintain ROCm, the software platform that enables AMD GPUs to run machine-learning and high-performance computing frameworks. While ROCm has traditionally been available through AMD’s own distribution channels, the process for activating support on Linux machines has varied, often requiring manual configuration, driver checks, or custom kernels. Canonical’s integration work is expected to remove many of those barriers by packaging ROCm directly into Ubuntu’s repositories and aligning updates with the platform’s broader maintenance cycle.

The move comes as AMD accelerates its expansion into the AI compute market, led by the Instinct MI300 series and a succession of platform-level updates designed to challenge Nvidia’s dominance. Industry analysts have noted that enterprise customers evaluating alternatives to Nvidia have frequently cited software readiness as a key factor, with mature and well-supported ecosystems proving as important as raw hardware capability. By offering ROCm as an officially maintained Ubuntu package, Canonical aims to close that gap for HPC operators, cloud providers, and AI-focused organisations considering AMD hardware.

Canonical engineers have emphasised that the packaged ROCm builds will undergo the same testing and quality assurance procedures that apply to other components of Ubuntu’s graphics and compute stack. This includes compatibility checks with specific GPU models, kernel versions and runtime libraries, as well as security reviews aligned with Ubuntu’s long-term support policies. Developers said the goal is to ensure users can install ROCm with a single command on systems that meet hardware requirements, reducing the complexity that previously discouraged adoption.

AMD’s leadership has repeatedly highlighted open-source collaboration as central to its AI strategy. ROCm itself is structured around open frameworks such as HIP, which provides a path to run CUDA-based software on AMD hardware through source-level translation. Making ROCm more widely accessible on a major Linux distribution is expected to support broader community efforts to optimise machine-learning libraries, containerised workloads and research-grade applications for AMD accelerators.

Cloud operators are also paying close attention to the integration. Ubuntu remains the most widely used Linux distribution on public cloud platforms, and easier access to ROCm could influence procurement and deployment patterns as hyperscalers diversify their GPU fleets. Analysts tracking AI infrastructure supply chains have reported sustained interest in AMD hardware, particularly as customers look for cost-efficient alternatives amid high demand for compute capacity. An integrated software stack on a mainstream Linux platform could strengthen AMD’s position as these providers plan future expansions.

Developers working in AI-heavy fields have expressed optimism that the integration will cut down on configuration time, improve reliability and reduce the need for bespoke environment setups. Machine-learning researchers have said that having ROCm available as a native Ubuntu package will simplify reproducibility across teams, especially in environments where multiple users share GPU clusters or run containerised workloads. Canonical has been working to ensure that the ROCm packaging accommodates both bare-metal installations and cloud instances, making the stack accessible across a wide range of hardware.

The improvement aligns with a broader industry trend in which software ecosystems around GPUs are becoming central to competitive positioning. Nvidia’s extensive CUDA tooling remains the benchmark, but the rapid adoption of AMD’s MI300 accelerators by cloud and enterprise customers has placed new pressure on rival vendors to refine their platforms. Canonical’s collaboration with AMD reflects this shift, as both companies seek to reduce fragmentation and ensure developers have consistent tools to build and deploy AI applications.

Ubuntu users have also called for clearer guidance on hardware compatibility, and Canonical is developing documentation to outline supported GPU models, validated drivers and recommended configurations for AI workloads. The organisation plans to update this guidance as ROCm support expands, ensuring system administrators and developers can make informed decisions when setting up GPU nodes. By embedding ROCm in the Ubuntu ecosystem, Canonical aims to foster a more predictable environment that encourages teams to experiment with AMD’s accelerators.

The article Ubuntu move aims to simplify AMD AI GPU use appeared first on Arabian Post.

The Tor Project has marked a significant milestone in its multi-year effort to reengineer its core software by advancing Arti, the Rust-based implementation of the anonymity network, with the launch of version 1.8.0. The update introduces enhanced circuit isolation to reduce fingerprinting risks and new tools designed to streamline the migration of critical onion service keys from the legacy C codebase — part of a broader shift aimed at addressing long-standing security and maintenance challenges inherent in Tor’s original C implementation.

Arti, conceived as a safer, more modular alternative to the traditional C code underpinning Tor, is built in the Rust programming language, which enforces memory safety guarantees at compile time. This architectural change is central to the project’s objectives, as C has historically been prone to memory corruption vulnerabilities such as buffer overflows and use-after-free errors that have required continuous vigilance from developers and security auditors. By contrast, Rust’s design greatly reduces the likelihood of such classes of flaws, a key driver behind the Tor Project’s investment in the Arti rewrite.

With the 1.8.0 release, a major focus is the overhaul of how Arti manages circuit timeouts. Tor’s existing model for circuit lifetime — known as Circuit Dirty Timeout — uses a single, predictable timer for ending circuits, a behaviour that can be exploited for traffic analysis. Arti replaces this with a dual-timer approach: one managing when a circuit can accept new connections and another that terminates idle circuits at randomized intervals. The aim is to make it harder for an external observer to recognise traffic patterns, thereby strengthening resistance to fingerprinting techniques that have been studied extensively in academic and operational settings.

The update also introduces an experimental command, arti hsc ctor-migrate, which assists operators of onion services to transfer “restricted discovery” keys — used for client authorisation — from the legacy C-based keystore into Arti’s own infrastructure. This tool reduces manual efforts at a time when many service operators are weighing the benefits and risks of transitioning away from the older codebase.

Development work in Arti goes beyond these headline features. The 1.8.0 release includes quality-of-life improvements to routing and protocol implementation, extended support for directory cache functionality, and refined handling of OR port listener configurations — components that are essential for eventual relay and directory authority support within the Rust implementation. These enhancements reflect a sustained focus on preparing Arti for broader network roles that until now have remained the province of the C codebase.

Although Arti can already act as a minimal command-line client to connect to the Tor network and serve as a SOCKS proxy, its roadmap envisages deeper feature parity with the classic Tor implementation. Core features — including full anti-censorship support and production-ready relay capabilities — remain under development, but the pace of releases and the continuous integration of new capabilities signal growing confidence among contributors and maintainers.

The shift to Rust is not merely about incremental improvements. It represents a strategic bet on the long-term sustainability and security of the Tor ecosystem. Tor’s original C codebase, which has powered the network since its creation in the early 2000s, has been the subject of ongoing scrutiny due to its complexity and susceptibility to memory safety bugs. By contrast, Rust’s compile-time guarantees ensure that large classes of bugs are eliminated before they can manifest at runtime — an attractive quality for software tasked with protecting user anonymity under adversarial conditions.

Responses from within the developer community underline both optimism and caution. Rust advocates highlight the potential for safer concurrency and fewer security pitfalls, while some long-standing observers of the Tor codebase note that a full migration will be a marathon rather than a sprint, requiring continuous contributions and extensive testing across diverse deployment scenarios. The incremental unlocking of features in successive Arti versions, including restricted discovery enhancements in version 1.7.0 and earlier onion service improvements in 1.2.2, underscores a measured but persistent trajectory toward maturity.

Industry experts view Arti as part of a broader trend in security-critical software towards safer languages and modular architectures, driven by a need to balance performance, resilience, and maintainability. As users increasingly depend on tools like Tor to circumvent censorship, protect privacy and secure sensitive communications, the stability and safety guarantees afforded by Rust may provide a competitive advantage over legacy implementations that have accumulated technical debt over decades.

The article Tor’s next-generation implementation boosts privacy and performance with Rust rollout appeared first on Arabian Post.

The tech company behind Ubuntu is winding down its long-standing public wiki sites by August 2026 and launching a completely rebuilt wiki to address mounting concerns over content quality, security and usability.

The existing public wikis — at wiki. ubuntu. com and help. ubuntu. com/community — have served the global Ubuntu community for more than two decades. But in a post titled “A new Ubuntu wiki, Part 1: Announcement,” the team at Canonical laid bare several structural issues that prompted this overhaul. The wiki software is built on an old version of MoinMoin running on Python 2, which is no longer supported with security patches. That exposes contributors and users to vulnerabilities.

Canonical highlighted content decay as another major concern. Many pages are outdated or redundant, while authoritative official documentation has shifted to other platforms. Users attempting to seek help often land on obsolete pages, leading to confusion and inefficiency.

Usability has also been degraded over time. Reports from community members note sluggish page loads, broken registration/login flows, poor mobile optimisation and a user interface that no longer meets modern web standards. The coexistence of two overlapping wikis — one for general Ubuntu content and another for community help — has added to confusion about where to look for reliable guidance.

To build the replacement, Canonical has assembled a compact cross-functional team drawing from technical authors, platform engineers, community engineers, designers, and core Ubuntu developers. This team is developing a new wiki instance behind closed doors, with a target milestone of an alpha release in 2026. According to Shane Crowley, a Canonical technical author involved in the project, the new platform will incorporate modern standards for documentation, security, and user experience. Community feedback will be solicited as the development advances.

The decision underscores the evolving role of knowledge platforms in open source ecosystems. Over time, official documentation has migrated to more specialised and actively maintained mediums — such as official docs sites, community forums, and discussion platforms. The legacy wikis, once central, have become vestigial and increasingly unreliable. By replacing them, Canonical aims to unify Ubuntu’s community knowledge base under a single, secure, maintainable platform.

For contributors and long-time Ubuntu users, this marks the end of an era. The original Ubuntu wiki launched in 2004 — the same year as Ubuntu’s first release — and grew into a vast archive spanning developer discussions, community governance, troubleshooting guides and technical documentation. With the planned decommissioning of both public wikis, all that accumulated content will need to be reconsidered: some will be migrated, some archived, and much may be left behind.

Canonical says it will periodically publish updates about the new wiki’s design, migration plans and community involvement opportunities. Users are encouraged to follow the project’s official discussion channels to participate, provide feedback and aid in rebuilding a more reliable, unified repository of Ubuntu knowledge.

The article Canonical to scrap current Ubuntu wiki for rebuilt platform appeared first on Arabian Post.

The grip of Chromium on the global browser ecosystem has grown so wide that many users now assume every modern browser is built on Google’s open-source architecture. That perception has taken root partly because major names such as Microsoft Edge, Opera, Brave, Vivaldi and Arc all rely on Chromium’s Blink rendering engine, creating a sense that browsing itself has become synonymous with Google-aligned foundations. The dominance is substantial, but it is not absolute. A parallel lineage continues to exist through Firefox’s Gecko and its modernised fork, Quantum, which power a smaller but distinctive set of browsers that prioritise independence, privacy and open standards. Understanding these alternatives matters because engine diversity is not simply a technical detail; it shapes web compatibility, competition and the long-term evolution of online experiences. This analysis examines why these Firefox-based options still hold significance and what they offer users seeking a meaningful departure from Chromium’s near-monopoly.

Firefox remains the most visible representative of the non-Chromium family. Despite pressure from platforms that increasingly optimise for Chromium-first rendering behaviours, Mozilla’s browser has continued refining its core engine to remain competitive on speed and stability while maintaining a sharper emphasis on user agency. Its tracking-protection framework, deliberate stance against invasive cookie models and resistance to proprietary APIs tied to Chrome’s ecosystem provide a roadmap quite different from the one driving Chromium’s expansion. Firefox’s strengths extend beyond ideology; independent benchmarks consistently show it performs well across hardware profiles and excels in memory management under multi-tab workloads. These traits have encouraged developers to adapt its engine to more specialised needs, leading to alternative browsers that leverage Firefox DNA while adding their own philosophies.

Waterfox emerged as one of the earliest Firefox-based forks designed to push performance boundaries. Its appeal was rooted in optimising for 64-bit systems long before Mozilla shifted to native 64-bit distribution. Over time, Waterfox evolved into a privacy-forward browser that removed or disabled elements users considered unnecessary, such as telemetry modules and certain connection handshakes to Mozilla servers. This made it a compelling option for those who wanted Firefox compatibility without Mozilla’s broader ecosystem integrations. While still dependent on upstream updates, its direction demonstrates how Firefox’s open-source licence enables independent teams to tailor functionality for niche audiences in ways Chromium-compatible builds rarely attempt.

Pale Moon represents another branch in this ecosystem, striking a more radical path by maintaining its own fork of the Gecko engine instead of following Firefox’s move to Quantum. The result is a browser designed around classic Firefox extensions, traditional interface design and heavy customisation features. Its developers argue that modern browsers have sacrificed user choice for interface minimalism and automated controls, and Pale Moon stands as a counter-statement embedded in code. However, this divergence comes with trade-offs. Compatibility with some newer web technologies is less seamless than mainstream browsers, requiring users to balance personalisation with the awareness that some sites may rely on scripts optimised for Chromium or recent Firefox iterations. Even so, Pale Moon’s existence broadens the definition of what a browser can be by maintaining features large vendors have retired.

LibreWolf is a newer but rapidly growing Firefox-based alternative. Built directly from Firefox’s stable releases, it strips away telemetry, account integrations and certain cloud-dependent functions to create a hardened privacy-first environment. It pairs this with opinionated security defaults, including built-in tracker blocking, stricter cookies, and enhanced protection settings. Its rise illustrates that there is a constituency of users who appreciate Firefox’s modern performance but desire a more locked-down profile without manually configuring dozens of settings. The project’s focus aligns closely with broader shifts in digital behaviour, where individuals want security reinforced by default rather than as an optional layer buried in menus.

Floorp, developed in Japan, is one of the more innovative newcomers built on Firefox’s engine. It blends Firefox’s underpinnings with desktop-productivity concepts, offering multi-layout customisation, vertical tabs, dual-view browsing and split-panel workflows that resemble professional workspace applications. Its design ethos suggests a broader reinterpretation of what a browser can do beyond simply rendering pages. By experimenting with concepts typically found in coding environments or research tools, Floorp caters to power users who seek more integrated workflows. Its growth shows how Firefox’s engine, despite not dominating the market, remains flexible enough for developers to innovate on form and function in ways that Chromium-based browsers sometimes limit due to tighter architectural constraints.

These examples demonstrate a principle that is essential for the web’s long-term health: engine diversity is not merely aesthetic choice but a strategic safeguard against monoculture. When a single engine family becomes the default target for developers, web standards risk tilting in its favour, potentially creating a feedback loop where non-Chromium engines struggle to keep pace with proprietary extensions or behaviours normalised through market dominance. Mozilla has raised warnings on this issue, arguing that over-concentration threatens the openness of the web. Technical debates about WebRTC, media codecs and emerging APIs often reveal how one dominant engine can shape the pace and direction of standards. By contrast, Firefox-based projects inject variation into the landscape, ensuring that decisions about web capabilities continue to involve multiple engines rather than a single de facto gatekeeper.

Another layer of this conversation relates to user autonomy. Chromium-based browsers, even those committed to privacy, still rely on an engine steered primarily by Google’s strategic priorities. This includes changes to extension frameworks, such as the transition from Manifest V2 to V3, which sparked concern among developers who feared reduced flexibility for blocking tools. Firefox and its forks, by preserving a more permissive extension environment, offer alternatives for users and developers who depend on higher-control browser modification. The vitality of these parallel ecosystems keeps innovation distributed rather than centralised.

At the same time, Firefox-based browsers face real challenges. They must operate with fewer resources, smaller development teams and a fraction of Chromium’s organisational backing. Ensuring compatibility with sites optimised primarily for Chromium requires persistent engineering effort. Some forks, especially the smaller ones, depend heavily on upstream Firefox updates to maintain security parity. The landscape is dynamic, with projects occasionally stalling due to limited contributors or funding shortages. These constraints underscore why Mozilla’s role remains critical; it anchors the broader ecosystem by maintaining a fully staffed engine that forks can rely on for core updates.

The article Not Every Browser Runs on Chrome Engine appeared first on Arabian Post.

Smartwatch pioneer Pebble has returned under the stewardship of its original founder, with both software and hardware released as openly available to developers and tinkerers. The relaunch is driven by Eric Migicovsky and his new venture Core Devices, aimed at reviving the once-beloved e-paper wristwear in a more transparent, sustainable form.

Migicovsky confirmed that the entire software stack behind modern Pebble devices — including the smartwatch OS, mobile companion apps for Android and iOS, developer tools and backend for the app store — is now 100 per cent open source. The release allows anyone to download, compile and maintain the code, ensuring long-term viability even if Core Devices scales back operations. Alongside this, the electrical and mechanical design files for the new hardware have been published, enabling hobbyists to build their own compatible devices or extend the existing design.

The renewed Pebble line comprises two devices previously revealed under different names: the e-paper watch Pebble 2 Duo and the colour-screen model Pebble Time 2. These are descendants of the original Pebble Time lineup, resurrected after the company’s 2016 shutdown and sale to Fitbit. With the Pebble trademark successfully reacquired, Core Devices has repositioned these new devices as official Pebble products, slated for shipping in early 2026 subject to production timelines and component sourcing.

Design choices for Pebble’s reboot emphasise longevity, repairability and community ownership rather than chasing the high-end hardware arms race. The back cover of Pebble 2 Duo is screwed in — allowing battery replacement — and all schematics are supplied in open formats like KiCad. The core OS, known as PebbleOS, remains lightweight and energy-efficient, continuing the brand’s tradition of always-on displays, long battery life and simple, button-based navigation rather than heavy touch-driven features.

The article Pebble Makes a Clean Comeback with Fully Open Source Hardware and Software appeared first on Arabian Post.

Google has released the variable-font typeface Google Sans Flex under an open-source licence, making the typeface used across many Google products available for free download and use in any project. The font is now hosted on Google Fonts and licensed under the SIL Open Font License, removing the proprietary restrictions that previously kept it exclusive to Google’s internal design ecosystem.

Google Sans Flex is described by its creators as the “next generation” of the company’s brand typeface, built to combine versatility with polished readability for both web and mobile interfaces. Its variable-font design supports five adjustable axes — weight, width, optical size, slant and rounded terminals — enabling developers and designers to fine-tune letterforms for different contexts and display resolutions. A single font file can produce a wide range of styles that previously required dozens of separate files.

Designers and developers have welcomed the move as a significant moment for typography on the open web. With no licensing fees or complex usage restrictions, Google Sans Flex becomes a viable option for web designers, app makers, and content creators who want a clean, modern sans-serif font that remains flexible across varied layouts, screen sizes and user-interface needs. The fact that it’s the core typeface used in many Google services adds to its appeal: many users are already familiar with its visual tone, which mixes geometric precision with a subtle humanist touch.

Typical earlier options for open fonts included families such as Roboto and Open Sans, both widely adopted across websites and applications for their readability and neutrality. Google Sans Flex, however, offers added nuance. The “roundness” axis, for instance, allows designers to shift the font’s character from crisp and professional to softer and more approachable without switching to a different family. The “width” axis enables layout flexibility — useful when adapting typography for narrow columns on mobile devices or wide expanses on desktops.

Font specialists note that the timing of this release is significant. As variable-font technology — more formally known as OpenType Variable Fonts — has matured, it has become increasingly supported across modern browsers, operating systems, and design tools. This means Google Sans Flex is not just a design curiosity but a practical asset for production across web, mobile and print. The potential reduction in font file load, thanks to consolidation of multiple styles into one variable font, can also improve site performance, thereby benefiting user experience at scale.

The article Google Sans Flex Goes Open Source appeared first on Arabian Post.

Self-hosting — running and maintaining software on privately controlled servers instead of relying on cloud providers — is drawing growing interest among developers and organisations, with Linux users often leading the shift. What began as a niche practice among privacy-conscious hobbyists is evolving into a broader movement driven by demand for data control, cost efficiencies and long-term stability.

At the heart of this trend lies a grounding in open-source software. Users deploy well-supported tools on Linux platforms — from file synchronisation, photo libraries, password vaults and personal wikis to even self-hosted AI models — enabling full ownership and control over data. For many, this replaces the vulnerability of depending on third-party services that may change their pricing, policy or shut down entirely. The reliability of Linux hosting is often cited as key: mature package managers, containerisation tools like Docker, and strong community documentation make self-hosting accessible even beyond hardcore sys-admins.

The motivations behind self-hosting are multifaceted. Control and privacy top the list — users know exactly where their data is stored, how it is managed and who can access it. For individuals or small organisations with predictable workloads — backups, media libraries, password management, private notes — self-hosting can be cheaper over time than subscription-based cloud services. Customisability and flexibility offer further appeal: self-hosters retain the ability to tweak configurations, integrate diverse applications, or deploy low-code platforms behind their own firewall for bespoke requirements.

Security considerations play a central role in the shift. Open-source software allows peer reviews and transparency in code, making it easier to detect vulnerabilities and enact patches promptly. This stands in contrast to closed-source, vendor-managed cloud services where users may lack visibility into underlying infrastructure and security practices. For entities handling sensitive or regulated data, self-hosting often becomes the only viable route to retain control and compliance.

Recent developments reinforce self-hosting’s broader viability. Enterprises increasingly use self-hosted tools to run internal applications. For example, some large organisations have deployed open-source low-code platforms on their private infrastructure to manage critical operations like server patching, internal dashboards and identity management. Such deployments benefit from avoiding vendor lock-in, maintaining compliance, and keeping data behind corporate firewalls.

In parallel, the growth of self-hosted AI tools marks a new chapter. As smaller, efficient models become capable of running on modest hardware, organisations dealing with proprietary or regulated workloads are opting to host inference locally. This not only avoids cloud-provider data policies, but also reduces latency and offers more predictable costs. Hybrid models — where non-sensitive tasks run locally and only high-uncertainty jobs go to cloud services — are shaping up as pragmatic deployments.

The economics of self-hosting, however, are not uniformly favourable. While long-term costs can undercut subscription models, the benefits depend heavily on workload patterns, technical competence, and willingness to handle maintenance tasks such as backups, updates and security hardening. For dynamic workloads, rapidly growing services, or high-availability demands, cloud providers may still offer advantages in scalability, redundancy and managed support.

The article Self-Hosting Momentum Gains Ground Under Linux appeared first on Arabian Post.

Collabora Office has rolled out a brand-new desktop office suite compatible with Windows, macOS and Linux, offering a unified user experience across both online and offline environments. The suite inherits the user interface of Collabora Online — known for its clean, tabbed layout and streamlined tools — while retaining the powerful document compatibility and core engine of LibreOffice. The earlier enterprise-grade LibreOffice-based package has been rebranded as Collabora Office Classic.

Collabora Office delivers word processing, spreadsheets, presentations and vector graphics editing through Writer, Calc, Impress and Draw — all within a modern interface built using web technologies like JavaScript, CSS, WebGL and Canvas. This architecture promises faster updates and a lighter footprint, eliminating the need for Java and reducing system dependencies. The design aims to feel familiar to users of Collabora Online, ensuring minimal learning curve for those switching to desktop.

Behind this shift is a deliberate strategy by the company to unify its offerings under a consistent visual and technical stack. Instead of maintaining separate code paths for online and desktop versions, Collabora now offers a single codebase with identical UI across environments. This alignment simplifies development and support, and ensures that users enjoy similar experiences whether editing in a browser or on a device — an advantage over most legacy office suites where web and desktop versions diverge significantly.

Despite matching core functionality, Collabora Office omits certain advanced features that Collabora Office Classic retains. Notably, there is no embedded database application, and macro support is limited to running existing scripts — full macro-editing tools and advanced scripting remain available only in Classic. Users with complex spreadsheet models, heavy database use, or deep scripting workflows may find Classic more suited to their needs.

For workforces and organisations that prioritise document interoperability and data sovereignty, the new suite supports both the OpenDocument Format and Microsoft’s OOXML formats such as DOCX, XLSX and PPTX, preserving layouts and formatting across platforms. Being fully open-source and offline-first, it ensures that files stay on the local device unless shared explicitly — a feature that appeals to institutions concerned about privacy, regulatory compliance or reliance on cloud providers.

The interface’s simplicity and streamlined defaults may appeal to individual users, small teams and enterprises seeking a lightweight, efficient office suite. Freed from legacy dependencies, the new offering is quicker to install and easier to maintain. The decision to preserve the more feature-rich Classic line alongside the new suite offers a clear choice: modern convenience or full-fledged functionality, depending on the user’s needs.

The article Collabora Unveils Modern Office Suite for All Desktops appeared first on Arabian Post.

Microsoft has officially opened the source code of the original Zork trilogy—Zork I, Zork II and Zork III—making the foundational text-adventure games freely available under the MIT licence. The company’s Open Source Programs Office, working alongside its Xbox and Activision divisions, announced that the historic repositories now include source code, build notes, comments and documentation intended to support study, teaching and development. The release does not grant rights to trademarks, commercial packaging or marketing materials, which remain protected.

The games were initially developed in the late 1970s and early 1980s by Infocom co-founders Tim Anderson, Marc Blank, Bruce Daniels and Dave Lebling, and became influential through their use of the Z-Machine virtual machine. That architecture allowed one game to run on multiple early microcomputers, giving Zork broad platform reach. Microsoft acquired the intellectual property through its 2023 purchase of Activision Blizzard, which had previously absorbed Infocom. Under the new terms, the code has been officially relabelled under MIT licence terms via upstream pull-requests to the historical GitHub repositories. Although parts of Zork’s code had been publicly available via archivist uploads years before, those versions lacked clear licensing. Microsoft now clarifies the legal status of the code for public use, modification and study.

The release further underlines Microsoft’s increased engagement with open-source preservation in gaming. Educational institutions, independent developers and retro-gaming communities are being offered access to the full Z-Machine engine and original story files—allowing analysis of early interactive narrative systems. Microsoft states the purpose is not to modernise Zork but to preserve its historical engineering and storytelling significance. One industry commentator observed that “our goal is simple: to place historically important code in the hands of students, teachers and developers so they can study it, learn from it, and, perhaps most importantly, play it”.

This move arrives amid a broader revival of interest in game preservation and source-code release. In addition to Zork, other titles have seen archival releases but few major publishers have actively provided the full original code along with clear licensing conditions. Some observers note that Microsoft’s announcement carries a strong symbolic dimension—affirming that even legacy game-software is part of digital heritage. Developers and historians are already discussing how the code reveals the inner workings of the Z-Machine interpreter, memory-limited hardware constraints of the era and design decisions around text-based environments.

While enthusiast developers welcome the access, questions remain about how the community will mobilise it. Accessibility for newcomers may hinge on modern tools: the ZILF compiler and Z-Machine runners are referenced in guides setting out how to compile original files and execute on modern systems. The archives include instructions and notes for building Zork locally using interpreters such as Frotz, or compiling ZIL files for the Z-Machine format. Users must still source any assets not covered by the open-source code—commercial packaging, graphics, sound-effects, if any, are excluded from the license.

From a legal standpoint, the MIT licence offers broad permissions: access, reuse, modification and redistribution with minimal restrictions, provided copyright notice and licence text are retained. Gaming historians highlight that prior versions of the Zork source code existed on GitHub since 2019 but lacked formal licensing, which created ambiguity around legal reuse. Now that Microsoft has formally adopted the MIT licence, that ambiguity is removed. Reddit threads from programming communities underscore the significance: one user noted that “this code is mostly in ZIL, which is compiled to Z-code” and that exploring the Z-Machine architecture remains a fascinating exercise. Other developers pointed out that the Z-Machine was “a marvel of portability” in an era of competing micro-computer platforms.

For educators, the release presents a new teaching resource. Computer science programmes can use Zork’s code to illustrate topics such as virtual machines, resource-constrained programming, and interactive narrative systems. Preservation advocates say the entry strengthens the argument for publishers treating older titles as cultural artefacts worthy of archival rather than commercial repackaging alone.

The article Historic Zork Trilogy Code Released under MIT Licence appeared first on Arabian Post.

Canonical has taken significant steps to address the needs of security-conscious organisations by introducing new features in both its Kubernetes distribution and Ubuntu Long Term Support offerings. The company’s latest enhancements focus on improving compliance and security, which are crucial for industries requiring stringent safeguards.

The addition of FIPS 140-3 validation to Canonical’s Kubernetes distribution marks a major update in the company’s commitment to security. FIPS 140-3 is a critical certification for cryptographic modules, particularly in environments where security is a top priority. This certification makes Kubernetes more suitable for sectors like healthcare, government, and finance, which often face rigorous regulatory requirements. Kubernetes, the open-source container orchestration platform, has become an essential tool in modern cloud environments, and the integration of FIPS-certified security aims to enhance its appeal to compliance-sensitive users.

In addition to this, Canonical has announced an extension of the support lifecycle for Ubuntu LTS releases. Historically, Ubuntu LTS releases have been supported for five years, offering users a stable and secure environment. However, the company has now extended this period to up to 15 years, providing long-term stability and support for businesses and government agencies that require a more extended support window for critical infrastructure. This change ensures that Ubuntu can meet the needs of large organisations that depend on stability and long-term planning for their operations.

This extended lifecycle is particularly significant in the context of industries that rely on legacy systems and are hesitant to upgrade frequently due to the cost and complexity involved. By extending the LTS period, Canonical is aiming to reduce the burden of managing frequent upgrades while maintaining security and stability. The extended support also includes security patches, bug fixes, and updates, ensuring that organisations using Ubuntu LTS can confidently rely on it for many years to come.

Canonical’s move to integrate FIPS 140-3 capabilities with Kubernetes and offer longer-term support for Ubuntu LTS is a clear response to growing demand for secure, reliable, and long-lasting open-source solutions in sectors like finance, healthcare, and government. As businesses and institutions continue to digitise their operations and move to cloud environments, the need for robust security features that meet compliance standards is becoming more pronounced.

The company’s decision to offer FIPS certification alongside its Kubernetes distribution is also indicative of the broader trend towards increasing security in the open-source ecosystem. With Kubernetes playing a central role in containerised application deployment, its adoption across various industries is only expected to grow. By ensuring that Kubernetes is compliant with FIPS 140-3, Canonical is positioning itself as a leader in the security-focused Kubernetes space.

Canonical’s broader strategy with Ubuntu also highlights its focus on long-term user trust. By extending Ubuntu’s LTS lifecycle, the company is not only catering to security and compliance needs but also addressing concerns around the sustainability of open-source projects. The extended support lifecycle ensures that organisations can continue to use Ubuntu with the assurance that they will receive updates and security patches for an extended period, making it an attractive option for enterprises that rely on consistent and reliable software.

For organisations that are looking to deploy Kubernetes in a security-sensitive environment, Canonical’s offering now provides a compelling solution. With the added FIPS certification, Kubernetes can be trusted to meet the stringent requirements of government agencies and other compliance-heavy industries. The inclusion of FIPS 140-3 makes it easier for organisations to adhere to regulatory standards without having to compromise on the flexibility and scalability that Kubernetes offers.

The article Canonical Strengthens Kubernetes Security and Extends Ubuntu LTS Lifecycle appeared first on Arabian Post.

AMD has secured a pivotal role in the U. S. government’s ambitions to bolster artificial intelligence and scientific research, with the announcement of its involvement in powering the next-generation supercomputer at Oak Ridge National Laboratory. The new system, named Discovery, will become one of the most advanced computational platforms in the world, supporting groundbreaking research in various scientific fields and accelerating the development of AI capabilities in the U. S.

The Discovery supercomputer is part of the U. S. Department of Energy’s ongoing efforts to establish a robust, national AI ecosystem that can compete with global supercomputing leaders. ORNL, located in Tennessee, is the primary site for the nation’s computational research. AMD’s involvement, announced in late 2025, solidifies its growing influence in the high-performance computing space. The company will supply its cutting-edge processors to meet the immense computational demands of Discovery, enhancing both AI research and scientific exploration across industries.

The supercomputer, expected to launch in the coming years, will be central to projects in a variety of sectors, including climate modelling, advanced materials development, and bioengineering. With its integration of AI tools, Discovery will serve as a crucial platform for simulating complex scenarios, from predicting climate patterns to advancing drug discovery. The system’s scale and speed will enable researchers to tackle some of the most pressing challenges facing humanity, all while contributing to the broader goal of enhancing U. S. technological leadership.

AMD’s role in the project is particularly significant given its focus on high-performance processors for AI and machine learning. The company’s processors, particularly the EPYC line, have become a cornerstone in supercomputing and AI infrastructure due to their ability to process vast amounts of data simultaneously. These chips will be at the heart of Discovery’s computing power, helping to drive the AI models and simulations necessary for next-generation scientific breakthroughs.

This partnership also aligns with the broader strategic initiative to develop an “Open American AI stack,” which aims to foster an open-source ecosystem for AI development in the U. S. Discovery will provide the computational foundation for this initiative, which is set to include contributions from various stakeholders across academia, industry, and government. By powering such an ambitious AI framework, AMD is helping to accelerate the U. S.’s AI capabilities and positioning the country to maintain a competitive edge in global AI research.

The scale of Discovery will make it one of the most powerful supercomputers in existence, providing an unprecedented computational capacity to the U. S. scientific community. The platform’s combination of advanced AI tools and HPC infrastructure will help push the boundaries of what is possible with AI-driven research. As such, the project represents a crucial milestone in the development of AI technologies, which are poised to transform industries such as healthcare, energy, and materials science.

This collaboration also demonstrates the U. S. government’s ongoing commitment to harnessing AI for national security, economic growth, and scientific innovation. By supporting the creation of Discovery, the government is not only advancing domestic research capabilities but also positioning the U. S. as a leader in the global AI arms race. The success of such projects will have far-reaching implications, potentially reshaping industries and creating new technological frontiers.

The article AMD to Drive US Supercomputing Revolution at Oak Ridge appeared first on Arabian Post.

IBM has committed to enhancing AI-powered search and retrieval capabilities by becoming a premier member of the OpenSearch Software Foundation. The tech giant’s involvement marks a significant step forward in its mission to improve open-source search technology and enrich data-driven decision-making for businesses across industries.

This collaboration aligns with IBM’s broader strategy to integrate artificial intelligence more deeply into enterprise systems. OpenSearch, an open-source search and analytics suite, was originally derived from Elasticsearch and Apache Lucene, focusing on providing powerful tools for search, log analytics, and data exploration. By joining the OSSF, IBM seeks to accelerate the development of features that improve relevance, scalability, and operational efficiency within AI applications.

AI’s growing role in the enterprise landscape, particularly in search and retrieval, has prompted companies to seek smarter, more intuitive search solutions. With AI’s capacity to understand context and user intent, the integration of AI into search technologies enables more refined and actionable insights. For IBM, this partnership is a natural extension of its longstanding commitment to open-source initiatives, which form the backbone of many of its enterprise solutions.

The move also signals IBM’s renewed focus on developing enterprise-grade capabilities for OpenSearch. As a premier member, IBM is positioned to play a pivotal role in the platform’s development, contributing both technical expertise and resources to the foundation. OpenSearch, with its powerful capabilities in full-text search, data visualisation, and real-time analytics, is increasingly sought after by businesses looking for scalable and flexible search engines that can be integrated with cloud-based infrastructure.

IBM’s involvement with OpenSearch is expected to bring enhanced AI-powered features to the platform, including more advanced retrieval-augmented generation models. RAG, which blends traditional search techniques with machine learning, enables systems to generate contextually relevant information based on search queries. This capability has been identified as a critical advancement in transforming how businesses use search data to generate insights and make decisions.

The partnership could also be a response to the growing interest in AI-driven search across various sectors, from e-commerce and customer service to healthcare and finance. Industries that rely on massive datasets are increasingly looking for tools that can not only index and search vast amounts of data but also use AI to generate real-time, meaningful outcomes. IBM’s contribution to OpenSearch could prove instrumental in ensuring that the platform meets the rising demand for sophisticated, intelligent search solutions.

OpenSearch, which was launched in 2020 by Amazon Web Services, has quickly gained popularity in the open-source community due to its flexible, community-driven approach. Its ability to scale across large datasets and handle complex search queries has made it a strong competitor in the search and analytics space. With the added expertise and resources from IBM, OpenSearch is expected to evolve rapidly, further positioning it as a leader in the open-source search engine market.

The collaboration is expected to drive both technical and strategic advancements within OpenSearch, particularly in areas like machine learning, natural language processing, and automation. AI-powered search systems can reduce manual intervention, improving operational efficiency while delivering more accurate results. Additionally, businesses will benefit from the integration of advanced analytics, enabling them to gain deeper insights into their data with greater speed and accuracy.

The article IBM Strengthens AI Search with OpenSearch Partnership appeared first on Arabian Post.

Ubuntu, the popular open-source operating system, has announced a significant extension to its long-term support offerings, with a new 15-year commitment aimed at bolstering enterprise adoption. The initiative will provide extended support for key versions of the operating system, including Ubuntu 14.04 LTS, which will receive five additional years of updates and maintenance. This bold move is designed to reassure businesses that depend on Ubuntu for critical infrastructure and software services, ensuring long-term stability and security.

The decision comes at a time when enterprises increasingly rely on Ubuntu for mission-critical applications, cloud deployments, and large-scale data centre operations. Ubuntu’s parent company, Canonical, has faced growing pressure to meet the demands of businesses that require dependable, long-term support for their systems. By extending the LTS support window, Canonical aims to offer a stable, secure environment for enterprises that require extended periods of reliability, a feature especially valued in sectors such as finance, healthcare, and government.

As part of this extension, Canonical has committed to providing security updates, bug fixes, and critical patches for a full 15 years from the initial release of each LTS version. This is a notable departure from the previous standard of a 10-year commitment for LTS releases. The expanded support is expected to make Ubuntu even more appealing to organisations that seek to minimise system disruptions, reduce costs associated with frequent upgrades, and maintain high uptime for their operations.

The introduction of five additional years of support for Ubuntu 14.04 LTS represents a major step in maintaining consistency for enterprise customers. While Ubuntu 14.04 LTS was originally set to end its support in April 2019, businesses can now continue using it with full security updates and patches until 2024. This gives IT departments ample time to plan for the transition to newer versions of Ubuntu, ensuring that they remain aligned with the latest technologies while avoiding the risk of running unsupported software.

Enterprise adoption of Ubuntu has grown steadily in recent years, largely due to its robust performance, extensive software ecosystem, and strong security features. The extended LTS commitment is seen as a strategic effort to solidify Ubuntu’s position as the preferred operating system for enterprise environments, particularly as cloud computing and containerisation continue to shape IT infrastructures. Businesses can now choose Ubuntu with greater confidence, knowing they will receive long-term support and access to an evolving ecosystem that meets the demands of modern computing.

The Ubuntu 14.04 LTS extension also marks a response to the increasing competition in the enterprise Linux market. Companies such as Red Hat and SUSE have long been known for their strong enterprise support models, and Canonical’s move to extend LTS commitments aims to close the gap in terms of providing a comprehensive, long-term service for business clients. This expansion ensures that Ubuntu remains a competitive choice for organisations looking to build scalable, secure, and cost-effective infrastructures.

The strategic decision to focus on long-term stability also reflects the evolving needs of enterprises that prefer predictable, well-supported environments. As the tech industry continues to shift towards continuous integration and deployment pipelines, businesses still need an operating system that offers a solid foundation. The extended LTS commitment provides businesses with the confidence that they can continue using Ubuntu without worrying about the need for rapid upgrades or facing security vulnerabilities due to the lack of support.

Canonical’s commitment aligns with broader trends in the software industry where enterprises are increasingly seeking solutions that allow for lower operational costs, improved security, and reduced complexity. By supporting older versions of Ubuntu for an extended period, Canonical ensures that businesses can maintain their existing systems while benefiting from ongoing improvements in the underlying architecture and security features.

The article Ubuntu Extends Long-Term Support Commitment to Enterprises appeared first on Arabian Post.

Ente, a popular cybersecurity tool, has successfully completed a rigorous audit sponsored by CERN, the European Organization for Nuclear Research. The audit, carried out by five experts from the German cybersecurity firm Cure53, took place over the span of two weeks and focused on evaluating the platform’s security framework and vulnerability to cyber threats.

CERN, one of the largest and most advanced scientific research organisations in the world, has been a long-term user of Ente’s services, particularly for protecting sensitive data and ensuring the integrity of its systems. Recognising the critical role cybersecurity plays in safeguarding research operations, CERN voluntarily initiated the audit as part of its commitment to maintaining the highest security standards.

The audit was comprehensive, covering various aspects of Ente’s platform, from its core encryption algorithms to its overall architecture and software design. Cure53, a renowned firm with a reputation for conducting thorough security evaluations, meticulously examined the system for potential weaknesses, vulnerabilities, and security risks. The team’s objective was not only to assess the existing security protocols but also to identify any areas for improvement that could enhance Ente’s reliability in real-world applications.

According to the audit results, Ente’s security measures were found to be robust and effective. The system demonstrated a high level of resilience against known attack vectors, and no critical vulnerabilities were discovered during the evaluation process. The findings confirmed that Ente’s implementation of cryptographic techniques and data protection mechanisms adhered to best practices, making it a reliable choice for high-security environments like CERN.

The audit’s success is a significant achievement for Ente, which has been gaining traction in the cybersecurity space for its innovative approach to secure data storage and transmission. With its emphasis on encryption and user-centric security, the platform has become a trusted solution for organizations requiring cutting-edge protection for sensitive information.

CERN’s sponsorship of the audit underscores its proactive stance on cybersecurity, especially as the organization continues to push the boundaries of scientific research. Given the vast amounts of data generated by CERN’s particle experiments, the need for secure systems to protect against cyberattacks and data breaches is paramount. The successful audit of Ente provides assurance that the platform is up to the task of safeguarding this critical information.

The positive outcome of this audit also highlights the growing collaboration between leading cybersecurity firms and global research institutions. As the digital landscape becomes increasingly complex, the demand for secure systems that can withstand sophisticated threats has never been higher. CERN’s decision to sponsor the audit of Ente reflects a broader industry trend where top-tier organizations are investing in rigorous third-party evaluations to ensure the continued security of their infrastructure.

The article Ente Successfully Passes CERN-Sponsored Audit appeared first on Arabian Post.

The shift towards subscription-based streaming and the rise in unauthorised distribution is exposing fundamental flaws in how consumers acquire digital media. Many users believe they “own” films, music or books that they purchase online, but industry analysts say what they actually hold is a license to access content under strict terms and conditions. One expert writes: “Most of us don’t control the files, formats, keys and servers. We rent access dressed up as possession.”

Streaming platforms such as Netflix, Spotify and Amazon Prime Video routinely update or remove titles when licensing rights expire, effectively revoking previously purchased-content access. Research confirms this pattern: one user reported that the complete video library they had “bought” vanished when the provider shut down.

As the licensing model dominates, the notion of permanent ownership becomes ever more tenuous. A licensing economy allows service providers to rotate catalogue titles rather than guarantee indefinite access, with digital-rights management, regional restrictions and revocation rights embedded in terms of service. On the consumer side, the convenience of streaming often masks these limits. According to a global piracy study, when lawful access is timely, comprehensive and fairly priced, unauthorised access declines — but when it isn’t, illegal channels proliferate.

Analysts estimate that the online video industry loses nearly US$75 billion annually to content theft, with growth of about 11 per cent per year. The report points to subscription fatigue, escalating prices and inconsistent content availability as major drivers. Global enforcement bodies warn that pirated sports and entertainment streams now attract tens of thousands of users per event, undermining rights-holders and the business models of major broadcasters.

In specific markets such as India, digital content piracy poses a substantial drag on growth. One industry report found that the online video sector generated US$4.2 billion in 2024, yet approximately 90 million users accessed pirated content, resulting in US$1.2 billion in revenue loss. Without intervention, the study forecasts a loss of nearly US$2.4 billion and 158 million users by 2029. Anti-piracy measures could help platforms recover as much as US$1.1 billion and inject US$0.5 billion in content investment.

For global rights-holders the challenge is mounting. Piracy has evolved from file-sharing and peer-to-peer networks to sophisticated streaming devices and “fully-loaded” set-top boxes that mimic legitimate services while distributing unauthorised content. Prosecution and server takedown efforts continue, but the scale and speed of illegal distribution makes traditional enforcement increasingly costly and complex. Rights protection organisations emphasise that digital piracy flourishes when pricing is misaligned, catalogue access is restricted and enforcement slackens.

Consumers, meanwhile, face uncertainty. Purchasing a digital movie or album often grants nothing beyond the right to stream a licensed version. When platforms lose rights, restructure their service or impose region locks, previously accessible content may disappear without refund. One journalist described the experience as “my whole library is just wiped out” after a shutdown notice.

The article Ownership of Digital Content Is a Myth appeared first on Arabian Post.

The Czech-based registry operator CZ. NIC has launched its new second-generation router, the Turris Omnia NG, which incorporates swappable Wi-Fi and cellular modules alongside a lifetime automatic update policy, signalling a push towards longer-term home network hardware.

At its core the Turris Omnia NG runs a quad-core ARMv8 64-bit processor clocked at 2.2 GHz and features a passively-cooled design to deliver silent operation under heavy load. The device supports Wi-Fi 7, with the 6 GHz band rated at up to 11,530 Mbps, the 5 GHz band at up to 8,647 Mbps and the 2.4 GHz band at up to 800 Mbps. What sets it apart is that the Wi-Fi module is not soldered but mounted as an M.2 card, allowing future upgrades when new Wi-Fi standards emerge. A dedicated M.2 slot also supports 4G/5G modem modules for cellular connectivity. The WAN port can handle 10 Gbps via SFP+ or 2.5 Gbps RJ-45, while the LAN side includes one 10 Gbps SFP+ plus four 2.5 Gbps RJ-45 ports.

On the software side the router runs Turris OS, and it is advertised with a lifetime firmware update promise: unlike many consumer routers which cease updates after a few years, the Omnia NG will continue to receive automatic system updates indefinitely, at least according to the manufacturer. In the product description the firm states that this ensures the home remains protected from emerging threats over the full lifespan of the device.

The introduction of swappable modules reflects a growing trend in hardware design geared towards sustainability and flexibility. By allowing the Wi-Fi board to be upgraded independently of the router chassis, the device aims to avoid obsolescence when new wireless standards are introduced. Similarly, the cellular expansion slot enables users to add backup internet connectivity or primary mobile broadband without requiring a separate router. Such modularity could be particularly appealing to tech-savvy users, small offices or homes with high demands on connectivity and security.

However, the approach does come with trade-offs. The price tag is reported to start at around €520, before taxes and shipping, which places it at a premium compared with many mainstream consumer routers that cost a fraction of that amount. Some users have also flagged compatibility issues; one review noted that the SFP modules sold by a fibre provider required forced negotiation to work with the original Turris Omnia model, adding a layer of complexity for end users. While the lifetime update promise is compelling, manufacturers’ long-term support commitments have come under scepticism in the past, so users may want to verify firmware-update policies and community support over time.

Security-wise the Turris line has offered features such as a distributed adaptive firewall: devices in the network feed threat-data into a shared system so that once one device detects an attacker, a signature is distributed to other devices within minutes. This level of integrated network protection remains atypical in consumer routers and adds value for users concerned about cyber-threats. The passive cooling and rack-mount capability also position the device as viable for compact server-room or SOHO environments, rather than just typical living-room Wi-Fi use.

From a marketing standpoint CZ. NIC is tapping into a niche of advanced users who place high value on longevity, upgradeability and open-source flexibility. The router’s open-source foundation and support for virtualization broaden its appeal beyond plug-and-play home networks into small server or self-hosted cloud use-cases.

The article Modular Upgrade Router Promises Lifetime Security appeared first on Arabian Post.

A significant security breach involving the open-source extension registry Open VSX Registry and maintained by Eclipse Foundation has exposed a vulnerability in the software-supply-chain ecosystem. Developer tokens that grant publish permissions were unintentionally made public, enabling threat actors to upload malicious extensions and target developers using the platform.

Security researchers from Wiz flagged more than 550 exposed secrets within public repositories, among which tokens belonging to Open VSX accounts were identified. The leaked tokens permitted unauthorised actors to publish or update extensions on the registry, raising alarms about the integrity of code distribution in the developer community.

The Eclipse Foundation’s response confirms that the root cause was human error—developers inadvertently committed tokens to public version-control systems—rather than a breach of Open VSX’s underlying infrastructure. Once identified, the tokens were revoked and all impacted extensions were removed from the registry.

One malware campaign tied to this incident has been termed “GlassWorm” by researchers at Koi Security. This operation used the compromised tokens to publish malicious extensions that appear benign at first, then target developer credentials and infrastructure. Despite the name, Open VSX says this campaign did not propagate autonomously like a classic worm, but required credential compromise to expand. Among the affected packages was one disguised as a popular Solidity-language extension, carrying a backdoor invoking Ethereum smart-contract functionality to deliver remote access capabilities.

Download figures circulating in the investigation suggest around 35,800 installs of the suspect extensions, but the registry maintainer cautions that the figure includes inflated counts generated by bots and visibility-manipulation tactics. Because of this, the actual user-impact is likely lower than the headline figure suggests.

In response to the incident, the Eclipse Foundation and Open VSX have enacted a number of security enhancements. Tokens issued for publishing now include a distinct prefix to enable easier detection of exposed credentials in public repositories, implemented in collaboration with Microsoft Security Response Center. Default token lifetimes have been reduced and a streamlined revocation process established to limit the risk exposure window. Automated security scanning of extensions will now run at publication time, enabling earlier detection of malicious code patterns. The registry is also enhancing partnerships with other marketplace operators to share threat intelligence and best practices for extension security.

Beyond the immediate fixes, the incident underscores a broader trend in the software-supply-chain domain: extensions, libraries and plugins represent high-leverage targets for adversaries seeking access to developer environments. Academic work has shown that extension ecosystems can leak credentials, and that a non-trivial share of extensions suffer from data-exposure risks. The decentralised nature of community-driven registries, while enabling innovation, may leave governance and security oversight less robust than enterprise-grade centres.

For development teams and organisations relying on extensions from Open VSX, steps such as verifying publisher authenticity, auditing extension behaviour and integrating secret-scanning tools in CI/CD pipelines are increasingly critical. The incident signals that, even when upstream infrastructure is well maintained, operational practices—especially around token management—remain a primary vector for exploitation.

The article Registry Token Leak Exposes Open VSX Supply-Chain Weakness appeared first on Arabian Post.

The Linux distribution Pop!_OS 24.04 Long-Term Support Beta from System76 introduces a ground-up rewrite of its desktop environment and enhanced hardware support, while still leaving some features unfinished and cautioning users about its beta status.

Built on the foundation of Ubuntu 24.04 LTS, Pop!_OS 24.04 adopts the new Rust-based COSMIC desktop environment, moving away from the GNOME-derived shell used in previous releases. System76 describes the transition as a bid to provide a modern, memory-safe, and highly customizable desktop experience. Key elements of the redesign include native Wayland support, per-application GPU assignment, and an integrated auto-tiling window manager.

One of the strongest enhancements in this release is the overhaul of hybrid-graphics management. For laptops equipped with both integrated and discrete GPUs, Pop!_OS 24.04 now allows users to switch between iGPU, dGPU or hybrid modes through a graphical interface, and assign discrete GPU usage to specific applications. These capabilities have been framed as a long-standing pain-point for Linux desktops.

The OS includes updated components aimed at improved compatibility and performance. For example, in the beta build the kernel is reported to be version 6.16, Mesa graphics stack version 25.1.5 and the NVIDIA driver version 580 for systems with NVIDIA GPUs.

On the desktop environment front, COSMIC brings its own native apps—such as COSMIC Files, COSMIC Terminal, COSMIC Edit and COSMIC Player—alongside a redesigned app-store experience via COSMIC Store. Customisation features include theme import-export, configurable panel and dock layouts, workspace orientation options and advanced window tiling and stacking.

Despite the ambition, reviewers underscore that this build remains a beta and some stability issues persist. A review of the alpha stage observed disk usage near 7GB and 1.4GB RAM at idle, as well as incomplete settings pages and some early UI alignment glitches. In the wider community, beta users report mixed results: one noted that “the whole system is just swamped with CPU 100% and is jittery on the graphical side” when used on a laptop with an NVIDIA 1060 GPU.

For existing Pop!_OS 22.04 users the upgrade path is supported but comes with caveats. Community feedback indicates dock favourites may not migrate, third-party PPAs may get disabled during upgrade and some users opted for clean installs to avoid configuration conflicts.

In terms of positioning in the Linux ecosystem, this iteration of Pop!_OS is pitched squarely at power users, creative professionals and gamers who demand GPU flexibility, workspace efficiency and hardware optimisation out-of-the-box. Its hybrid-graphics enhancements and native tiling support mark meaningful differentiation from many peer distributions. On the other hand, users seeking a completely polished, stable daily driver may find certain rough edges—particularly relating to early CUDA/Wayland support or migration hassles.

The article Pop!_OS 24.04 LTS Beta Offers Major Desktop Overhaul with Some Rough Edges appeared first on Arabian Post.

A new entrant to the Linux desktop space, the distro known as NebiOS, has been unveiled by Turkish developer Sarp Mateson under the umbrella of his company NebiSoft. Built on the foundation of Ubuntu and tailored for Wayland graphics instead of the older X11 system, NebiOS marks a distinct shift in how independent desktop Linux distributions are conceived and delivered.

Mateson’s project began as a personal experiment in 2023 and has since evolved into a fully fledged operating system with its own desktop environment, dubbed NebiDE. According to his statement, NebiDE was “built from the ground up for Wayland”, emphasising a modern graphics architecture rather than backward-compatibility with legacy protocols. The upcoming release, named NebiOS X “Cappadocia” and based on Ubuntu 24.04 LTS, is slated for public availability on 1 November 2025.

The architecture of NebiOS centres on kernel 6.14 with NTSYNC support as well as integrated indicators for privacy and Bluetooth battery status in the top panel. Mateson positions the product as suitable not only for everyday use but also for creative and gaming workloads, touting the “container-based architecture” and tooling support optimised for developers and gamers alike. The official website highlights ecosystem features such as a NebiCloud file service and a NebiSoft Location Services platform for apps, signalling ambitions beyond a simple desktop OS.

That said, early hands-on reviews signal mixed impressions. In a virtual-machine test, reviewers noted lag and visual glitches—though they attributed those issues to the VM environment rather than the OS itself. The installer is the familiar Calamares toolkit, easing adoption for users familiar with Ubuntu-based systems. The desktop layout uses a Windows-7–style button placement and incorporates widgets for music, RSS and sticky notes; users appreciated the familiarity but flagged rough edges in display resolution settings and icon scaling.

The distro’s ambitions are bold: while there have been many Ubuntu derivatives, fewer have introduced a wholly new desktop environment optimised for Wayland. This places NebiOS in a somewhat niche category—straddling between mainstream distributions like Ubuntu, Fedora or openSUSE and more specialist projects. Its independence from canonical UI frameworks could appeal to users seeking something fresh; however, it also raises longer-term questions about ecosystem support, driver compatibility and maintenance frequency.

In terms of trends, NebiOS reflects the broader momentum around Wayland adoption in Linux environments. Major distributions have been gradually shifting away from X11 as the default graphics system amid hopes of improved security, smoother rendering and better multi-monitor support. Nevertheless, many users still face compatibility issues—desktop-environment developers caution that Wayland is not yet a universal replacement for all workflows. NebiOS’s alignment with Wayland thus places it at the leading edge of that transition, but also potentially among the earlier risers in the risk-zone of growing pains.

Turning to the market and community dynamics, the key players are numerous: core Ubuntu maintainers, desktop-environment projects, Wayland compositor developers and hardware-vendor driver teams. NebiSoft is operating as a smaller, independent actor—meaning its success may hinge on whether it can build sufficient community engagement, maintain timely updates and ensure compatibility with major applications and games. Early reviews note that standard productivity apps run out of the box, but for day-one gamer readiness and hardware optimisation the distro will need to demonstrate depth of testing and driver support.

In interviews with users exploring NebiOS, the appeal of a “fresh feel” without the corporate skin of larger distros comes through strongly. One tester observed: “There are cool pre-configured widgets … this reminds me of a simpler time,” while cautioning that “on a virtual machine I saw lag and visual glitches” and noting the resolution change workflow felt clunky.

The article Fresh Ubuntu-based Distro NebiOS Launches With Its Own Wayland Engine appeared first on Arabian Post.

The Free Software Foundation has unveiled an ambitious new project aimed at transforming mobile computing. Named the “Librephone,” this initiative goes far beyond typical Android modifications, focusing instead on creating a fully open-source, privacy-respecting mobile ecosystem. It seeks to address growing concerns over data privacy and surveillance, marking a pivotal moment in the ongoing debate about control in the mobile space.

At the heart of the Librephone project is the drive to liberate mobile technology from the proprietary systems that dominate the market. FSF has long been a proponent of free software and the principles of open-source development. With smartphones becoming ubiquitous, the foundation sees a unique opportunity to challenge the status quo and offer an alternative to users who are increasingly wary of corporate influence and invasive data practices.

The Librephone will not merely be an Android fork. While many open-source projects have attempted to modify Android to make it more privacy-friendly, FSF aims to create a complete open-source mobile operating system. By doing so, it ensures that users retain full control over the software running on their devices. This includes everything from the underlying kernel to the apps and services that interact with the phone’s hardware. It promises a phone where users can see and modify the entire stack of software, without relying on closed systems or proprietary software.

Security and privacy are paramount in the Librephone’s design. The FSF’s vision goes hand in hand with its broader mission to reduce the control of large tech companies over personal data. Modern smartphones often collect vast amounts of user information, from location data to browsing habits, which can be accessed by both manufacturers and third-party companies. FSF’s open approach to mobile technology intends to put users back in control, ensuring that their personal information is secure and that they are not at the mercy of corporate interests.

While the project remains in its early stages, FSF has already secured partnerships with several hardware manufacturers who are interested in supporting open-source initiatives. This collaboration is critical, as the Librephone project requires more than just software development; it needs a dedicated hardware infrastructure to match. FSF aims to create a hardware-software ecosystem that respects user autonomy, in stark contrast to the closed-off models that currently dominate the market.

Unlike its predecessors, which often relied on using alternative operating systems like Ubuntu or Replicant, the Librephone will be built from the ground up. FSF has stressed that the Librephone will integrate with modern smartphone hardware, ensuring that it doesn’t compromise on performance. This is a key difference from many earlier efforts that often struggled with hardware compatibility or lacked the functionality users expect from a modern mobile device.

One of the more intriguing aspects of the Librephone project is its potential to redefine the concept of “mobile freedom.” The project is about more than just replacing proprietary software; it is about reshaping how we think about mobile devices. With the increasing reliance on mobile phones for both personal and professional tasks, the FSF aims to offer a phone that allows users to not only control their data but also contribute to the development and improvement of the phone itself.

The Librephone is positioned to attract a niche but growing audience: users who prioritize privacy and autonomy over convenience. These users are already familiar with the limitations of proprietary operating systems and are seeking alternatives that offer greater transparency. FSF is betting that this segment will grow as more individuals become disillusioned with the current state of mobile technology and the data practices of major corporations.

The FSF’s initiative has the potential to spark a broader conversation about the ethics of mobile technology. As the tech industry faces increasing scrutiny over data privacy issues, the Librephone could serve as a powerful example of how open-source principles can be applied to areas previously dominated by closed ecosystems. This project aligns with the growing movement towards decentralization and user autonomy, which is expected to gain further momentum in the coming years.

The article Free Software Foundation Drives Bold Initiative with Librephone appeared first on Arabian Post.

ONLYOFFICE Docs 9.1 has been launched, bringing with it a significant overhaul aimed at boosting both productivity and collaboration. Among its notable additions is a new set of PDF redaction tools, enabling users to efficiently remove sensitive content from documents, as well as various editor upgrades that promise to streamline workflows.

The introduction of PDF redaction tools addresses growing concerns around privacy and data security, allowing users to permanently delete text and images from PDF files. This update is especially crucial for professionals in legal, healthcare, and financial sectors where confidential information must be carefully managed. The tools ensure that redacted content is fully removed, leaving no trace that could potentially be recovered or exposed.

Another highlight of ONLYOFFICE Docs 9.1 is the improvement in performance across its suite of applications. The software is designed to handle larger documents with more ease, significantly reducing the load times and enhancing user experience when dealing with complex files or multiple users accessing documents simultaneously. These upgrades are part of a broader initiative to refine the software’s functionality, making it more suitable for both individual users and businesses with demanding needs.

Collaboration features have also been strengthened in this release, with the inclusion of enhanced real-time editing and commenting capabilities. The new updates ensure that team members can work on documents concurrently without experiencing lag, with changes appearing instantly across all devices. The ability to track edits and leave detailed feedback within documents is set to improve team communication, making ONLYOFFICE Docs a more robust tool for collaborative work environments.

In addition to these key updates, the release also introduces a more streamlined user interface, making it easier to navigate between tools and features. The updated layout allows for quicker access to commonly used functions, thereby improving overall efficiency. This is especially beneficial for organisations that rely on fast-paced, continuous workflows where time-saving is crucial.

The 9.1 version’s focus on security extends beyond PDF redaction. The software now offers enhanced encryption for cloud-based files, ensuring that documents remain secure when shared across the internet. This added layer of protection is particularly relevant in today’s increasingly digital workplace, where data breaches and cyber threats are constant concerns for businesses of all sizes.

For those looking for seamless integration, ONLYOFFICE Docs 9.1 further improves compatibility with other major office suites, making it easier to collaborate with clients or colleagues who use different platforms. The software supports a wide range of file formats, ensuring that documents can be opened, edited, and saved without issues, regardless of the tools others may be using.

The update to ONLYOFFICE Docs 9.1 also takes into account user feedback, incorporating changes that reflect the needs of businesses and organisations. The ability to customise the toolbar and interface to better suit individual preferences is another feature aimed at improving the user experience.

The article ONLYOFFICE Docs 9.1 Enhances PDF Editing and Collaboration Features appeared first on Arabian Post.

A public beta of Zorin OS 18 has been launched, offering a reimagined interface and a suite of tools aimed at easing the migration from Windows as support for Windows 10 ends on 14 October 2025. The developers position this release as a compelling alternative for PCs that don’t qualify for Windows 11, while businesses, schools and individual users explore paths away from Microsoft’s ecosystem.

The new beta introduces a floating, rounded taskbar style and a lighter theme across system apps to modernise the user experience. A revamped window-tiling system allows users to drag and snap windows into layouts or set up custom presets — features designed to appeal to those accustomed to Windows’ Snap behaviour. The desktop redesign comes with enhanced multi-monitor support, a reactive workspace indicator, and refinements to default app interfaces.

Under the hood, Zorin OS 18 is built upon Ubuntu 24.04.3 LTS and uses Linux kernel 6.14, which broadens hardware compatibility for newer devices. The distribution now enables PipeWire by default to improve audio performance with lower latency, especially over Bluetooth connections.

One of the most notable additions is native OneDrive integration: signed-in Microsoft 365 users can browse and manage cloud files directly within the Files app via the Online Accounts tool. The system also offers a Web Apps utility, allowing any website to behave like a desktop app, which helps bridge reliance on web-based services such as Office 365, Google Docs or Teams. To assist users migrating from Windows, the beta version scans for Windows installer files and suggests native or web-based equivalents within Zorin.

The development team emphasises long-term support, committing to software security and stability updates through April 2029. It is expected that upgrades from Zorin OS 17 will be enabled once the final stable build is released. Meanwhile, Zorin maintains its “release when ready” policy and has not yet confirmed a precise launch date beyond the indicated second half of 2025 window.

The beta’s arrival coincides with the termination of support for Windows 10, a milestone that leaves an estimated 240 million devices unsupported by Microsoft’s updates. Zorin’s branding leans hard into this moment, positioning OS 18 as a transition path for users whose machines are incompatible with Windows 11.

Analysts of Linux and open-source ecosystems say Zorin’s strategy mirrors that of other “Windows-friendly” distributions — combining visual familiarity, migration tools, and cloud integration to reduce switching friction. But some observers caution that the scope of support and stability in the release candidate will matter greatly. A preview from one open-source commentary warns that while layout switching and performance gains are impressive, the full system stability of core apps under real-world workloads must be proven.

In the user community, responses are cautiously optimistic. Some praise the streamlined user experience and Microsoft-style transitions, while others note caveats: the beta label implies unfinished elements, and critics say migration aids will have limits when proprietary or niche Windows software is involved. Zorin’s pro version is expected to include additional desktop layouts and design themes as part of its paid offering.

The article Zorin OS 18 Beta Unveils Windows-Friendly Pipeline to Post-Windows 10 Era appeared first on Arabian Post.

NordVPN has released the full source code for its Linux graphical user interface and reversed its earlier decision to discontinue its Meshnet feature—moves that mark a shift in strategy toward openness and community engagement.

The VPN provider published the GUI code under an open-source licence and made it available on GitHub, complete with build instructions. At the same time, it announced that Meshnet, once slated for shutdown on 1 December 2025, will remain active and supported, with plans to open-source it in due course.

By opening up the Linux GUI, NordVPN aims to invite contributions and scrutiny from the community, allowing users to inspect, modify or improve the client. The company noted that while the graphical tool is now open-source, its core VPN infrastructure—including authentication and server operations—remains proprietary to preserve security and stability. The GUI is now also distributed via the Snap package, simplifying installation and updates across Linux distributions.

The decision to reverse Meshnet’s retirement comes after the company faced strong backlash from its user base. Meshnet lets users securely interlink up to 60 devices, enabling file sharing, private tunnels, and even LAN-style gaming connectivity. NordVPN had justified the planned discontinuation by citing low adoption—reportedly only about 1 per cent of users employed the feature—and high ongoing maintenance costs. Yet the volume of user feedback underscored how valued the tool was by its dedicated adopters.

“After announcing the Meshnet shutdown, we received feedback from our users in many forms… their stories made it clear how valuable it was to them. That perspective made us reconsider our decision, and ultimately, we’ve decided to keep it,” said Marijus Briedis, NordVPN’s chief technology officer.

In its announcement, NordVPN admitted that Meshnet had not achieved mass traction, but emphasised that its value extended beyond raw numbers. The company now plans to keep developing Meshnet while investigating ways to reduce resource overhead and expand its appeal. The open-sourcing of the feature is expected to spark third-party development and innovation.

Industry observers see the moves as an attempt by NordVPN to reorient its product philosophy. By leveraging open-source principles, the company can build greater trust among technically minded users—even as it retains control over critical backend systems. Enabling community involvement in GUI and Meshnet development might also help reduce internal burdens over time.

Competitive VPN services have varied in their approach to openness and modular tools. Some providers restrict even client-side code, while others adopt open standards for subcomponents. NordVPN’s approach—open-sourcing user-facing layers while maintaining proprietary control over sensitive infrastructure—suggests a hybrid path intended to balance transparency and security.

Analysts say the decision may help NordVPN lock in niche users who care deeply about transparency, particularly within the Linux community. But challenges remain in making Meshnet more broadly appealing: its complexity, niche utility, and the engineering cost of supporting cross-platform interconnectivity are nontrivial hurdles.

The article NordVPN’s Linux GUI Goes Open Source as Meshnet Shutdown Is Reversed appeared first on Arabian Post.

Organisers have confirmed that Bengaluru will host India’s inaugural UbuCon conference on 15–16 November at the Indian Institute of Science. The event is expected to bring together developers, contributors and Ubuntu enthusiasts from across the country to engage on topics spanning cloud, IoT, documentation and AI.

The Ubuntu India LoCo group leads the organisation, emphasising the grassroots, volunteer-driven nature of UbuCon events. Unlike many conferences dominated by corporate agendas, UbuCon is conceived as a community platform for knowledge sharing, collaboration and local ecosystem building.

Attendees will see sessions on desktop environments, infrastructure, open source tooling and project contributions. The organisers say that the event aims not just to showcase Ubuntu developments but to galvanise a domestic Ubuntu-oriented community. Early bird, student and standard passes are listed via a registration portal to manage participation.

Ubuntu Weekly News describes UbuCon India as part of the Ubuntu ecosystem’s global conference schedule. The newsletter notes that UbuCon India 2025 is scheduled for Bengaluru and includes references to the registration and event details. Meanwhile, the Ubuntu community website confirms that UbuCon gatherings are volunteer-led regional events that bring together Ubuntu teams, users and organisations.

In prior years, UbuCon Asia has been held in Kathmandu, offering a template for regional engagement with the wider Ubuntu community. That Asia edition focused on bringing together engineers, creators and contributors across national boundaries to explore Ubuntu’s role in education, infrastructure and applications.

Organisers in India aim to replicate that cross-border spirit on a national scale, creating connections between hobbyists, professionals and academics. Inside the Ubuntu community, a growing interest in contributions from countries beyond the traditional core has gained traction. The India LoCo’s push is viewed as part of broader decentralisation, encouraging local events, translation efforts, regional infrastructure and community outreach.

One of the challenges in India will be to ensure sustained momentum after the two-day event. Ubuntu contributors often struggle with coordination across time zones, sparse resource allocation, and volunteer burnout. The LoCo group has said it plans follow-up meet-ups, hackathons and contributor mentoring to build on the conference’s momentum.

Speakers are expected from both within India and internationally; proposals for talks are reportedly open to the community. The organisers emphasise inclusivity, inviting both seasoned and new participants without imposing steep barriers to entry.

The article Ubuntu Community to Host India’s First UbuCon in Bengaluru appeared first on Arabian Post.

A compact, hackable AI assistant designed for privacy-conscious users is now drawing attention as the latest challenger to Big Tech’s voice assistants. Built around the Raspberry Pi, Ubo Pod aims to give users full control over their data, local compute, and software customization.

Ubo Pod’s lead designer, Mehrdad Majzoobi, positions it as a protest against closed-box “smart” assistants whose voice and camera data typically funnel through cloud servers. The device runs on Raspberry Pi 4 or 5, and users can host AI processing locally, opt for hybrid cloud setups, or connect to external LLMs of their choice.
The hardware includes a 1.54-inch colour TFT display, dual microphones, stereo speakers, a built-in 5MP camera, a seven-button keypad, RGB LED ring, infrared transmitter/receiver, ambient light and temperature sensors, and a physical microphone kill switch. On the software side, Ubo Pod supports over 50 AI service providers across speech-to-text, text-to-speech, vision and language models, while exposing a gRPC API for developers to build modular assistants.

The project is currently live on Kickstarter, with pledges open until early November. Backers can choose between Ubo Pro 4 and Ubo Pro 5 starter units, starting at US$109 and US$129, respectively. The campaign’s goal is $25,000, and delivery is slated between December and March.

In design philosophy, Ubo Pod draws comparisons to past open-source voice assistants like Mycroft, which processed commands locally to minimise cloud reliance. Mycroft’s development was stymied by a patent-related lawsuit in 2023, after which community forks like OpenVoiceOS continued development. Ubo’s differentiator is modular hardware and software, enabling users to upgrade individual components without discarding the whole device. Majzoobi emphasises repairability and reuse, suggesting some parts could be 3D printed by users.

Privacy is central to Ubo Pod’s proposition. Its hardware design includes a camera curtain and microphone disconnect switch as physical safeguards. Users who run models locally can ensure that voice data never leaves the device. Majzoobi has argued in his blog that proprietary assistants position themselves as black boxes—making verification of privacy claims difficult—and that Ubo is built to make every aspect inspectable.

Yet Ubo Pod faces challenges. Running advanced AI models locally requires substantial compute resources; while Ubo supports external AI accelerators on the Pi 5 setup, not all users will opt for—or afford—such hardware. Performance, energy consumption, latency and heat management remain technical hurdles for edge AI platforms.

Also, competing ecosystems are advancing. Some voice assistant platforms now offer hybrid models—local inference for privacy-sensitive tasks, cloud fallback for heavy computation. Ubo will need to balance flexibility with user convenience. Further, ensuring security across modular hardware and extensible APIs is critical; any vulnerabilities in third-party modules or extensions could undermine the privacy promise.

The article Ubo Pod Offers DIY Alternative to Big Tech Assistants appeared first on Arabian Post.

The state of Schleswig-Holstein has successfully migrated its entire public administration email infrastructure from Microsoft Exchange and Outlook to open source platforms. Over the course of six months, more than 40,000 mailboxes—holding in excess of 100 million emails and calendar entries—were transferred to Open-Xchange and Thunderbird, covering roughly 30,000 employees across ministries, judiciary, police and other agencies.

Dirk Schröder, the state’s minister for digital affairs, framed the move as a pivotal step toward “digital sovereignty”, arguing that it reduces dependence on large tech companies and boosts transparency and control over IT infrastructure. Earlier phases of the state’s open source agenda had rolled out LibreOffice as the standard office suite. With the email migration now complete, plans are underway to phase out Microsoft Office entirely and replace Windows with open source operating systems such as Linux. The state also intends to substitute Microsoft SharePoint with Nextcloud for collaboration and adopt open source telephony and video conferencing platforms.

The heimliciNor Schleswig-Holstein is not the first German state to explore open source transitions, but the scale and comprehensiveness of this project have drawn attention. Analyses in tech policy circles now view it as a benchmark for public sector IT reform in Europe. Critics and observers note that although the objectives are ambitious, the process has exposed gaps in planning, stakeholder engagement, and practical resilience.

Police unions have voiced sharp criticism of the implementation. Torsten Jäger, head of the Schleswig-Holstein branch of the German Police Union, described the rollout as “disastrous,” warning that critical information may have been lost and asserting that the transition was rushed. Meanwhile, senior judicial bodies raised alarms about disruptions in court operations and subpoenas when email access lagged or failed altogether. In response, Schröder issued formal apologies to staff in a letter, acknowledging that the scale and complexity of the migration imposed heavy burdens on users.

At a session of the Schleswig-Holstein Landtag, the FDP parliamentary group led calls for stronger oversight and better communication from the digital ministry. Lawmakers cited lengthy periods during which judges reportedly lacked access to their mailboxes and police stations that were effectively cut off from vital digital systems. The FDP proposed a motion demanding a more user-centred approach, insisting that employees be consulted and fully supported—through training, interface optimisation and contingency mechanisms.

Proponents argue the state’s bold approach is now yielding informational returns: having complete control over software stacks enables more agile adaptation to local needs and security strengthening. The government has already committed to sharing its migration tools and experiences with other states and public institutions, positioning Schleswig-Holstein as a de facto standard-setter in open source governance.

Still, technical challenges persist. Users report latency in mailbox syncing, occasional outages, and hurdles in archiving judicial records in compliance with archival law. State officials say a dedicated task force has been assembled to monitor performance, resolve bugs, and stabilise delivery. They emphasise that the first weeks of operation remain a stress test of the system’s robustness.

The article Schleswig-Holstein Completes Full Open Source Email Switch appeared first on Arabian Post.

Xogot has extended its reach: the full Godot engine can now run natively on iPhone, allowing developers to build, edit, test and export games entirely from their pocket.

Xogot, developed by Xibbon Inc., launched for iPad earlier in 2025, and its iPhone version is built upon Godot 4.4 with a rewritten user interface in SwiftUI, tailored for touch and smaller screens. The app supports both 2D and 3D development, integrating the Godot runtime so projects remain compatible with desktop workflows.

This upgrade introduces Xogot Lite, a free tier with constraints on project size, active projects and certain advanced settings, alongside a Pro version offering full features. Pricing for Pro is available via monthly, annual or lifetime licences.

The iPhone release brings core Godot tools to mobile: tile map editors, animation panels, scripts, and embedded preview with debugging are all intact. Accompanying features include the Jolt physics integration for 3D simulation, a Metal rendering backend optimised for Apple hardware, and Camera3D preview tools.

Xogot ensures seamless round-trip compatibility: projects created or edited on iPhone or iPad can be opened in Godot on desktop and vice versa. Imports via iCloud, USB or GitHub are supported.

Co-founder Miguel de Icaza emphasised that enabling mobile development addresses a gap in creative tooling: whereas music and visual arts already have mobile professional apps, game development remained desktop-bound. He noted that adaptation to touchscreen and small displays was one of the biggest challenges in the project.

Joseph Hill, co-founder, pointed out a growing interest among educators and indie developers: with iPhone support, development can continue outside formal studio settings, during commutes or in casual environments. Students participating in game jams may also benefit through time-limited free access to Pro features.

Although Xogot uses Godot’s open source runtime, the app itself is not open source.

The article Godot Now Runs Natively on iPhone via Xogot appeared first on Arabian Post.

Wikimedia Deutschland has introduced a new vector database designed to make Wikidata’s knowledge graph directly usable by AI systems. The initiative, known as the Wikidata Embedding Project, aims to convert structured facts into vector representations so that large language models and related AI tools can conduct semantic queries grounded in verified data.

Under this system, the 119 million or more entries of Wikidata are embedded into high-dimensional vectors using a model developed in collaboration with Jina. AI. Those vector embeddings are hosted on DataStax’s Astra DB, which is serving as the scalable backend. The data snapshot currently captures Wikidata information up to September 18, 2024; while new entries made after that date are not yet incorporated, minor edits are unlikely to disrupt the vector representation as the embeddings encode a general “idea” of each item.

The key innovation lies in replacing or augmenting the traditional use of SPARQL and keyword searches with semantic similarity methods. AI systems can now issue natural-language queries and retrieve contextually related items, rather than relying solely on exact-match lookups—a shift intended to reduce hallucinations and improve traceability of AI output. The embedding infrastructure supports the Model Context Protocol, enabling better alignment between AI models and vector databases.

The project currently supports English, French, and Arabic, with further language support planned. Among its intended use cases are fact-checking, entity disambiguation, zero-shot classification, and hybrid search models combining graph reasoning with vector retrieval. Wikimedia is hosting a webinar for developers interested in integration and feedback is being solicited for future updates.

Wikidata has long been a backbone of Wikimedia’s open knowledge ecosystem. It is a collaboratively edited multilingual knowledge graph that feeds into other projects such as Wikipedia and makes structured data available under a public domain license. The challenge for AI systems has been that while the data is machine-readable, it has not always been formatted in ways optimal for semantic or generative AI workflows. The new embedding layer bridges that gap.

Philippe Saadé, the project’s AI manager, emphasises the goal of providing fair access: “This Embedding Project launch shows that powerful AI doesn’t have to be controlled by a handful of companies,” he said, underscoring the project’s open ethos. Lydia Pintscher, Wikidata Portfolio Lead, describes the move as a step toward more trustworthy, transparent AI founded on verifiable data.

The article Wikidata Unveils Open Vector Database for AI Use appeared first on Arabian Post.

openSUSE Project has rolled out the beta of Leap 16, marking a substantial shift in its Linux distribution strategy by extending community support to 24 months and introducing core architectural changes. The transition signals a deliberate move toward modernization and longer-term stability for users.

Leap 16’s codebase is now aligned with SUSE Linux Enterprise 16 and built atop the SUSE Linux Framework One. The beta ships with the 6.12 kernel, GNOME 48, KDE Plasma 6.3.4, and default SELinux enforcement, while maintaining AppArmor as an option. Leap 16 demands hardware supporting x86_64-v2, leaving older 64-bit systems unsupported.

One of the boldest changes is the complete retirement of the traditional YaST stack within Leap. YaST has served as the installer, configuration tool, and system manager for two decades. In Leap 16, Agama becomes the default installer, while Cockpit assumes system management duties and Myrlyn replaces YaST’s software GUI frontend. The removal of YaST from Leap has prompted debate over its future role in the SUSE/openSUSE ecosystem.

The beta also highlights repository and package-management improvements. Leap 16 adopts RIS-based repository layout, splitting metadata by architecture to reduce overhead. An experimental parallel package download feature in Zypper aims to speed installation and updates.

Under the new support structure, each Leap 16 release is slated to receive 24 months of community maintenance and security updates, meaning the Leap 16 line could extend through version 16.6 in Fall 2031. The shift marks a departure from Leap’s previous cycle, which offered roughly 18 months of lifetime for each minor release. To accommodate this, the support window for Leap 15.6 was extended, ensuring a six-month overlap between versions.

The beta phase anticipates a release candidate by July and full general availability in October 2025. This timeline allows users a scheduled path to transition while allowing developers to test and polish core changes.

The hardware requirement of x86_64-v2 raises concerns for users who run older machines. Community forums note that those systems will be left behind unless they adopt Tumbleweed, openSUSE’s rolling-release branch, which remains more forgiving for legacy hardware. Meanwhile, the dropped SysV init further signals a move toward modern service design; legacy init support is now absent.

Community responses are mixed. Many longtime users express nostalgia for YaST’s flexibility and are cautious about depending entirely on Agama, Cockpit, and Myrlyn. Some contributors speculate that YaST components stored in GitHub may be maintained independently, but that it will no longer be part of Leap’s default package set.

Despite the transitions, openSUSE emphasizes that upgrade paths from Leap 15.6 will be supported. Users may perform in-place upgrades via zypper dup –releasever 16.0 or migrate from Leap Micro, with guidance on repository management and fallback strategies. Documentation suggests disabling unsupported third-party repositories before upgrading to reduce system conflicts.

The article openSUSE Leap 16 Unveils 24-Month Support With Modern Overhaul appeared first on Arabian Post.

Eric S. Raymond, one of the foundational figures behind the Open Source Initiative, has called for a wholesale rejection of codes of conduct in open-source communities, characterising them as counterproductive. His outspoken position has revived a heated debate over governance, community norms and enforcement in open software ecosystems.

Raymond argues that codes of conduct, designed to promote civil discourse and inclusion, have become tools for disruption and “power plays” by what he terms “shit-stirrers.” He urges developers to refuse adoption of new codes and to eliminate existing ones, or at most replace them with a single principle: “If you are more annoying to work with than your contributions justify, you’ll be ejected.” Raymond maintains that fleshed-out rules merely provide leverage for bad actors to weaponise.

This polemic has already drawn support from other prominent critics. David Heinemeier Hansson, the creator of Ruby on Rails, described strict codes like the Contributor Covenant as Trojan horses that erode autonomy. Their combined critique has gained traction following turmoil in RubyGems governance, which re-energised discussion on the balance between regulation and freedom in project communities.

Supporters of codes of conduct counter that they remain vital for safeguarding underrepresented groups and curbing harassment. Many large open-source projects, including the Linux kernel and Fedora, maintain policies on acceptable behaviour, reporting procedures, and consequences for violations. Proponents assert that without explicit guidelines, vulnerable contributors may be deterred from participating.

A more moderate strand of thought suggests a middle path: adopt lightweight, context-sensitive norms rather than sweeping, detailed codes. Critics of rigid enforcement argue that a one-size-fits-all approach ignores the diversity of projects, sizes and cultures. As one blogger put it, extensive codes often become “weapons turned inward” when used against dissenters rather than as shields against abuse.

Technical researchers are also exploring how to automate conduct enforcement without heavy institutional framework. A 2025 study proposed a bot-based model that helps OSS projects define, monitor, and enforce a Contributor Covenant–style code. The system aims to reduce overhead while maintaining a consistent ethical baseline. The authors acknowledge the difficulty of interpretation and adaptivity, noting that bots can only flag potential violations, not adjudicate nuance.

The emerging schism reflects deeper tensions over authority, community and the evolution of open source governance. For decades, the ethos “show me the code” seated meritocracy and technical contribution as the primary arbiter. As projects scale and diversify, social norms and behavioural expectations have become increasingly salient. Raymond’s position reopens the question of how—or whether—to formalise them.

The article Open-Source Pioneer Urges Scrapping Conduct Codes appeared first on Arabian Post.

Calibre version 8.11.1 now includes an “Ask AI” tab inside its e-book viewer, enabling users to highlight text and query artificial intelligence models for summaries, context or explanations of the selected passage. The feature remains entirely optional — no AI modules are loaded unless a user configures a provider.

The new capability supports a broad spectrum of AI models, including cloud services and locally hosted models via frameworks like Ollama. Developers emphasise that the integration is modular: the core software does not incorporate any AI routines until users explicitly enable a provider.

Alongside the AI addition, 8.11.1 brings several refinements and bug fixes. The e-book viewer now handles highlights more robustly, resolves duplication during edits, ensures footnote popups close with the Esc key, and corrects selection handle placement when modifying existing annotations. On Windows, very large e-books that previously omitted some internal links now restore full link functionality. Additional fixes address malformed PDB input files, resolve issues in the icon-rule tool in Tag Browser, and improve preference tooltips to show keyboard shortcuts. The Windows build has also extended DLL signing to include. pyd files. The update further refreshes news-source integrations such as The New York Times, The Economist, El Diplo, and New York Review of Books.

The “Ask AI” tab appears in the dictionary lookup panel within the viewer, letting readers pose queries about the text in situ. This design situates the AI function alongside traditional lookup tools, rather than replacing them. Because the integration is optional, users uninterested in AI can continue using Calibre as before, with no overhead from the AI code.

Open source advocates say the move aligns with broader trends of embedding AI tools into user workflows without compromising user control or privacy. The local model support — via frameworks such as Ollama — underscores the aim to reduce reliance on external cloud services. Some users and commentators, however, remain sceptical of the utility: one Linux-oriented news site cautioned that critics might see the feature as “AI that isn’t even really AI” if not backed by substantial capabilities.

Calibre has long been valued by readers and librarians alike for its flexible library management, metadata editing, format conversion and compatibility across platforms. Its capability to fetch news, convert RSS into e-books, and host a content server for remote access adds to its appeal. The community-driven development model has delivered frequent updates, responsive bug fixes, and plugin extensibility.

Analysts suggest the AI enhancement could help Calibre stay competitive in a landscape where even e-reading tools are pressed toward intelligence layering. By offering the feature as an opt-in plugin rather than a core shift, the project balances innovation with respect for user autonomy. Some in the open source space view it as a test case for how small to medium projects can incorporate AI without transforming their fundamental ethos.

For users already reliant on Calibre for large or multilingual libraries, the AI addition may act as a value add—especially for academic, research, or study use cases where summarisation and context help accelerate reading workflows. At the same time, the modular design should prevent performance or security overhead for users uninterested in AI.

The article Calibre Unveils “Ask AI” Feature in Open-Source Reader appeared first on Arabian Post.