Currently if I go in and edit the translations of an OONI Run v2 descriptor or the copy it will bump the version number, triggering a notification saying the run link has changed.
This is a bit suboptimal as it will mean users that have installed an OONI Run v2 link will get spammed with notifications asking them to re-confirm it while the nettests haven't changed.
We discussed with @FedericoCeratto of splitting this out into two separate version numbers or potentially even having a different API for serving localization text that following a different versioning scheme.
This would also allow sending updates to probe users for things like unreliable / broken tests etc.
Currently if I go in and edit the translations of an OONI Run v2 descriptor or the copy it will bump the version number, triggering a notification saying the run link has changed.
This is a bit suboptimal as it will mean users that have installed an OONI Run v2 link will get spammed with notifications asking them to re-confirm it while the nettests haven't changed.
We discussed with @FedericoCeratto of splitting this out into two separate version numbers or potentially even having a different API for serving localization text that following a different versioning scheme. This would also allow sending updates to probe users for things like unreliable / broken tests etc.
cc @bassosimone @majakomel