Avec ce modèle, Eureka fait le choix d’une approche « light tech » : pas de surenchère de technologies, mais un appareil simple, efficace et pas trop cher. On vous dit dans notre test si le contrat est rempli.
L’article Test de l’aspirateur laveur Eureka FloorShine 460 : le pari d’un prix mini mais d’une efficacité maxi est apparu en premier sur Toms Guide.
If you care about privacy and don't take too well to governments and Big Tech companies snooping on your messages, then Session has probably come up at some point. It's a free, open source, end-to-end encrypted messaging app that doesn't ask for your phone number or email to sign up.
Messages are routed through an onion network rather than a central server, and the combination of no-metadata messaging, anonymous sign-up, and decentralized architecture has earned it a loyal following among privacy-conscious users.
Unfortunately, the project has sent out a mayday call as it risks closure.
Your donations have helped, and the Session Technology Foundation (STF) has received enough funding to support critical operations for 90 days.
— Session (@session_app) April 9, 2026
This means that Session will remain available on the app stores and essential services (such as the file server and push notification…
The Session Technology Foundation (STF) sent out what can only be described as a distress signal, announcing that the app's survival is now in serious peril. The day it was posted on was also the last working day for all paid staff and developers at the STF.
From that point on, Session is being kept running entirely by volunteers.
The donations that they received earlier are enough to keep critical infrastructure online until July 8, but not nearly enough to retain a development team. With nobody left on payroll, development has been paused.
Due to that, introducing new features is off the table, existing bugs will most likely go unaddressed, and the STF says new releases are unlikely during this period.
Session co-founder Chris McCabe had already flagged the trouble coming. In a personal appeal published earlier in March, he wrote that the organizations safeguarding Session had faced many challenges over the years and that the project's very survival was now at risk.
He had concluded by appealing that:
The project is on a path to self-sustainability, but the future is fragile. If every Session user contributed just one dollar, it would go a long way towards Session reaching sustainability. If you've ever considered donating, now is the time to act.
The above didn't accomplish enough to change the outcome, so the Session folks had to sound the alarm. The foundation says it needs $1 million to complete the work still in progress.
That includes Protocol v2, which adds forward secrecy (PFS), post-quantum cryptography, and improved device management, as well as Session Pro, a subscription tier intended to put the project on a self-sustaining footing.
If that goal is hit, the STF says it hopes Session could stand on its own without needing to go back to the community for more.
As of writing, $65,000 of that $1 million has been raised. Anyone who wants to see this privacy-focused messaging app survive, especially at a time when surveillance is only getting worse, can donate at getsession.org/donate.
Suggested Read 📖: Session's Other Co-Founder Thinks You Don't Need to Ditch WhatsApp
France's national digital directorate, DINUM, has announced (in French) it is moving its workstations from Windows to Linux. The announcement came out of an interministerial seminar held on April 8, organised jointly by the Directorate General for Enterprise (DGE), the National Agency for Information Systems Security (ANSSI), and the State Procurement Directorate (DAE).
The Linux switch is not the only move on the table. France's national health insurance body, CNAM, is migrating 80,000 of its agents to a set of homegrown tools: Tchap for messaging, Visio for video calls (more on this later), and France transfert for file transfers.
The country's national health data platform is also set to move to a sovereign solution by the end of 2026.
Beyond the immediate moves, the seminar laid out a broader plan. DINUM will coordinate an interministerial effort built around forming coalitions between ministries, public operators, and private sector players, with interoperability standards at the core (the Open Interop and Open Buro initiatives are specifically named).
Every French ministry, including public operators, will be required to submit its own non-European software reduction plan by Autumn 2026.
The plan is expected to cover things like workstations, collaboration tools, antivirus, AI, databases, virtualization, and network equipment. A first set of "Industrial Digital Meetings" is planned for June 2026, where public-private coalitions are expected to be formalized.
Speaking on this initiative, Anne Le Hénanff, Minister Delegate for Artificial Intelligence and Digital Affairs, added that (translated from French):
Digital sovereignty is not optional — it is a strategic necessity. Europe must equip itself with the means to match its ambitions, and France is leading by example by accelerating the shift to sovereign, interoperable, and sustainable solutions.
By reducing our dependence on non-European solutions, the State sends a clear message: that of a public authority taking back control of its technological choices in service of its digital sovereignty.
You might remember, a few months earlier, France set out on a similar path for video conferencing. The country mandated that every government department switch to Visio, its homegrown, MIT-licensed alternative to Teams and Zoom by 2027.
Part of the broader La Suite Numérique initiative, it had already been tested with 40,000 users across departments before the mandate was announced. So this move looks like an even more promising one, and we shall keep an eye on how this pans out.
Suggested Read 📖: ONLYOFFICE Gets Forked
Méfiez-vous des messages vocaux qui auraient été envoyés par votre opérateur téléphonique. Des escrocs se font passer pour Orange, Bouygues et consorts pour dérober vos données personnelles.
L’article Arnaque au répondeur : comment la repérer et éviter la catastrophe est apparu en premier sur Toms Guide.
With the rise of AI and humanoid robots, the word "Clanker" is being used to describe such solutions, and rightly so. In their current state, these are quite primitive, and while they can act like something resembling human intelligence, they still can't match what nature cooked up.
Now that terminology has made its way into the Linux kernel thanks to Greg Kroah-Hartman (GKH), the Linux stable kernel maintainer and the closest thing the project has to a second-in-command.
He has been quietly running what looks like an AI-assisted fuzzing tool on the kernel that lives in a branch called "clanker" on his working kernel tree. Before you ask, fuzzing is a method of automated software testing that bombards code with unexpected, malformed, or random inputs to trigger crashes, memory errors, and other misbehavior.
It is a critical line of defense for a massive codebase like Linux.
It began with the ksmbd and SMB code. GKH filed a three-patch series after running his new tooling against it, describing the motivation quite simply. He picked that code because it was easy to set up and test locally with virtual machines.
What the fuzzer flagged were potential problems specific to scenarios involving an "untrusted" client. The three fixes that came out of it addressed an EaNameLength validation gap in smb2_get_ea(), a missing bounds check that required three sub-authorities before reading sub_auth[2], and a mechToken memory leak that occurred when SPNEGO decode fails after token allocation.
GKH was very direct about the nature of the patches, telling reviewers: "please don't trust them at all and verify that I'm not just making this all up before accepting them."
These pictures show the Clanker T1000 in operation.
It does not stop there. The clanker branch has since accumulated patches across a wide range of subsystems, including USB, HID, WiFi, LoongArch, networking, and more.
If you are not well versed with the kernel world, GKH is one of the most influential people in Linux development.
He has been maintaining the stable kernel branch for quite a while now, which means every long-term support kernel that powers servers, smartphones, embedded devices, and pretty much everything else running Linux passes through his hands.
He also wrote Linux Kernel in a Nutshell back in 2006, which is freely available under a Creative Commons license. It remains one of the more approachable references for anyone trying to understand kernel configuration and building, and it is long overdue for a new edition (hint hint).
Speaking at Open Source Summit Japan last year, Linus Torvalds said the upcoming Linux Kernel Maintainer Summit will address "expanding our tooling and our policies when it comes to using AI for tooling."
He also mentioned running an internal AI experiment where the tool reviewed a merge he had objected to. The AI not only agreed with his objections but found additional issues to fix.
Linus called that a good sign, while asserting that he is "much less interested in AI for writing code" and more interested in AI as a tool for maintenance, patch checking, and code review.
There is an important distinction worth making here. What GKH appears to be doing here is not having AI write kernel code. The fuzzer surfaces potential bugs; a human with decades of kernel experience reviews them, writes the actual fixes, and takes responsibility for what gets submitted.
If that's the case, then this is the sensible approach, and it mirrors what other open source projects have been formalizing. LLVM, for instance, adopted a "human in the loop" AI policy earlier this year, requiring contributors to review and understand everything they submit, regardless of how it was created.
Suggested Read 📖: Greg Kroah-Hartman Bestowed With The European Open Source Award
He managed to work nearly 65 years in the biggest city in the U.S., and in doing so, earned the admiration of his broadcast engineering peers.
Richard Ross, a longtime chief engineer in New York City, died on Feb. 12 at the age of 89. He is survived by his daughter Erica, who shared many details with us from his life.
Ross joined 1280 WADO(AM) in the summer of 1972 as a relief engineer. By his count, he would withstand eight ownership changes until his retirement as chief engineer from Univision Radio in June 2020 at the age of 84.
Fellow engineers would call Ross frequently after his retirement, and for a time, he offered consulting services.
“He had a kind of Harry Potter-like knowledge of it all,” Erica said.
“Those who knew Richard lost a member of their family with his passing,” said Santos Lebron, engineering supervisor at Univision Radio New York.
Lebron’s relationship with Ross went back decades; they met when Lebron was hired as a relief engineer at WADO in 1977. He and others remembered Ross for being well-dressed and possessing a level-headedness, amicable toward all and harboring a bit of a mischievous side.
Ross knew of his fortune to work in the Big Apple for so many decades. “It is a rare occasion where one starts their career in any major city and they eventually work their way up the line to more important positions in major communications hubs,” he wrote in a piece for Storyworth.
Along with WADO, Ross spent many hours with the equipment above the Empire State Building when Heftel Broadcasting purchased 105.9 WNWK(FM). Univision’s radio footprint in New York would continue to grow with the addition of 92.7 WQBU(FM) in Garden City, followed by the trade of 105.9 with New York Public Radio for 96.3, then WQXR(FM), in 2009.
Ross was born to Helen and Edward Ross in May 1936 as an only child on Manhattan’s Upper West Side.
Erica recounted how he developed a knack for machines and tinkering early on. By age 10, Ross was already experimenting with his apartment building’s elevator controls — even figuring out how to send the doorman to the wrong floors.
For several years, he attended a boarding school in western North Carolina near the Blue Ridge Mountains. The experience of navigating his way back to Manhattan via train sparked a lifelong fascination with locomotives.
He later attended Brooklyn Technical High School, where he joined the radio club and, according to Erica, officially “caught the bug.”
Ross studied at the University of Bridgeport, earning his associate’s degree in electrical engineering. He went on to serve three years in the communications division of the New York Air National Guard and completed basic training at Keesler Air Force Base in Biloxi, Miss.
In 1958, he got his break into the radio business, joining Municipal Broadcasting System’s WNYC(AM/FM) as a provisional engineer.
Ross aimed to become permanent pending a civil service exam. Passing the exam, however, didn’t guarantee a full-time position due to fierce competition from others. But WNYC’s chief engineer at the time, Hom Hong Wei, offered some reassuring advice, and Ross got the position.
He would credit Wei as being one of his most influential mentors. At WNYC, Ross found himself exploring hidden corners of the city.
“I got to go places that nobody else goes such as walking to the top of Washington Square Arch and yes, there is a locked stairway in the south leg of the arch,” Ross would recount.
By the early 1970s, Ross transitioned to WADO as a summer relief engineer.
For a time, he found the energy to work at both WADO and WNYC, before becoming permanently entrenched at the Spanish-language AM station, where he’d work well into the 21st century.
He wondered how he had the stamina to manage it all.
He’d go solely full-time at WADO, but Ross’ role went beyond its day-to-day. During the ’70s, the AM station would broadcast Black gospel music on Sundays, and it had brokered agreements with several churches in the south Bronx and Harlem.
Ross was tasked with recording the services, lugging RCA reel-to-reel machines to the locations. Others were known to turn down those assignments for one reason or another, but Ross happily obliged.
Even after WADO stopped airing the programming, he became entrenched with the churches, who would ultimately approach Ross to do separate recordings of the services. He would handle multiple recordings in a single day during the 1980s, and continued doing so through at least 2005.
They affectionately referred to him as “Brother Ross, our Gospel engineer,” viewing him as a part of their community. The services would be taped and sent to radio stations across the U.S. that aired Black gospel.
His spirit was evident in other ways. Ross became a member of the IBEW Local 1212, the labor union for broadcast engineers, in 1963.
He rose in its ranks, becoming part of the union’s executive board. Ross would stay even after he became WADO’s chief engineer in 1985, following the passing of his good friend Phil Greenstone.
With what would have been considered a management position, it was unusual for someone like Ross to remain in the union, both Erica and Lebron said. Ross wrote that he felt it was an honor.
“He was more than a colleague; he was a brother in every sense of the word,” IBEW 1212 wrote while remembering Ross on its website.
“All of us in this profession share the same situation,” Ross wrote in his Storyworth of his IBEW role. “We all know each other in New York City and once each month we meet to eat, drink and be merry and discuss our war stories.”
Ross was also a loyal member of the Society of Broadcast Engineers.
As the broadcast landscape evolved, Lebron remembered Ross best for coordinating WADO’s transmitting power increase in the New Jersey Meadowlands at the end of 1999.
As recounted by Scott Fybush, WADO had used a Blaw-Knox diamond-shaped tower from its transmitter site on Paterson Plank Road in Carlstadt. It ran 5 kW day and night as part of a power restriction on regional channels like 1280.
But the FCC lifted that restriction in the early 1990s. WADO sought to upgrade to 50 kW by day and 7.2 kW at night, which required a new antenna system.
The venerable Blaw-Knox tower came down, and three new towers were needed, along with a complete renovation of the 1930s-era building that housed its transmitters.
Then-owner Hispanic Broadcasting had filed for a construction permit, but most of the actual work did not commence until just prior to its expiration, which acted as a hard deadline.
As Ross wrote in his Storyworth, from October 1999 and for the next four months, he visited the Meadowlands site daily to complete the project under great stress and pressure.
Construction took place on sensitive riparian land. It required a year of hearings costing over $1 million, involving the state of New Jersey, the Army Corps of Engineers and the U.S. Coast Guard.
Laying down and completely removing temporary wooden plank roads alone cost $675,000, according to Ross. Union dock workers were hired to build a 1,000-foot boardwalk to the towers, and a crane had to be rented from the Tappan Zee Bridge.
With the main transmitter building modified and the heat shut off, crews worked late into the winter nights, running copper straps between the four towers with only a porta-potty out back.
He recounted the moment of truth:
“On February 1, I invited David Lykes, Hispanic Broadcasting’s chief operating officer, to come up from Dallas to push the activate button at 6 p.m.,” Ross wrote. “My heart was in my throat, but the damn system worked.”
The antenna system was designed by Ron Rackley of du Treil, Lundin & Rackley, who consulted on the project and praised Ross for its execution.
There were many other, less high-profile wins as well, often accompanied by 2 a.m. phone calls.
Ross was also well-known for his thorough tours of the Empire State Building’s broadcast facilities — Erica said multiple people have told her that those tours were highlights of their careers.
Also an amateur radio operator (K2RNR), Ross had many interests outside of radio, including locomotives and nature.
He loved the city, but ever since his boarding school days in western North Carolina, he became infatuated with the peace of a mountainside setting. Since the late 1960s, Ross owned a property in Kunkletown, Pa., in the southern portion of the Pocono Mountain region.
A lover of nature and an adamant conservationist, he viewed the country home as a sanctuary for wild animals. But he’d continue to call the Big Apple his main home and it was the only place he’d ever work.
In 2013, Univision honored his 50 years of broadcasting service by naming a studio after him.
True to his nature, he hated the attention and adamantly hoped people wouldn’t use the milestone to do the math on his age.
Ross passed away at home in his Hell’s Kitchen apartment — where he lived since 1964 — just shy of his 90th birthday.
Fittingly, the coroner described the lifelong engineer’s unforeseen cause of death as “an electrical short circuit of the heart.”
A memorial and celebration of life for Ross will be held Sunday, April 12, at the Masonic Lodge No. 72 in Secaucus, N.J.
The post How Richard Ross Kept the City That Never Sleeps On the Air appeared first on Radio World.
Microsoft has had a complicated relationship with the open source world. VSCode, TypeScript, and .NET are all projects it created, and its acquisition of GitHub put it in charge of the world's largest code hosting platform.
But it is also the same company that bakes telemetry into Windows by default and has been aggressively pushing Copilot AI into every corner of its software. That last part especially has been nudging a growing number of people toward open alternatives.
And now, a wave of developer account suspensions has given some open source developers a new headache.
Microsoft rolled out mandatory account verification for all partners enrolled in the Windows Hardware Program who had not completed verification since April 2024. The requirement kicked in on October 16, 2025, giving partners 30 days from notification to verify their identity with a government-issued ID.
Plus, that ID has to match the name of the Partner Center primary contact. Miss the deadline or fail verification, and your account gets suspended with no further submissions allowed.
This matters because signing Windows kernel drivers requires one of these accounts. Without it, developers cannot push driver-signed updates for Windows, and Windows will flag unsigned drivers, blocking them from loading at the kernel level.
Three major open source projects found this out the hard way. VeraCrypt, WireGuard, and Windscribe all had their developer accounts suspended, cutting off their ability to ship updates on Windows.
It appears @Microsoft is actively suspending developer accounts with no warning or reason of various security tools like VeraCrypt, WireGuard and also Windscribe. We've had this VERIFIED account for 8+ years to sign our drivers.
— Windscribe (@windscribecom) April 8, 2026
We've been trying to resolve this for over a… https://t.co/iwkryuwKuO pic.twitter.com/7VcnAQIbnP
VeraCrypt developer Mounir Idrassi was the first to go public. In a SourceForge forum post, he wrote that Microsoft had terminated his account with no prior warning, no explanation, and no option to appeal.
Repeated attempts to reach Microsoft through official channels got him nothing but automated replies. The suspension hit his day job too, not just VeraCrypt.
WireGuard creator Jason Donenfeld hit the same wall a couple of weeks later, when he went to certify a new WireGuard kernel driver for Windows and found his account showing as access restricted. He eventually tracked down a Microsoft appeals process, but it carried a 60-day response window.
Windscribe's situation was arguably the messiest. The company says it had held a verified Partner Center account for over eight years and spent more than a month trying to sort things out before going public.
Moreover, once an account is suspended, Partner Center blocks users from opening a support ticket directly.
This eventually got Microsoft's attention as Scott Hanselman, VP and Member of Technical Staff at Microsoft and GitHub stepped in on X to say the accounts would be fixed. He pointed to the October 2025 blog post (linked earlier) and said the company had been sending emails to affected partners since then.
Scott confirmed he had personally reached out to both Mounir and Jason to get their accounts unblocked, and that fixes were already in progress.
Anyway, this doesn't look good, and leaving developers of critical security software without recourse for weeks only erodes trust. But, in the end, this won't really affect a behemoth like Microsoft, who has a dominating hold on the operating system market.
Suggested Read 📖: Proton Workspace and Meet launched as alternatives to Big Tech offerings
APT, or Advanced Package Tool, is the package manager on Debian and its derivatives like Ubuntu, Linux Mint, and elementary OS. On these, if you want to install something, remove it, or update the whole system, you do it via APT.
It has been around for decades, and if you are on a Debian-based distro, then you have almost certainly used it without giving it much thought. That said, it has seen active development in the last couple of years.
We covered the APT 3.0 release this time last year, which kicked off the 3.x series with a colorful new output format, the Solver3 dependency resolver, a switch from GnuTLS/GnuPG to OpenSSL, and Sequoia for cryptographic operations.
The 3.1.x cycle that followed has now closed out with APT 3.2 as the stable release, and it brings some notable changes with it.
The biggest additions with this release are transaction history with rollback support, some new commands, and per-repository package filtering.
APT now keeps a log of every package install, upgrade, and removal. You can view the full list with apt history-list, which shows all past operations with an ID assigned to each. To see exactly what packages were affected in a specific operation, you can use apt history-info <ID>.
From there, apt history-undo <ID> can be used to reverse a specific operation, reinstalling removed packages or removing installed ones as needed. If you undo something mistakenly and want it back, run apt history-redo <ID> to reapply it.
For cases where you want to revert everything back to the state at a particular point, apt history-rollback <ID> does that by undoing all operations that happened after the specified ID. Use this with care, as it makes a permanent change.
apt why and apt why-not are another set of new additions that let you trace the dependency chain behind a package. Run apt why <package> and APT will tell you exactly what pulled it onto your system. Run apt why-not <package> and it will tell you why it is not installed.
Similarly, Include and Exclude are two new options that let you limit which packages APT uses from a specific repository. Include restricts a repo to only the packages you specify, and Exclude removes specific packages from a repo entirely.
Solver3, which shipped as opt-in with APT 3.0, is now on by default. It also gains the ability to upgrade packages by source package, so all binaries from the same source are upgraded together.
Additionally, your system will no longer go to sleep while dpkg is running mid-install and JSONL performance counter logging is also in, though that is mostly useful for developers.
If all of that's got you interested, then you can try Apt 3.2 on a Debian Sid installation as I did below or wait for the Ubuntu 26.04 LTS release, which is reportedly shipping it.
I almost got lost in the labyrinth of Vim, unable to exit.
After installing some new programs using APT, I tested a few commands to see how rollback and redoing transactions worked. First, I ran sudo apt history-list in the terminal and entered my password to authorize the command.
The output was a list of APT transactions that included the preparatory work I had done to switch to Debian Sid from Stable, as well as the two install commands to get Vim and Nala installed.
Next, I ran sudo apt history-info 4, the number being the ID of the transaction, and I was shown all the key details related to it, such as the start/end time, requested by which user, the command used, and packages changed.
After that, I ran sudo apt history-undo 4 to revert the Vim installation and sudo apt history-redo 4 to restore the installation; both of these commands worked as advertised.
Finally, I tested sudo apt history-rollback 3 to get rid of Nala, and the process was just about the same as before, with me being asked to confirm changes by typing "Y".
When I tried to run apt history-redo for this one, the execution failed as expected.
💬 Do these new additions look useful to you? Can't be bothered? Let me know below!
La justice serre la vis face au trafic d’IPTV illégales. À Arras, deux hommes ont été condamnés pour avoir revendu des codes permettant d’accéder illégalement à des contenus protégés. Ils ont été démasqués par un détective privé missionné par la Ligue de football professionnel.
L’article IPTV pirate : deux Français lourdement condamnés, la LFP leur réclame 100 000 € est apparu en premier sur Toms Guide.
Anthropic has handed the Apache Software Foundation (ASF) a $1.5 million donation. The money is earmarked for build and security infrastructure, project services, and community support.
If you have used the internet today, you have almost certainly touched something the ASF maintains. Some of its projects like Kafka, Spark, Cassandra, the Apache HTTP Server, are not some niche tools, but a critical part of the modern IT infrastructure.
The ASF does not sell anything. It runs on donations, and without sustained funding, the infrastructure behind all of that software does not maintain itself.
Anthropic's framing for the donation is essentially that AI runs on this stuff and someone has to fund it. As AI development moves forward more quickly, the open source foundations underneath it need to be in good shape to keep up.
On the topic, Ruth Suehle, President of the Apache Software Foundation, added that:
Open source software is the foundation of modern digital life — largely in ways the average person is completely unaware of — and ASF projects are a critical part of that. When it works, nobody notices, and that’s exactly the goal.
But that kind of reliability isn’t a given. It is the result of sustained investment in neutral, community-governed infrastructure by each part of the ecosystem. Support like Anthropic’s helps ensure long-term strength, independence, and security of the systems that keep the world running.
Similarly, Vitaly Gudanets, Chief Information Security Officer at Anthropic, said that:
AI is accelerating rapidly, but it’s built on decades of open source infrastructure that must remain stable, secure, and independent. Supporting the Apache Software Foundation is a direct investment in the resilience and integrity of the systems that modern AI — and the broader software ecosystem — depend on.
You might remember Anthropic was part of a similar donation campaign back in March, when the Linux Foundation announced $12.5 million in grants to strengthen open source software security. Anthropic was one of seven contributors to that pool, alongside AWS, Google, Google DeepMind, GitHub, Microsoft, and OpenAI.
That funding was managed by Alpha-Omega and the Open Source Security Foundation (OpenSSF), with the goal of helping open source maintainers deal with the growing flood of AI-generated vulnerability reports they simply do not have the bandwidth to handle.
It is great to see open source receiving monetary support, but the smaller players who are equally important in the ecosystem also need to be supported better. Big donations like this tend to flow toward well-established foundations, while the countless smaller projects that hold up just as much critical infrastructure quietly struggle for resources.
The PyTorch Foundation has taken on two new projects: Helion, a tool for writing machine learning kernels contributed by Meta, and Safetensors, a secure model file format contributed by Hugging Face.
Both were announced at PyTorch Conference Europe in Paris, and the two now join DeepSpeed, Ray, vLLM, and PyTorch itself as foundation-hosted projects.
Moreover, the foundation has confirmed that ExecuTorch, Meta's solution for running PyTorch models on edge and on-device environments, is being merged into PyTorch Core.
If you were looking for the why, it is fairly straightforward.
Both moves come as AI teams increasingly focus on getting models into production rather than just training them. Running kernels efficiently across different hardware and keeping model files safe to load are two problems the ecosystem has been dealing with for a while.
Talking about Helion joining up, Matt White, the CTO of the PyTorch Foundation, added that:
Helion gives engineers a much more productive path to writing high-performance kernels, including autotuning across hundreds of candidate implementations for a single kernel.
As part of the PyTorch Foundation community, this project strengthens the foundation for an open AI stack that is more portable and significantly easier for the community to build on.
Luc Georges, Chief Open Source Officer, Hugging Face echoed similar excitement:
Safetensors joining the PyTorch Foundation is an important step towards using a safe serialization format everywhere by default. The new ecosystem and exposure the library will gain from this move will solidify its security guarantees and usability. Safetensors is a well-established project, adopted by the ecosystem at large, but we're still convinced we're at the very beginning of its lifecycle: the coming months will see significant growth, and we couldn't think of a better home for that next chapter than the PyTorch Foundation.
The PyTorch Foundation is a Linux Foundation-hosted organization that acts as the vendor-neutral home for PyTorch and a growing set of open source AI projects. The main goal here is to keep governance and technical direction community-driven rather than tied to any single company's whims.
The Linux Foundation is the broader stewardship body behind over 1,000 open source projects, covering everything from the Linux kernel and Kubernetes to OpenSSF. The PyTorch Foundation sits under that umbrella, giving its projects access to LF's governance infrastructure and oversight.
Helion comes in as a tool that makes writing the low-level code that runs AI models on GPUs significantly less painful. It handles a lot of the tedious groundwork automatically, and finds the best configuration for your hardware on its own.
Whereas Safetensors is a file format for storing and sharing AI model weights that doesn't come with the security baggage of older formats.
Sur Windows 11, la fonctionnalité Delivery Optimization, activée par défaut, utilise votre connexion pour envoyer des fichiers de mise à jour à d'autres PC. Ce qui peut engendrer des ralentissements dispensables. Voici comment faire pour le désactiver.
L’article Windows 11 : ce paramètre peut nuire à votre connexion Internet, comment le désactiver est apparu en premier sur Toms Guide.
Zendure passe à la vitesse supérieure avec le SolarFlow 2400 AC+, une batterie domestique monobloc plus puissante et plus simple à installer. Avec sa sortie de 3200 W et sa gestion intelligente par application, ce système modulaire promet d'optimiser radicalement votre autoconsommation solaire. Voici notre verdict après quelques jours de test.
L’article Test SolarFlow 2400 AC+ : la batterie de Zendure tient sa promesse de haut rendement est apparu en premier sur Toms Guide.
KDE Plasma's two classic themes, Oxygen and Air, are making a comeback. A group of KDE contributors is actively restoring both ahead of the Plasma 6.7 release, which is scheduled for June 16, 2026.
Both themes trace their roots back to the KDE 4 era. Oxygen shipped as the default theme from KDE 4.0, defined by its dark tones and glassy aesthetic. It held that spot until KDE 4.3, when Air took over as the default, bringing a lighter look built around transparency and white as its base color.
While Oxygen stuck around into the Plasma 5 and 6 eras, it did so in an increasingly broken condition, and Air eventually got dropped from Plasma entirely.
Now, both are getting a second shot thanks to the restoration effort led by KDE contributor Filip Fila, alongside the original Oxygen designer Nuno Pinheiro and several other KDE developers.
On the Oxygen side, the panel has been fully reworked and is now orientation-aware, so vertical panels actually behave correctly. A minimized window indicator and a proper switch design were both missing entirely and have now been added.
Similarly, adaptive opacity is now supported and enabled by default, and the color scheme bug that was causing readability issues in widgets like System Monitor has been fixed.
Air needed its transparency restored to match its original KDE 4 character. That is done now, with blur added behind widgets, improving readability and visual appeal in the process. The panel has also been reworked, a new header and footer design has been added, and Air now has its own switch SVGs.
Why now after all this time? Well, KDE's 30th anniversary coincides with the Plasma 6.7 release, and the people behind this want to ship these historically significant themes for the occasion.
As of writing, 26 of 40 checklist items have been completed (linked below), with some pending work including gradient banding fixes in Oxygen, missing SVGs for checkmarks, radio buttons, toolbar, and menubar items across both themes, and a timer SVG for Air.
And if you want to see what that progress looks like, continue reading! 😬
From left to right, we have Breeze, Oxygen, and Air.
I checked out how Plasma's default Breeze theme compared to Oxygen and Air on a KDE Neon setup, and I must say, things are looking promising. The themes have things like the panel styling, widget backgrounds, and the new switch designs in place.
I specifically took a look at the panel and widgets, and these looked very clean, feeling like they belonged in the modern Plasma experience, which is not something you would expect from themes this old.
One thing worth noting is that the icons stayed as Breeze regardless of which Plasma Style I picked.
As for the difference between these, Breeze is flat by design. Minimal, no frills, gets out of your way kind. Oxygen and Air are not like that, bringing visible depth and some bling to the desktop, but in different ways.
While Air leans hard into transparency, making panels and widgets look light and barely there, Oxygen goes the other direction with darker gradients and more visual weight across the board.
Personally, I prefer Oxygen as it looks a lot like Windows 7's Aero, which I quite liked back in the day.
First, you have to download the files for Oxygen and Air on a KDE Plasma-equipped system. Next, you have to go into System Settings > Appearance > Colors & Themes > Plasma Style.
Here, click on "Install from File..." and select a theme file to install it. Repeat for the other one, then select whichever theme you want and hit "Apply" on the bottom-right.
If you want to stay in sync with the development of these, you can keep an eye out on the GitLab issue tracker and Telegram group for this project.
If you did not know already, Puter is an operating system that runs inside a web browser. It is open source and you can self-host it if you like.
It has everything you would expect in a desktop. A file system, app store, text editor, IDE, video player, etc. The video below shows it in action. See, how somooth it is.
Why not give it a try yourself here.
As you can see in the video above, Puter has a text editor which is capable of taking notes. But it is not enough for rich text format and proper documents.
Now, they are offering ONLYOFFICE in their app center. The open source ONLYOFFICE is a collaborative productivity suite like MS Office 365.
With this integration, you also get spreadhseet, pdf editor and presentation tools. This make the online browser based desktop operating system more capable and complete than ever.
If you ever used Nextcloud, you know that the cloud storage also has office integration with ONLYOFFICE and Collabora (sort of LibreOffice online). The difference I see here is that Puter gives you the entire filesystem, not just cloud storage and productivity tools. This is excellent for people who prefer the comfort of a desktop like environment in the cloud.
I have used ONLYOFFICE in Nextcloud in the past. I have noticed that it does take a bit of time to load the application in both Puter and Nextcloud. Sure, we cannot expect a full office app to open in a jiffy like a text editor. These applications take longer to start, even on local desktop system. It takes pretty much the same in Puter.
Creating the document was smooth. The in-built grammar checker worked well too. For some reason, the Save button on the top interface did not work. The print and open and other buttons were working fine and so did the keyboard shortcut. Not a dealbreaker but something worth mentioning. I am sure the Puter team will fix it in the next iteration.
Since I didn't have any complicated word document with macros and images, I uploaded a csv file with 1000 rows and opened it in ONLYOFFICE. I was expecting it to take some time to load and struggle but it did not. Obviously, that's a good thing.
I recorded it in a video so that you can see if yourself if it takes too long or lags while moving down the sheet.
I also created a simple presentation slide. Unsurprisingly again, it went smoothly. ONLYOFFICE actually works quite well in a web browser. That is their USP, afterall.
The entire ONLYOFFICE integration gives Puter the complete desktop OS features. After all, ONLYOFFICE also has PDF editor and diagram app (Visio alternative). All your office needs are sorted, that too in a web browser.
Puter Marketplace (app store) has many more applications that you can explore and use as per your requirement. From games to coding to AI, there are plenty of options.
We had covered Puter last summer. In less than a year, Puter has grown and created an ecosystem that is admirable. I was skeptical of the actual, real-world usage of an online operating system that lives in a web browser but it seems there is demand for such a thing. Good to see an open source project filling up this demand.
If you are coming across Puter OS for the first time, you should know that the files you uploaded or created will be available as long as the browser session is not deleted. But if you want to save them for longer period, you can create an account with Puter. If you see a good use of Puter in your workflow or it could help your team (if you have one), you can also self-host it or pay to Puter for their managed hosting.
I have been gaming (not to be confused with gambling ☠️) for quite some time now. In that time, I have seen my fair share of gaming-centric platforms, storefronts, and applications, ranging from the genuinely useful to the elaborate solutions to problems that nobody really had.
Opera is a name that never fully disappeared from my mind because it has been consistent in delivering a browsing experience that many people prefer. I used it for a while, mostly for the free built-in VPN, before eventually moving to Firefox when I felt it was time for a change.
However, they also have a gaming-focused browser called Opera GX, which has been available on Windows and macOS for some time now. Earlier this year, we got word that a Linux port was in the works, and it did eventually arrive.
Curious about what took them so long, I asked Maciej Kocemba, Product Director at Opera GX, and he had this to add:
Bringing Opera GX to Linux has been a priority for us for some time now, especially since we've seen such public support among the community. One group even launched an online petition that collected several hundred signatures, which was pretty cool to see.
With gaming on Linux growing so fast right now, this is the perfect moment for us to bring a browser designed for gamers to a platform that values customization and control as much as we do. We’re so happy to finally make it available to this community of users, and we're eager to see how they'll take advantage of the GX features they’ve been waiting for.
That got me hyped enough to see for myself what a gaming browser actually feels like and whether there was anything a regular browser couldn't already do.
I took Opera GX for a run on a Nobara Linux 43 setup, using an Early Access version to test it across various scenarios ranging from general browsing to playing YouTube content to running internet speed tests.
On first launch, the browser asked me if I wanted to send telemetry; I declined and moved on to the initial setup. It asked me to pick a theme, and I went with the default GX Classic since it felt more Opera than the rest.
It then asked whether I wanted background music that reacts to my browsing, sound effects for in-browser actions, and keyboard sounds as I typed. I left all of these at their defaults since, honestly, they went right over my head (don't call me a boomer pls).
Opera GX on Linux new user onboarding.
I could also enable a bunch of sidebar integrations for Telegram, X, Instagram, and so on, but I left those turned off. Opera GX even asked me to import data from another web browser, but it failed to detect Vivaldi, which was already installed.
The next step involved me manually turning on the ad blocker (and later the block trackers option), but the other two features, GX Control and GX Cleaner, were toggled on by default.
Opera GX on Linux new user onboarding continued.
I also had to disable Opera AI from the hamburger menu, as I didn’t need it. What did catch my eye, though, were the many pre-installed sponsored speed dials I had to clear out.
And, to little surprise, the default search engine was set to Google, but that is changeable from the Settings menu.
On the left are the toggles to configure the ad blocker and Opera AI. On the right are the sponsored speed dials.
Interestingly, while the ad blocker does work, it fails to show data on how many ads and trackers were blocked when I clicked on the widget for it in the top bar (the shield-looking icon).
Left: The ad blocker widget. Right: The Privacy and Security settings.
I headed into the Privacy and Security section of the settings and found quite a few things enabled by default: automatic sending of crash reports, fetching images for suggested news sources, displaying promotional notifications, and receiving promotional speed dials, bookmarks, and campaigns.
Not great for anyone who takes their privacy seriously and just doesn't want to be bombarded with spammy notifications and speed dial suggestions.
A demo of GX Control on Linux.
I then fired up Arc Raiders and tried my hand at GX Control. It is Opera GX's built-in resource management panel that lets you cap how much RAM, CPU, and network bandwidth the browser can use with individual toggles and sliders for each limiter. It worked as advertised and even threw up warnings when I set the limits too low.
Similarly, GX Cleaner is the browser's built-in browser cleanup tool that clears out cache, cookies, history, tabs, downloads, and more. It has handy presets, MIN, MED, and MAX, that control how deep the sweep goes, ranging from a light clear of recent temporary files all the way to a full wipe of just about everything. It worked as expected during my use.
A few things that I skipped testing were the stuff most browsers have like bookmarks and extensions, the latter of which Opera GX supports from the Opera catalog.
Then there are the other GX-specific bits, account sync for carrying your data across devices, and the sidebar webapps for Twitch and ChatGPT, which let you keep a stream or an AI assistant open without leaving your current tab.
GX Mods is also there, giving you access to over 10,000 community-made themes, sounds, shaders, and UI tweaks, though you will need an Opera account to get into it.
Depends. For someone like me who tends to close any unnecessary apps running in the background before launching a game, I don't see much use for a gaming browser. For casual browsing tasks, the occasional Alt+Tab to a regular browser does just fine, and the Steam overlay's built-in browser is handy too (albeit very barebones).
That said, if you are the kind of person who RGBs everything in sight and already has a riced-out Linux setup, Opera GX could be a decent addition to the collection.
Just go through the default settings before you do anything else. A lot of what's enabled out of the box won't sit well with most Linux users.
You can grab the DEB and RPM binaries for Opera GX from the official website.
Another morning, another moderately (but pleasantly) surprising move in the Linux development storyline. In the big 2026, Linux is definitively fixing its support for the GD-ROM driver, which is used by Sega Dreamcast.
For context, Sega Dreamcast is a gaming console made by Sega and released in 1999. At the time, Sega came up with a proprietary disc format called GD-ROM, which could store more data than a normal, everyday CD-ROM disc. This gave Sega an edge in their game storage as well as performance.
Even though it had to take on a giant opponent, the PlayStation 2, Sega did well with its Dreamcast. It had a robust set of titles to start with, like "Jet Set Radio," "Phantasy Star Online," "Crazy Taxi," "Sonic Adventure," and "Soul Calibur." It had equally robust hardware, with a unique controller and a proper arcade feel that the people got attached to. The Dreamcast still, however, maintains a cult following, with new titles being developed for it even now.
The unsurprisingly brilliant part of all this is the endurance that open source development has always shown, and still shows. The arrival of support for something that was fresh almost 27 years ago now, with only an infinitesimal part of the community asking for it is not a minor feat, it is a testament to the core philosophies of FOSS. The beautiful cornerstone principle of open source software is that it exists mostly and purely because the developers want good software to exist. There are no bounds to the whimsy and personal gratification that they can bring.
It has been known that Linux gives a second life to old hardware, making it usable when the software that it came with has already discarded the possibilities. Posts about revival of old hardware with Linux to make them into something usable, like servers or media centers or so on are very commonplace on platforms like Reddit. That extends not only to personal computers, as we can see, but also specialized hardware, like the Sega Dreamcast.
Even though there have been some recently drastic support drops on Linux, such as the abandonment of support for floppy disks, or the plan of dropping support for i486 processors starting from Linux 7.1, the extension of support for old technology is not an old phenomenon for Linux. The shift is perspective comes when you realize that even though these things are dropped from the main kernel, there are versions of Linux still on the internet, and still being actively supported that keep the "obsolete" hardware going.
Linux has a rich community for retro gaming, with entire distributions like RetroArch dedicated to it. There are simulators for all kinds of old gaming consoles and platforms, and most of the old controllers and even their cheap generic rip-offs are mostly supported by Linux. Combined with cheap (debatable?) hardware like the Raspberry Pi and the distribution RetroPie, you can really make a platform for yourself.
All-in-all, it is always a good day in Linux-land when we get more support for more enthusiast-oriented projects and hardware. To not let worthy old hardware die out is the greatest emotional and technical gift that its users can receive and well, Linux provides. Cheers 🥂
Plenty of CPU architectures have come and gone over the last few decades. The x86 family alone has seen a long line of chips rise to prominence and fade away as newer generations took over.
The i486 is one such chip, and it has been holding on in the Linux kernel far longer than most people expected. It was launched in 1989 as Intel's answer to what came next after the i386.
It was faster, smarter, and arrived right as personal computers were making their way from offices into living rooms. For many people, a 486-powered PC was their first computer.
By the early 1990s, the chip was everywhere. It was so dominant that AMD, Cyrix, and IBM all jumped in with their own compatible versions to grab a slice of the market. Intel kept producing the i486 well past its prime too, with embedded versions rolling off the line until 2007.
Most major platforms dropped i486 support a long time ago. Microsoft's last operating systems to officially support it were Windows 98 and Windows NT 4.0. The Linux kernel, however, has kept the lights on for i486 users well into the 2020s.
But that is now changing. 😅
Back in April 2025, kernel maintainer Ingo Molnár posted an RFC patch series to the Linux Kernel Mailing List, proposing to raise the minimum supported x86-32 CPU. The new floor would require chips with both a Time Stamp Counter (TSC) and CMPXCHG8B (CX8) instruction support.
Anything short of that, including the i486 and some early Pentium variants, would be out.
Prior to that, Linus Torvalds had already made his position clear on the mailing list, saying that:
I really get the feeling that it's time to leave i486 support behind. There's zero real reason for anybody to waste one second of development effort on this kind of issue.
Ingo's RFC had covered a fair amount of ground. The full cleanup would touch 80 files and remove over 14,000 lines of legacy code, including the entire math-emu software floating-point emulation library.
Now, the first of those patches removes the CONFIG_M486, CONFIG_M486SX, and CONFIG_MELAN Kconfig build options. It has been committed and is queued for Linux 7.1. Once it lands, building a Linux kernel image for i486-class hardware will no longer be possible.
Ingo noted in the commit that no mainstream x86 32-bit distribution has shipped an M486=y kernel package in some time, so the real-world impact on active users should be close to zero.
If you have an i486 machine tucked away somewhere, it is not suddenly useless. Older kernel releases will continue to run on the hardware just fine.
Yes, those older kernels are not getting security patches. But if you are keeping a decades-old machine around for historical or educational purposes, it will not be your daily driver.
Just keep it off the internet, pair it with an older LTS kernel, and it will do what you need it to do without much fuss.
The Association of Public Radio Engineers is preparing the 26th Public Radio Engineering Conference, which returns to Las Vegas with a focus on navigating the uncertain future of public broadcasting.
The event will take place Thursday, April 16, and Friday, April 17, at the Tuscany Suites and Casino, preceding the NAB Show.
This year’s speakers include engineers, representatives from product manufacturers and other recognizable industry names. PREC is public radio’s yearly gathering for broadcast engineers of all experience levels.
This year’s guiding theme is “what’s next.” While the content remains mostly technical, the dramatic changes in public media over the past year give the discussions a unique context.
According to APRE President Scott Hanley, the association board designed the event with that shifting landscape in mind. He also believes this is the one time of year such a large and diverse group of public radio technology experts can gather.
“We decided that our conference had become even more important than years past, as we face a future where effective, sustainable operation is at risk and important to our communities,” Hanley said.
Sample Thursday sessions include:
[Related: “How Boosters Can Help AM Stations”]
A sample of Friday’s schedule:
The newly formed Public Media Infrastructure will also present on Friday; its speakers were pending at this writing.
Organizers have held the in-person conference price flat at $350 for members since 2024. They also offer a virtual attendance option for engineers unable to travel.
He also said APRE is expanding its financial aid footprint. The funds are designated both to assist attendees with financial needs and “to encourage the next generation of technical talent to get firmly engaged in the public media engineering community sooner rather than later,” according to Hanley.
The conference concludes on Friday evening with the annual APRE Awards Dinner at Lawry’s Prime Rib.
[Read more Radio World preview coverage of the NAB Show and related events happening in Las Vegas this month]
The post PREC Returns Amid Turbulent Times in Pubradio appeared first on Radio World.
Le menu Démarrer est au cœur de l'expérience utilisateur de Windows 11. Or son outil de recherche souffre de ralentissements et affiche des résultats inutiles. Reconnaissant les problèmes, Microsoft planche sur des améliorations.
L’article Windows 11 : Microsoft va s’attaquer aux deux points faibles du menu Démarrer est apparu en premier sur Toms Guide.
Connexion