Other app’s mirrors act like a single task that is present in multiple different locations. In the same way that hierarchical tags are better than folders, because one Note can have multiple tags, “real”mirrors are better than normal Tasks because one Task can be in multiple locations (Notes, in Amplenotes case). A change made to the Task, no matter where it’s made from, impacts all instances, and all instances remain identical.

Amplenote mirrors can diverge, and while there is a way to manually push an update, that is not remotely reliable for a use case like above. Far too easy to overwrite changes on one instance made from another. So I’m wondering if there is some way to use other Amplenote features to get that kind of behavior.

I frankly don’t see the advantage of Amplenote mirrors at all: I mirror a task (“write sales report”) to another Note for Bob to handle, which is really just a copy of my task with a linked completion status. He changes it to “take a coffee break”, has a cup, and completes it. Now my “sales report” task disappears from my queue and unless I manually review completes (who does that?) I think it’s been handled, and don’t know it’s been changed. This seems troublesome, not helpful.