Random idea for the git distributer @Laeserin 🇻🇦:
publish conventional commits as nostr events. Make a Github/Gitlab app which can be treated as relay.
Webhook -> Ingest and sign -> Publish
et voila, you‘ve got notable Github commits in nostr.
Login to reply
Replies (3)
You mean, instead of the patch events?
What are patch events?
I‘m talking proprietary Github webhooks, e.g. 
A nostr messaging system could for example replace the current Chrome extension we have in place at our company (
and make it realtime. With a nostr relay in the middle, I can still hack my own client workflow.
GitHub Docs
Webhook events and payloads - GitHub Docs
Learn about when each webhook event occurs and what the payload contains.
GitHub
GitHub - renuo/github-pull-request-counter: A chrome extension to remove mental load when working with pull requests
A chrome extension to remove mental load when working with pull requests - renuo/github-pull-request-counter
she means using nostr as a transport in place of ssh or http
contextvm could cover that side and make use of the relay as middleman
using nostr event subscriptions instead of webhooks would be pretty neat. you could have a relay feed for the gitea or whatever instance that could update real time so you can just open the tab and see the latest activity.
nostr could also handle stuff like issue boards, kanban and other planning boards, and even collab document editors like gdocs but markdown/asciidoc and the extensions (for diagrams etc), there could be a slack-style threaded chat, the whole shebang. it fits perfectly with the requirements for an organisation dev suite.