From: Matthew Goodall <dogsaw@thecyberplains.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Twitter - new release
Date: Sat, 25 Sep 2010 10:45:20 +1200 [thread overview]
Message-ID: <1285364787-sup-7922@ethicsgradient.lan> (raw)
In-Reply-To: <1285319574-sup-2845@dhcp-87-233.eduroam.ucl.ac.uk>
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
prev parent reply other threads:[~2010-09-24 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 8:50 [sup-talk] Twitter Matthew Goodall
2010-09-13 16:02 ` William Betts
2010-09-23 17:26 ` [sup-talk] Twitter - new release Matthew Goodall
2010-09-24 9:34 ` João Taveira Araújo
2010-09-24 22:45 ` Matthew Goodall [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1285364787-sup-7922@ethicsgradient.lan \
--to=dogsaw@thecyberplains.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox