Twitter API 1.1 and OAuth

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Twitter API 1.1 and OAuth

stevepiercy
I'm using the twitter tag from TagSwap to automatically send a
tweet (status update) whenever my client publishes an article on
their website.
http://www.lassosoft.com/tagswap/detail/twitter

The tag uses SuperTweet for basic authorization.
http://www.supertweet.net/about/documentation

However that page says:

     Important Notice: Effective September 7, 2012 Twitter has released
     version 1.1 of the Twitter API. At the same time, version
1.0 of the API
     is officially deprecated. XML and RSS formats are no longer
supported in
     the v1.1 API. Twitter is providing a 6 month window before
turning off
     v1.0. Starting March 5th, 2013, the 1.0 endpoints will no
longer be
     available. Since the SuperTweet.net API is simply a proxy
of the Twitter
     API, those endpoints will no longer be available through the
     SuperTweet.net API when they are removed at Twitter.

     Read more at Twitter: Overview: Version 1.1 of the Twitter API
     http://dev.twitter.com/docs/api/1.1/overview

So in order to continue sending tweets starting March 5, 2013,
Lassoers need to switch to using OAuth.  Has anyone done any
work with an OAuth library in Lasso?  I'm tempted to just punt
and use a Python or PHP library.

--steve

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

Marc Pinnell-3
Ugh. More unpaid work fixing sites...

marc


On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder wrote:

> I'm using the twitter tag from TagSwap to automatically send a tweet (status update) whenever my client publishes an article on their website.
> http://www.lassosoft.com/tagswap/detail/twitter
>
> The tag uses SuperTweet for basic authorization.
> http://www.supertweet.net/about/documentation
>
> However that page says:
>
>    Important Notice: Effective September 7, 2012 Twitter has released
>    version 1.1 of the Twitter API. At the same time, version 1.0 of the API
>    is officially deprecated. XML and RSS formats are no longer supported in
>    the v1.1 API. Twitter is providing a 6 month window before turning off
>    v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
>    available. Since the SuperTweet.net API is simply a proxy of the Twitter
>    API, those endpoints will no longer be available through the
>    SuperTweet.net API when they are removed at Twitter.
>
>    Read more at Twitter: Overview: Version 1.1 of the Twitter API
>    http://dev.twitter.com/docs/api/1.1/overview
>
> So in order to continue sending tweets starting March 5, 2013, Lassoers need to switch to using OAuth.  Has anyone done any work with an OAuth library in Lasso?  I'm tempted to just punt and use a Python or PHP library.
>
> --steve
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Steve Piercy               Web Site Builder               Soquel, CA
> <[hidden email]>                  <http://www.StevePiercy.com/>
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

Marc Pinnell
1027 Design
PO Box 990872
Redding, CA 96099-0872
530.941.4706
fax: 866.232.5300
www.1027Design.com


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

stevepiercy
You must have an awfully generous warranty clause.  Why would
you put yourself in a position where you are financially
responsible for the actions of another party?

Do you also give away free website redesigns for mobile
devices?  ;P

--steve


On 1/10/13 at 10:39 AM, [hidden email] (Marc
Pinnell) pronounced:

