[openstreetmap/openstreetmap-website] API for user blocks (#1618)

[Andy Allan]

> every other use case that needs to access any user information already hits the user endpoint (at least once)

That's not a good thing. What information are we not putting into the various planet/history/changeset etc dumps?

> not to mention premature optimisation etc

It's an important design philosophy. Making access available to *all* the OSM data via dumps is in stark contrast to many other "open data" projects where you need to scrape an API to get the whole data set.

I can understand that it is often easier to use an API than to process dumps, but if scraping our API is the *only* way to get some particular information then I think it's important for us to fix.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1618#issuecomment-325188750
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20170827/6ca4630d/attachment-0001.html>