-->
Page 1 of 2

direct twitter posting without 3rd party API. / lib

PostPosted: Sun Apr 17, 2016 4:20 am
by chaeplin
I have created a dirty sketch to tweet without 3rd party gateway.
Based on https://github.com/mharizanov/tweeting_silicon , http://harizanov.com

twitter account : https://twitter.com/mydailyview

source : https://gist.github.com/chaeplin/32dd00 ... 130a519b72

to use oauth : make a app at https://apps.twitter.com, generate Access Token / Secret. Use 4 keys to sketch


edited)
Lib is here : https://github.com/chaeplin/esp8266twitter

Use ntp or rtc to sync time
constructors : esp8266Twitter esp8266Twitter(consumer_key, consumer_secret, access_token, access_secret);
to tweet : esp8266Twitter.tweet(message, value_timestamp, value_nonce)

Limitations
no rate limit checking
no 140 limit checking


Enjoy.

Re: direct twitter posting without 3rd party API.

PostPosted: Sat May 21, 2016 1:22 pm
by dagorald
Hello! great project, I have just checked your twitter where the data is uploaded and notticed that besides the date, hour and temp, it also posts a picture of the current view, how do you achieve that? do you use some special camera? does the ESP handles everything?

Thank you! :)

Re: direct twitter posting without 3rd party API.

PostPosted: Sun May 29, 2016 10:29 am
by chaeplin
dagorald wrote:Hello! great project, I have just checked your twitter where the data is uploaded and notticed that besides the date, hour and temp, it also posts a picture of the current view, how do you achieve that? do you use some special camera? does the ESP handles everything?

Thank you! :)



I use Gopro wifi and spiffs. check https://github.com/chaeplin/esp8266_and ... fig-on-rtc

Re: direct twitter posting without 3rd party API. / lib

PostPosted: Fri Aug 19, 2016 11:10 am
by jiberjaber
I'm struggling to get this working, I seem to always get a failure using the example code

[TWEET] tweet : esp-01 + direct tweet / test 04
[DEBUG] do_http_text_post httpCode : -1
[TWEET] tweet : failed

I've got the 4 keys/tokens/secrets in place from registering an app, is there any more verbose debugging or a change to the twitter API which is causing problems?