[Moderation] Welcome to the first 20 subscribers!

[John Smith]

2009/9/30 David Earl <david at frankieandshadow.com>:

> 3. Tools to see more easily what has changed (colour coding tag changes
> to highlight the differences, drawing lines of old and new locations to
> show position changes). The delay in rendering Mapnik ironically meant
> that you could do this by seeing the new data tracks on the old
> rendering but now that's not possible any more.

+1

It's very difficult at present to know if any changes were malicious,
and some kind of graphical diff system would be very helpful.

> being able to revert your own changesets should be unrestricted. The
> tool needs to give more information than currently available about what
> conflicts arise and how they should be dealt with.

+1

Someone else mentioned something about the best way to deal with
potential conflicts due to later changes was to approach this on a
node by node and way by way and relation by relation basis rather than
attempting to make one big revert, this could be still achieved via a
single changeset though.

It might also be useful to deal with all future changes to elements in
the change set you want to revert and revert those changes too so you
get back to a point in time that is known to be "good"