Hello Happy Birds!
I have a question about Twitter contents licensing, and storing tweets or tweet IDs.
Background: I’m attempting to build a better commenting/discussion system for blogs and forums. I’m thinking about having the software I’m developing search for Twitter tweets, and include popular tweets in the discussion section of a blog post, or among the replies in a forum thread.
The Twitter tweet aspect of the page would be somewhat reminiscent of a “tweet timeline”, for tweets related to a certain blog article or forum thread, rather than a certain user. And it’d remember which tweets it’d shown in the past, so if you visited the website after 1 year, the same tweets (and some new tweets) would still be there. And you’d be able to leave comments to the tweets via the web pages standard commenting system (and reply via tweets to “normal” comments).
I wonder which one of 1, 2, 3 below is correct:
- I’m allowed to store tweets related to a blog/forum-page-discussion in the database, and serve them directly to the end user. That is, fetch them from Twitter only once, and then serve them from my servers. (I don’t think this is allowed though.)
- I may store and server neither tweets nor tweet IDs. (If this is not allowed, then completely different tweets would/could appear whenever someone reloaded the browser page / forum post.)
Best regards, KajMagnus
(I’ve found this relevant section in the Twitter api-terms:
Section I. Twitter Content
Bullet point 4 A
(But I’m asking anyway because I don’t completely understand how it affects my use case.)
Here is a related discussion: https://dev.twitter.com/discussions/5481 )