You can try to look into SuperTweet (www.supertweet.com). You register
with them as a proxy. Once you do that, you adjust your own script to
include your proxy in the script statement, and they convert the
script to a valid OAuth command.

There are limitations. For instance, you can only have one user, not
multiple users, per OAuth account, but for most people that should be
fine.

Here is a sample of my original statement. NOTE: I just included the
active code,

'START CODE

   Set objXML = CreateObject("Msxml2.XMLHTTP")

   objXML.Open "POST", _
         "http://"; & _
         strUserName & ":" & _
         strTwitterPassword & "@twitter.com/statuses/update.xml?
status=" & _
         strMessage, _
         False

   objXML.setRequestHeader _
         "Content-Type", _
         "text/xml"

   objXML.Send

'END CODE

The above code is obsolete.

What I did was to register my new account with Supertweet. You supply
ST with your username and Twitter password. Finally, you create a
DIFFERENT password for ST. Once your registration is finished, you
structure your code a bit different.

The big difference, is that you don't use your Twitter password in the
new code, but you use the SuperTweet password. Here is the new code:

'BEGIN CODE

   Set objXML = CreateObject("Msxml2.XMLHTTP")

   objXML.Open "POST", _
         "http://api.supertweet.net/1/statuses/update.xml";, _
         False, _
         strUserName, _
         strTweetPassword

   objXML.setRequestHeader _
         "Content-Type", _
         "application/x-www-form-urlencoded "

   objXML.Send "status=" & strMessage

'END CODE

As you can see, there are two major differences. The first difference
is the different CURL statement, along with using the SuperTweet
password instead of the Twitter password.

The second difference is the Request Header parameter. Replace "text/
xml" with "application/x-www-form-urlencoded "

(NOTE: There is a space at the end of "application/x-www-form-
urlencoded " . This may or may not have an effect on your own stuff.

Hope this helps. Obviously, there are a lot of other commands to
check, but this should be a good start.



On Aug 30, 7:31 pm, Timo <elliott.t...@gmail.com> wrote:
> Hi,
>
> I have an application that posts tweets automatically from PowerPoint
> each time a presenter gets to a particular slide:
>
> It's a relatively simple VBA script that uses basic authentication
> (until tomorrow, when it gets turned off!) . Because it's a full-
> client application, I requested, and obtained, the ability to use
> xAuth.
>
> But I've struggled to find an easy way to use xAuth / Oauth from VBA.
> I'm not even sure it's possible at all using only VBA -- specifically,
> I haven't found any "native VBA" HMAC-SHA1 code, and lack the skills
> to write one (I found this post on SHA1 in VBA, but don't know how to
> include the key / HMAC part -- anybody 
> know?:http://splinter.com.au/blog/?p=86).
>
> As a workaround, I tried adding a DLL to do the HMAC-SHA1 part, based
> on this 
> post:http://blog.gobansaor.com/2008/02/22/xlaws-excel-vba-code-for-accessi...,
> and haven't completely given up, but my attempts so far don't seem to
> generate the right signature (i.e. when I cut and paste the available
> xAuth demo code from twitter, I get a different result than they do).
> I also started checking out the HMAC-SHA1 library 
> fromhttp://www.cryptosys.net/#api,
> but my application is freeware, so trying to avoid commercial code...
>
> And I know there are .Net VB libraries  like 
> TwitterVBhttp://twittervb.codeplex.com/,
> but I don't know how to access those methods/properties from VBA -- is
> it possible? Could somebody point me to demo code that shows how to
> use something like that from VBA?
>
> Many, many thanks in advance to anybody who can help my application
> from dying tomorrow!...

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to