API compatibility for item ids parameters: ot, nt
cbliu opened this issue · comments
Google Reader API used "ot" parameter only, not "nt". Parameter "ot" in Google Reader API simply means "start time" and is used when "r=o" only. Therefore, "ot" actually means "newer than" which is contrary to your implementation.
Just want to point out this difference for potential API compatibility issue. You might want to make it compatible to Google Reader API or highlight this difference in your API doc.
Hi!
you are not right. Google Reader had both ot and nt parameters
ot = oldest time (newer than)
nt - newest time (older than)
Thanks @evgenynacu.
Should them work only for r=o? Could you point me at some doc where it is described?
https://code.google.com/p/google-reader-api/wiki/ApiStreamContents
as I remember, nt doesn't work when you fetch items from oldest to newest
ot - otherwise. (it works only if you do so)
as I know, small number of clients use these parameters so it's up to you implement them or not
Thank you
Just deployed update, see doc. Thank you!