>Ugh. More unpaid work fixing sites...
>
>marc
>
>
>On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder wrote:
>
>>I'm using the twitter tag from TagSwap to automatically send a tweet (status
>update) whenever my client publishes an article on their website.
>>http://www.lassosoft.com/tagswap/detail/twitter
>>
>>The tag uses SuperTweet for basic authorization.
>>http://www.supertweet.net/about/documentation
>>
>>However that page says:
>>
>>Important Notice: Effective September 7, 2012 Twitter has released
>>version 1.1 of the Twitter API. At the same time, version 1.0 of the API
>>is officially deprecated. XML and RSS formats are no longer supported in
>>the v1.1 API. Twitter is providing a 6 month window before turning off
>>v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
>>available. Since the SuperTweet.net API is simply a proxy of the Twitter
>>API, those endpoints will no longer be available through the
>>SuperTweet.net API when they are removed at Twitter.
>>
>>Read more at Twitter: Overview: Version 1.1 of the Twitter API
>>http://dev.twitter.com/docs/api/1.1/overview
>>
>>So in order to continue sending tweets starting March 5, 2013, Lassoers need to
>switch to using OAuth.  Has anyone done any work with an OAuth
>library in Lasso?  I'm tempted to just punt and use a Python or
>PHP library.
>>
>>--steve
>>
>>-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>Steve Piercy               Web Site Builder               Soquel, CA
>><[hidden email]>                  <http://www.StevePiercy.com/>
>>
>>#############################################################
>>This message is sent to you because you are subscribed to
>>the mailing list Lasso
>>[hidden email]
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>
>Marc Pinnell
>1027 Design
>PO Box 990872
>Redding, CA 96099-0872
>530.941.4706
>fax: 866.232.5300
>www.1027Design.com
>
>
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso
>[hidden email]
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

Marc Pinnell-3
That's me the sucker!

Marc


On Jan 10, 2013, at 10:55 AM, Steve Piercy - Web Site Builder wrote:

> You must have an awfully generous warranty clause.  Why would you put yourself in a position where you are financially responsible for the actions of another party?
>
> Do you also give away free website redesigns for mobile devices?  ;P
>
> --steve
>
>
> On 1/10/13 at 10:39 AM, [hidden email] (Marc Pinnell) pronounced:
>
>> Ugh. More unpaid work fixing sites...
>>
>> marc
>>
>>
>> On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder wrote:
>>
>>> I'm using the twitter tag from TagSwap to automatically send a tweet (status
>> update) whenever my client publishes an article on their website.
>>> http://www.lassosoft.com/tagswap/detail/twitter
>>>
>>> The tag uses SuperTweet for basic authorization.
>>> http://www.supertweet.net/about/documentation
>>>
>>> However that page says:
>>>
>>> Important Notice: Effective September 7, 2012 Twitter has released
>>> version 1.1 of the Twitter API. At the same time, version 1.0 of the API
>>> is officially deprecated. XML and RSS formats are no longer supported in
>>> the v1.1 API. Twitter is providing a 6 month window before turning off
>>> v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
>>> available. Since the SuperTweet.net API is simply a proxy of the Twitter
>>> API, those endpoints will no longer be available through the
>>> SuperTweet.net API when they are removed at Twitter.
>>>
>>> Read more at Twitter: Overview: Version 1.1 of the Twitter API
>>> http://dev.twitter.com/docs/api/1.1/overview
>>>
>>> So in order to continue sending tweets starting March 5, 2013, Lassoers need to
>> switch to using OAuth.  Has anyone done any work with an OAuth library in Lasso?  I'm tempted to just punt and use a Python or PHP library.
>>>
>>> --steve
>>>
>>> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> Steve Piercy               Web Site Builder               Soquel, CA
>>> <[hidden email]>                  <http://www.StevePiercy.com/>
>>>
>>> #############################################################
>>> This message is sent to you because you are subscribed to
>>> the mailing list Lasso
>>> [hidden email]
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>> Marc Pinnell
>> 1027 Design
>> PO Box 990872
>> Redding, CA 96099-0872
>> 530.941.4706
>> fax: 866.232.5300
>> www.1027Design.com
>>
>>
>> #############################################################
>> This message is sent to you because you are subscribed to
>> the mailing list Lasso
>> [hidden email]
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Steve Piercy               Web Site Builder               Soquel, CA
> <[hidden email]>                  <http://www.StevePiercy.com/>
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

Marc Pinnell
1027 Design
PO Box 990872
Redding, CA 96099-0872
530.941.4706
fax: 866.232.5300
www.1027Design.com


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

fletcher sandbeck-2
In reply to this post by stevepiercy
On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder <[hidden email]> wrote:

