I just made the following post on gReader's Google Group: https://groups.google.com/d/msg/g_reader/kiBfAPr-moU/FpGS3SxdgM8J. I wasn't sure who was at fault here, but it seems that the issue is on TOR's end. I didn't realize this was an issue on the desktop version of TOR either, thought it only affected the mobile API. Hopefully this can be worked out in the near future.
I just made the following post on gReader's Google Group: https://groups.google.com/d/msg/g_reader/kiBfAPr-moU/FpGS3SxdgM8J. I wasn't sure who was at fault here, but it seems that the issue is on TOR's end. I didn't realize this was an issue on the desktop version of TOR either, thought it only affected the mobile API. Hopefully this can be worked out in the near future.