One of the many things I’m concerned about with free online services is that the service you are getting isn’t the product. You are the product, or more specifically the data about you that is made available to paying advertisers and other third parties.
This means that you are not in control of your data in their system. As such I try to keep a copy of the data that I put into the service, in a place that I control. Especially if that data is valuable to me.
For the longest time my Twitter account was something that didn’t have high value data in it for me. Recently I’ve realised that I engage with the service at a significant level, as such I’ve decided it is time for me to store a copy of the Tweets in an archive. Especially as now I have the basis of a system to make that easier.
To integrate my dashboard with Twitter, I have used the following two libraries:
Where possible I like to use existing libraries, as it means I can reach my goals faster.
To get started with integrating Twitter with my dashboard I first downloaded an archive of my data. I then wrote a small console command to import the data into the dashboard.
Next, I integrated the dashboard with the Twitter OAuth api using the socialite provider. This was similar to the way I integrated with the WordPress platform, and was surprisingly easy.
Lastly, I wrote a small console application that uses the Twitter API library to periodically check for new tweets, and import them into the archive. To date the console application has worked really well.
Below is a screen capture of what the Twitter archive page looks like at the moment.
The pagination bar at the bottom of the page is provided by code Laravel pagination functionality. The more I use the Laravel framework, and the libraries that have been built around it, the more I want to continue to develop with it.
I’m currently developing plans for the next set of features for the dashboard. Check back here soon for a post on my progress.