> I'm using the twitter tag from TagSwap to automatically send a tweet (status update) whenever my client publishes an article on their website.
> http://www.lassosoft.com/tagswap/detail/twitter
>
> The tag uses SuperTweet for basic authorization.
> http://www.supertweet.net/about/documentation
>
> However that page says:
>
>    Important Notice: Effective September 7, 2012 Twitter has released
>    version 1.1 of the Twitter API. At the same time, version 1.0 of the API
>    is officially deprecated. XML and RSS formats are no longer supported in
>    the v1.1 API. Twitter is providing a 6 month window before turning off
>    v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
>    available. Since the SuperTweet.net API is simply a proxy of the Twitter
>    API, those endpoints will no longer be available through the
>    SuperTweet.net API when they are removed at Twitter.
>
>    Read more at Twitter: Overview: Version 1.1 of the Twitter API
>    http://dev.twitter.com/docs/api/1.1/overview
>
> So in order to continue sending tweets starting March 5, 2013, Lassoers need to switch to using OAuth.  Has anyone done any work with an OAuth library in Lasso?  I'm tempted to just punt and use a Python or PHP library.

OAuth doesn't seem too bad.  Facebook uses the same system I believe.  You need to get an access token from Twitter and then sign every request to the API using an Authorization header.

However, reading the notice above it isn't clear to me that SuperTweet is going to stop working.  It sounds like as long as you use the JSON methods rather than the XML or RSS methods it should continue to work.

These API calls should work: http://www.supertweet.net/about/api

These API calls will not: http://www.supertweet.net/about/api-1-0

[fletcher]

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

stevepiercy
On 1/10/13 at 12:25 PM, [hidden email] (Fletcher Sandbeck) pronounced:

>On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder
><[hidden email]> wrote:
>
>>I'm using the twitter tag from TagSwap to automatically send a tweet (status
>update) whenever my client publishes an article on their website.
>>http://www.lassosoft.com/tagswap/detail/twitter
>>
>>The tag uses SuperTweet for basic authorization.
>>http://www.supertweet.net/about/documentation
>>
>>However that page says:
>>
>>Important Notice: Effective September 7, 2012 Twitter has released
>>version 1.1 of the Twitter API. At the same time, version 1.0 of the API
>>is officially deprecated. XML and RSS formats are no longer supported in
>>the v1.1 API. Twitter is providing a 6 month window before turning off
>>v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
>>available. Since the SuperTweet.net API is simply a proxy of the Twitter
>>API, those endpoints will no longer be available through the
>>SuperTweet.net API when they are removed at Twitter.
>>
>>Read more at Twitter: Overview: Version 1.1 of the Twitter API
>>http://dev.twitter.com/docs/api/1.1/overview
>>
>>So in order to continue sending tweets starting March 5, 2013,
>>Lassoers need to switch to using OAuth.  Has anyone done any
>>work with an OAuth library in Lasso?  I'm tempted to just punt
>>and use a Python or PHP library.
>
>OAuth doesn't seem too bad.  Facebook uses the same system I
>believe.  You need to get an access token from Twitter and then
>sign every request to the API using an Authorization header.
>
>However, reading the notice above it isn't clear to me that
>SuperTweet is going to stop working.  It sounds like as long as
>you use the JSON methods rather than the XML or RSS methods it
>should continue to work.
>
>These API calls should work: http://www.supertweet.net/about/api
>
>These API calls will not: http://www.supertweet.net/about/api-1-0

Ah, OK, I misinterpreted the notice.

I use JSON, so that's not an issue for me.

I'll do some testing by toggling the version in the ctag to 1.1
from 1 and see what happens.  The status update method is the
same between the two API versions, so it should just work.

I was getting all worked up over having to port Tweepy.  I might
still do it for giggles.
https://github.com/tweepy/tweepy

--steve

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

Tim Taplin
Despite the fact that you may not need it, I'll answer your question about OAuth anyway.

