Création de Christophe Lemoine, le site tiquettes.fr propose simplement de construire et d’imprimer en PDF les étiquettes nécessaires pour habiller correctement votre tableau électrique. Un outil fort pratique si vous voulez un affichage des différents disjoncteurs parfaitement lisible.

Respectant la norme électrique NFC 15-100 (ainsi qu’un œil sur la norme RGIE Belge), le site propose une aide précise et efficace pour développer des étiquettes normalisées faciles à comprendre et à identifier. La mise en page des éléments est automatisée et l’ajout des différents modules crée en parallèle un schéma unifilaire correspondant pour plus de lisibilité. La nomenclature est également proposée et tout est fait pour vous aider à imprimer l’étiquette la plus « efficace » possible pour identifier rapidement le circuit à manipuler.

Tiquettes.fr est simple, précis, gratuit, documenté et lisible

Le site rappelle que la norme exige que chaque disjoncteur soit correctement étiqueté, avec la mention du type de circuit – souvent via un symbole – et la pièce desservie. Cela permet à un tiers (électricien, assureur, pompier) d’intervenir aisément sur l’installation comme à des membres du foyer de pouvoir réinitialiser un circuit après un court-circuit. Le site est très bien fichu, totalement gratuit, permet de commencer un tableau neuf et de le sauvegarder sur votre PC.

La documentation permet une prise en mains rapide d’un projet et le côté Opensource permet d’accéder à ses entrailles techniques sur Github. 

Tiquettes ne fait pas de publicité et ne conserve pas de données. Si vous le souhaitez, vous pouvez faire un don à son créateur via sa page Ko-fi

Merci à Renaud pour l’info.

Tiquettes.fr : faites vos tableaux électriques en OpenSource © MiniMachines.net. 2026

The free/open source project OrcaSlicer is a popular fork of 3D printer slicing software from Bambu Lab. But Tuesday independent developer Pawel Jarczak shuttered the project "following legal threats from Bambu Lab," reports Tom's Hardware: Jarczak's fork of OrcaSlicer would have allowed users to bypass Bambu Connect, a middleware application that severely limits OrcaSlicer's access to remote printer functions in the name of security. Jarczak said in a note on GitHub that Bambu Lab threatened him with a cease and desist letter and accused him of reverse engineering its software in order to impersonate Bambu Studio. From Bambu Lab's blog post: Bambu Studio is an open-source project under the AGPL-3.0 license. Anyone can take its code, modify it, and distribute it... That's what OrcaSlicer does, and 734 other forks do as well. We have no issue with that and never have. At the same time, a license for code is not a pass to our cloud infrastructure... Our cloud is a private service. Access to it is governed by a user agreement, not the AGPL license... [T]he modification in question worked by injecting falsified identity metadata into network communication. In simple terms: it pretended to be the official Bambu Studio client when communicating with our servers... If this method were widely adopted or incorrectly configured, thousands of clients could simultaneously hit our servers while impersonating the official client. "User-Agent is not authentication," counters OrcaSlicer's developer. "It is only self-declared client metadata. Any program can set any User-Agent." And "the User-Agent construction comes directly from Bambu Lab's own public AGPL Bambu Studio code.... So on what basis can anyone claim that I am not allowed to use this specific part of AGPL-licensed code under the AGPL license...? My work was based on publicly available Bambu Studio source code together with my own integration layer." But the bottom line is that Bambu Lab "contacted me directly and demanded removal of the solution." I asked whether I could publish the private correspondence in full for transparency. That request was refused... They also referred to legal materials and stated that a cease and desist letter had been prepared... I removed the repository voluntarily. That removal should not be interpreted as an admission that all legal or technical allegations made against the project were correct. I removed it because I have no interest in maintaining a prolonged dispute around this particular implementation, and no interest in continuing to distribute it. YouTuber and right-to-repair advocate Louis Rossmann reviewed the correspondence from Bambu Lab — then pledged $10,000 for legal expenses if the developer returned his code online. ("I think that their legal claim is bullshit," Rossman said Saturday in a YouTube video for his 2.5 million subscribers. "I'm not a lawyer, but I'm willing to put my money where my mouth is.") The video now has over 129,000 views so far. "Rossman has not started a crowdfunding site yet," Tom's Hardware notes, "stating in the comments that he wants to prove to Jarczak that he has supporters willing to put their money where their mouth is. The video had over 129,000 views so far, with commenters vowing to back the case as requested."

