fiatjaf on Nostr: I was thinking that exposing files at exact commits would be simpler, but then I ...
I was thinking that exposing files at exact commits would be simpler, but then I realized that to get the exact commit you would need an API that returns all references and HEAD (separate from the repository state event) and then I realized that to build a GitHub-like way to browse files on gitworkshop you'll also need all these things, plus a history of commits, metadata about all commits and so on, right?
Which brings me back to: why not do a full repository clone on the browser and get all that data at once? Is it just the big size of things?
Published at
2024-09-03 00:57:48Event JSON
{
"id": "0000fb0c72a2ea872aa1f684026bf9d8e401a6a946e4d963e0a6d50f3bea09e8",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1725325068,
"kind": 1,
"tags": [
[
"client",
"gossip"
],
[
"p",
"a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d"
],
[
"p",
"8685ebef665338dd6931e2ccdf3c19d9f0e5a1067c918f22e7081c2558f8faf8"
],
[
"e",
"059aad0de51a1e9f6c9f7ff6169244af0bdd473234cd1b42c443af5049abdb62",
"wss://relay.damus.io/",
"root"
],
[
"e",
"34b1bf2fb6ad0ad3fbdf7afb53ffe7292e50219e9d986676aa948e42a7e2ddc5",
"wss://a.nos.lol/",
"reply"
],
[
"nonce",
"9223372036854779674",
"16"
]
],
"content": "I was thinking that exposing files at exact commits would be simpler, but then I realized that to get the exact commit you would need an API that returns all references and HEAD (separate from the repository state event) and then I realized that to build a GitHub-like way to browse files on gitworkshop you'll also need all these things, plus a history of commits, metadata about all commits and so on, right?\n\nWhich brings me back to: why not do a full repository clone on the browser and get all that data at once? Is it just the big size of things?",
"sig": "0ff57d8d49d08a0426135da92021c6e91b3e07974c1471a0a23ba11e48a3baa183ac46ae1fdafc66a50fa7b374684ca09329ca4b3072e24b8cff45856579eb91"
}