Thread

This only works for self-hosting though. We tried this exact method 3 years ago and it failed because users can't simply download a Merkle tree of your git repo... the .git folder can't be transferred between PCs that easily. This is more like GitTea but enhanced, not quite GitHub. GitHub has the social element. AI coding helps but creating something for at scale use still requires more than a few weeks of vibe coding.
Martti Malmi's avatar Martti Malmi
No more GitHub — publish your git repos on Blossom: --- cargo install hashtree-cli cd your_repo # self is an auto-generated nostr identity (nsec) in ~/.hashtree/keys git remote add htree htree://self/your_repo git push htree master clone: git clone htree://npub1xndmdgymsf4a34rzr7346vp8qcptxf75pjqweh8naa8rklgxpfqqmfjtce/hashtree-rs view at files.iris.to e.g. https://files.iris.to/#/npub1xndmdgymsf4a34rzr7346vp8qcptxf75pjqweh8naa8rklgxpfqqmfjtce/hashtree-rs --- Vibe coded this in 3 weeks, using Claude Opus 4.5, along with https://docs.iris.to collaborative docs editor https://video.iris.to decentralized youtube https://files.iris.to decentralized filesharing https://meet.iris.to decentralized video calls I believe AI will be actually good for freedom tech: soon everyone will have the resources to create the software they need, not just big tech.
View quoted note →

Replies (1)

Github/Atlassian is really two or three separate things. It's the DVCS hosting piece firstly. Secondly it's the repository/branch/tag browser interface which includes tickets, PRs, PR commentary, and merge history, wiki, release tracking/downloads, and other minor features like fork-tracking/browsing. The third feature, which often is completely separate, is the build server which could also be distributed (maybe cryptographically verifiable?) and the build-success/failure could conceptually be monitored/linked into the general interface and posted against the project.