In troubleshooting the server I have added and removed the device many times, adding countless unnecessary revisions to the library. While this is not a big deal, it prompted me to want to review the revisions and realized I had no way to even see how many there were (beyond the .revs folder), let alone what they contained.
Depending on what data is represented and what can be done with it, this could have countless useful benefits for good library hygiene, and reviewing/reversing previous actions.
We currently do have a simple revision browser for debugging purposes. This is not compiled into the release version, but it wouldn’t really hurt to do so. In order to make it useful from a user’s point of view, we’ll have to add a lot of polish and add some features, though.
It would require adding fine-grained control over what can be reverted, but the ability to restore files from a previous revision, as well as reverting things like changes to collection contents would definitely have a lot of value. Also, having a way to see hidden issues would be nice, like for example revisions that cannot be cleaned up, because some library instance hasn’t been synchronized for a long time.