<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Scripting News - Latest Comments in Twitter as coral reef, cont'd (Scripting News)</title><link>http://scripting.disqus.com/</link><description></description><atom:link href="https://scripting.disqus.com/twitter_as_coral_reef_contd_scripting_news/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 29 May 2009 21:42:02 -0000</lastBuildDate><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10282400</link><description>&lt;p&gt;i'm late to the party as usual dave, but i love this. can't wait to start using it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fredwilson</dc:creator><pubDate>Fri, 29 May 2009 21:42:02 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10263142</link><description>&lt;p&gt;Because I want it to be a static site, not dynamic. :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Fri, 29 May 2009 12:43:54 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10261722</link><description>&lt;p&gt;Why not use the unique Tweet ID as part of your URL?&lt;/p&gt;&lt;p&gt;Arrignton's tweet was &lt;a href="http://twitter.com/arrington/status/1945677741" rel="nofollow noopener" target="_blank" title="http://twitter.com/arrington/status/1945677741"&gt;http://twitter.com/arringto...&lt;/a&gt;  so make the comments thread be &lt;a href="http://twdsc.us/1945677741" rel="nofollow noopener" target="_blank" title="http://twdsc.us/1945677741"&gt;http://twdsc.us/1945677741&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Thus each tweet can spawn a unique comments thread&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Sanger</dc:creator><pubDate>Fri, 29 May 2009 12:03:23 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10259938</link><description>&lt;p&gt;FriendFeed. It's a floor wax and a dessert topping and it'll do your taxes&lt;br&gt;too. :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Fri, 29 May 2009 11:15:32 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10258885</link><description>&lt;p&gt;Note that FriendFeed can bring in your Disqus posts as well as tweets. Which isn't the same thing as what you're suggesting, but another spin...&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">BillSeitz</dc:creator><pubDate>Fri, 29 May 2009 10:43:02 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10248587</link><description>&lt;p&gt;SMS is relevant and it's how it all began as logging and sharing Mobile Status Updates... but now most people are using internet access in conjunction with micro-messaging.... but SMS is still necessary when no net connection is available.  and the same applies to email.... as you can send an email from your phone same as you would send an SMS (in most cases).&lt;/p&gt;&lt;p&gt;it's just that it is now realized that twitter and the micro-messaging phenomena does not depend on SMS.  its just the mobile fallback now.  most new users are using the web or desktop clients.  so limiting people who are not concerned with mobile messaging limits may not make sense as this plays out.  but then there is the risk of shifting away from micro-messaging and into longer form messaging (blogging?).  at some point.... it may begin to not make sense anymore.  especially if google rolls out real-time search... then your own blog can be just as useful as a twitter stream with some added relationship hooks.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sull</dc:creator><pubDate>Fri, 29 May 2009 01:55:18 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10248414</link><description>&lt;p&gt;the 140char limit (SMS) can always be a graceful fallback but we might see intuitive ways direct from twitter to have extended messages that can go beyond this limit... or have the first 140chars be able to transmit via SMS and the rest available on the web and client apps (optionally).&lt;/p&gt;&lt;p&gt;but at the same time, if you have your own site you can shift the conversation there.  if you could easily embed a widget with the twitter thread then that helps to keep evereything in context.  i suppose this is what google wave can tackle.  twitter need not be the solution for long-form content.  but they could provide such solutions if it makes sense to do so.  and it might.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sull</dc:creator><pubDate>Fri, 29 May 2009 01:45:09 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10245012</link><description>&lt;p&gt;hey dave.  here is what i do and at least a few others... &lt;br&gt;a year ago i created &lt;a href="http://tweetshots.com" rel="nofollow noopener" target="_blank" title="http://tweetshots.com"&gt;http://tweetshots.com&lt;/a&gt; which is a bookmarklet.  &lt;br&gt;it takes a screenshot of a tweet and lets you share it elsewhere with an emphasis on tumblr integration.&lt;/p&gt;&lt;p&gt;so, tweetshots bookmarklet + tumblr + disqus works well for what you are interested in.  &lt;br&gt;an example and entertaining site that is doing this combo is:&lt;/p&gt;&lt;p&gt;&lt;a href="http://twitterhallofshame.com" rel="nofollow noopener" target="_blank" title="http://twitterhallofshame.com"&gt;http://twitterhallofshame.com&lt;/a&gt;&lt;/p&gt;&lt;p&gt;or a post on my tumblr.... &lt;a href="http://sull.outputs.it/post/114377865" rel="nofollow noopener" target="_blank" title="http://sull.outputs.it/post/114377865"&gt;http://sull.outputs.it/post...&lt;/a&gt;&lt;br&gt;(notice links in tweet are extracted and tweetshot is clickable to tweet permalink)&lt;/p&gt;&lt;p&gt;i also had built an area on &lt;a href="http://tweetshots.com" rel="nofollow noopener" target="_blank" title="tweetshots.com"&gt;tweetshots.com&lt;/a&gt; that listed ALL tweetshots with disqus but decided not to focus on that central approach.  &lt;br&gt;i also experimented with audio comments to tweets and tweet slideshows with audio for presentations.&lt;/p&gt;&lt;p&gt;just thought my past experiment(s) might be of interest to you since it is the "coral reef" approach as well.  i also like immortalizing tweets by via screenshots and being able to see some of the users background design around the tweet.  social artifacts.&lt;/p&gt;&lt;p&gt;cheers,&lt;/p&gt;&lt;p&gt;@sull&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sull</dc:creator><pubDate>Fri, 29 May 2009 00:34:54 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10173836</link><description>&lt;p&gt;How about FriendFeed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bas Grasmayer</dc:creator><pubDate>Thu, 28 May 2009 18:20:16 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10165332</link><description>&lt;p&gt;I thought that word for that was "Enterprise Solution."&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AndrewBurton</dc:creator><pubDate>Thu, 28 May 2009 17:13:41 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10165297</link><description>&lt;p&gt;for the URL's any chance you can ditch the ".html" part, and have them be 5 characters shorter?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">playerx</dc:creator><pubDate>Thu, 28 May 2009 17:12:29 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10164643</link><description>&lt;p&gt;I don't even know how to ask the company :). But even if I knew it would be easier to ask, will you bring back/support X than "hey, what are the features dropped in new friendfeed".&lt;/p&gt;&lt;p&gt;The company may be aware of what features they dropped. I asked only for my awareness. I'm a friendfeed(not heavy) user but didn't notice  any features being dropped. Hence the curiosity. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Manu J</dc:creator><pubDate>Thu, 28 May 2009 16:54:15 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10164324</link><description>&lt;p&gt;Not my place to list them. I'm sure they're aware of what features they no&lt;br&gt;longer support. Ask the company. It is their job to support their users.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 28 May 2009 16:44:40 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10164147</link><description>&lt;p&gt;Which features did FF throw out of the window ? Just curious.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Manu J</dc:creator><pubDate>Thu, 28 May 2009 16:38:59 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10163909</link><description>&lt;p&gt;Quite possibly.&lt;/p&gt;&lt;p&gt;We need a name for this kind of software.&lt;/p&gt;&lt;p&gt;Something big designed to satisfy a company's lust for world domination,&lt;br&gt;with absolutely no chance of achieving it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 28 May 2009 16:31:51 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10163655</link><description>&lt;p&gt;Google Wave == Groove?&lt;/p&gt;&lt;p&gt;Ray Ozzie must be stewing today.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Micah Alpern</dc:creator><pubDate>Thu, 28 May 2009 16:24:38 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10162808</link><description>&lt;p&gt;You think I have chutzpah or they do? :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 28 May 2009 15:57:25 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10162015</link><description>&lt;p&gt;#Chutzpah -- "The big announcement is Google Wave. How much you want to bet in 5 years it'll be as famous as OpenDoc is today."&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jamtoday</dc:creator><pubDate>Thu, 28 May 2009 15:37:53 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10158648</link><description>&lt;p&gt;I think SMS won't go away for a while.  Disposable phones, the $20~40 kind you get at Wal-Mart, are still locked into WAP for the web and SMS for texting.  At least the little Motorola I bought last year is, I haven't got this year's model.  I would think making Twitter compatible with the cheap phones kids and college students use now would lock-in (so to speak) those users a few years down the road when they have jobs and can afford better phones.  That's my guess anyway.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AndrewBurton</dc:creator><pubDate>Thu, 28 May 2009 13:58:16 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10157878</link><description>&lt;p&gt;That may well happen but it's a ways out. This medium is practical and&lt;br&gt;usable in the current configuration - building services on top of the&lt;br&gt;140base keeps the medium open and still fills the need for longer length&lt;br&gt;messaging.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Thu, 28 May 2009 13:34:48 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10156713</link><description>&lt;p&gt;I'm interested to see if we can't just kill off SMS as web access becomes more and more ubiquitous on phones. If your phone is just a pipe, why 140 characters? 160 characters? Why can't I write 5 GB of text if I want to? SMS is great *now*, but in the future I think its dominance is probably going to wane significantly.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">curtisschweitzer</dc:creator><pubDate>Thu, 28 May 2009 12:56:43 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10156574</link><description>&lt;p&gt;Why would I want to "leverage" FF over Disqus?&lt;/p&gt;&lt;p&gt;The Disqus guys respond to every email I send them, when I hit a bug, they fix it. When I hit a limit in their system they give me  a workaround. They  treat me great, the FF guys -- well they ripped up the pavement a month ago and threw a bunch of features out the window, ones that I depended on. So that doesn't bode well for the future -- will they do it again?&lt;/p&gt;&lt;p&gt;When there's  choice, and when people work to help you accomplish what you want to, you go with them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Thu, 28 May 2009 12:52:57 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10155878</link><description>&lt;p&gt;Try &lt;a href="http://tinycrowd.com" rel="nofollow noopener" target="_blank" title="tinycrowd.com"&gt;tinycrowd.com&lt;/a&gt; to send a tweet with more than 140 characters.   Subject and a URL gets tweeted.   The link gives the rest of your comment to the user, embed content, etc.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Charles</dc:creator><pubDate>Thu, 28 May 2009 12:30:38 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10155111</link><description>&lt;p&gt;140 characters is still essential for SMS compatibility which is a core attribute of the medium and important to the global and public benefit potential. What you just did is, I think a good crack at a solution. A macro-layer that can weave around micromessages. I also think you could evolve this into real-time algae blooms... conversation clouds based on a micro-message thread that can intensify the conversation and just as easily disipate when the meomentum goes. Much less static than creating groups/discussion lists.  The other key is that this does not further the fracturing of the medium and the web. These need to be openly transferrable objects.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Lewkowitz</dc:creator><pubDate>Thu, 28 May 2009 12:03:40 -0000</pubDate></item><item><title>Re: Twitter as coral reef, cont'd (Scripting News)</title><link>http://www.scripting.com/stories/2009/05/28/twitterAsCoralReefContd.html#comment-10154985</link><description>&lt;p&gt;I have not found a better place to express and discover ideas (and have a conversation around them) than FriendFeed.&lt;br&gt;In fact, your tweet about Arrington already has a ton of comments on FriendFeed: &lt;a href="http://friendfeed.com/davew/a16f0e12/mike-arrington-says-today-will-be-very-big-news" rel="nofollow noopener" target="_blank" title="http://friendfeed.com/davew/a16f0e12/mike-arrington-says-today-will-be-very-big-news"&gt;http://friendfeed.com/davew...&lt;/a&gt;&lt;br&gt;Any particular reason why you don't want to leverage FF more?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dsims</dc:creator><pubDate>Thu, 28 May 2009 11:59:48 -0000</pubDate></item></channel></rss>