Hi David,
the UI way is definitely not the only solution. A few weeks ago I worked
with the twitter API for crawling purposes and had to connect my code to
their API. I used the 'scribe' library to accomplish the oauth stuff.
The only needed pieces have been the 'consumerKey', 'consumerSecret' and
the application tokens 'accessToken' and 'accessTokenSecret'. The UI way
you mentioned is *one* way to obtain a temporary accessToken+secret.
However, you can log into the twitter developer API and create a new
application for yourself. This application will then be equipped with a
permanent access token+secret that you can further use in your API:
// create a new OAuth service
//
authService = new ServiceBuilder().provider(TwitterApi.class)
.apiKey(consumerKey)
.apiSecret(consumerSecret)
.build();
// if you already have the accessToken+secret from the developer
// API you're done:
//
Token token = new Token(accessToken, accessTokenSecret);
Then I accessed the twitter REST API directly. For sure, that's not
as convenient as it should be, but at least it's a way to access Twitter
without the UI solution.
I haven't looked into the pebble code for a long time and do not know
much about it. If it uses the twitter4j library directly, it will be
difficult to modify it. If there is a thin custom layer in between, it
might be possible to extend it with scribd.
Happy new year to all!
Chris
Am 01.01.2013 um 05:47 schrieb David Brown <[email protected]>:
> Hi James. Thnx for the reply. I anticipated this answer. Unfortunate. Looking
> into the Fb and twitter APIs it appears their UI way is the only solution.
>
> James Roper <[email protected]> wrote:
>
> Pebbles support for posting to Twitter was implemented before Twitter
> introduced their oauth only authentication policy. It still tries to use a
> username and password, which Twitter now disallows, hence it simply won't
> work. A few years ago I had a look at what it would take to add OAuth
> support, and found that the Twitter library that Pebble uses doesn't support
> OAuth, and it didn't look like it ever would. Adding OAuth support would
> probably require rewriting that plugin, and would require implementing new
> actions to support doing the OAuth dance to get the access token from Twitter
> for the account you want to post with. This is no small task.
>
> As far as I am aware, Pebble has never supported posting to Facebook. It
> does support commenters getting their username and profile picture from
> Facebook automatically associated with their posts, but that's all. This is
> mostly done client side. Posting to Facebook would require server side work,
> and would not be trivial.
>
> What Pebble does support is rendering social links below a blog post, this
> includes Twitter and Facebook I think, and when you click them brings up a
> popup from those websites that let you share the link to the blog post.
> These links are incredibly out of date, and include links to sites that no
> longer exist. It needs to be updated by someone who is interested in using
> these features still.
>
> On 1 January 2013 12:00, David Brown <[email protected]> wrote:
> Hi All, in some previous Pebble revision long ago I know that Pebble
> would post to either FB or Twitter.
>
> Looking at the Pebble plugin config and the 2.6.4 sourcecode FB and
> attemping to use a so-called FB app id it appears posting to FB might be
> a longshot for Pebble.
>
> Twitter on the otherhand appears more likely to work since I have been
> able to get some Pebble logs feedback.
>
> If anyone has something to say about the logs posted below please advise.
>
> Thanks in advance, David.
>
> ************************************************************************************************
> Jan 1, 2013 12:51:40 AM
> net.sourceforge.pebble.event.blogentry.PostToTwitterBlogEntryListener
> getProperty
> SEVERE: Twitter credentials (url) not found. Please configure
> twitter.url in order to post to twitter
> Jan 1, 2013 12:51:41 AM
> net.sourceforge.pebble.event.blogentry.PostToTwitterBlogEntryListener
> getProperty
> SEVERE: Twitter credentials (simulate) not found. Please configure
> twitter.simulate in order to post to twitter
> Jan 1, 2013 12:51:43 AM
> net.sourceforge.pebble.webservice.UpdateNotificationPingsClient$UpdateNotificationPingsAsyncCallback
> handleResult
>
> ************************************************************************************************
>
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> Pebble-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pebble-user
>
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512_______________________________________________
> Pebble-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pebble-user
------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
Pebble-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pebble-user
