[OSM-talk] Code of conduct for automated (mass-) edits

[Hugh Barnes]

On Monday 29 September 2008 18:37:53 Gert Gremmen wrote:
> I'd suggest a special usertype for batch operations,
> and combine that with a notification system
> so as to enable that account for one batch.
>
> The usertype should have the username of the uploader
> with a random number attached (fe cetest0000 to cetest9999)
> to distinguish between sessions.
>
> The username should be enabled shortly before
> carrying out the scripts/upload by the server.
> The uploader could enable his temp account by filling in a web form
> with sufficient "required fields"
>
> I suggest:
> username
> bounding box for all changes
> description of change
> modified data (list of tags)
> intention of batch operation
>
> The form would return by email the username
> to be used for this upload. The email ensures
> that the uploader can be contacted.
>

All worthy ideas.

I would probably look at using a custom, temporarily-useful User Agent string 
in the HTTP request rather than specific "user" hoodoo, to summarise it 
lazily. Is this a possibility?

Cheers