Read more of this story at Slashdot.

Under the nonprofit Linux Foundation, "a new Sustaining Package Registries Working Group will seek to identify concrete funding, governance, and security practices," reports ZDNet, "to keep code flowing as download counts grow.... Because software builds, continuous integration pipelines, and AI systems hammer registries at machine speed rather than human speed, the sites can't keep up. "That growth has brought a surge in bot traffic, automated publishing, security reports, and outright abuse, exposing what the working group bluntly calls a 'sustainability gap'." Sonatype CTO Brian Fox, who oversees the Maven Central Java registry, estimates open-source registries saw 10 trillion downloads in 2025. And "The same pattern is appearing across ecosystems. More machine traffic. More automation. More scanning. More expectations around uptime, integrity, provenance, and policy enforcement. More cost. More support burden. More dependency on infrastructure that the industry still talks about as though it runs on goodwill and spare time." ZDNet reports that "To tackle that, Sonatype has teamed up with the Linux Foundation and other package registry leaders, including Alpha-Omega, Eclipse Foundation (OpenVSX), OpenJS Foundation, OpenSSF, Packagist, Python Software Foundation, Ruby Central (RubyGems), and the Rust Foundation (Crates)." The idea is to give operators a neutral forum to discuss money, governance, and shared operational burdens openly. Once that's dealt with, they'll coordinate how to explain those realities back to companies and organizations that have long assumed registries are "free." No, they're not. They never were. As the Linux Foundation pointed out, "Registries today run primarily on two things: (1) infrastructure donations and credits; and (2) heroic efforts from small paid teams (themselves funded by donations and grants) and unpaid volunteers that operate and maintain registry services. The bulk of donations and grants comes from a small set of donors and doesn't scale with demands on the registry." The working group is explicitly positioned as a venue where registry leaders and ecosystem stakeholders can align on "practical, community-minded" ways to sustain that infrastructure, rather than each operator improvising its own survival plan in isolation. ZDNet says the group will also coordinate security practices and information, and craft frameworks "that make it politically and legally possible to introduce sustainable funding models without fracturing communities." And they will also "align messaging and educational content so developers, companies, and policymakers finally understand what it costs to run these services."

Read more of this story at Slashdot.

An anonymous reader quotes a report from Ars Technica: Several times in the last couple of decades, Microsoft has released source code for the original MS-DOS operating system that kicked off its decades-long dominance of consumer PCs. This week, the company has reached further back than ever, releasing "the earliest DOS source code discovered to date" along with other documentation and notes from its developer. Today's source release is so old that it predates the MS-DOS branding, and it includes "sources to the 86-DOS 1.00 kernel, several development snapshots of the PC-DOS 1.00 kernel, and some well-known utilities such as CHKDSK," write Microsoft's Stacey Haffner and Scott Hanselman in their co-authored post about the release. [...] This source code is old enough that it hadn't been stored digitally. "A dedicated team of historians and preservationists led by Yufeng Gao and Rich Cini," calling itself the "DOS Disassembly Group," painstakingly transcribed and scanned in code from paper printouts provided by Paterson. This process was made even more difficult because modern OCR software struggled with the quality of the decades-old printout.

Read more of this story at Slashdot.

Kdenlive 26.04, c’est l’aboutissement d’un gros chantier visant à stabiliser le logiciel, lui apporter des évolutions techniques, une interface plus lisible et améliorer son utilisation. C’est l’occasion de découvrir cet outil disponible aussi bien sur Windows, Linux ou MacOS, totalement gratuit et probablement suffisant pour la majorité des utilisateurs.

Kdenlive est un produit très complet, capable de prendre en charge de nombreux codecs sur du multipiste audio et vidéo. Il propose de nombreux effets et transitions, permet de configurer celles-ci et donc de sauvegarder les vôtres. Il propose la génération de titres, l’insertion d’images et même l’automatisation de montage à partir de répertoires. Toute l’interface peut s’adapter à vos besoins, des raccourcis clavier pour correspondre à d’autres habitudes jusqu’à la gestion de l’habillage et des barres d’outils. Le logiciel sait même travailler pendant que vous effectuez un rendu ou utiliser une machine différente pour calculer des éléments très lourds en UltraHD par exemple. De la documentation, des guides et des forums sont disponibles pour appréhender l’outil en profondeur.

Kdenlive permet dans cette version 26.04 d’utiliser un second moniteur pour passer l’image sur laquelle vous travaillez en plein écran. Il offre de nouveaux effets et de nouvelles transitions avec la prise en charge du glisser-déposer.

Les transitions proposent désormais de petites animations qui permettent de voir exactement à quoi elles correspondent. Un détail qui fait gagner du temps à l’utilisateur qui n’aura plus forcément à se souvenir précisément de la différence entre des fonctions aux noms très proches. Le logiciel sait également ajuster automatiquement la longueur des transitions en fonction de chaque clip dans la timeline ou agrandir la durée de clips sélectionnés ensemble.

Une meilleure gestion de la partie montage avec la prise en charge de fonctions de navigation avancées est désormais proposée. La sélection à la souris, le zoom ou le déplacement en utilisant la molette peuvent désormais être effectués à la volée. Des éléments assez standards que l’on retrouve dans les outils majeurs du secteur mais qui n’étaient pas forcément la priorité de Kdenlive jusqu’alors. Un autre gros chantier a été une meilleure prise en charge de système de capture audio externe avec une adaptation des options proposées aux possibilités réelles offertes par le matériel. Enfin, une meilleure gestion des sous-titres et de leur ajustement est proposée.

Enfin, une série de détails ont été mis à jour : la gestion de la fonction undo est plus claire, les montages en 1366 × 768 pixels sont disponibles dans les profils de projets, une meilleure gestion de la file d’attente des projets à rendre est proposée, des fonctionnalités supplémentaires de gestion de marqueurs d’aide au montage sont proposées et beaucoup d’autres détails comme la disparition du curseur sur le rendu d’une vidéo plein écran après 2 secondes d’inactivité.

Kdenlive pour les petites configurations et les grands projets

Bref, si vous êtes à la recherche d’un logiciel de montage vidéo gratuit, complet, ouvert et peu gourmand, Kdenlive vaut le coup d’être essayé. Le logiciel peut être téléchargé de manière classique avec une installation sur le système, mais également de manière « portable » ce qui autorise une exploitation directe, sans installation. Il est également fort peu gourmand avec la possibilité de monter des vidéos en 480P dès 4 Go de mémoire vive, une carte graphique OpenGL 2.0 ou DirectX 9 ou 11 et un processeur un cœur à 2 GHz. Pour des vidéos de plus grande définition, ces éléments changent évidemment mais restent légers : 16 Go de mémoire et une puce 8 cœurs suffisent pour monter en UltraHD. C’est le cas de nombreux MiniPC.

Le téléchargement se passe ici vous pouvez faire un don pour le développement du logiciel par là.

Kdenlive 26.04 est dispo, montez vos vidéos en Open source © MiniMachines.net. 2026

Nextcloud joined a project to create a sovereign replacement for Microsoft Office called "Euro-Office". But after that project forked OnlyOffice, OnlyOffice suspended its partnership with Nextcloud. "They removed all references to our brand/attribute as required by our license," argued OnlyOffice CEO Lev Bannov on March 30th. ("The core issue here isn't just about what the AGPL license states, but about the additional provisions we, as the authors, have included... If the Euro-Office team believes our approach conflicts with the AGPLv3 license, we invite them to submit an official request to FSF for review.") But this week the FSF responded (as "the steward of the GNU family of General Public Licenses"), criticizing OnlyOffice's "attempt to impose an additional restriction on the AGPLv3" and calling it "inconsistent with the freedoms granted by the license," in a blog post from FSF licensing/compliance manager Krzysztof Siewicz: It is possible to modify the (A)GPLv3 with additional terms, but only by adhering to the terms of the license... The (A)GPLv3 makes it clear that it permits all licensees to remove any additional terms that are "further restrictions" under the (A)GPLv3. It states, "[i]f the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term"... We urge OnlyOffice to clarify the situation by making it unambiguous that OnlyOffice is licensed under the AGPLv3, and that users who already received copies of the software are allowed to remove any further restrictions. Additionally, if they intend to continue to use the AGPLv3 for future releases, they should state clearly that the program is licensed under the AGPLv3 and make sure they remove any further restrictions from their program documentation and source code. Confusing users by attaching further restrictions to any of the FSF's family of GNU General Public Licenses is not in line with free software. "If FSF determines that our license and project align with AGPLv3, we will continue as an open-source initiative," OnlyOffice's CEO had written in March. "However, if the decision goes against us, we are ready to consider other options."

Read more of this story at Slashdot.