<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for AlexSchleber</title><link>http://disqus.com/people/AlexSchleber/</link><description></description><language>en</language><lastBuildDate>Tue, 03 Nov 2009 10:03:07 -0000</lastBuildDate><item><title>Re: Techmeme vs. Twitter lists?</title><link>http://scobleizer.disqus.com/techmeme_vs_twitter_lists/#comment-21760837</link><description>Here is a link to an app that grabs the RSS feed for any Twitter List: &lt;a href="http://twiterlist2rss.appspot.com/" rel="nofollow"&gt;http://twiterlist2rss.appspot.com/&lt;/a&gt;  .... Still working out some bugs but has worked for me so far.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">JesseNewhart</dc:creator><pubDate>Tue, 03 Nov 2009 10:03:07 -0000</pubDate></item><item><title>Re: Techmeme vs. Twitter lists?</title><link>http://scobleizer.disqus.com/techmeme_vs_twitter_lists/#comment-21742818</link><description>A complete list like your tech-news-brands is great, as long as it also has persistence and searchability for the items over time. That's been the problem with Tweetdeck &amp; Seesmic so far, that they have been compromised on both counts. &lt;br&gt;&lt;br&gt;FriendFeed solved it for the most part, but the integration with Twitter was less than elegant. As long as Twitter doesn't offer the RSS or similar feed off of each list page (to pipe them into FF or similar), or Tweetdeck and Seesmic create a mass-storage/archiving option, the Lists will be compromised as described above.&lt;br&gt;&lt;br&gt;And as long as that is the case, surfacing a la Techmeme will work better for people that can't/don't want to spend the amount of time monitoring that you do, Robert.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Tue, 03 Nov 2009 02:54:04 -0000</pubDate></item><item><title>Re: The chat room/forum problem (&amp;#038; an apology to @Technosailor)</title><link>http://scobleizer.disqus.com/the_chat_roomforum_problem_038_an_apology_to_technosailor/#comment-21653322</link><description>I think a large number of people came to the same conclusion because the FF founders employed an amateurish PR strategy during the buy out at best, at worst simply didn't level with the community that yes, FF is eventually going by the wayside. (Let's hope they at least keep the servers on for archiving purposes.)&lt;br&gt;&lt;br&gt;So that made it pretty hard to keep investing a ton of time into FF. Heck, I had started modifying some Greasemonkey scripts to customize FF, hoping that FF would eventually launch those features natively. Now pretty much all new development on FF has ceased. That's no way to keep people around in earnest.&lt;br&gt;&lt;br&gt;And parallel to the "death throes" of FF, everybody after a few weeks of shock has gotten way more emo than is good for everyday consumption.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 02 Nov 2009 04:00:45 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/08/twitterfall-launches-twitter-reply.html</title><link>http://louisgray.disqus.com/thread_780/#comment-15418634</link><description>Louis, the best way I know of to show ongoing conversation between 2 Twitter users regardless of whether the "in reply to" chain was broken or not (by Twitter clients, etc.) is to simply search for both users' usernames (MINUS the @ symbols), as in this example:&lt;br&gt;&lt;br&gt;&lt;a href="http://search.twitter.com/search?q=alexschleber+thebrandbuilder" rel="nofollow"&gt;http://search.twitter.com/search?q=alexschleber...&lt;/a&gt;&lt;br&gt;(should have about a 7 day shelf-life)&lt;br&gt;&lt;br&gt;The only case where this breaks down to mostly show third-party tweets is if both usernames are (relative) Web celebs such as in this example:&lt;br&gt;&lt;br&gt;&lt;a href="http://search.twitter.com/search?q=scobleizer+louisgray" rel="nofollow"&gt;http://search.twitter.com/search?q=scobleizer+l...&lt;/a&gt;&lt;br&gt;&lt;br&gt;I had actually considered writing a Greasemonkey script to surface these queries: On clicking a special link added to each FriendFeed entry from Twitter starting with or containing an @username, scrape the Twitter Search result and display as a small "popup" overlay DIV.&lt;br&gt;&lt;br&gt;Thoughts?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Wed, 26 Aug 2009 09:48:17 -0000</pubDate></item><item><title>Re: Oh, FriendFeed is now Facebook&amp;#8217;s &amp;#8220;official&amp;#8221; R&amp;#038;D department!</title><link>http://scobleizer.disqus.com/oh_friendfeed_is_now_facebook8217s_8220official8221_r038d_department/#comment-14622950</link><description>its interesting bret said zuckerberg was on the same wavelength.. of course you can read that in many ways.. ;)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">razorshine</dc:creator><pubDate>Tue, 11 Aug 2009 05:14:37 -0000</pubDate></item><item><title>Re: Oh, FriendFeed is now Facebook&amp;#8217;s &amp;#8220;official&amp;#8221; R&amp;#038;D department!</title><link>http://scobleizer.disqus.com/oh_friendfeed_is_now_facebook8217s_8220official8221_r038d_department/#comment-14606557</link><description>FriendFeed guys used the term "for the time being"..which could mean..well..anything.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 10 Aug 2009 20:20:51 -0000</pubDate></item><item><title>Re: Oh, FriendFeed is now Facebook&amp;#8217;s &amp;#8220;official&amp;#8221; R&amp;#038;D department!</title><link>http://scobleizer.disqus.com/oh_friendfeed_is_now_facebook8217s_8220official8221_r038d_department/#comment-14606416</link><description>+1 Louis.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 10 Aug 2009 20:16:55 -0000</pubDate></item><item><title>Re: louisgray.com: Hi Facebook, It's Me, FriendFeed. This Relationship? It's Complicated.</title><link>http://louisgray.disqus.com/louisgraycom_hi_facebook_its_me_friendfeed_this_relationship_its_complicated_97/#comment-14605211</link><description>Wow Louis, congrats on keeping your wits about you to write this powerful post. Your analogy reminds me of the quote from &lt;a href="http://Dickipedia.org" rel="nofollow"&gt;Dickipedia.org&lt;/a&gt; I used to point people to at times:&lt;br&gt;&lt;br&gt;"In 2004, Zuckerberg debuted a primitive online social networking site called Facebook, named for the annual publication that collegiate upper classmen use to identify attractive freshmen girls with low self-esteem. At the time, Zukerberg planned to offer the service only to students within the Ivy League, because, as is widely known, Ivy League students have long had problems finding ways to network with one another."</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 10 Aug 2009 19:42:23 -0000</pubDate></item><item><title>Re: Oh, FriendFeed is now Facebook&amp;#8217;s &amp;#8220;official&amp;#8221; R&amp;#038;D department!</title><link>http://scobleizer.disqus.com/oh_friendfeed_is_now_facebook8217s_8220official8221_r038d_department/#comment-14601660</link><description>OK, so: "FriendFeed is dead. I will keep using it until Paul unplugs the last server, which could be years, but let’s be honest"&lt;br&gt;&lt;br&gt;but also: "put me down as excited. Very excited. I’m looking forward now to that next walk with Mark Zuckerberg" &lt;br&gt;&lt;br&gt;?!?!?&lt;br&gt;&lt;br&gt;How do those two go together? &lt;br&gt;&lt;br&gt;If the FriendFeed functionality and archived data/archiving capabilities become inaccessible that is going to suck, frankly. I guess the bottom line is that (cloud-based) social services can't be trusted with your data for the long haul. Grab what you can while you can, but make sure to draw all the data you really want into your own systems.&lt;br&gt;&lt;br&gt;With Twitter Search being essentially broken, FF was a way to archive/search/filter Twitter, and even though only about 1/3 of my following on Twitter were on FF, it was getting pretty productive to manage both mostly from within FF (even though there were tons of further FF/Twitter integration improvements I could think of, and began to implement to some extent via Greasemonkey scripts).&lt;br&gt;&lt;br&gt;Obviously, with the uncertainty, it makes no sense to invest much thought into this until some clarity is provided. In the meantime, we'll have to scour for other tools, and I for one am becoming more and more inclined to build my own. It may well be that the social "mega" services will permanently be unable to give good back-data access due to shear volume.&lt;br&gt;&lt;br&gt;So I guess use them for discovery only, and then "hoover up" what you need from it into your own systems. Of course if you're relying on RSS to do this for you, you better save the feed to somewhere from day ONE! (Biggest issue of RSS, it always only goes back 20 or so items from the time you set up).&lt;br&gt;&lt;br&gt;IMO blogs and their comment systems became a lot more relevant again today due to this development.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 10 Aug 2009 18:40:39 -0000</pubDate></item><item><title>Re: tr.im announces shutdown (Scripting News)</title><link>http://scripting.disqus.com/trim_announces_shutdown_scripting_news/#comment-14559876</link><description>Dave, here is a simple "Roll your own" solution using Wordpress: &lt;a href="http://3on.us/diy-tinyurl" rel="nofollow"&gt;http://3on.us/diy-tinyurl&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 10 Aug 2009 04:32:42 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s platform shortcomings</title><link>http://scobleizer.disqus.com/twitter8217s_platform_shortcomings/#comment-14559656</link><description>Great post, Robert. Couldn't have really said it better myself. I have previously warned about the URL shortener "captive" issue here: &lt;a href="http://3on.us/diy-tinyurl" rel="nofollow"&gt;http://3on.us/diy-tinyurl&lt;/a&gt;&lt;br&gt;&lt;br&gt;It is a shame that Twitter is already displaying some of the same signs of big co. arrogance that MSFT and more recently Apple (see Jason Calacanis' current post/email) are tending towards. Before Twitter ever having earned a dime no less...&lt;br&gt;&lt;br&gt;Just wrote this today as a footnote to Jason's post:&lt;br&gt;&lt;br&gt; "... am musing about the question of whether all large/successful companies (in this case a post-1997 resurgent Apple riding the wave of their iPod and iPhone dominance) are more or less "doomed" to live out "The Powerbroker" archetype, becoming paranoid/controlling, throwing their proverbial weight around, and beginning to bully all and sundry.&lt;br&gt;&lt;br&gt;Maybe I have been a little too harsh in judging Microsoft in the past, maybe these developments are psychologically... almost unavoidable...?!?"</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 10 Aug 2009 04:14:54 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s platform shortcomings</title><link>http://scobleizer.disqus.com/twitter8217s_platform_shortcomings/#comment-14559591</link><description>In addition to Alex's points, developers are what got me onto Twitter and who kept me there. I noticed the developers weren't leaving and neither were the real early adopter types (I follow them wherever they go).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Scobleizer</dc:creator><pubDate>Mon, 10 Aug 2009 04:07:26 -0000</pubDate></item><item><title>Re: Twitter&amp;#8217;s platform shortcomings</title><link>http://scobleizer.disqus.com/twitter8217s_platform_shortcomings/#comment-14559564</link><description>The reason: branding / brand names. "Twitter" works well, while Jaiku and Pownce sucked as brand names. Yeah, it can be as simple as that...&lt;br&gt;&lt;br&gt;Twitter and the "Tweety-bird" are evocative to some extent of what Twitter is all about, hence the mass proliferation of an entire Twitter/Tweet lingo, tons of new 3rd party app names, etc.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 10 Aug 2009 04:05:25 -0000</pubDate></item><item><title>Re: Facebook? Up 10%. Twitter? Up 16%. FriendFeed? Flat</title><link>http://scobleizer.disqus.com/facebook_up_10_twitter_up_16_friendfeed_flat/#comment-12597471</link><description>You point is well taken, AND shows the way that FriendFeed can win:&lt;br&gt;&lt;br&gt;1) Make a few addtl. changes to become a robust Twitter client (needs Reply and RT links/buttons, as well as easy import of all Twitter "following" accounts not yet on FF as Imaginary Friends - or some other way if that were too resource intensive).&lt;br&gt;&lt;br&gt;2) Become the de facto feed reader better than Google Reader by adding a "Subscribe to this" bookmarklet and similar button on items within FriendFeed that link to an RSS'able source. These subscriptions (to sources rather than users) could be managed either as Imaginary Friends, or as "Groups/Rooms" managed by FF admin, asf.&lt;br&gt;&lt;br&gt;3) Find a way to import the Facebook Home page (friends' updates), and you then have a unified inbound feed with everything important going on (say under "Favorites"). &lt;br&gt;&lt;br&gt;I have been doing something close to this, minus the FB import, for a while now manually, and it works, it's just too much work to set up currently for most people to do it.&lt;br&gt;&lt;br&gt;Once you combine the 3 top Web 2.0 uses this way, it becomes a lot more compelling. That's what FF needs, a compelling use case that is easy to set up and easily DEMONSTRATED. Loic just came out with the Seesmic Web-based Twitter client, FF is not that far off at all from offering that and more. &lt;br&gt;&lt;br&gt;The infrastructure is there, now all it needs is a few tweaks.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 13 Jul 2009 15:24:43 -0000</pubDate></item><item><title>Re: Really Secret Scoble</title><link>http://scobleizer.disqus.com/really_secret_scoble/#comment-12026531</link><description>Gladwell's "Tipping Point" had a whole chapter on this phenomenon "5: ... the magic number 150" (Dunbar Number) that is a worthwhile read. It seems that the human brain on average is equipped to handle about that number of social group connections but not many more.&lt;br&gt;&lt;br&gt;Of course, you Robert have been pushing the envelope on this for quite some time :)&lt;br&gt;&lt;br&gt;Have our Web 2.0 technologies enabled us to do things that turn out to be unsustainable? Quite possibly. Then again, improved filtering/sorting may be the answer. We're all experimenting with a way that might work for us...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Thu, 02 Jul 2009 07:21:25 -0000</pubDate></item><item><title>Re: Real-time systems hurting long-term knowledge?</title><link>http://scobleizer.disqus.com/real_time_systems_hurting_long_term_knowledge/#comment-11896203</link><description>Jesse, the Google search on your Tweet Stream is a very poor substitute, as it still has more holes than a Swiss cheese. So far I've found only piping of (single user) Twitter RSS feeds into Tumblr to be a reasonably simple/sound solution as far as archiving is concerned (tweet frequency can't be too high, else Tumblr will shut it down). &lt;br&gt;&lt;br&gt;Of course that won't solve Robert's wish for Time-bound snap-shots that can be easily resurfaced: Google itself, even with the recent "Recency Operator" improvements (Last 24hrs/week/month/year), still has a way to go before you can say "give me date range from: ... until: ..."&lt;br&gt;&lt;br&gt;Sound to me like there are plenty of business opportunities around providing archiving abilities around given real-time queries. I.e. Robert can find what he wants on a given day or recent sequence of days SHORTLY AFTER the event, and then says: "Hoover up" all of this info and archive it for later... e.g. for the recent "140conf" or "140tc" etc.&lt;br&gt;&lt;br&gt;That implies taking timely action because Twitter seems in no mood to let you back-search past about 30 days (at best, often it's only about 7 days anymore during daytime loads). They may of course already be selling access to the full range to corp. researchers for a lot of money.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 29 Jun 2009 12:42:55 -0000</pubDate></item><item><title>Re: Facebook vs. Twitter: Round two with URL shorteners as the judge</title><link>http://evbart.disqus.com/facebook_vs_twitter_round_two_with_url_shorteners_as_the_judge/#comment-11779272</link><description>The result is not that surprising, since Twitter users have been "trained" to practice openness, engagement, and most importantly propagation via Retweets (which Facebook "Likes" cannot match as they don't create the same degree of surfacing, largely because FB users don't (yet) expect to interact with other users' Friends of Friends or their "fanned" FB Pages, etc. to the same degree as on Twitter's wide-open platform).&lt;br&gt;&lt;br&gt;Granted Zuckerberg is hard at work at retraining them... &lt;br&gt;&lt;br&gt;Nonetheless, smart bit of research using a relatively simple tool like bit.ly. Shows how important it is to get actual confirmation/feedback via stats on how postings to the various communities are received.&lt;br&gt;&lt;br&gt;I have been arguing this over on FriendFeed for a number of weeks now, as there currently is no good way to measure clicks on either links shown internally on FF, or the shortened ff.im links shown if FF actions/postings are forwarded to Twitter. &lt;br&gt;&lt;br&gt;Ever since I've been using FriendFeed in an accelerated fashion starting about two months ago, this has been an issue, since I have no real way of knowing to what degree my Twitter followers are engaging with my FF materials. Anecdotally, it seems that click-throughs on ff.im are currently much lower than on bit.ly links, in part simply because fewer users are familiar with them, asf.&lt;br&gt;&lt;br&gt;Here is the thread:&lt;br&gt;&lt;a href="http://friendfeed.com/friendfeed-feedback/481ec19a/we-need-friendfeed-post-ff-im-clickthrough" rel="nofollow"&gt;http://friendfeed.com/friendfeed-feedback/481ec...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Fri, 26 Jun 2009 12:33:45 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/05/dont-tempt-online-mob-they-come-bearing.html</title><link>http://louisgray.disqus.com/thread_7809/#comment-9357278</link><description>@Alex - I am NOT condoning the attitude or the behaviour of Twitter management. What I'm trying to get across is that Twitter is just one of many possible ways to publish content. If people are unhappy with Twitter, they can use other free or non-free alternatives. No one is being forced to use Twitter, or for that matter, FriendFeed, FaceBook, LinkedIn, or any of the other social media sites. Sites that meet user expectations will win users over. Sites that don't will drive users away. It was always thus.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">victorpanlilio</dc:creator><pubDate>Fri, 15 May 2009 05:46:22 -0000</pubDate></item><item><title>Re: Twitter: &amp;#8220;We Screwed Up&amp;#8221; on #fixreplies</title><link>http://mashable.disqus.com/twitter_8220we_screwed_up8221_on_fixreplies/#comment-9357063</link><description>Now you disappoint me, Scott Stratten (@unmarketing). You didn't want to see what your closest 25k friends were writing to others? :) &lt;br&gt;&lt;br&gt;(Ironically the larger your following/follower set gets for someone such as yourself, the larger the % of @ reply tweets that will surface in your timeline even with the default setting.)&lt;br&gt;&lt;br&gt;I am now seeing A LOT less of you, is that truly what you are arguing for? See, I used to click through a lot of your little "Well played Sir!" and "...and by XYZ, I mean..." type @ reply banter with peeps. Most of it is GONE now... If anything, Twitter should be integrating MORE conversation threading/visibility into the platform, not less. It already works on &lt;a href="http://Search.twitter.com" rel="nofollow"&gt;Search.twitter.com&lt;/a&gt;, so what gives?&lt;br&gt;&lt;br&gt;The point is, it's better to have access to the full data set (which should also be less expensive database lookup-wise), and then filter down from there as you see fit. Twitter's spirit is openness (maybe a lot more open than its founders foresaw), why deny access to an entire class of Tweets out of hand?&lt;br&gt;&lt;br&gt;BTW, I find Mashable's lauding here of Twitter's apology as "frank and honest" almost as Orwellian as Twitter's language in all of this from the get-go. They (Biz, et al.) still continue to try (rather clumsily) to tell us what to think. Propaganda that can easily be spotted is... 2nd rate propaganda.&lt;br&gt;&lt;br&gt;Also agree with people further down that the 3% of users number feels "massaged". If it were % of active users it should be a good bit higher. Don't trust any statistic you haven't forged yourself...&lt;br&gt;&lt;br&gt;(Wrote a longer retort here:&lt;br&gt;&lt;br&gt;&lt;a href="http://alexschleber.posterous.com/my-comment-on-this-excerpt-from-twitter-blog" rel="nofollow"&gt;http://alexschleber.posterous.com/my-comment-on...&lt;/a&gt;&lt;br&gt;)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Fri, 15 May 2009 05:22:20 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/05/dont-tempt-online-mob-they-come-bearing.html</title><link>http://louisgray.disqus.com/thread_7809/#comment-9355521</link><description>Totally agree with you Louis, see what I just wrote here:&lt;br&gt;&lt;br&gt;&lt;a href="http://alexschleber.posterous.com/my-comment-on-this-excerpt-from-twitter-blog" rel="nofollow"&gt;http://alexschleber.posterous.com/my-comment-on...&lt;/a&gt;&lt;br&gt;&lt;br&gt;In a word, @Biz explanation is baloney, and the tone of the posts is only getting MORE Orwellian. Plus this latest PR fail has none of all that "aw shucks FailWhale grass roots" cuddliness (which has already had them getting away with A LOT).&lt;br&gt;&lt;br&gt;Oh, and @Victor, you are wrong: The users are what build the value of SOCIAL MEDIA. So it would behoove the people expecting to (someday) make money from their creation to treat that resource with some care. Anyone can throw up some servers and code, the value is in the USERS.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Fri, 15 May 2009 04:06:08 -0000</pubDate></item><item><title>Re: Digital Signals: Hashtags - Communicating via Twitter . .  Faster</title><link>http://digitalsignals.disqus.com/digital_signals_hashtags_communicating_via_twitter_faster/#comment-8255384</link><description>Hi Alex, like Melissa above I owe you an apology, I can only assume it was the inclusion of # ironically that might have meant your comment being condemned to the spam folder!&lt;br&gt;&lt;br&gt;I agree with your comment entirely, as mentioned in my reply to Melissa, the recent claim that the value hashtag functionality is over, has only strengthened my belief in this. &lt;br&gt;&lt;br&gt;Placing a hashtag is a conscious decision to add specific content for a specific purpose. Content in tweets can be accidentally associated with unrelated topics.&lt;br&gt;&lt;br&gt;Careful placement of hashtags in-line with body seems the most efficient if not the most aesthetic method of doing this.&lt;br&gt;&lt;br&gt;Thanks for taking the time to comment!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">DigitalSignals</dc:creator><pubDate>Thu, 16 Apr 2009 04:34:34 -0000</pubDate></item><item><title>Re: Digital Signals: Hashtags - Communicating via Twitter . .  Faster</title><link>http://digitalsignals.disqus.com/digital_signals_hashtags_communicating_via_twitter_faster/#comment-7622979</link><description>I'd say that hashtags can provide extremely valuable meta-information, because they signal both intent, as well as a certain amount of sophistication/insider information (compared to "incidental"/unconscious use of the same keywords). &lt;br&gt;&lt;br&gt;E.g. during SXSW Interactive, Twitter's time-line on &lt;a href="http://Search.twitter.com" rel="nofollow"&gt;Search.twitter.com&lt;/a&gt; was overflowing with SXSW references, and cutting that down by searching for the #sxsw hashtag only was a first step toward cutting through the noise.&lt;br&gt;&lt;br&gt;And the great thing is that they can be added to the text flow without needing to repeat the term twice. E.g. you can just write: "This post deals with the way #wordpress handles...". What's not to like? Only 1 character need be added...&lt;br&gt;&lt;br&gt;Agreed that people need to avoid abusing them by making anything a hashtag. Basic rules for viral "spreadability" still apply: Keep it short, logical/meaningful, easy/enjoyable to say ("#followfriday") , etc. &lt;br&gt;&lt;br&gt;But if used properly, each tweet using them adds an entire additional dimension of communication opportunities, because a vast number of people monitoring Twitter, who are not yet your followers, can find you via hashtags (that number will only grow with increasing Twitter Search literacy coming to the mainstream). &lt;br&gt;&lt;br&gt;You can join a much larger conversation. Also see the success of #journchat, #brandchat, etc. as virtual, timebound meetups on Twitter.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Mon, 30 Mar 2009 00:58:15 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/03/3-twitter-tools-that-enhance-new.html</title><link>http://louisgray.disqus.com/thread_814/#comment-7487513</link><description>Alex - One thing that isn't emphasized in this post, is that with Topify we do simplify the two steps process - you can follow back and reply to DMs right from your inbox (no need to go to the Twitter site for that).&lt;br&gt;&lt;br&gt;And to Corvida - our design changed a lot since the beginning - you should try again ;-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">arikfr</dc:creator><pubDate>Wed, 25 Mar 2009 01:47:55 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/03/3-twitter-tools-that-enhance-new.html</title><link>http://louisgray.disqus.com/thread_814/#comment-7485414</link><description>This is important stuff, as the number of steps for diligent following are cumbersome, even if you abbreviate the sequence you describe by simply going to one's /followers page. Since Twitter is so far only showing people's bios on mouse-over on that page, rather than at least that plus following/follower numbers, it is increasingly difficult to guess the spammers up front without clicking through first (they are getting smarter on their bio texts).&lt;br&gt;&lt;br&gt;I will test out some of the services you mention, but really email without 1-click follow/block from within the email client is still extra steps. Twitter should make decent solutions natively available, especially when they could reduce their server loads (showing the following/follower #s to weed out spammers should be cheaper than loading a full profile page, #s plus bio plus 5 tweets could even be on-click inline AJAXed to avoid potentially unnecessarily loading it 20 times per page).&lt;br&gt;&lt;br&gt;Also, frankly there should be a 1-click option for blocks as well (as you really don't want spammers in your follower list, especially since some have been using the "top of follower heap" approach to follow/unfollow multiple times for exposure), the current 2-step process can be cumbersome especially when Twitter has slowed down. This should be inline AJAXed as well.&lt;br&gt;&lt;br&gt;Follow me on Twitter, I follow back:&lt;br&gt;&lt;a target="_blank" href="http://twitter.com/alexschleber" rel="nofollow"&gt;Twitter.com/AlexSchleber&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Tue, 24 Mar 2009 23:23:12 -0000</pubDate></item><item><title>Re: http://mashable.com/2009/03/24/newspaper-best-practices/</title><link>http://mashable.disqus.com/thread_66345/#comment-7484944</link><description>"Doing nothing is not an option" - I strongly agree. &lt;br&gt;&lt;br&gt;E.g. I am working on a post about how it's crazy not to have 1) commenting 2) that is easy &amp; OPEN (moderate later, filter only for offensive words &amp; obvious multi-link spam) and instantly visible (without immediate feedback you are subtly disincentivising the behavior) on just about every single content item placed by your media outfit. In the age of blogs, people have quickly gotten used to and then come to expect this and other Web2.0 realities. &lt;br&gt;&lt;br&gt;It feels downright strange now to read something where we can't comment, or only after running a gauntlet of sign-ups, then mostly unnecessary moderation hold-ups, only to be relegated to some labyrinthine sub-page. &lt;br&gt;&lt;br&gt;ENGAGEMENT is the key. Embrace the new realities, anything else is madness.&lt;br&gt;&lt;br&gt;Follow me on Twitter, I follow back:&lt;br&gt;&lt;a target="_blank" href="http://twitter.com/alexschleber" rel="nofollow"&gt;Twitter.com/AlexSchleber&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AlexSchleber</dc:creator><pubDate>Tue, 24 Mar 2009 23:00:08 -0000</pubDate></item></channel></rss>