From: "João Taveira Araújo" <lists@syshex.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Twitter - new release
Date: Fri, 24 Sep 2010 10:34:45 +0100 [thread overview]
Message-ID: <1285319574-sup-2845@dhcp-87-233.eduroam.ucl.ac.uk> (raw)
In-Reply-To: <1285262666-sup-1123@ethicsgradient.lan>
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.
Excerpts from Matthew Goodall's message of Thu Sep 23 18:26:36 +0100 2010:
> I have released a new version:
> http://github.com/downloads/lionicsheriff/rfc5322/rfc5322-1.0.1.gem
>
> Features:
> + attached images and videos are uploaded to yfrog & url is appended to
> tweet
> + long urls are automatically shortened
> + --pastebin option in sendtweet uploads unused parts of body to
> pastebin. Again urls are appended
> + long tweets are sent to tweetshrink.com before rejecting them
>
> Documentation at: http://github.com/lionicsheriff/rfc5322
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. Having a .fetchtweetrc fits in a lot better alongside .fetchmailrc too. +1 if the config options are similar too.
Cheers,
Joao.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-09-24 9:42 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 [this message]
2010-09-24 22:45 ` Matthew Goodall
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=1285319574-sup-2845@dhcp-87-233.eduroam.ucl.ac.uk \
--to=lists@syshex.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