Designed and built for Humanitarian OpenStreetMap Team collaborative emergency/disaster mapping, the OSM Tasking Manager 2.0 divides an area into individual squares that can be rapidly mapped by thousands of volunteers.
To make sure all TM instances don't break if these tokens are revoked, we should probably move them into the .ini file, add a write up for how an instance owner can generate their own keys, and then create a separate set for the HOTOSM live instance different from this codebase.
Right now, anyone who sets up a new TM instance is using the same default application oauth keys unless they manually edit the keys in https://github.com/hotosm/osm-tasking-manager2/blob/master/osmtm/views/osmauth.py#L24-L25.
To make sure all TM instances don't break if these tokens are revoked, we should probably move them into the
.ini
file, add a write up for how an instance owner can generate their own keys, and then create a separate set for the HOTOSM live instance different from this codebase.