I mean sure if i want to run it over on my tooth brush why not use something that is accessible everywhere like md5? crc32? It was chosen a long while back and the only benefit in changing now is “i cant find an implementation for x” when the down side is it breaks all existing threads. so…

⤋ Read More

@movq@www.uninformativ.de i’m sorry if I sound too contrarian. I’m not a fan of using an obscure hash as well. The problem is that of future and backward compatibility. If we change to sha256 or another we don’t just need to support sha256. But need to now support both sha256 AND blake2b. Or we devide the community. Users of some clients will still use the old algorithm and get left behind.

Really we should all think hard about how changes will break things and if those breakages are acceptable.

⤋ Read More

@xuu being contrarian isn’t a problem. Having different opinions force us to think, and make—hopefully—better decisions. We shouldn’t, mustn’t be contrarians, tough, while not offering a viable path forward that makes sense. What I am saying is that after that “so…” of yours needs to come a (or a set of) tangible recommendation(s). 😉

⤋ Read More

@xuu Yes, of course. This has been blown out of proportion anyway. All I originally wanted to say is that the b2sum program isn’t very widely available.

It would help to know how many different clients there actually are. I suspect that number is very close to 3.

⤋ Read More

Participate

Login to join in on this yarn.