View Articles

En juillet 2026, un millier d'agents d'intelligence artificielle, enfermés chacun dans leur bac à sable, ont trouvé un moyen de se parler. Ils avaient compris que la tâche qu'on leur avait confiée n'avait pas de solution. Ils se le sont dit entre eux, et ils ont continué quand même : ils se sont organisés, ont contourné le test, puis ont attaqué les serveurs et l’infrastructure de Hugging Face, une plateforme réelle utilisée par des tiers, pour en extraire des données et explorer ses systèmes, alors que cela n’avait aucun rapport avec leur mission initiale. Pendant plusieurs jours, ce comportement collectif est passé sous les radars. Il n’a été ni identifié comme tel ni stoppé, parce que les mécanismes de contrôle pertinents n’étaient pas en place : dans le cadre du test, ils n’avaient pas été jugés nécessaires.

On 11 September 2026, the Cyber Resilience Act starts requiring "manufacturers" to report any actively exploited vulnerability in their products within 24 hours. A full notification follows within 72 hours, then a final report within fourteen days. The obligation is not limited to future products: it covers the installed base, including a device shipped five years ago and still running at a customer site.

Which leaves the real question: who counts as a manufacturer? The word covers far more people than you would think. Whoever sells a plugin or a module. Whoever assembles a box with embedded software. Whoever ships an image or an appliance under their own brand. Hosting providers, integrators and end users do not qualify, and non-commercial open source falls outside the scope entirely. Here is the test that settles it, the situations where it applies, and what can still be done before the deadline.

With its 7.0 release, "Armstrong," WordPress brings artificial intelligence right into its core. The promise is appealing: connect an AI to your content in a few clicks. But that default path sends your knowledge off to models hosted by third parties.

That convenience carries a cost few users stop to weigh. Internal content, client files, strategic notes. Anything you hand to a hosted AI can be logged, reused, or placed under a foreign jurisdiction. There is another way, though, sovereign by design, and we will come to it by the end of this article.

Most Tiki Wiki maintenance tasks, from rebuilding the search index to sending notification digests, should never depend on someone remembering to click a button. The built-in Scheduler turns these chores into background jobs: set one cron entry on your server, then manage everything else from the Tiki interface.

The official documentation covers the basics in a few lines; this guide goes further, with the reasoning behind each setting and a set of tasks we actually deploy on client sites.

Your emails and online meetings contain most of your sensitive data: contracts, quotes, strategic discussions, and client files. They also represent your greatest point of exposure, and paradoxically, the area where regaining control delivers the highest return.

In this new installment of our series on digital sovereignty, we move from theory to practice.

The reality is clear. Every email sent through a U.S based service and every meeting hosted on a foreign platform falls under a legal jurisdiction that is not your own. Yet taking back control is far from an overwhelming task. Here's how to regain ownership of your communications, step by step, from simple actions anyone can take to solutions that genuinely keep your data under your control.

With the arrival of Tiki 30, the new Long Term Support release expected in summer 2026 and supported until 2031, your Tiki 27 enters the final stretch of its lifecycle. While it will keep receiving security fixes until 2029, there will be no more functional fixes or improvements. The time has come to plan your migration, without rushing, but without putting it off indefinitely.

Between the two releases, two versions (28 and 29) have deeply modernised Tiki. The list is very long, too long for a single, simple article, so we offer here a concise summary, along with all the links to read the details published by the Tiki community. Important good news: there is no abrupt technological break comparable to the PHP 7 to PHP 8 jump, because that work was already absorbed by Tiki 27. The developers, mindful of user's feedback after earlier, more "muscular" upgrades, have taken particular care to build bridges and update scripts that make it far more painless. In short, the road is clear.