@prologic@twtxt.net Hmm. 🤔

Okay, suppose you host a project using this new forge, and I want to send a pull request. What do I have to do?

@movq@www.uninformativ.de In the meantime tell me all your “wishes” and things you wish/want a good decent “pure” decentralised Git forge should do 😅

I am finally building a Twtxt / Yarn.social inspired Git forge. I’m actually quite confident that y’all will quite like it, but I won’t post links yet until I’m quietly confident in its design, functionality and behaviour(s).

Stay tuned 🤞 It’ll be like no other Git forge you’ve ever seen! 🤣 Actually, it’s already more like cgit than anything with plain text feeds that power it’s “pure decentralization” as you can no doubt imagine 😅 #twtxt #git #forge

@movq@www.uninformativ.de I am seriously rethinking and re-contemplating building a new Git forge of some description that avoids all of these stupid problems that we’re now seeing in the wild

@prologic@twtxt.net Oh, yes, just for clarity: This wasn’t a “pro GitHub” argument. 😅 I won’t go back there (or to another “forge”).

I think we’re totally on the same page: Decentralized Git hosting is good, but we haven’t solved the “collaboration” part yet. Or rather: We have to modernize it. The tools are already there, but (many) people don’t want to use them and think they’re clunky.

FOSS infrastructure is under attack by AI companies
What do SourceHut, GNOME’s GitLab, and KDE’s GitLab have in common, other than all three of them being forges? Well, it turns out all three of them have been dealing with immense amounts of traffic from “AI” scrapers, who are effectively performing DDoS attacks with such ferocity it’s bringing down the infrastructures of these major open source projects. Being open source, and thus publicly accessible, means these scrapers have … ⌘ Read more

The Six Platonic Solids
⌘ Read more