[OSM-talk] healthsites.io breaks OSM data, do not use

[Simon Poole]

We currently are lacking a simple lightweight way of blocking write
access to the API, but it is being looked at.

This would normally be the ultima ratio as it essentially means all work
already done before an upload is lost, but in the case of a 1 change per
changeset app as healthsite.io it could be justified.

Simon

Am 21.03.2020 um 17:44 schrieb Mikel Maron:
> Yikes. Good catch and agreed. 
>
> Can anyone track the extent of the damage, and prepare to restore the thrown away tags, while keeping the good new data?
>
> * Mikel Maron * +14152835207 @mikel s:mikelmaron
>
>
>
>
>
>
> On Saturday, March 21, 2020, 12:42:01 PM EDT, Frederik Ramm <frederik at remote.org> wrote: 
>
>
>
>
>
> Hi,
>
> the "healthsites.io" web app allows you to contribute data to OSM,
> however if you modify existing OSM objects, it throws away all tags it
> does not know of. Until this bug is fixed, please refrain from using
> healthsites.io!
>
> You can track progress here
> https://github.com/healthsites/healthsites/issues/1357#issuecomment-602068556
>
> Bye
> Frederik
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20200321/e8475c4e/attachment-0001.sig>