On Feb 26, 2017, at 2:34 PM, Richard Hipp <d...@sqlite.org> wrote: > > On 2/23/17, Warren Young <war...@etr-usa.com> wrote: >> >> I think Fossil is in a much better position to do this sort of migration >> than, say, Git, due to its semi-centralized nature. > > it is reasonable to argue that Git(Hub) is more centralized than > Fossil.
Yes, but that’s my point: because so many people use Git in conjunction with some large service with many users — not just GitHub, but also BitBucket, visualstudio.com, etc. — they can’t as easily change a hash algorithm like this because cutting off “only” some small percentage of users means annoying many thousands of users. Whereas with Fossil, few Fossil instances host many Fossil repositories, so that the number of users affected by any decision to upgrade to a better hash algorithm affects few enough people that in many cases, they can all be contacted personally to coordinate the upgrade. GitHub may have the power to declare a flag day[1] but imagine the hue and cry if they tried! Thus, Git is going to have a very hard time moving away from SHA1. [1]: https://en.wikipedia.org/wiki/Flag_day_(computing) _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
