support user stats for other Tasking Manager instances

[Hagellach37]

OSM Perú is hosting their own TM instance and would like to integrate the user stats endpoint of the ohsomeNow stats API. They can't use the existing endpoint as it would not give the correct numbers. For their projects they use the hashtags osmpe-project-*.

Problem:

• the current user stats endpoint only considers mapping for the hashtag hotosm-project-*
• there is no way to specify in the API call which hashtags should be considered for user stats

Potential Solution:

• adjust the existing user stats endpoint and add the hashtag parameter (as it is done for the other endpoints of ohsomeNow stats API)
• to not break the existing HOT Tasking Manager instance we could set hotosm-project-* as the default value of this new parameter if no explicit value is provided
• OSM Peru could use the new endpoint and pass osmpe-project-* to receive the correct stats
• EUthmappers would use this hashtag EUthmappers-project-*

[mmerdes]

An influencing factor for the solution might be if we expect this to happen more often. Will other OSM subcommunities ask for such an integration or do we expect just this new one for the foreseeable future?

[Hagellach37]

There are at least a dozen active instances of the Tasking Manager out there. The OSM Wiki lists a few of them, but I'm not sure if all of these are actually operational:

https://wiki.openstreetmap.org/wiki/Tasking_Manager

[kresp0]

We are also affected by this issue. Our hashtag will be EUthmappers-project-*

[ElJocho]

@Hagellach37 do we want an endpoint which has the hashtag parameter, or do we want to connect the token to the hashtag internally, so that the token does not grant unrestricted user queries to whoever holds any token? I think once we start distributing more keys we cannot guarantee them not leaking to unauthorized users.

[Hagellach37]

I think the expected behavior here is that once you have the token, you will get stats for any user.

For the existing endpoint this means that you need to be able to pass the hashtag filter as a parameter.

We don't want to connect tokens to specific hashtags in our code.

[ElJocho]

940835a now introduced hashtag parameter for topic endpoint -> this will enable different Tasking Manager instances to supply their own hashtag in the future

The authorization for this endpoint will probably be handled based on the origin request url - thus will not concern service code itself.

I will keep this issue open until we can provide a way for users to give us their TM instance urls