delf

GitSocial needs just git and object store, nothing else.

No, I was not! GitSocial originally, in Jan 2025, started as a Twitter/Bluesky over git app (as a VSCode extension with just social features), and then pivoted to being a full-fledged git platform, to include issues, PRs, releases, etc. You can still "follow" repositories though!

Artifacts is a vendor lock-in, as you can't easily migrate. Much better alternative would be git being able to pull and push to object storage natively.

Author of GitSocial here. It is now possible to break most hosting dependencies by using such tools as Walgit or GitSocial to store all collaboration data in git itself and pushing it all to an S3-compatible bucket. https://gitsocial.org/ is hosted on an R2 bucket. Cross-forge, cross-bucket collaboration is built in to it, further decentralizing hosting. Happy to answer any questions!

Will do it going forward. Thank you for the feedback!

Git-bug looks amazing! Author of GitSocial here, would love to hear your opinion:

https://gitsocial.org/

You can use GitSocial to mirror to your own bucket for situations like this: `gitsocial mirror https://gitlab.com/owner/repo s3://s3.example.com/mybucket/repo`

https://gitsocial.org/

Not that I know of as I don't have a way track this. I did test importing and mirroring everything for Ghostty and Meshtastic projects, found out that initial import and push steps may take a while.

Great to have issues, PRs, etc in git, but requires each participant to set up a fork to participate.

No CI though, but an extension to capture job logs is on the roadmap.

This is exactly what GitSocial does: https://gitsocial.org/. Plus it can generate static sites for repositories, letting you serve it all from a bucket.

I'm working on CLI/TUI tool that stores all code collaboration (issues, PRs, etc) in git itself. It lets you publish repositories as static sites to S3 buckets and use them as remotes:

https://gitsocial.org/ https://github.com/gitsocial-org/gitsocial

You can use GitSocial CLI to push git repositories straight to S3 without any dependencies: https://gitsocial.org/.

The buckets then are actual remotes and double as static sites. GitSocial website itself is hosted on Cloudflare R2.

Or just store it in an S3 bucket with GitSocial: https://gitsocial.org/

Or just push to an S3 bucket with `gitsocial mirror <s3>`

Creator of GitSocial here: it's a Go binary CLI/TUI that lets you store all your issues, PRs, etc. in the git itself and self-host on any S3-compatible bucket: https://gitsocial.org/.

On more detailed level, it allows forgeless issue management, cross-forge PRs, git-native discussions, and much more.

It has not dependencies, just git itself. Happy to answer any questions!

I created GitSocial, it stores issues, PRs, etc straight in git. Works on any git forge and allows cross-forge PRs and collaboration in general.

https://github.com/gitsocial-org/gitsocial

If you would like less dependence on GitHub for issues and PRs, please check out GitSocial, it stores everything in git itself, making them portable and offline-first.

Discovery is still in the works, but the core idea is that all collaboration data is stored in git itself (be that the project or a fork). It's git all the way down :)

You're welcome! I'm the creator of GitSocial, happy to answer any questions.

In "What I gave up" section author mentions his social graph. It is possible to take your social graph and collaboration history using GitSocial. It also allows cross-forge pull requests between any git hosts. All without 3rd party dependencies.

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

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

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.

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

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.