#softwareheritage — Public Fediverse posts

As you may know I have been working for a while on a content-addressed language that I call Möbius (https://github.com/amirouche/mobius). Then, I dabbled, and I am proud to say I cracked the aphorism about John Shutt's Kernel, the one that goes "Kernel is impractical to compile". It is practical to compile when reified environments are immutable: https://github.com/amirouche/seed. Also, I have been working on the letloop distribution (https://github.com/amirouche/letloop) for Chez Scheme (https://github.com/cisco/chezscheme). Also, I dabbled with a new search engine (more about that another time).

I also have been writing a lot about Möbius, with good reason: it is exciting to hold so much in such a small substrate. I think I used to sell that too much, with too much grandiose machination, even if backed by code: no users yet. A lot of what Möbius promises is halfway delivered in bb.py (https://github.com/amirouche/bb.py) and bb.scm (https://github.com/amirouche/bb.scm). Most already exists in the wild by way of #scheme, #unison, #nixos and #softwareheritage.

It matters to underline: that line of work is neither new, nor disruptive, nor bullet-proof.

My goal was, and still is, to promote that sphere, and I am happy to share that the bus factor is honest.

Also, I don't want to let the idea spread that it is collapse-proof, unlike what #collapseos #duskos #permacomputing people try to achieve.

My goal is to fix the ship while flying it.

Tho Möbius, which will eventually be folded into #letloop, will not turn dirt into fresh water, or the fog into... a naziproof naziproof continuation that can be handed to the next generation...

That's why I poked holes in what you may have read in the previous articles, in a new essay entitled: What the hash cannot prove => https://hyper.dev/2026/mobius-what-the-hash-cannot-prove/#essay

Archiving software source code never waits... Even on holidays.

#SoftwareHeritage

I have spent a year telling you what a content-addressed commons can prove: authorship, priority, lineage. New essay: what it cannot prove. Cisneros burned five thousand manuscripts and kept the three hundred he had a use for, the filter, not the fire, is the enemy. https://hyper.dev/2026/mobius-what-the-hash-cannot-prove/ #mobius #scheme #unison #softwareheritage

600+ computer science papers. Only 40% of their software actually installs.
On August 21, Simon Tournier presents at RRPR 2026:
📄 "Reproducible computational environment: Archiving and beyond"
https://tc22-team.github.io/rrpr2026/program.html
#Guix #ResearchSoftware #Reproducibility #OpenScience #SoftwareHeritage

Preservation is only half the job. Making code accessible when you need it is the other.
🔗 Explore the Vault: https://docs.softwareheritage.org/devel/swh-vault/getting-started.html
#OpenSource #CodeRescue #SoftwareHeritage

29 billion unique source files. 438 million projects. One open archive. https://archive.softwareheritage.org
#OpenSource #SoftwareHeritage #DigitalPreservation #PublicCode

@dvzrv wtf. #softwareheritage to the rescue. You're right.

But in my ad-hoc check of 1.21-3.1 from swh snapshot 2020-02-08 it seems treesame. And the swh-referenced commits are in my clone from salsa just now. git log diff too copious to make sense of.

idk what prompted them to do this. I guess one could ask.

Much of Debian have a very ill-advised pattern of reusing version numbers &c, thinking apparently that things that don't make it to the ftp archive aren't real, or something. :-/

A look at the #SoftwareHeritage team during #UNOpenSource week.

Cc @swheritage

I just submitted Family Size VM to Software Heritage, which collects and preserves public Git repositories. It hasn't seen every repository, especially on Codeberg and other smaller Git hosts. Check if your own project is crawled and save it if it isn't yet.
https://archive.softwareheritage.org/

#SoftwareHeritage #Git #decentralization #preservation #FamilySizeVM #Codeberg

#SoftwareHeritage is recruiting!

Backend Engineer ⚙️ https://www.softwareheritage.org/2026/04/08/backend-engineer/

DevOps Engineer ⛏️ https://www.softwareheritage.org/2026/04/08/devops-engineer-2/

Internal Applications Manager 🧰 (Odoo/IT) - https://www.softwareheritage.org/2026/04/08/internal-applications-manager-odoo-it/

cc @swheritage

Everything you need to know about #SoftwareHeritage and why long-term preservation of source code matters is in @zacchiro interview here 👉 https://www.youtube.com/watch?v=R8kBztTivNw

cc @swheritage

@bertkoor @zimpenfish @fisharebest The Software Heritage Archive #softwareheritage has been crawling
github.com/fisharebest/webtrees for some time now:

https://archive.softwareheritage.org/browse/origin/visits/?origin_url=https://github.com/fisharebest/webtrees

The latest git commit archived is from Apr 24 and has permanlink https://archive.softwareheritage.org/swh:1:rev:a8d95ceb87651e17ade08efee7a3b8b35001603b

Source Code Exhibition explore le code comme œuvre d'art et témoignage historique. Découvrez Fortran, ELIZA, XMODEM. #SourceCodeExhibition #Tech #Histoire #PatrimoineNumérique #Inria #SoftwareHeritage ... https://www.linkedin.com/posts/gabriel-chandesris_sourcecodeexhibition-tech-histoire-ugcPost-7459595298152226816-3okl

#SoftwareHeritage, #Nix, and #Guix cited as tools to improve the #reproducibility of research artifacts:
https://cacm.acm.org/news/is-there-a-way-to-solve-the-reproducibility-problem/

Reading post: « Git mirror and #Nix flakes – a practical approach to supply chain security »

🤔 I’m not convinced that mirroring is “the Right Thing” here; it sounds to me as some “worse and holed is maybe better”.

Instead of mirrors for tackling the upstream troubles, it seems more elegant to have an archive that collects all the public code and then fallback to it when needed.

Guess what? #Guix does that using #SoftwareHeritage!

https://www.softwareheritage.org/2025/05/21/software-heritage-guix-deployment

https://blog.networld.to/git-mirrors-and-nix-flakes-a-practical-approach-to-supply-chain-security/

I wish people from #Codeberg and #Zenodo would collaborate to get the same clever integration features that allow people to preserve #GitHub releases at Zenodo. I bet people from the scientific community would like that. Is it too much to wish some big sciency inftrastructure group would fund this? ;-)

I'm going to archive stuff at Zenodo as I move out of GitHub.

Update - Tip from Ale Abdo: let's use #SoftwareHeritage !

#hopeful #FLOSS

📣 Hey, do you know that now #SoftwareHeritage implements SWHEP?

SWHEP: SoftWare Heritage Enhancement Proposals

Please checkout the two accepted first ones:

• Switching from ORC to Parquet for graph exports
• Paving the way for more versatile object storages by turning shards into mosaic

🤔 Still puzzled where are numbers 0002 and 0003. 🙃

https://gitlab.softwareheritage.org/swh/swhep/-/blob/dd2bddd99b6a8912c1ad21f7723480541356dc9d/swheps/0001.md
–
https://gitlab.softwareheritage.org/swh/swhep/-/blob/dd2bddd99b6a8912c1ad21f7723480541356dc9d/swheps/0004.md
https://gitlab.softwareheritage.org/swh/swhep/-/blob/dd2bddd99b6a8912c1ad21f7723480541356dc9d/swheps/0005.md

Via @aprilorg, @HenriVerdier : « J’aime bien le concept de #communs qui nous vient d’une autre tradition. Un commun numérique, a digital commons, c’est une ressource qui est cultivée par ses contributeurs et sa gouvernance est opérée par les gens qui contribuent. Ce sont, par exemple #wikipedia #openstreetmap #softwareheritage ces grandes ressources avec beaucoup de contributeurs et dont le destin est décidé par les contributeurs. »

https://www.librealire.org/l-ia-a-rendu-tout-le-monde-dingue-henri-verdier

Bonne lecture !

The « Software Source Code Exhbition », co-curated by Mathilde Fichen from @swheritage, is now on display at Cité des Sciences et de l'Industrie, the most prominent science museum in #Paris, France.

https://www.cite-sciences.fr/fr/au-programme/lieux-ressources/carrefour-numerique2/evenements/source-code-exhibition

It's until March 25th, 2026 and in the free part of the museum, no ticket needed.

If you are around and into software, I recommend visiting it, as it's super super fascinating.

#SoftwareHeritage #DigitalPreservation

"In 2026, Software Heritage is celebrating its 10th anniversary. To mark this milestone, Software Heritage and [the INRIA] have decided to set up a special display: a Source Code Exhibition."
https://www.sourcecode-exhibition.softwareheritage.org/introduction/
Most of the art pieces art cool, go see them!

I’m still disappointed that they only considered *procedural* code, and desk-rejected *declarative* code. This is a sad editorial misunderstanding of what "source code" is :-(

#code #art #inria #softwareHeritage

Welcoming @benhermann at #SoftwareHeritage headquarters today, to talk about « What We Learned in 15 Years of #ArtifactEvaluation » #research #digitalpreservation #softwareEngineering

« there are the systemic drivers:

• FAIR data mandates from funders
• Open-lab notebook movements
• Persistent Identifier (PID) expansion into every layer of research
• Preprint-to-publication workflows that treat research as a continuum

All of these point toward a future where the “unit of science” is no longer a PDF but a rich, evolving digital object grounded in data, workflows, and provenance. »

🧐 Guess what?

‣ #Guix and #Nix are designed around Persistent IDentifier (PID) for dealing with reproducible computational environments.

‣ Software Hash IDentifier (#SWHID) proposed by #SoftwareHeritage folk provides a Persistent IDentifier (PID) for source code.

https://scholarlykitchen.sspnet.org/2026/02/05/back-to-the-article-of-the-future-an-interview-with-sami-benchekroun-and-rod-cookson/
#ReproducibleResearch #OpenScience
2/3

« #SoftwareHeritage expands mirror network to Spain »

These distributed nodes are designed to ensure data redundancy and load distribution, protecting the archive’s accessibility against technical, commercial, or geopolitical disruptions.

https://www.softwareheritage.org/2026/02/05/software-heritage-mirror-network-spain/
#SWH #OpenSource #ReproducibleResearch

At #FOSDEM this weekend? Find us in building K on Sunday—we'll be hanging out and talking about how to archive & protect your work for the long haul.
#FOSS #OpenSource #SoftwareHeritage #coderescue

Thanks @swheritage for this #SoftwareHeritage symposium.

Great day! Nice program with speakers from a wide range of expertise sharing their perspectives. 🤩

Fruitful discussions around. 👍

Interesting Source Code Exhibition; my favorite: story of Git Stash. 🧐

Last but not least, cherry on the top: yeah the cake! 🥳

Thank you!

https://www.sourcecode-exhibition.softwareheritage.org/in-case-of-emergency-git-stash

#SWH2026

#SoftwareHeritage a 10 ans