Password protect changes to a camp

[bobinush]

Does not need to be super secure.. Just so that it is harder for people to move, edit, delete other camps.

Although it reduces potential problems, it kind of takes away the beauty of it being an open-to-all process.

[bobinush]

With this implemented, do we still need to have the revision/history feature?
Sure it might be a nice to have to restore to an older version, but it is no longer as an important feature as it might have been before.

I think less is more (at least in software development😅) and also like to not have unused features laying around.

[lyret]

With this implemented, do we still need to have the revision/history feature? Sure it might be a nice to have to restore to an older version, but it is no longer as an important feature as it might have been before.

I think less is more (at least in software development😅) and also like to not have unused features laying around.

I started thinking about this when I saw your comment this morning - I agree in sentiment but comes to the conclusion that its still to nice to have to remove. It enables admin help in worst case scenarios and also enables the statistics feature for seeing activity over time :) So would recommend not remove it. Also the backend is built around the concept of revisions.