Subject: Re: [sup-talk] Twitter

From: William Betts <[email-masked]>
Date: Mon, 13 Sep 2010 09:02:06 -0700

That's pretty cool. Thank you.

On Mon, Sep 13, 2010 at 1:50 AM, Matthew Goodall
<[email-masked]>wrote:

> As a part an honest attempt at twitter, and my ongoing quest to put
> everything into sup; I created a twitter client that stores into a
> maildir and sends an email as a tweet.
>
> I figure someone else might be interested:
> http://github.com/downloads/lionicsheriff/rfc5322/rfc5322-0.4.0.gem
>
> It provides two binaries: fetchtweet and sendtweet. I'd recommend
> running 'fetchtweet --add-account accountname' first to create the
> config file.
>
> There are some examples of using (along with some sup hooks) at
> http://github.com/lionicsheriff/rfc5322
> _______________________________________________
> sup-talk mailing list
> [email-masked]
> http://rubyforge.org/mailman/listinfo/sup-talk
>
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: João Taveira Araújo <[email-masked]>
Date: Fri, 24 Sep 2010 10:34:45 +0100

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.

---

From: Matthew Goodall <[email-masked]>
Date: Mon, 13 Sep 2010 20:50:34 +1200

---

From: Matthew Goodall <[email-masked]>
Date: Fri, 24 Sep 2010 05:26:36 +1200

Features:

Note for upgraders:
The config file has been renamed ~/.rfc5322.rc and a couple keys have
been renamed:
    :oauth_token: -> :access_key: 
    :oauth_token_secret: -> :access_secret:

I did a complete rewrite since the previous attempt reflected my recent
stint in shell programming and would be very hard to maintain.
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Matthew Goodall <[email-masked]>
Date: Sat, 25 Sep 2010 10:45:20 +1200

> 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 tim…
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
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk