Re: Message 47 characters too long
bear
Just got back from Portland and I'll rework this either tonight or tomorrow
On Mon, Jul 21, 2008 at 5:39 PM, Vicki Brown <v...@cfcl.com> wrote:
>
> I'm getting errors now from Twerp 4 (that I didn't get from twerp 3)
> that my message is "47 characters too long"
>
> Yes, it's over 140 chars (it's re-tweeting a message plus adding the
> link to that message). But that doesn't matter. Twitter doesn't care.
>
> See http://help.twitter.com/index.php?pg=kb.page&id=26 for docs
> How long can my updates be?
> We have a 140 character limit on Twitter updates. If your update
> is longer than
> that, the full update will post to the web where it can be viewed
> in its entirety.
> We'll still send the truncated version: only the first 140
> characters will go to
> phones and IM.
>
> The full update will post to the web. See
> http://twitter.com/twikifriends/statuses/856942112
> for proof. It's actually quite well-handled on the Twitter side. I'm impressed.
>
> I was very happy with this before. I don't want to rework my script
> to truncate the post when I don't have to (afa Twitter is concerned.)
> And I'm rather loathe to try to go in and edit the Python. :(
>
> Please turn that check off. Or make it an option for people who care.
>
> Thank you.
> --
> - Vicki
>
> ZZZ
> zzZ San Francisco Bay Area, CA
> z |\ _,,,---,,_ Books, Cats, Tech
> zz /,`.-'`' -. ;-;;,_ http://cfcl.com/vlb
> |,4- ) )-,_. ,\ ( `'-' http://cfcl.com/vlb/weblog
> '---''(_/--' `-'\_) http://twitter.com/vlb
>
> >
>
--
---
Bear
be...@seesmic.com (work)
be...@code-bear.com (jabber & email)
http://code-bear.com/bearlog (weblog)
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
Decklin Foster
> >
> > I'm getting errors now from Twerp 4 (that I didn't get from twerp 3)
> > that my message is "47 characters too long"
> >
> > Yes, it's over 140 chars (it's re-tweeting a message plus adding the
> > link to that message). But that doesn't matter. Twitter doesn't care.
Er, I definitely don't want something truncated for me after it goes
out, which is why I added the check. This can be an option. (I'd do
-F/--force...)
The API spec and my empirical testing disagree on how long your statuses
can be beyond that -- 160 vs. 250 (maybe. cuts off at word boundaries).
Do you care about this at all?
Also, may I suggest xrl.us? Might save an additional click-through
to the status's page in some cases. And they have an API; I use a
three-line script to create them when posting with Twerp.
#!/usr/bin/python
import sys
import urllib
api = 'http://metamark.net/api/rest/simple'
args = urllib.urlencode({'long_url': sys.argv[1]})
print urllib.urlopen(api, args).read()
--
things change.
dec...@red-bean.com
Vicki Brown
> Er, I definitely don't want something truncated for me after it goes
> out, which is why I added the check. This can be an option. (I'd do
> -F/--force...)
Sounds good. I like options. :)
>
> The API spec and my empirical testing disagree on how long your statuses
> can be beyond that -- 160 vs. 250 (maybe. cuts off at word boundaries).
I'm guessing 160 is the spec for SMS (140 + overhead of user name, etc).
250 would match the "we'll put everything on your statuses page" docs.
> Do you care about this at all?
Not particularly. I think -force should just send and Caveat Twitterer.
> Also, may I suggest xrl.us? Might save an additional click-through
> to the status's page in some cases. And they have an API; I use a
> three-line script to create them when posting with Twerp.
>
Wonderful to know about. Not what I need for this particular use case (I'm
retweeting, so I pretty much know what the max will be for anything I
send) but Very useful to know about!