Excerpts from João Taveira Araújo's message of Fri Sep 24 21:34:45 +1200 2010: > Excellent, this is potentially really useful, although I think we'll end up > needing a twitter mode for sup to handle this properly. I might get round to > having a crack at it myself if I get the time, but I haven't really looked > into Ruby or sup internals properly. Yeah we probably would need a real mode. It turns out that Twitter is a little more fast paced than email.
As it stands, if you have a particularly active stream you are best off auto-archiving and filtering mentions into your inbox. That is just speculation though, I am hardly following anyone, so it is all easily manageable from the inbox. > I think the name is terrible. I'm not familiar with that RFC, but I'm pretty > sure it's not twitter specific, which "fetchtweet" and "sendtweet" imply. It's the spec for email messages. Personally, I'm unsure about it. I enjoy the 'via rfc5322' you see on the web interface, but it seems to me the name would be better served by an email parsing library. Incidentally the new interface, the so-called #newtwitter, doesn't readily show the source of the tweet any more (you have to click on it). >Having a .fetchtweetrc fits in a lot better alongside .fetchmailrc too. I like the .fetchtweetrc, it links the rc to the tools better. Both tools use the same config file though, so maybe I could make it accept .fetchtweetrc and .sendtweetrc with .fetchtweetrc having precedence. >+1 if the config options are similar too. That would be interesting, been a long while since I have looked at them though. I use getmail and offlineimap. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
