Identica timeline reposts replies over and over

[aaron.toponce@…]

Please see this pastebin: ​http://ae7.st/p/59l

This is an Idenitca timeline. It seems that the reply notice to me continues to come down the timeline until there is a new notice from anyone other than me. This does not happen with my Twitter account.

[roughnecks@…]

I'm currently experiencing the same issue: full log is here ​http://laltromondo.dynalias.net/~nopaste/view/raw/4081163

[aaron.toponce@…]

Here is another paste. According to this paste, new posts from someone other than me do not stop the reply flood. ​http://ae7.st/p/9do

[Wilmer van der Gaast <wilmer@…>]

I wonder whether this is a problem with cursor behaviour. This could probably be confirmed with a tcpdump (assuming you're not using SSL).

What I expect is the response will say "I have messages up to ID $blah", and the next request says "I want messages frmo $blah and up".

This happens with mentions only? Have you tried disabling those?

[anonymous]

I am using SSL, actually. I'll reconnect without, and run a tcpdump, and post the result as an attachment. Also, what do you mean by disabling mentions? In the Identi.ca settings, or in Bitlbee?

[Wilmer van der Gaast <wilmer@…>]

The "fetch_mentions" account setting in BitlBee. The messages that get stuck are all mentions.

[aaron.toponce@…]

tcpdump(1) of the repeated reply ontices.

[aaron.toponce@…]

Here is the pastebin to accompany the packet capture: ​http://ae7.st/p/7v0

[Flexo <bugs.bitlbee.org@…>]

I'm also getting this problem, I just don't get many replies on identi.ca! I also often have my own statuses echoed a day (exactly a day) after sending them, although that seems to be intermittent so I'm guessing it's identi.ca's fault.

[Flexo <bugs.bitlbee.org@…>]

I let the reply from yesterday repeat until now, looks like it wasn't a time zone issue like I speculated after all, since it's still going more than 24 hours after it stopped.

[Flexo <bugs.bitlbee.org@…>]

I've been looking into this some more. I'm pretty sure it's an identi.ca bug now but I'd like to try pinning down the behaviour anyway. If anyone else could give it a try that'd be handy.

Bitlbee makes the request for recent mentions by requesting something along the lines of ​https://identi.ca/api/statuses/mentions.xml?since_id=97553878 where 97553878 is the id of the most recent mention status. (You can get this from the website's URL for that status, or by sticking something like imcb_chat_log(td->timeline_gc, "since_id : %s", args[5]); below line 879 (in r938) in protocols/twitter/twitter_lib.c)

For me, that's still returning the most recent mention (the one with the given ID) even though it shouldn't. Changing since_id to 0 shows a lot more mentions, so identi.ca's obviously doing /something/ here. My first test was to add one to the ID in case identi.ca was off by one; didn't help. I put in a massively higher number though, and the response was correctly empty. Narrowing it down, it seems that adding 75 finally makes the response empty! (ie, for my number above, 97553953 did the trick, while anything <= 97553952 still returned the mention.)

The mind boggles.

​http://status.net/open-source/issues/3559 files a bug saying that the since_id is off by 1, whereas I'm finding it's off by 75. Maybe we can get some more numbers together here :)

[wilmer]

Strangely I seem to be getting the same behaviour with Twitter now in the JSON branch, if you turn off the streaming API.

[wilmer]

That was happening only with retweets and fixed by changeset:json,986. This seems to be a different issue since the pastebin above was repeating non-RT posts.

Is this still happening at all?

[Flexo <bugs.bitlbee.org@…>]

I haven't had anybody retweet me or others on my identica timeline, but I'm not getting the issue with replies any more, no.

[wilmer]

Ok, let's assume identi.ca folks fixed whatever it is that they broke.

[gregoa]

interesting. especially since I'm still seeing this right now.

[skizzhg]

It's not fixed at all indeed, and on the identi.ca side I don't see anyone interested in...

[wilmer]

Ok, not sure what this is then, but I must admit that I don't care much about fixing what really seems to be identi.ca's fault either. I appreciate the free software spirit behind it and all, but it's the *Twitter* API they're implementing, so they better do it right. Plus, from what I hear it's slowly turning into a ghost town..

What Flexo describes clearly sounds like they're not handling the since_id parameter properly. If someone can tell me how BitlBee can work around this (or what other clients are doing differently from BitlBee), I'll fix it.

I've considered a workaround (just manually de-duping) but I don't like the idea of it.