An interesting discussion is brewing over at Trac about the new Twitter Importer which many users have been looking forward to for their own WordPress-powered properties:
This ticket is to track the development of a plugin that can import tweets from a downloaded twitter.com archive. Presumably, such a plugin would be added to the importers list on wp-admin/import.php.
The gist of the conversations so far that have interested me is the discussion of whether these should be imported as posts, which is the original proposed implementation, or another view presented by Mike Schinkel:
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.
For those that have an exceptional amount of tweets (I have over 41k+ tweets) the idea of creating 41,000 blog posts does cause me significant heartburn.
There are those that share this opinion with much more fervor than I can muster, like Chris Wallace:
I cannot truly express the depth of my hatred for importing tweets into WordPress. That is all.
This conversation isn’t entirely new as it’s been a few weeks in the making, but with Wallace’ update it was brought back into my view and it made me really think about which I’d rather prefer.
So, the question is passed on to you: Would you rather see them imported as posts (perhaps as an “aside” or “status” or other post format or just as posts) or would you rather see them imported in some other manner, perhaps as comments?
Love to hear your thoughts on the matter.
Join the conversation