Comments on: ‘Flow’ – day 7 – My Twitter thousands http://solyoung.com/2008/03/30/flow-day-7-my-twitter-thousands/ Out In His Elements Mon, 02 Jan 2012 03:59:16 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Sol Young http://solyoung.com/2008/03/30/flow-day-7-my-twitter-thousands/comment-page-1/#comment-2930 Sol Young Mon, 31 Mar 2008 17:07:51 +0000 http://solyoung.com/2008/03/30/flow-day-7-my-twitter-thousands/#comment-2930 Glad to have another developer in the flow...<br><br>This isn't the client app for the user wanting to stay in touch with a touchable group of people. This is for the user that finds RSS feed reading not immersive or real-time enough. In a sense, it <em>is</em> information crack.<br><br>Every person who signs up for Twitter is a citizen reporter. You should connect your <a href="http://everydayandeverynight.com" rel="nofollow">everydayandeverynight.com</a> to Twitter so blog entries are announced, btw. Followers immediately receive links and can provide commentary, follow-up tweets, and related links.<br><br>The use case: A user receives links to articles, blog entries, photos, and value-added commentary that enhances his or her life. It's not so much information crack as information vitamins. Glad to have another developer in the flow…

This isn't the client app for the user wanting to stay in touch with a touchable group of people. This is for the user that finds RSS feed reading not immersive or real-time enough. In a sense, it is information crack.

Every person who signs up for Twitter is a citizen reporter. You should connect your everydayandeverynight.com to Twitter so blog entries are announced, btw. Followers immediately receive links and can provide commentary, follow-up tweets, and related links.

The use case: A user receives links to articles, blog entries, photos, and value-added commentary that enhances his or her life. It's not so much information crack as information vitamins.

]]> By: Sol Young http://solyoung.com/2008/03/30/flow-day-7-my-twitter-thousands/comment-page-1/#comment-2591 Sol Young Mon, 31 Mar 2008 13:07:51 +0000 http://solyoung.com/2008/03/30/flow-day-7-my-twitter-thousands/#comment-2591 Glad to have another developer in the flow...<br><br>This isn't the client app for the user wanting to stay in touch with a touchable group of people. This is for the user that finds RSS feed reading not immersive or real-time enough. In a sense, it <em>is</em> information crack.<br><br>Every person who signs up for Twitter is a citizen reporter. You should connect your <a href="http://everydayandeverynight.com" rel="nofollow">everydayandeverynight.com</a> to Twitter so blog entries are announced, btw. Followers immediately receive links and can provide commentary, follow-up tweets, and related links.<br><br>The use case: A user receives links to articles, blog entries, photos, and value-added commentary that enhances his or her life. It's not so much information crack as information vitamins. Glad to have another developer in the flow…

This isn't the client app for the user wanting to stay in touch with a touchable group of people. This is for the user that finds RSS feed reading not immersive or real-time enough. In a sense, it is information crack.

Every person who signs up for Twitter is a citizen reporter. You should connect your everydayandeverynight.com to Twitter so blog entries are announced, btw. Followers immediately receive links and can provide commentary, follow-up tweets, and related links.

The use case: A user receives links to articles, blog entries, photos, and value-added commentary that enhances his or her life. It's not so much information crack as information vitamins.

]]> By: Shai http://solyoung.com/2008/03/30/flow-day-7-my-twitter-thousands/comment-page-1/#comment-2590 Shai Mon, 31 Mar 2008 05:03:26 +0000 http://solyoung.com/2008/03/30/flow-day-7-my-twitter-thousands/#comment-2590 As one of the newest people you are following on Twitter (<a href="http://twitter.com/sgluskin" rel="nofollow">http://twitter.com/sgluskin</a>), I'm curious what your use-case is for a high-volume Twitter device. Maybe for a central disaster-monitoring center that would try to follow lots of people, possibly citizen-reporters who would be designated to Twitter when a disaster happens, reporting on key needs. <br><br>For a user with no grand responsibility or purposes, such a plan for a high-volume Twitter device sounds like a recipe for a 21st century chemical-free kind of crack. :) As one of the newest people you are following on Twitter (http://twitter.com/sgluskin), I'm curious what your use-case is for a high-volume Twitter device. Maybe for a central disaster-monitoring center that would try to follow lots of people, possibly citizen-reporters who would be designated to Twitter when a disaster happens, reporting on key needs.

For a user with no grand responsibility or purposes, such a plan for a high-volume Twitter device sounds like a recipe for a 21st century chemical-free kind of crack. :)

]]>