Four prevailing themes in the discussion
| # | Theme | Key points & representative quotes |
|---|---|---|
| 1 | Fossil vs. Git – feature set & “local‑first” philosophy | “I really enjoy how local‑first it is, as someone who sometimes work without internet connection.” – embedding‑shape “Fossil integrates all the data around the code too in the 'repository', so issues, wiki, documentation, notes and so on are all together.” – embedding‑shape “Git is just as 'local‑first' (a git repo is just a directory after all), and the standard git‑toolchain includes a server, so…” – usrbinbash |
| 2 | Git internals & performance trade‑offs | “Git uses SHA‑1, which is an old and cryptographically broken algorithm… Git is considering switching to SHA‑256.” – b1temy “The bottleneck with git is actually the on‑the‑fly packfile generation.” – storystarling “sha256 is a very slow algorithm… BLAKE3 would probably make a noticeable performance difference.” – jrockway |
| 3 | AI/LLM training data scraping & privacy | “I feel weird to think that LLMs are being trained on my code.” – TonyStr “The instance is crawled by AI crawlers… they never cloned, they just browse and take it directly from there.” – Phelinofist “Blocking AI bots on my server… it’s the only thing I had to block to stay sane.” – Zambyte |
| 4 | Re‑implementing Git / learning by building a VCS | “Nice work, it's always interesting to see how one would design their own VCS from scratch.” – b1temy “I love how local‑first it is… I use Fossil for personal projects.” – embedding‑shape (also shows why people try it) “There are tutorials like CodeCrafters and Jon Gjengset’s Rust challenge that make you rebuild Git.” – gkbrk |
These four threads—Fossil’s integrated workflow, Git’s low‑level mechanics, concerns over AI training data, and the educational value of building a VCS—dominate the conversation.