[wp-trac] [WordPress Trac] #22981: Tweets import plugin tracking ticket

[WordPress Trac]

#22981: Tweets import plugin tracking ticket
----------------------------+----------------------------
 Reporter:  nacin           |       Owner:  PeteMall
     Type:  task (blessed)  |      Status:  accepted
 Priority:  high            |   Milestone:  WordPress.org
Component:  Plugins         |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+----------------------------
Changes (by MikeSchinkel):

 * cc: mike@… (added)


Comment:

 Although I fear the ship may have already sailed I figure I'd post about
 an alternate approach per chance it wasn't considered and might be
 considered instead.

 Instead of posts could we instead **consider using comments for tweets?**
 Comments model tweets better than posts, and comments already have meta so
 they can be extended by plugins and themes as needed.

 I'd love to use this feature but the idea of dumping 20,000+ posts into a
 WordPress site that might have less than 100 total real posts causes me a
 lot of heartache, and I would expect the same might be true for many other
 advanced users.  Just looking at some of the people on this ticket, here's
 the number of tweets they have to import at this moment:

 - petemall - 4033
 - otto - 7831
 - nacin - 19,436
 - me - 21,056
 - norcross - 65,583'''''(!)'''''

 Having that many extra posts could be a real pain for those who do a lot
 of debugging at the SQL level, i.e. I could no longer just browse tables
 but instead would always have to run a query.

 We could create a post type of `'twitter_account'` and another post type
 of `'tweet_period'` and then have the comments associated with the
 `'tweet_period'` post type where tweet periods could default to ''maybe''
 `'weekly'` but be configurable via a filter to `'daily'`, `'monthly'`,
 etc.  Then the posts of type `'tweet_period'` could be child posts for
 `'twitter_account'` posts and we could use comment meta to provide a
 direct link back from the comment to the parent `'twitter_account'` post
 ID ''(or even use the `comment_parent` field to point to parent post to
 reduce joins required, but that approach might be iffy.)''

 Using comments in this way would allow plugins a lot of built-in
 flexibility such as theme-able pages for `tweet_period` posts without any
 extra infrastructure to build, and it would allow plugins to work with and
 segment multiple Twitter accounts in a clean and standard way, and it
 would obviously keep the `wp_posts` table from being overwhelmed with
 tweets.

 I'd be willing to tackle coding this over the weekend  if people think
 it's a worthy approach to consider ''(assuming I get my current client
 project complete before then.)'' I'd hate to code it up though and find
 zero interest in the approach.

 And even if people don't like the idea can we at least make the post
 storage engine replaceable via hooks so that a plugin could be developed
 to use comments instead?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22981#comment:18>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software