I have done some work with OAuth on lasso. While developing an OAuth based workflow with Intuit's platform, I used the twitter oauth interface to do some testing because their OAuth api is better documented and explained.

I hope to parcel out some time to organize the methods and types for lasso to act as OAuth client some time soon, but havent gotten around to it yet. If someone is in need of some code to work from, I'd be happy to provide.

Tim Taplin
On Jan 10, 2013, at 2:00 PM, Steve Piercy - Web Site Builder <[hidden email]> wrote:

> On 1/10/13 at 12:25 PM, [hidden email] (Fletcher Sandbeck) pronounced:
>
>> On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder <[hidden email]> wrote:
>>
>>> I'm using the twitter tag from TagSwap to automatically send a tweet (status
>> update) whenever my client publishes an article on their website.
>>> http://www.lassosoft.com/tagswap/detail/twitter
>>>
>>> The tag uses SuperTweet for basic authorization.
>>> http://www.supertweet.net/about/documentation
>>>
>>> However that page says:
>>>
>>> Important Notice: Effective September 7, 2012 Twitter has released
>>> version 1.1 of the Twitter API. At the same time, version 1.0 of the API
>>> is officially deprecated. XML and RSS formats are no longer supported in
>>> the v1.1 API. Twitter is providing a 6 month window before turning off
>>> v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
>>> available. Since the SuperTweet.net API is simply a proxy of the Twitter
>>> API, those endpoints will no longer be available through the
>>> SuperTweet.net API when they are removed at Twitter.
>>>
>>> Read more at Twitter: Overview: Version 1.1 of the Twitter API
>>> http://dev.twitter.com/docs/api/1.1/overview
>>>
>>> So in order to continue sending tweets starting March 5, 2013, Lassoers need to switch to using OAuth.  Has anyone done any work with an OAuth library in Lasso?  I'm tempted to just punt and use a Python or PHP library.
>>
>> OAuth doesn't seem too bad.  Facebook uses the same system I believe.  You need to get an access token from Twitter and then sign every request to the API using an Authorization header.
>>
>> However, reading the notice above it isn't clear to me that SuperTweet is going to stop working.  It sounds like as long as you use the JSON methods rather than the XML or RSS methods it should continue to work.
>>
>> These API calls should work: http://www.supertweet.net/about/api
>>
>> These API calls will not: http://www.supertweet.net/about/api-1-0
>
> Ah, OK, I misinterpreted the notice.
>
> I use JSON, so that's not an issue for me.
>
> I'll do some testing by toggling the version in the ctag to 1.1 from 1 and see what happens.  The status update method is the same between the two API versions, so it should just work.
>
> I was getting all worked up over having to port Tweepy.  I might still do it for giggles.
> https://github.com/tweepy/tweepy
>
> --steve
>
> -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> Steve Piercy               Web Site Builder               Soquel, CA
> <[hidden email]>                  <http://www.StevePiercy.com/>
>
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

stevepiercy
GitHub it!  Someone may work on it and offer pull requests.  ;)

--steve


On 1/10/13 at 2:17 PM, [hidden email] (Tim Taplin) pronounced:

> Despite the fact that you may not need it, I'll answer your question about OAuth
> anyway.
>
> I have done some work with OAuth on lasso. While developing an OAuth based
> workflow with Intuit's platform, I used the twitter oauth interface to do some
> testing because their OAuth api is better documented and explained.
>
> I hope to parcel out some time to organize the methods and types for lasso to act
> as OAuth client some time soon, but havent gotten around to it yet. If someone is
> in need of some code to work from, I'd be happy to provide.
>
> Tim Taplin
> On Jan 10, 2013, at 2:00 PM, Steve Piercy - Web Site Builder <[hidden email]>
> wrote:
>
> > On 1/10/13 at 12:25 PM, [hidden email] (Fletcher Sandbeck) pronounced:
> >
> >> On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder
> <[hidden email]> wrote:
> >>
> >>> I'm using the twitter tag from TagSwap to automatically send a tweet (status
> >> update) whenever my client publishes an article on their website.
> >>> http://www.lassosoft.com/tagswap/detail/twitter
> >>>
> >>> The tag uses SuperTweet for basic authorization.
> >>> http://www.supertweet.net/about/documentation
> >>>
> >>> However that page says:
> >>>
> >>> Important Notice: Effective September 7, 2012 Twitter has released
> >>> version 1.1 of the Twitter API. At the same time, version 1.0 of the API
> >>> is officially deprecated. XML and RSS formats are no longer supported in
> >>> the v1.1 API. Twitter is providing a 6 month window before turning off
> >>> v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
> >>> available. Since the SuperTweet.net API is simply a proxy of the Twitter
> >>> API, those endpoints will no longer be available through the
> >>> SuperTweet.net API when they are removed at Twitter.
> >>>
> >>> Read more at Twitter: Overview: Version 1.1 of the Twitter API
> >>> http://dev.twitter.com/docs/api/1.1/overview
> >>>
> >>> So in order to continue sending tweets starting March 5, 2013, Lassoers need
> to switch to using OAuth.  Has anyone done any work with an OAuth library in
> Lasso?  I'm tempted to just punt and use a Python or PHP library.
> >>
> >> OAuth doesn't seem too bad.  Facebook uses the same system I believe.  You need
> to get an access token from Twitter and then sign every request to the API using
> an Authorization header.
> >>
> >> However, reading the notice above it isn't clear to me that SuperTweet is going
> to stop working.  It sounds like as long as you use the JSON methods rather than
> the XML or RSS methods it should continue to work.
> >>
> >> These API calls should work: http://www.supertweet.net/about/api
> >>
> >> These API calls will not: http://www.supertweet.net/about/api-1-0
> >
> > Ah, OK, I misinterpreted the notice.
> >
> > I use JSON, so that's not an issue for me.
> >
> > I'll do some testing by toggling the version in the ctag to 1.1 from 1 and see
> what happens.  The status update method is the same between the two API versions,
> so it should just work.
> >
> > I was getting all worked up over having to port Tweepy.  I might still do it for
> giggles.
> > https://github.com/tweepy/tweepy
> >
> > --steve
> >
> > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> > Steve Piercy               Web Site Builder               Soquel, CA
> > <[hidden email]>                  <http://www.StevePiercy.com/>
> >
> > #############################################################
> > This message is sent to you because you are subscribed to
> > the mailing list Lasso
> > [hidden email]
> > To unsubscribe, E-mail to: <[hidden email]>
> > Send administrative queries to  <[hidden email]>
>
> #############################################################
> This message is sent to you because you are subscribed to
>   the mailing list Lasso
> [hidden email]
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Steve Piercy               Web Site Builder               Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

Rachel Guthrie
In reply to this post by Tim Taplin
On 2013-01-10, at 4:17 PM, Tim Taplin wrote:

> Despite the fact that you may not need it, I'll answer your question about OAuth anyway.
>
> I have done some work with OAuth on lasso. While developing an OAuth based workflow with Intuit's platform, I used the twitter oauth interface to do some testing because their OAuth api is better documented and explained.
>
> I hope to parcel out some time to organize the methods and types for lasso to act as OAuth client some time soon, but havent gotten around to it yet. If someone is in need of some code to work from, I'd be happy to provide.

Sound like a potential topic for the next LDC...


Rachel Guthrie
LassoSoft
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

stevepiercy
In reply to this post by stevepiercy
On 1/10/13 at 1:00 PM, [hidden email] (Steve Piercy - Web
Site Builder) pronounced:

>I'll do some testing by toggling the version in the ctag to 1.1
>from 1 and see what happens.  The status update method is the
>same between the two API versions, so it should just work.

Yup, it does.  Sorry for the FUD.

--steve

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso
[hidden email]
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

