My brain feels like exploding.

0d97beae567fcec9...

npub1pktmatjk0l8vn3jhfuwxaasjd65kn4ye9sce3egup7k993f8fg2q5tpxa6

hex

14a6a5434a6081095eed1b23762b89c6b1e882db32807bce641bf34a0bfe3e39

nevent

nevent1qqspff49gd9xpqgftmk3kgmk9wyudv0gstdn9qrmeejphu62p0lruwgprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsqm9a74et8lnkfcet578rw7cfxa2tf6jvjcvvcu5wqltzjc5n559qd59xmh

Kind-1 (TextNote)

2026-03-08T19:35:58Z

↳ 回复 事件不存在

05576ea4847e4defe2ebba0df3d4607b97457a4da91493d88dcea5eebc584829...

My brain feels like exploding.

I get that nostr is the source of truth for allowing a repo to be created, and ngit uses hooks, what is another implementation I can look at for http based auth?

Then for pushes, there seems to be 2 methods of pushing afaik:

Post a patch to nostr (kind of curious how author is determined here and/or if there can be signed commits)

Post a pr reference to nostr and push to a /ref/nostr/ branch. So then I guess the git server will merge or move the commits to the right branch?

And then I see there is the permission under the spec to block spam, but no guides on how to identify it.

I think seeing a http implementation would help me here.

And maybe a chat after that if you have time.

FYI; I just set up a custom homelab, everything defined in ansible and backups etc. and am looking to finally expand it with some nostr services.

But first I wanted to host a git server and I wanted to make sure it is compatible with ngit so I can use it over nostr.

I just need to understand how it is protected against malicious actors before making a public git server.

原始 JSON

{
  "kind": 1,
  "id": "14a6a5434a6081095eed1b23762b89c6b1e882db32807bce641bf34a0bfe3e39",
  "pubkey": "0d97beae567fcec9c6574f1c6ef6126ea969d4992c3198e51c0fac52c5274a14",
  "created_at": 1772998558,
  "tags": [
    [
      "alt",
      "A short note: My brain feels like exploding.\n\nI get that nostr i..."
    ],
    [
      "e",
      "9676ce208874815e064d868db9a200de0b3b00a2141d5235dfc0e0ed2bc7f47e",
      "wss://nos.lol/",
      "root",
      "0d97beae567fcec9c6574f1c6ef6126ea969d4992c3198e51c0fac52c5274a14"
    ],
    [
      "e",
      "05576ea4847e4defe2ebba0df3d4607b97457a4da91493d88dcea5eebc584829",
      "wss://relay.damus.io/",
      "reply",
      "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d"
    ],
    [
      "p",
      "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d",
      "wss://relay.damus.io/"
    ],
    [
      "p",
      "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d",
      "wss://relay.damus.io/"
    ],
    [
      "p",
      "0d97beae567fcec9c6574f1c6ef6126ea969d4992c3198e51c0fac52c5274a14",
      "wss://nos.lol/"
    ]
  ],
  "content": "My brain feels like exploding.\n\nI get that nostr is the source of truth for allowing a repo to be created, and ngit uses hooks, what is another implementation I can look at for http based auth?\n\nThen for pushes, there seems to be 2 methods of pushing afaik:\n\nPost a patch to nostr (kind of curious how author is determined here and/or if there can be signed commits)\n\nPost a pr reference to nostr and push to a /ref/nostr/ branch. So then I guess the git server will merge or move the commits to the right branch?\n\nAnd then I see there is the permission under the spec to block spam, but no guides on how to identify it.\n\nI think seeing a http implementation would help me here.\n\nAnd maybe a chat after that if you have time.\n\nFYI; I just set up a custom homelab, everything defined in ansible and backups etc. and am looking to finally expand it with some nostr services.\n\nBut first I wanted to host a git server and I wanted to make sure it is compatible with ngit so I can use it over nostr.\n\nI just need to understand how it is protected against malicious actors before making a public git server. ",
  "sig": "23b347d1a6ef19ffacb37ed31e72e44131c278036e65902f44ef4ef300de8280b46d77906e38cc014f5f132b3280a195d3fcf1d2a565b0838f410167adf21885"
}