Yeah this definitely feels like a Python 2/3 type situation. They solved one minor issue but require the whole world to update.
I'm not even convinced they couldn't have done it in a backwards compatible way. Why not stick with SHA-1 but also add SHA-256 for verification for clients that support it?
> Why not stick with SHA-1 but also add SHA-256 for verification for clients that support it?
Apparently you can do that with 'hybrid' magnet links.
The problem is the two swarms are different so as more people move over to v2 the v1 swarms will become smaller and smaller -- thus giving people an incentive to upgrade, I suppose.
...and they seem to have solved more than one minor issue since they were breaking things anyway...
I'm not even convinced they couldn't have done it in a backwards compatible way. Why not stick with SHA-1 but also add SHA-256 for verification for clients that support it?