HedgeDoc is incorrectly named as hackmd
-
In the CL App store, linking to the app gives the following URL: https://www.cloudron.io/store/io.hackmd.cloudronapp.html
Clearly this is a fork of CodiMD not HackMD and needs a bit of correction to 'org.hedgedoc.cloudronapp'.
Side note: it seems HackMD is still being developed and has a different feature set than HedgeDoc, and it would be useful to have it as a separate package as well.
-
Unfortunately, the appstore ids cannot be changed once published and it's been kept the same as before for compatibility.
-
@girish then it's simpler to make a new package for hedgedoc and keep hackmd as, well, hackmd.
@robi we use the appstore id to figure out the updates. Making a new hedgedoc package (just to fix the id) means that existing hedgedoc instances are kept dangling.
See, https://stackoverflow.com/questions/17582289/is-it-possible-to-change-the-package-name-of-an-android-app-on-google-play for the same "issue". It gives an example of Talk changing name to Hangouts but it has to retain the old id. It's for the same reasons.
-
@robi we use the appstore id to figure out the updates. Making a new hedgedoc package (just to fix the id) means that existing hedgedoc instances are kept dangling.
See, https://stackoverflow.com/questions/17582289/is-it-possible-to-change-the-package-name-of-an-android-app-on-google-play for the same "issue". It gives an example of Talk changing name to Hangouts but it has to retain the old id. It's for the same reasons.
@girish wow, that's, ... ahem, .. questionably lovely.
One response there does mention how to transition in a few steps via unpublishing, etc, however users must deal with the old app as well as the new app manually. Less of an issue with Cloudron Admins.
If you were to now package HackMD, what would you do to name it?
Since the two apps are still data compatible, it would be a good time to migrate. Harder later.
