Hacker Newsnew | past | comments | ask | show | jobs | submit | delf's commentslogin

Not if you do it over git itself on the existing forge. You basically store everything in git and federate via git forks/mirrors.

One approach is to keep it all in git itself, the way GitSocial does: https://gitsocial.org/

GitSocial solves this: https://gitsocial.org/

GitSocial allows cross-forge collaboration without any 3rd party dependencies as it keeps everything in git: <https://github.com/gitsocial-org/gitsocial/blob/main/documen...>

Git IS the federation layer in this case.


How do you authenticate the identity when people are submitting patches between two repositories running on two different servers?

There's a federated identity spec and implementation: https://github.com/gitsocial-org/gitsocial/blob/main/documen.... For GH/GL, just an api call to verify signature, for custom domains, it's .well-known/gitmsg-id.json

GitSocial is a cross-forge collaboration platform that allows you to store all collaboration data (issues, PRs, releases, etc) as git commits with structured trailers on gitmsg/* branches, syncing via git fetch and git push.

This allows you to stay independent from forges and to collaborate across them (open issues and PRs across forges).


Creator of GitSocial here, check it out if you'd like to have better control of your data and be protected from such things: https://github.com/gitsocial-org/gitsocial

I built GitSocial that allows you to bypass Twitter/Bluesky in favor posting and following straight in your repository: https://github.com/gitsocial-org/gitsocial.

Similarly, VS Code extension is at: https://marketplace.visualstudio.com/items?itemName=gitsocia...


I'm working on GitSocial - decentralized open source social network built entirely on Git.

https://gitsocial.org/

Think of it as tool that can turn any repository into a blog/social network in place.


The outage impacted GitSocial minor version bump release: https://marketplace.visualstudio.com/items?itemName=GitSocia...

There's no way to tell, and after about 30 minutes, the release process on VS Code Marketplace failed with a cryptic message: "Repository signing for extension file failed.". And there's no way to restart/resume it.


Decentralized social layer for Git repositories.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: