You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would this involve making a "Twitter listener" device that runs as server which listens for one or more user's tweets? Or maybe tweets belonging to one or more queries, whether that query be user, hashtag, mentions, etc. Maybe it would have a sensor for every query.
I'd like to learn more about how it worked in DoppelLab.
There is a twitter account called doppellab which never tweets but follows. The idea is that the daemon that feeds data into Chain will log into the API as the doppellab user and listen for tweets from all the people it follows. So editing the set of accounts that show up in Chain/Doppellab is done by logging into twitter and following/unfollowing people.
This is necessary to fully port DoppelLab over to Chain. It should have timestamp and text content, and link it to a Person resource.
The text was updated successfully, but these errors were encountered: