Hey @justyy, thanks for your comment.

I have regular contacts with @stoodkev about his great SteemPlus Chrome add-on and its usage of SteemSQL. We already talked together about "proxy risk" of publicly exposing API and this something @stoodkev perfectly understand.

you are missing a (NOLOCK) which might impose load to the steemsql server

As explained in this post, the NOLOCK hint is no more required.

making assumptions that the ID increases as the timestamp increases.

This is partially correct. ID indeed increase over time as it is an autonumber column. Anyway, should I implement non-linear blocks processing to improve performances, this assumption would become false.