Duplicate labels in unread counts

[Sergio-Muriel]

Just got a duplicated ID in https://theoldreader.com/reader/api/0/unread-count?all=true&output=json

You can check the result of the request here: http://pastebin.com/8EmgEeX5

Duplicated id:
{
"id": "user/-/label/Mobile",
"count": 0,
"newestItemTimestampUsec": "1425996225000000"
}
and
{

"id": "user/-/label/Mobile",
"count": 1,
"newestItemTimestampUsec": "1425996471000000"

},

Is it "normal", and wich result should be considered as the good one?

[Sergio-Muriel]

I think this may be the cause of #31 ?

[jfiorato]

Would you be able to send the email address of the account that had this duplicate to [email protected]?

[jfiorato]

This user actually has 2 different folders titled "Mobile".

[Sergio-Muriel]

Damn filling sorry 'bout this erroneous bug report.

[jfiorato]

Well, I don't know if it's erroneous, I just think it's probably a bug in the TOR interface.

How are you supposed to tell which folder is 0 unread and which is 1 unread? We don't provide enough info via the API.

The interface ensures that when moving a subscription to a new folder that if you use an existing folder name, it just moves the feed to the existing folder. However, if you rename a folder to an existing folder name, it doesn't move the feeds to the existing folder, it just creates a new duplicate folder name.

I imagine most API clients work around this by synthetically using only one folder, combining the unread counts into one folder.

I'll investigate the issue of renaming folders, and work on a way to cleanup existing users. I'll update this issue when that's complete.