Closed asturcon3 closed 11 years ago
Google Reader used 20 characters user id so I placed the fake id to have the same format. No app developer has yet complained about this.
And I'm not complainig. The id's mismatch is too easy to solve... in a way compatible with other greader_like servers.
Regards again.
Hm. I'm returning 01234... everywhere where 20 characters user id is expected and "-" everywhere google reader returned it. Not sure returning "-" instead 20 digits will make API implementation more compatible.
Are you developing an app?
Yes.
Not sure about the 20digits/placeholder thing. Leave it as is, and wait to see if someone coimplaints.
Two samples: theoldreader is using user/-/label/whatever in BOTH unread-count and tag-list inoreader is using user/(10 digits user id)/label/whatever in both pages
My app was using ids as returned by the server, working good when connected to those sites but not here. Now for user id's I'm removing... pf... id.split("/").slice(2).join("/"). That. It's working fine.
The Old Reader is not fully compatible with GR API. Inoreader made its API after GR was closed. BazQux API was done May before GR is closed and it's one-to-one copy including all the quirks and inconsistencies.
It's right thing to ignore user id. I'm just using "user/./label/(.)" regexp internally to get tags/labels passed.
What app you're developing?
ThOR. It's already published on Nokia Store (it's symbian, you know, that obsolete thing where no other developer is :D )
Currently it connects to theoldreader, next update will connect with a handful greader-like servers. I'm having a funny week testing.
( ClientLogin client=ThOR&accountType=HOSTED_OR_GOOGLE&service=reader&Email=... )
Just noticed that the user in the tag id's is filled with the string 01234567890123456789. Should be either the user id or a - string, just as in unread-count.
I'm fixing that in my code, maybe you want to fix it in yours.
Regards