{"id":460,"date":"2017-06-19T12:11:17","date_gmt":"2017-06-19T09:11:17","guid":{"rendered":"http:\/\/tuijasonkkila.fi\/?p=460"},"modified":"2024-09-20T13:21:35","modified_gmt":"2024-09-20T10:21:35","slug":"consuming-ifttted-twitter-favs","status":"publish","type":"post","link":"https:\/\/tuijasonkkila.fi\/?p=460","title":{"rendered":"Consuming IFTTTed Twitter favs"},"content":{"rendered":"

\u202aI consider my Twitter favourites to be mainly bookmarks although endorsements happen too. Liking<\/em> comes from Instagram and Facebook but because my social media communities do not really overlap, I sometimes want to send digital respect in Twitter too. I’ve tried to unlearn the classic liking in Twitter and instead reply or retweet, but old habits – you know.\u202c<\/p>\n

\u202aThere’s little point in bookmarking if you cannot find your bookmarks afterwards. The official Twitter archive that I unzip to my private website<\/a> few times a year, does not include favourites, which is a pity. The archive looks nice out of the box, and there is a search facility. \u202c<\/p>\n

\u202aSince late 2013, I have an active IFTTT rule that writes metadata of the favourited tweet to a Google spreadsheet. IFTTT<\/a> is a nifty concept but oftentimes there are delays and other hickups. \u202c<\/p>\n

\u202aMy husband and I lunch together several times a week. Instead of emailing, phoning or IM’ing the usual 5 minutes and I’m there bye<\/em> message, I had this idea of enhanced automation with IFTTT. Whenever I entered the inner circle around our regular meeting point, IFTTT sent me an email announcing Entered the area.<\/em> This caused a predefined email rule to trigger which forwarded the message to the receiver. Basta! At first this simple digital helper was fun, but as soon as it didn’t deliver, trust started to erode rapidly.<\/p>\n

– Where are you? Didn’t you get the message?
\n– What message?<\/p>\n

Sometimes the email came doubled, sometimes it arrived the next day (or never). After few months I had to deactivate the rule.\u202c<\/p>\n

\u202aWith tweets it’s not so critical. In the beginning I checked few times that the spreadsheet do was populated, but then I let it be. From time to time Google (or IFTTT) opens up a new document but fortunately keeps the original file name, just adds a version number.\u202c<\/p>\n

\"IFTTT<\/a>
IFTTT rule<\/figcaption><\/figure>\n

\u202aI appreciate Google’s back office services but don’t often use their user interfaces. Besides, my IFTTT’ed archive does not include the tweet status text, so without some preprocessing the archive is useless anyhow. In theory I could get the text by building calls myself to the Twitter API with the Google Query Language, or become a member of the seemingly happy TAGS community. TAGS<\/a> is a long-lasting and sensible tool by Martin Hawksey. But what would blogging be without the NIH spirit, so here we go.\u202c<\/p>\n

\u202aBecause I have access to a shinyapps.io<\/a> instance, I made a searchable tweet interface as an R Shiny web app. For that I needed to\u202c<\/p>\n