HackerTrans
トップ新着トレンドコメント過去質問紹介求人

delf

no profile record

投稿

GitSocial

gitsocial.org
1 ポイント·投稿者 delf·2 か月前·1 コメント

[untitled]

1 ポイント·投稿者 delf·8 か月前·0 コメント

GitSocial - Decentralized social layer for Git repositories.

github.com
2 ポイント·投稿者 delf·9 か月前·1 コメント

コメント

delf
·先月·議論
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 か月前·議論
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 か月前·議論
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 か月前·議論
You're welcome! I'm the creator of GitSocial, happy to answer any questions.
delf
·2 か月前·議論
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 か月前·議論
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 か月前·議論
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 か月前·議論
One approach is to keep it all in git itself, the way GitSocial does: https://gitsocial.org/
delf
·2 か月前·議論
GitSocial solves this: https://gitsocial.org/
delf
·2 か月前·議論
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 か月前·議論
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 か月前·議論
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 か月前·議論
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 か月前·議論
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 か月前·議論
[dead]
delf
·8 か月前·議論
[dead]
delf
·8 か月前·議論
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 か月前·議論
Decentralized social layer for Git repositories.