Just because you don't get any tracebacks doesn't mean that the server didn't return an error message. You'll also want to read back from the socket and see what the server actually had to say.
With that said, here are some other hints which may or may not be helpful:
* I doubt that Twitter allows posting over HTTP anymore--IIRC they switched to
HSTS and you have to connect over HTTPS. All you're going to get from HTTP
is a 301 redirect.
* For that matter, I don't think they support Basic Authentication anymore either--
you'll probably need to use OAuth.
* I think the /status/update.json API has been deprecated or removed in favour
of https://dev.twitter.com/rest/reference/post/statuses/update
(This API also expects an actual JSON object to be sent, I think.)
--
You received this message because you are subscribed to the Google Groups "MOO Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOO-talk+u...@googlegroups.com.
To post to this group, send email to MOO-...@googlegroups.com.
Visit this group at https://groups.google.com/group/MOO-talk.
For more options, visit https://groups.google.com/d/optout.
Yeah, you're gonna hit a wall with this because moo can't connect via SSL and I've not seen anyone doing OAuth with MOO (and not suffering the lag monster). Been down this road, twitter hates people using its API anyway. :(