ReconnectingTheSmallPieces

Context : SmallPiecesLooselyJoined

When you've broken your content into MicroContent. After BangTheRocksTogether, you also need to reconnect the pieces. There are, of course, explicit links. In a HyperText A reader can trawl through and connect them in whatever order suits.

But it is also useful to have some notion of an aggregations of pieces. Maybe explicit DataStructures to represent these aggregations.

Today

• ThreadReader is a great idea that pulls Twitter threads back into a single page / document.
• Authory
• The WebLog is one possible aggregation ... chronologically
  • And BlogChains is the new way of threading them back together
• ThreadServer tries to make it explicit.
• The derivitive RSS syndication feed is also a (normally) chronological list (also AlgebraOfFeeds)
• Microsoft think ThreadedConversations are a core object. (So ThreadedDiscussion / TypedThreadedDiscussion)
• SearchEngines find similar or cluster them into search result pages
• WeblogContinuums (use SparkLines)

JonUdell worrying about it : http://weblog.infoworld.com/udell/2004/08/16.html#a1060

See also : OnlyHandleItOncePrinciple, PublishAndSubscribe

Now what about comments between or on blogs?

• http://weblog.infoworld.com/udell/2006/05/24.html#a1454

• http://www.tbray.org/ongoing/When/200x/2006/05/15/Comment-System

Thinking of aggregations of pieces as data-structures. An RSS feed is a list. A wiki is a dictionary. And threaded conversations are trees. (See MindTrafficGeometry)

Sceptical CounterThinking

Is microcontent really a good idea? WhyMicroContent?

Contrast :

• BlogRoll and
• PersonalizedBlogReading

Gone

• Delicious
• TopicExchange
• VerticalTechnoratae

See also :

• OnlineWriting

• HistoryFlow picking out the changes of a wiki page.

• WeblogOrdering

• ThreadMap

• SemanticWeb

• ExMosis : http://www.exmosis.net/node.AConversationServer

Tools for Reconnecting Small Pieces

• Bridgy : https://brid.gy/
• Authory