Digest Support #9

Open
alexkingorg opened this Issue Jan 22, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@alexkingorg
Contributor

alexkingorg commented Jan 22, 2012

Perhaps a separate plugin?

Daily and weekly digests.

@iamwebrocker

This comment has been minimized.

Show comment
Hide comment
@iamwebrocker

iamwebrocker Oct 26, 2012

That's an interesting one. The Daily Digest was the main feature I once installed the TT for :-)
I think there are two possible routes:

  • Using the downloaded Tweets to make one regular (i.e. visible in the blog) post at an given interval (day, week, month whatever).
    -- Pros: Use the local db and data, this should work really fast and smooth.
    -- Cons: You'll have alot 'useless' tweetposts lurking in the database. The distinction between "data" and "posts" is blurry, since both digest and fetched-tweet posts are living in the same db-table.
  • Using the framework provided by social to directly fetch the tweets and saving a post (kind of how the "old" digest worked).
    -- Pros: You'd only have the digest posts in the db
    -- Cons: no local backup of the original tweets (if there's an option to tell TT to not fetch the tweets - if the db is populated anyway, this route is useless)

To me when swapping to the new version (3.x) of TT it wasn't clear that TT will populate the wp_post table with tweets (using the aktt_tweet post-type), and that enabling "make posts from tweets" would just make a "real" post. So initially I had the misunderstanding that only "posted" tweets would appear in the wp_post table.

Since I use(d) TT to keep an archive of may tweets, there's no need to publish additional posts when a new tweet has been fetched. It took me a while to get that.

This goes slightly off-topic now, but why did you decide to insert the fetched tweets directly into the wp_posts table? Naivly looking from the outside, an aktt_tweets-table seems cleaner?

thanks,
Tom

That's an interesting one. The Daily Digest was the main feature I once installed the TT for :-)
I think there are two possible routes:

  • Using the downloaded Tweets to make one regular (i.e. visible in the blog) post at an given interval (day, week, month whatever).
    -- Pros: Use the local db and data, this should work really fast and smooth.
    -- Cons: You'll have alot 'useless' tweetposts lurking in the database. The distinction between "data" and "posts" is blurry, since both digest and fetched-tweet posts are living in the same db-table.
  • Using the framework provided by social to directly fetch the tweets and saving a post (kind of how the "old" digest worked).
    -- Pros: You'd only have the digest posts in the db
    -- Cons: no local backup of the original tweets (if there's an option to tell TT to not fetch the tweets - if the db is populated anyway, this route is useless)

To me when swapping to the new version (3.x) of TT it wasn't clear that TT will populate the wp_post table with tweets (using the aktt_tweet post-type), and that enabling "make posts from tweets" would just make a "real" post. So initially I had the misunderstanding that only "posted" tweets would appear in the wp_post table.

Since I use(d) TT to keep an archive of may tweets, there's no need to publish additional posts when a new tweet has been fetched. It took me a while to get that.

This goes slightly off-topic now, but why did you decide to insert the fetched tweets directly into the wp_posts table? Naivly looking from the outside, an aktt_tweets-table seems cleaner?

thanks,
Tom

@alexkingorg

This comment has been minimized.

Show comment
Hide comment
@alexkingorg

alexkingorg Oct 31, 2012

Contributor

There are some notes on the upgrade in my blog: http://alexking.org/blog/2012/10/17/twitter-tools-data-upgrade-process

Contributor

alexkingorg commented Oct 31, 2012

There are some notes on the upgrade in my blog: http://alexking.org/blog/2012/10/17/twitter-tools-data-upgrade-process

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment