One last check, are the following api services similar?
#define TWITUX_API_FOLLOWING_ADD "https://twitter.com/friendships/create/%s.xml"
"http://api.supertweet.net/1/friendships/create/{id}.xml"
#define TWITUX_API_FOLLOWING_DEL "https://twitter.com/friendships/destroy/%s.xml"
"http://api.supertweet.net/1/friendships/destroy/{id}.xml"
Regards,
Fitlad
> --
> You received this message because you are subscribed to the Google Groups
> "SuperTweet MyAPI Proxy" group.
> To post to this group, send email to
> supertweet-...@googlegroups.com.
> To unsubscribe from this group, send email to
> supertweet-myapi-...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/supertweet-myapi-proxy?hl=en.
>
>
You should really consider updating the code to use oAuth directly.
To your specific question, please see the current twitter API (twitter docs) and see what URL appears to give you want you want and if that is not working on the supertweet.net API, let us know. Supertweet.net is not trying to emulate some version of the twitter API from two years ago, but is simply a proxy to the current twitter API with whatever bugs and limitations the current twitter api holds.
What does "not working" mean? Please provide a capture of the full http request sent by your code to supertweet.net and the full response returned by the supertweet.net API including all headers (password scrubbed)
On Oct 22, 2011, at 12:37 AM, fitlad <fit...@gmail.com> wrote:
> Mr. Blog,
>
> Thanks for the advice, Twitux the linux application which I currently
> update does not alllow users to simply change/subtitute the API URL
> from api.twitter.com to api.supertweet.net. Thus I'm currently hacking
> the source code, compliling, installing and testing the new Twitux to
> make sure that all bugs have been fixed. I'm currently having a
> difficulty to view the list of all the direct message which I sent to
> my followers; Twitux uses the following API URL to retrieve direct
> messages but this URL does not work http://api.supertweet.net/1/statuses/user_timeline/%s.xml
> Any suggestion please? Thanks
>
> Regards,
>
> Ahmed
@mrblog,
thanks for your quick respond and wise suggestion. I managed to find the proper api url to view direct messages to use with my linux app twitux. After that I removed my post. Apologies for the inconvenience that I caused. The reason why I'm updating the source code urls to use supertweet.net rather than changing the code to use OAuth because I'm not a developer; I was trying to make my favourite twitter app works with minimal effort. I can confirm now after 48 hours of testing that all twitux options and features work now very smoothly with supertweet.net. Thanks for your great support.
Regards,
Fitlad
On Oct 22, 2011 6:27 PM, "David Beckemeyer" <mrblog...@gmail.com> wrote:
I suggest changing the code so that in the future it will be easy to change the URL parts quickly in one place, especially the host, because this could change again. Even better is making that a run-time config, through environment variables or a config file etc. It would make it easy to allow users to use the stand-alone local proxy, http://www.supertweet.net/about/localproxy which we suggest instead of the supertweet.net service.
You should really consider updating the code to use oAuth directly.
To your specific question, please see the current twitter API (twitter docs) and see what URL appears to give you want you want and if that is not working on the supertweet.net API, let us know. Supertweet.net is not trying to emulate some version of the twitter API from two years ago, but is simply a proxy to the current twitter API with whatever bugs and limitations the current twitter api holds.
What does "not working" mean? Please provide a capture of the full http request sent by your code to supertweet.net and the full response returned by the supertweet.net API including all headers (password scrubbed)
On Oct 22, 2011, at 12:37 AM, fitlad <fit...@gmail.com> wrote:
> Mr. Blog,
>
> Thanks for the a...