HackerTrans
TopNewTrendsCommentsPastAskShowJobs

delf

no profile record

Submissions

GitSocial

gitsocial.org
1 points·by delf·2 bulan yang lalu·1 comments

[untitled]

1 points·by delf·8 bulan yang lalu·0 comments

GitSocial - Decentralized social layer for Git repositories.

github.com
2 points·by delf·9 bulan yang lalu·1 comments

comments

delf
·bulan lalu·discuss
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
delf
·2 bulan yang lalu·discuss
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.
delf
·2 bulan yang lalu·discuss
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 :)
delf
·2 bulan yang lalu·discuss
You're welcome! I'm the creator of GitSocial, happy to answer any questions.
delf
·2 bulan yang lalu·discuss
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.
delf
·2 bulan yang lalu·discuss
Not if you do it over git itself on the existing forge. You basically store everything in git and federate via git forks/mirrors.
delf
·2 bulan yang lalu·discuss
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
delf
·2 bulan yang lalu·discuss
One approach is to keep it all in git itself, the way GitSocial does: https://gitsocial.org/
delf
·2 bulan yang lalu·discuss
GitSocial solves this: https://gitsocial.org/
delf
·2 bulan yang lalu·discuss
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.
delf
·2 bulan yang lalu·discuss
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).
delf
·3 bulan yang lalu·discuss
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
delf
·7 bulan yang lalu·discuss
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...
delf
·8 bulan yang lalu·discuss
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.
delf
·8 bulan yang lalu·discuss
[dead]
delf
·8 bulan yang lalu·discuss
[dead]
delf
·8 bulan yang lalu·discuss
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.
delf
·9 bulan yang lalu·discuss
Decentralized social layer for Git repositories.