this post was submitted on 02 Oct 2026
85 points (96.7% liked)

Programming

28764 readers
452 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
85
Github co-creator & Pro Git author skewers Git 3.0's SHA-256 move (blog.gitbutler.com)
submitted 1 week ago by tetrislife@leminal.space to c/programming@programming.dev
23 comments fedilink hide all child comments
 

In a well-fleshed-out post, Scott Chacon shows how unneecessary Git 3.0's move to replace SHA-1 with SHA-256 is.

you are viewing a single comment's thread
view the rest of the comments
[–] panda_abyss@lemmy.ca 6 points 1 week ago (1 children)

I would have thought they’d prefix the hash with “sha256-“ or something, or even just 256 prefix the hash.

[–] setsubyou@lemmy.world 35 points 1 week ago

They have different fixed lengths, no prefix needed to tell them apart.