handle twitter in right way

[vanopen@…]

I don't think bitlbee handle twitter in the right way. Everytime I log on bitlbee, twitter always pops up the status from twitter, no matter if I've read it or not. For most irc client, it will cause many many duplicated msgs logged in log, if I connect to bitlbee in many times in a time (e.g., due to bad net working condition to make bitlbee disconnected/reconnected).

For old status, user can enable their irc client's log function, and see the log for it.

[wilmer]

I'll just ignore the vagueness and arrogance of your bug report.

BitlBee is stateless. And it doesn't know which statuses you did and did not read. If you don't like it, use something else.

[anonymous]

Replying to wilmer:

I'll just ignore the vagueness and arrogance of your bug report.

BitlBee is stateless. And it doesn't know which statuses you did and did not read. If you don't like it, use something else.

Sorry for my poor English and expression in a wrong way, I really didn't mean to do it, and thank you for the explanation why it can't support that.

[wilmer]

"the right way" is a personal thing and with this funcitonality existing for almost 2 years it's a bit bold to claim that BitlBee is doing it wrong :-)

Either way, this just won't happen. BitlBee doesn't know which posts you read or not. For example if your IRC host crashed while you weren't connected to it, it's wrong to assume the user read all tweets up to then. The user should just use the timestamps to see for him/herself which msgs are new.

It's indeed noisy when you keep reconnecting, but you can just read the most recent backlog up to the point you recognise the tweets. It's not like you'll miss out on something huge if you miss a few tweets, one will just have to miss out on some of their friends' bathroom breaks. :>

[vanopen@…]

Thank you wilmer for the detailed explanation! A question arises with "if your IRC host crashed", in this condition you mensioned, will the gtalk/msn's msgs get lost?

[wilmer]

It all depends on your setup. BitlBee passes msgs to your IRC client, it won't remember them. So probably they will be in your IRC logs if you save those to disk. If you don't, then those msgs would also be lost.

Keep in mind there's a difference between a regular IM client and BitlBee. Whereas a regular IM client has a UI in which it shows you messages - and also has some idea of what you looked at and what you did not look at, BitlBee relays the messages to your IRC client and then forgets about them. It's not a user agent, it's a relay, a translator.

So all you need is on-disk logs. And of course real IRC geeks never detach from their IRC screen session. :>