TTYtter Updates

@jasonwryan Could be, though I'm not aware of IP being a factor there.

@colindean OIC. Let me think about that one, though it doesn't sound too difficult to implement.

@jasonwryan The rate limits are, unfortunately, the new reality. I'm still having trouble reproducing the autofetch glitch.

@chosig There *is* a /block command.

@krisshaffer Probably not :)

@colindean You can just /re to a direct message. No /dmreply necessary.

@smunsch Is T:RL:T installed in the right place? Does perl -MTerm::ReadLine::TTYtter -e'' work, or complain?

@HerrFachidiot No good? (This was "/ra e9") Do you have some extension installed that might be conflicting?

@HerrFachidiot What exactly are you typing? Is this 2.1.0? (This command was: "/ra zb9 What exactly ...")

@GShang You're welcome!

@Caramboo This is a known bug (you're supposed to get DMs you send, but they should be marked as -> rather than you). 2.1.1 will fix.

@HerrFachidiot Seems okay (just did it with this command).

@encycl Welcome to the new rate limits. I am tracking an issue where the fetch does not restart after that message, but I can't repro.

just found @ttytter source code, didn't realise it was TTYtter, thought it was a automated pentest framework due to use of death remarks

@ttytter upgraded to 2.1.0 in #FreeBSD. /cc @wicked_x

@x_wicked Yeah, it got on my nerves as well.

@nipsespin I'm going to try to confirm this with Twitter (nothing personal, but when it did thread we had a lot of issues with that).

@felesaerius /rtsof (e.g., /rtsof a5)

@dpreacher No, it looks like it's clashing with the short version of /delete, but it modifies keys. I didn't think of the cognitive clash.

@RealIvanSanchez Okay. Let me know.