Hi everyone! Thanks for putting together this COMP - this has helped open up a world of possibilities for connecting projects to web sources.
I’m working on an interactive projection activation, and we’re trying to build a very simple trigger to start playback on movie files, activated by a Twitter feed. We have a third party app that will write the tweets on a @“testAccount” we’ve set up with the appropriate developer API’s, we have our app key/secret/OAuth token/secret in place in the COMP, and we’ve entered the Twitter account in table4 (where @nasa appears in the original). We even beat some initial 401 Unauthorized issues. It seems like everything should be working, but…
After entering our @“testAccount” in table4, switching web1 to Active, and pulsing Go, we get our code 200 back, but then the script seems to hang with no feedback. Pulsing Stop or switching Active to Off (on web1) does not break the loop, and requires a full restart of TD to regain control of Textport.
python >>>
{'status': 'Thread Started'}
python >>>
{'status': '##start post request'}
python >>>
{'code': 200, 'encoding': None}
python >>>
Followed by an indefinite hold (10min+ tested)
This only seems to specifically be a problem with our “fresh” Twitter account we created specifically for this activation. Testing @nasa yields no problems - the following Textport comes from only changing our tracked Twitter handle in table4 from @“testAccount” to @nasa (stop initiated by pulsing Stop in web1).
python >>>
{'status': 'Thread Started'}
python >>>
{'status': '##start post request'}
python >>>
{'code': 200, 'encoding': None}
python >>>
{'msg': b'{"created_at":"Tue Feb 21 18:58:41 +0000 2017","id":834115142975705095,"id_str":"834115142975705095","text":"Nasa announces major press conference on a \'discovery beyond our solar system\' https:\\/\\/t.co\\/HWG2qPOdXy","source":"\\u003ca href=\\"http:\\/\\/twitter.com\\" rel=\\"nofollow\\"\\u003eTwitter Web Client\\u003c\\/a\\u003e","truncated":false,"in_reply_to_status_id":null,"in_reply_to_status_id_str":null,"in_reply_to_user_id":null,"in_reply_to_user_id_str":null,"in_reply_to_screen_name":null,"user":{"id":3012613095,"id_str":"3012613095","name":"Barfield Educational","screen_name":"BarfieldEd","location":"Batley and surrounding areas","url":"http:\\/\\/www.barfieldeducational.co.uk\\/","description":"Providing STEM sessions in schools and social enterprise for disadvantaged children and senior citizens","protected":false,"verified":false,"followers_count":51,"friends_count":147,"listed_count":16,"favourites_count":25,"statuses_count":1243,"created_at":"Mon Feb 02 17:51:27 +0000 2015","utc_o
python >>>
{'status': 'Execution Interrupted, waiting for new commnad'}
python >>>
{'status': '##end of message'}
python >>>
Some other accounts seem to work just fine - we’ve tried with @cubs and @Yankees (accounts selected arbitrarily), which both worked with no issues (maybe an extra second or two of latency on @Yankees?).
However, we had a similar-but-different issue when we tried to access @AppleSupport - there is roughly a ~20 second latency between Activating/pulsing Go web1 and receiving tweets. Similarly with sending pulses/Offs, Textport holds for 15-20 seconds before returning the Execution Interrupted. Maybe there’s a connection?
We’ve recreated this issue identically on both a laptop running Windows 10 and a desktop running Windows 7 SP1. We’re using 099 Commercial, but also have access to 088.
So. With all this in mind - what could we be possibly doing wrong here? Is our testTwitter account not configured properly? Yet that’s where we got our OAuth tokens etc from. Any suggestions or insight?
Thanks in advance!