{"action":"created","issue":{"url":"https://api.github.com/repos/tyrasd/overpass-turbo/issues/269","repository_url":"https://api.github.com/repos/tyrasd/overpass-turbo","labels_url":"https://api.github.com/repos/tyrasd/overpass-turbo/issues/269/labels{/name}","comments_url":"https://api.github.com/repos/tyrasd/overpass-turbo/issues/269/comments","events_url":"https://api.github.com/repos/tyrasd/overpass-turbo/issues/269/events","html_url":"https://github.com/tyrasd/overpass-turbo/issues/269","id":180158222,"number":269,"title":"Leveraging /api/status","user":{"login":"mmd-osm","id":5842757,"avatar_url":"https://avatars.githubusercontent.com/u/5842757?v=3","gravatar_id":"","url":"https://api.github.com/users/mmd-osm","html_url":"https://github.com/mmd-osm","followers_url":"https://api.github.com/users/mmd-osm/followers","following_url":"https://api.github.com/users/mmd-osm/following{/other_user}","gists_url":"https://api.github.com/users/mmd-osm/gists{/gist_id}","starred_url":"https://api.github.com/users/mmd-osm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmd-osm/subscriptions","organizations_url":"https://api.github.com/users/mmd-osm/orgs","repos_url":"https://api.github.com/users/mmd-osm/repos","events_url":"https://api.github.com/users/mmd-osm/events{/privacy}","received_events_url":"https://api.github.com/users/mmd-osm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-09-29T20:45:11Z","updated_at":"2016-10-01T11:47:42Z","closed_at":null,"body":"In case there's too much load on the server or a user has exceeded the available quota, a [new error message](https://github.com/drolbr/Overpass-API/blob/275a5af856cac85eda5fec212a5b8d143e08b378/src/overpass_api/dispatch/db_timestamp.cc#L56) now points to the `/api/status` endpoint. (http://overpass-api.de/api/status)\r\n\r\nI would assume that some users might find it a bit challenging to deal with this error message, given the only relevant information being the minimum wait time before trying again.\r\n\r\nExample:\r\n```\r\nConnected as: 4352345243\r\nRate limit: 1\r\nSlot available after: 2016-09-30T17:43:32Z\r\nCurrently running queries (pid, space limit, time limit, start time):\r\n```\r\n\r\n\r\nIs this something overpass turbo could help with, e.g. by enhancing the error pop up with an additional  \"minimum wait time: xyz minutes\" explanation, taking the /api/status details into account?\r\n\r\nThinking about this issue a bit more,  it would be even easier for data consumers to have the minimum wait time information right in the error message itself. @drolbr \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/tyrasd/overpass-turbo/issues/comments/250908178","html_url":"https://github.com/tyrasd/overpass-turbo/issues/269#issuecomment-250908178","issue_url":"https://api.github.com/repos/tyrasd/overpass-turbo/issues/269","id":250908178,"user":{"login":"mmd-osm","id":5842757,"avatar_url":"https://avatars.githubusercontent.com/u/5842757?v=3","gravatar_id":"","url":"https://api.github.com/users/mmd-osm","html_url":"https://github.com/mmd-osm","followers_url":"https://api.github.com/users/mmd-osm/followers","following_url":"https://api.github.com/users/mmd-osm/following{/other_user}","gists_url":"https://api.github.com/users/mmd-osm/gists{/gist_id}","starred_url":"https://api.github.com/users/mmd-osm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmd-osm/subscriptions","organizations_url":"https://api.github.com/users/mmd-osm/orgs","repos_url":"https://api.github.com/users/mmd-osm/repos","events_url":"https://api.github.com/users/mmd-osm/events{/privacy}","received_events_url":"https://api.github.com/users/mmd-osm/received_events","type":"User","site_admin":false},"created_at":"2016-10-01T11:47:42Z","updated_at":"2016-10-01T11:47:42Z","body":"I'm not sure I'm following you. I'm simply prosing to  add something like \"minimum wait time: xyz minutes before running next query\" to the error popup. That's all. Forget about the details in /api/status. They're only confusing.\r\n\r\n\r\n"}}
{"actor":{"display_login":"mmd-osm"}}