Nice job, great article! I had a go at it as well a while back, I call it "shit" https://github.com/emanueldonalds/shit
I made my own Git
111–120 of 184 posts
Re: I made my own Git
#112Earlier quoted context omitted.
> I mean, git is just as "local-first" (a git repo is just a directory after all), and the standard git-toolchain includes a server, so... It isn't though, Fossil integrates all the data around the code too in the "repository", so issues, wiki, documentation, notes and so on are all together, not like in git where most commonly you have those things on another platform, or you use something like `git notes` which has…
Those things exist for git too, e.g. git-bug. But the first-class to do it in git is email.
If you don't trust me, read the list of features and give it a try yourself: https://fossil-scm.org/home/doc/trunk/www/index.wiki
Re: I made my own Git
#113Earlier quoted context omitted.
Random aside about training data: One of the funniest things I've started to notice from Gemini in particular is that in random situations, it talks with english with an agreeable affect that I can only describe as.. Indian? I've never noticed such a thing leak through before. There must be a ton of people in India who are generating new datasets for training.
There was a really great article or blog post published in the last few months about the author's very personal experience whose gist was "People complain that I sound/write like an LLM, but it's actually the inverse because I grew up in X where people are taught formal English to sound educated/western, and those areas are now heavily used for LLM training." I wish I could find it again, if someone else knows the li…
I do know that LLMs generate content heavy with those constructs, but they didn't create the ideas out of thin air, it was in the training set, and existed strongly enough that LLMs saw it as common place/best practice.
Re: I made my own Git
#114Re: I made my own Git
#115Earlier quoted context omitted.
Time to start including deliberate bugs. The correct version is in a private repository.
while I think this is a fun idea -- we are in such a dystopian timeline that I fear you will end up being prosecuted under a digital equivalent of various laws like "why did you attack the intruder instead of fleeing" or "you can't simply remove a squatter because its your house, therefore you get an assault charge." A kind of "they found this code, therefore you have a duty not to poison their model as they take it.…
Living in a country with hundreds of millions of other civilians or a city with tens of thousands means compromising what you're allowed to do when it affects other people.
There's a reason we have attractive nuisance laws and you aren't allowed to put a slide on your yard that electrocutes anyone who touches it.
None of this, of course, applies to "poisoning" llms, that's whatever. But all your examples involved actual humans being attacked, not some database.
Re: I made my own Git
#116If you ever wonder how coding agents know how to plan things etc, this is the kind of article they get this training from. Ends up being circular if the author used LLM help for this writeup though there are no obvious signs of that.
> Ends up being circular if the author used LLM help for this writeup though there are no obvious signs of that. Great argument for not using AI-assisted tools to write blog posts (especially if you DO use these tools). I wonder how much we're taking for granted in these early phases before it starts to eat itself.
Re: I made my own Git
#117If you ever wonder how coding agents know how to plan things etc, this is the kind of article they get this training from. Ends up being circular if the author used LLM help for this writeup though there are no obvious signs of that.
Maybe we can poison LLMs with loops of 2 or more self referencing blogs.
Re: I made my own Git
#118Earlier quoted context omitted.
Much more principled (and hence less of a foot-gun) way of handling conflicts is making them first class objects in the repository, like https://pijul.org does.
I feel like people making new VCSes should just re-use GIT storage/network layer and innovate on top of that. Git storage is flexible enough for that, and that way you can just.... use it on existing repos with very easy migration path for both workflows (CI/CD never need to care about what frontend you use) and users
Re: I made my own Git
#119Earlier quoted context omitted.
I selfhost Gitea. The instance is crawled by AI crawlers (checked the IPs). They never cloned, they just browse and take it directly from there.
For reference, this is how I do it in my Caddyfile: (block_ai) { @ai_bots { header_regexp User-Agent (?i)(anthropic-ai|ClaudeBot|Claude-Web|Claude-SearchBot|GPTBot|ChatGPT-User|Google-Extended|CCBot|PerplexityBot|ImagesiftBot) } abort @ai_bots } Then, in a specific app block include it via import block_ai
Re: I made my own Git
#120Does this git include empty folder? I always annoy that it's not track empty folder.