Oddbean new post about login | logout Patches are crap — the commit hash isn’t preserved. Don’t waste your time.
The commit hash can be preserved if you set the commiter and gpg signature.
I find it disheartening that you are actively discurraging, @Karnage, a valued contributor from working on my project. If you read NIP-34 you would known that it enables preserving the commit hash. Let's work together constructively as a community towards the future we want to live in rather than FUDing each others projects. We share the same goal right?
Told this to @Karnage in private. Is pathetic that someone that hasn't even read the spec is toxic towards people working on it. I hope @Karnage gets excited by the project and keeps contributing.
When a git server applies a Git Patch, the commit hash within the server’s git tree is changed so that it does not match the commit hash within the user’s git tree. Patches cannot ensure that the git tree is replicated perfectly across every git server. NIP-34 includes the commit hash in a JSON, which is rather trivial compared to reassembling the git tree in a way that is perfectly consistent across every server it is hosted on. On GitNestr, the user’s git tree is completely identical to the git tree hosted on each git server — down to every last commit hash. https://v.nostr.build/ml9QQ.mp4