Wade Maxfield
In reply to this post by stevepiercy
On 11/01/2013, at 10:00 AM, Steve Piercy - Web Site Builder <[hidden email]> wrote:

>
> On 1/10/13 at 12:25 PM, [hidden email] (Fletcher Sandbeck) pronounced:
>
>> On Jan 10, 2013, at 10:23 AM, Steve Piercy - Web Site Builder <[hidden email]> wrote:
>>
>>> I'm using the twitter tag from TagSwap to automatically send a tweet (status
>> update) whenever my client publishes an article on their website.
>>> http://www.lassosoft.com/tagswap/detail/twitter
>>>
>>> The tag uses SuperTweet for basic authorization.
>>> http://www.supertweet.net/about/documentation
>>>
>>> However that page says:
>>>
>>> Important Notice: Effective September 7, 2012 Twitter has released
>>> version 1.1 of the Twitter API. At the same time, version 1.0 of the API
>>> is officially deprecated. XML and RSS formats are no longer supported in
>>> the v1.1 API. Twitter is providing a 6 month window before turning off
>>> v1.0. Starting March 5th, 2013, the 1.0 endpoints will no longer be
>>> available. Since the SuperTweet.net API is simply a proxy of the Twitter
>>> API, those endpoints will no longer be available through the
>>> SuperTweet.net API when they are removed at Twitter.
>>>
>>> Read more at Twitter: Overview: Version 1.1 of the Twitter API
>>> http://dev.twitter.com/docs/api/1.1/overview
>>>
>>> So in order to continue sending tweets starting March 5, 2013, Lassoers need to switch to using OAuth.  Has anyone done any work with an OAuth library in Lasso?  I'm tempted to just punt and use a Python or PHP library.
>>
>> OAuth doesn't seem too bad.  Facebook uses the same system I believe.  You need to get an access token from Twitter and then sign every request to the API using an Authorization header.
>>
>> However, reading the notice above it isn't clear to me that SuperTweet is going to stop working.  It sounds like as long as you use the JSON methods rather than the XML or RSS methods it should continue to work.
>>
>> These API calls should work: http://www.supertweet.net/about/api
>>
>> These API calls will not: http://www.supertweet.net/about/api-1-0
>
> Ah, OK, I misinterpreted the notice.
>
> I use JSON, so that's not an issue for me.
>
> I'll do some testing by toggling the version in the ctag to 1.1 from 1 and see what happens.  The status update method is the same between the two API versions, so it should just work.

So toggling that did work for me as well, but now SuperTweet is dead:

http://www.supertweet.net/

"Important Notice: Effective January 24, 2014 Twitter has suspended the SuperTweet.net API."

Any suggestions on alternatives or courses of action?  I'm just interested in posting status updates, basically the same situation Steve started with. Client system is still Lasso 8.5.x

 - Wade


#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

Daniel Parker

On 12/02/2014, at 11:26 am, Wade Maxfield <[hidden email]> wrote:

> Any suggestions on alternatives or courses of action?  I'm just interested in posting status updates, basically the same situation Steve started with. Client system is still Lasso 8.5.x

Host your own Supertweet Proxy was our solution to this issue. Code is on their site.

Daniel
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Twitter API 1.1 and OAuth

Laurent-40
Well, it seems a little bit out of my skill.

Is there another third party that can do the job like super tweet before ?

Laurent



From:  Daniel Parker <[hidden email]>
Reply-To:  <[hidden email]>
Date:  mardi 11 fĂ©vrier 2014 17:52
To:  "[hidden email] Talk" <[hidden email]>
Subject:  Re: Twitter API 1.1 and OAuth



On 12/02/2014, at 11:26 am, Wade Maxfield <[hidden email]> wrote:

>  Any suggestions on alternatives or courses of action?  I'm just interested in
> posting status updates, basically the same situation Steve started with.
> Client system is still Lasso 8.5.x

Host your own Supertweet Proxy was our solution to this issue. Code is on
their site.

Daniel
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>



#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>