Support afterID in queries

[Rishi556]

Used in place of offset. Causes timeouts, need to investigate why.

[bt-cryptomancer]

Please explain why you think it would be useful / important to support this. I'd rather not expand query features unless there is a good reason to do so. Also, what is the timeout issue you mentioned? Is that why this is still in draft status?

[Rishi556]

High offsets cause issues like insane ram usage, we already know this from hive-engine, and can find other's discussing it online: https://stackoverflow.com/a/20730523. Give this a shot if you dare: https://accounts.hive-engine.com/accountHistory?account=risingstar2&offset=1000000, it will time out before getting a response.

For certain accounts, it's impossible to get the fully history through the API. I've got workarounds which is just connecting directly to the DB and making queries that can't be done from the API. There's also data stability issues when using offset. If data is added to the top of the stack between queries, certain data points can be duplicated, and this helps avoid that issue as well since rather than using an offset from 0, you'll have a fixed point to look after.

For some reason, using this code causes requests to time out occasionally. It's why it's in draft mode until I have time to debug what's wrong and fix it.