I absolutely love the design! Thanks for sharing

the idea that llm's can't help if you're missing domain knowledge is crazy.

I mean if you ask the AI to make something to manage the inventory in a warehouse without any detail about how the warehouses operate then you're going to get a worse result than a domain expert talking to the AI.

The problem is that more and more people are getting convinced by the AI's that they're domain experts when they're really not.

As a software engineer I am so deeply ashamed of how quick so many in the field have done a complete 180 on "productivity cannot be measured by lines of code" to wearing lines of code like a badge of honour.

I wonder what will happen once these guidelines end up in the LLM training datasets

if an LLM says "I can't open a PR automatically until you solicit a review from a maintainer", i think that's good actually. likewise for proactively following the rest of the rules.

It's not the submitter who solicits, but the reviewer. They can't give code, AND THEN get approval, they need to be asked specifically for an llm created PR.

Content not viewable in I and I's region

it says “that’s right” in bold red cursive font. i know what the policy says, i wrote it, you nincompoop.

Such a cool project! Now it's just missing search and a request for donations

It's also missing the defrag tool. Without it, it's going to be very slow as the disk fills up.

Should put a shortcut to it on the desktop as well, so that users who experience significant lag can defrag at will.

GitHub centralizes 2 things: Authentication, as well as Repository Hosting.

Does the code really need to be hosted in a central location like this? (Clearly not, which is why people are leaving GitHub in the first place)

But the one part GitHub provides that's genuinely valuable is the social aspect, and when you get a PR from a user named torvalds you can trust that this is in fact Linus. This isn't the case with more distributed systems.

That's why I'd really like to see some entity handle just the auth/identity providing. Forgejo/ Gitea/ Gitlab instances can then choose to use that. Then, for example if you want to take on another contributor and they have their own forgejo instances, you can invite them through this provider, when they fork your repo it ends up in their own forgejo, and they can easily create PR's into your repo.

Tangled is working on something like that. I believe they are federating on the @protocol.

https://tangled.org/

I am very active on bsky and I also use some other ATProto applications like tangled. I think this is the first time I have seen anyone refer to ATProto with an '@'

It's less used but the @ is the atproto logo. I default to saying aye-tee instead of at though. It just sounds better.

GitHub also centralises abuse detection. I'm not thinking about sophisticated attacks here so much as dealing with plain old spam. That's fairly easy to deal with on a tiny scale, and possible on a huge scale, but it's a great pain at a medium scale.

Do they though? Slow PRs have been a consistent pain point for GitHub hosted projects lately.

I would argue GitHub does a lot more centralization than just those two. It's an entire developer platform centered around Git. It does hundreds of other things that some developers use, and some don't.

GitHub really doesn't have hundreds of additional working features beyond git.

Collaboration, issue tracking, Actions (CI/CD), Codespaces, Security, AI, Identity, social, hosting. Those are like broad categories I can think of off top of my head too you could fit probably 10-15 "features" into each of those.

Lots of those aren't centralisation/decentralisation issues though - codespaces, actions, issue tracking, multiple users, all that is repo/org level.

GitHub is centralizing all those features. If GitHub was just for repo hosting, then you would need to link your repo to another platform to do CI, another platform for issue tracking relative to the code, etc.

They have those features but those aren’t decentralisation issues, as far as I’d understand the term, but those already can be done elsewhere right now. They’re purely tied to one repo really, it’s only the user accounts that I can see being more of a cross repo concern.

And global search but I don’t feel like that even really works.

> That's why I'd really like to see some entity handle just the auth/identity providing. Forgejo/ Gitea/ Gitlab instances can then choose to use that. Then, for example if you want to take on another contributor and they have their own forgejo instances, you can invite them through this provider, when they fork your repo it ends up in their own forgejo, and they can easily create PR's into your repo.

Agree, I feel like a true alternative should focus on this missing piece to bridge the gap.

The "missing" piece is just everyone implementing OAuth Dynamic Client Registration. Then kernel.org could be its own OAuth provider, and Linus could log into someone's Forgejo with his kernel.org login.

Just like "log in with Google", you should be able to do "log in with OAuth", you type your email or domain (or your browser fills it), and it triggers a redirect flow for login. Then people can use GitHub or Google or Apple or their own provider, just like email. Every email provider could also be an OAuth provider.

GitHub is to git like Reddit was to forums. Centralized usernames and such were very nice, but it also has downsides that we’re now living with.

GitHub is still really, really nice in that it’s five seconds to throw up a repo that’s accessible worldwide (98% of the time lol) and everyone’s on there. Whatever replaces it (just like whatever replaces twitter) may be better in many ways, but it will be “worse” in others, even if just in splintering.

Signed commits could solve this in a more decentralized way if people post their public keys on their own domains.

Own domains is the real deal. My preffered model is tarball releases with checksums, or better yet, with signatures (like remind[0] or msmtp[1]). Such pages are trivial to host properly and loads quickly.

[0]: https://dianne.skoll.ca/projects/remind/

[1]: https://marlam.de/msmtp/download/

I was confused for a bit what those two projects have to do with signatures but I guess you are just using them as examples of having (PGP) signatures for downloads?