<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for nickhalstead</title><link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#usercomments-336b4bd7" type="application/json"/><link>http://disqus.com/people/nickhalstead/</link><description></description><language>en</language><lastBuildDate>Thu, 27 Aug 2009 20:02:05 -0000</lastBuildDate><item><title>Re: http://blog.louisgray.com/2009/08/better-retweet-button-is-out-there-via.html</title><link>http://blog.louisgray.com/2009/08/better-retweet-button-is-out-there-via.html#comment-15503305</link><description>But this new button is 'totally' tied to bit.ly - we support 12 shortener services, so you are not tied to anyone. I think @jeresig is awesome and a click count button is an interesting idea. I believe myself that 'clicks' is much less valuable as a click doesnt mean someone liked something whereas a retweet is someone specifcally saying they 'like' something. &lt;br&gt;&lt;br&gt;Of course you are relying upon us a single point of failure - but we server 75 million buttons a day now, and still growing. We arnt going anywhere :) &lt;br&gt;&lt;br&gt;Look out tomorrow for a massive reason why our button will suddenly bring you a whole new world of engagement.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Thu, 27 Aug 2009 20:02:05 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/08/better-retweet-button-is-out-there-via.html</title><link>http://blog.louisgray.com/2009/08/better-retweet-button-is-out-there-via.html#comment-15502908</link><description>Can you explain better? We are all for competition with our service, but better is totally inaccurate. &lt;br&gt;&lt;br&gt;We have the following advantages,&lt;br&gt;&lt;br&gt;* Customizable shortener service (rather than being fixed to bit.ly) &lt;br&gt;* Custom @[whoever]&lt;br&gt;* Logged in retweeting (you will find out why this is important tomorrow)&lt;br&gt;* RSS / Email support - to embed the button&lt;br&gt;&lt;br&gt;Lastly a known brand, people press our button because they know what it does.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Thu, 27 Aug 2009 19:50:33 -0000</pubDate></item><item><title>Re: How to fix URL-shorteners, part II (Scripting News)</title><link>http://www.scripting.com/stories/2009/08/25/howToFixUrlshortenersPartI.html#comment-15383880</link><description>Dave, &lt;br&gt;&lt;br&gt;Interesting plan, but &lt;a href="http://www.adjix.com/" rel="nofollow"&gt;http://www.adjix.com/&lt;/a&gt; is not doing proper redirects, it currently builds a page with a META REFRESH tag in to do the redirect, which only a browser can follow.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Tue, 25 Aug 2009 19:11:51 -0000</pubDate></item><item><title>Re: Disqus Forks Into Two Products, Launches Revamped Real-Time Comment System</title><link>http://www.techcrunch.com/2009/08/25/disqus-forks-into-two-products-launches-revamped-real-time-comment-system/#comment-15363471</link><description>is anyone else seeing live updates? I have it on 'newest first' - but havent seen one new comment pop-up?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Tue, 25 Aug 2009 13:17:21 -0000</pubDate></item><item><title>Re: louisgray.com: ReTweet.com's Rip-off Of TweetMeme Is Embarrassing and Wrong</title><link>http://blog.louisgray.com/2009/08/retweetcoms-rip-off-of-tweetmeme-is.html#comment-15323026</link><description>definitely not coasting -&amp;gt; &lt;a href="http://blog.tweetmeme.com/2009/08/19/comments-are-coming-and-they-can-be-retweeted/" rel="nofollow"&gt;http://blog.tweetmeme.com/2009/08/19/comments-a...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Mon, 24 Aug 2009 16:08:56 -0000</pubDate></item><item><title>Re: louisgray.com: ReTweet.com's Rip-off Of TweetMeme Is Embarrassing and Wrong</title><link>http://blog.louisgray.com/2009/08/retweetcoms-rip-off-of-tweetmeme-is.html#comment-15309571</link><description>John,&lt;br&gt;&lt;br&gt;TweetMeme was around way before twitturly, if you look at the date of this original coverage for TweetMeme -&amp;gt; &lt;a href="http://www.techcrunch.com/2008/01/28/the-killer-twitter-tracker-just-arrived-and-its-name-is-tweetmeme/" rel="nofollow"&gt;http://www.techcrunch.com/2008/01/28/the-killer...&lt;/a&gt; it launched in January 2008 &lt;br&gt;&lt;br&gt;But it only become popular when we revisited it in February this year, so you can be forgiven for thinking that :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Mon, 24 Aug 2009 11:18:20 -0000</pubDate></item><item><title>Re: Coming Soon: Retweetable Blog Comments</title><link>http://mashable.com/2009/08/19/retweet-comments/#comment-15075689</link><description>I dont anticipate any outcry, as we are only doing what Digg/Mixx/Reddit do - and allow people to leave comments in reference to a story link, you have to go to the blog/news/image/whatever to read the story, you then come back (if you want) and can leave comments. We purely want to build a community that is active on TweetMeme itself. And by getting further retweets of comments, we then hope that the story itself gets further coverage.&lt;br&gt;&lt;br&gt;So definitely better for blog owners, as we hope to drive them more traffic. What people do with our API is up to the developers.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Wed, 19 Aug 2009 13:40:02 -0000</pubDate></item><item><title>Re: Coming Soon: Retweetable Blog Comments</title><link>http://mashable.com/2009/08/19/retweet-comments/#comment-15072724</link><description>We are not trying to be a replacement comment system for blogs. The comments occur on TweetMeme. If Disqus or others want to aggregate our comments into their stream of comments like they do for Twitter/Friendfeed more the better. This post is a little miss-leading on our purpose - go read our post here and you will understand &lt;a href="http://blog.tweetmeme.com/2009/08/19/comments-are-coming-and-they-can-be-retweeted/" rel="nofollow"&gt;http://blog.tweetmeme.com/2009/08/19/comments-a...&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Wed, 19 Aug 2009 12:59:32 -0000</pubDate></item><item><title>Re: http://blog.louisgray.com/2009/08/favorit-shuts-down-as-companys-focus.html</title><link>http://blog.louisgray.com/2009/08/favorit-shuts-down-as-companys-focus.html#comment-14491692</link><description>It would be a boring world if we all agreed all the time, I think at the time my frustration showed through that the vision I had for the reader ended up being overly complex + not approachable. The concepts + vision (as I stated in my post) have certainly been picked up by the &lt;a href="http://lazyfeed.com" rel="nofollow"&gt;lazyfeed.com&lt;/a&gt; people and executed in a way that does make it have the 'potential' for mainstream.&lt;br&gt;&lt;br&gt;But most importantly, the work we did and the lessons we learnt meant when we approached tweetmeme, we really focused on keeping it simple, and making sure those simple things are what the users want.&lt;br&gt;&lt;br&gt;btw - we need to help you sort out your retweet button, so it retweets you instead of us! :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Sat, 08 Aug 2009 12:51:34 -0000</pubDate></item><item><title>Re: Confirmed: Digg Just Hijacked Your Twitter Links</title><link>http://mashable.com/2009/07/19/digg-twitter-links/#comment-12930540</link><description>From TweetMeme's point of view if this stays the same way we will be forced to remove it from our whitelist of shorteners, as by definition this no longer makes Digg a shortening service. We included &lt;a href="http://Digg.com" rel="nofollow"&gt;Digg.com&lt;/a&gt; because we felt the addition allowed users the ability to gain extra traction along with the shortening support.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Sun, 19 Jul 2009 19:07:18 -0000</pubDate></item><item><title>Re: Marketing is what hurts startups. If you&amp;#039;re famous how hard can it be? </title><link>http://blog.omgponi.es/post/131741428#comment-11860711</link><description>Just a slight correction - it is not 'twitturlys' retweet button, it is &lt;a href="http://TweetMeme.com" rel="nofollow"&gt;TweetMeme.com&lt;/a&gt; - the one you have on this blog :)&lt;br&gt;&lt;br&gt;But great article apart from that :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Sun, 28 Jun 2009 16:12:42 -0000</pubDate></item><item><title>Re: Repeets Tracks the Hottest Retweets</title><link>http://mashable.com/2009/05/17/repeets-retweets/#comment-9515250</link><description>Just a quick one, TweetMeme has always had the feature to track what a user has previously tweeted (you can inline retweet them as well!) -&amp;gt; e.g. here is my twitter account &lt;a href="http://tweetmeme.com/user.php?user=nickhalstead" rel="nofollow"&gt;http://tweetmeme.com/user.php?user=nickhalstead&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Mon, 18 May 2009 18:31:35 -0000</pubDate></item><item><title>Re: Retweet is stupid (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/26/retweetIsStupid.html#comment-8711213</link><description>Your missing the point completely - its a simple KISS statement, yes they could add a field for like/tweet whatever, but that changes the simple model of why twitter is kicking friendfeeds arse and will continue to do so. For all the techie goodness that FF has it is too fecking complicated for the average user and that isnt going to changed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Sun, 26 Apr 2009 18:42:32 -0000</pubDate></item><item><title>Re: Retweet is stupid (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/26/retweetIsStupid.html#comment-8710899</link><description>I agree it should be simple - so for the tweetmeme button/widget thats now on mashable, RRW, (and a shed load of others) - Very soon when you press the button it wont require you to redirect back to twitter, we will just do it for you. So it will be very much your 'like' on friendfeed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Sun, 26 Apr 2009 18:21:39 -0000</pubDate></item><item><title>Re: Celebrating Aggregation</title><link>http://www.avc.com/a_vc/2009/04/celebrating-aggregation.html#comment-8691909</link><description>Totally agree, they are scared by what they see - and would right now prefer to try and stop the aggregation. Let us hope they see the error in their thinking, but am sure AP in general and lots of the companies that make it up all think the same.&lt;br&gt;&lt;br&gt;You may also want add &lt;a href="http://tweetmeme.com" rel="nofollow"&gt;tweetmeme.com&lt;/a&gt; to your list Fred, we do have a Food &amp; Drink section which picks up all kinds of stuff people are sharing on twitter -&amp;gt; &lt;a href="http://tweetmeme.com/?category=lifestyle-fooddrink" rel="nofollow"&gt;http://tweetmeme.com/?category=lifestyle-fooddrink&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Sat, 25 Apr 2009 18:19:32 -0000</pubDate></item><item><title>Re: Predictions on How Twitter Will Change Blogs in 2009 | SocialComputingMagazine.com</title><link>http://www.socialcomputingmagazine.com/viewcolumn.cfm?colid=738#comment-7067107</link><description>Bill, a good read. These things are certainly already happening. You will see on mashable that they have a widget that shows the tweet count (like a digg button) - this is coming form our site &lt;a href="http://www.tweetmeme.com" rel="nofollow"&gt;http://www.tweetmeme.com&lt;/a&gt; , the buttons can be embedded anywhere and we also have a wordpress plugin to automate the whole process.&lt;br&gt;&lt;br&gt;We also have widgets to show the most popular stories - &lt;a href="http://widget.tweetmeme.com" rel="nofollow"&gt;http://widget.tweetmeme.com&lt;/a&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Tue, 10 Mar 2009 08:20:07 -0000</pubDate></item><item><title>Re: Why Andrew Orlowski from The Register is a twat</title><link>http://paulfwalsh.com/why-andrew-orlowski-from-the-register-is-a-twat/#comment-6615675</link><description>Frank you are a f**king retard - how can you attack a venture that is purely designed to help people with no financial gain for any parties involved, you must have a seriously f**ked up view of life if this is what makes you happy. &lt;br&gt;&lt;br&gt;Amanda + the rest of the team worked so amazingly hard to raise money for those less fortunate than ourselves and the best you can do is question how much they raised. &lt;br&gt;&lt;br&gt;You have have no integrity at all.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Wed, 25 Feb 2009 12:27:22 -0000</pubDate></item><item><title>Re: Winklevoss twins made $65 million on Facebook &amp;#8220;copycat&amp;#8221; settlement</title><link>http://venturebeat.com/2009/02/10/winklevoss-twins-made-65-million-on-facebook-copycat-settlement/#comment-6144452</link><description>"but this is PHP code, not exactly hard-to-write stuff." - are you a coder? if you were you wouldnt make a stupid throw away statement like this, PHP drives a very large % of the best websites out there, and that with 150 million users on Facebook (written in PHP) that you don't think it is complex?&lt;br&gt;&lt;br&gt;All programming languages are just tools, what you do with them is down to the intelligence of the individual. Unless of course your still playing with logo?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Tue, 10 Feb 2009 14:16:59 -0000</pubDate></item><item><title>Re: The Twitter tsunami</title><link>http://www.theequitykicker.com/2009/01/27/the-twitter-tsunami/#comment-5575634</link><description>What interested me was to look at Google search volume for the word 'twitter' as mainstream TV audience in the UK will likely not have a clue what it is, and would be interesting to see how many Jonthan Ross viewers did a search - alas Google insight DB is out of date - &lt;a href="http://www.google.com/insights/search/#q=twitter&amp;geo=GB&amp;date=today%25207-d&amp;cmpt=q" rel="nofollow"&gt;http://www.google.com/insights/search/#q=twitte...&lt;/a&gt; &lt;br&gt;&lt;br&gt;Also the BBC has had a surge in twitter related articles (mainly related to Stephen Fry + Ross coverage from the show) - but this must be creating a massive mainstream spike. I think the lack of UK SMS is still doing terrible damage but they have made noises that this will soon be rectified.&lt;br&gt;&lt;br&gt;But overall I think this is good for twitter + for anyone who has / or is developing twitter related apps.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Tue, 27 Jan 2009 09:27:33 -0000</pubDate></item><item><title>Re: Twitter lays the foundation for it&amp;#8217;s revenue model</title><link>http://www.theequitykicker.com/2009/01/22/twitter-lays-the-foundation-for-its-revenue-model/#comment-5462154</link><description>Like everything a balance must be found between allowing growth through free access and the move towards a model in which twitter has revenue. I do not think that a move to paid could work for at least 6 months - as right now we are starting to see a tipping point into mainstream which of course must be largely due to the app support. But giving notice right now of intention would give confidence and also allow developers build a roadmap.&lt;br&gt;&lt;br&gt;One thing I did not cover on my post was the typical requests that are allowed free on other services, fav.or.it integrates with I think 18 external services, some of which we have special arrangements with because of the default limitations. But it is not unusual for most API's to limit to 5000 a day - which kind of puts 20,000 an hour in perspective, and even the mighty google attaches a 50,000 per day limit on most of its services.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Thu, 22 Jan 2009 09:34:41 -0000</pubDate></item><item><title>Re: Why VCs Will Block Good Exits</title><link>http://www.angelblog.net/Why_VCs_Block_Good_Exits.html#comment-5446157</link><description>Good post, &lt;br&gt;&lt;br&gt;And this is a good point to learn, do NOT let the VC have a block on your sale. Of course that is much much easier to say than actually get. A lot will want a veto even if they are a minority share holder. But to me I would rather let them have a liquidation preference that gives them the comfort that below a certain threshold that the Angel starts getting hurt if he tries to exit at a low amount.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Wed, 21 Jan 2009 16:18:36 -0000</pubDate></item><item><title>Re: louisgray.com: TwitOrFit Says All You Blokes Are Ugly Twits, Worse than Dogs</title><link>http://blog.louisgray.com/2008/12/twitorfit-says-all-you-blokes-are-ugly.html#comment-4605862</link><description>I only have anecdotal evidence - but from what I hear a lot more women were concerned about security, but it is more likely that security is really about not wanting to attract more stalkers (twitter has enough).&lt;br&gt;&lt;br&gt;My real thought when it comes to OAuth - is all about implementation - is it going to be a friendly experience - what we really need is the equivilient of 'facebook connect' for twitter - although from a technical standpoint I hate these 'surface identification models' - from the user point of view facebook connect really does feel really easy + secure to use.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Wed, 24 Dec 2008 05:56:43 -0000</pubDate></item><item><title>Re: louisgray.com: TwitOrFit Says All You Blokes Are Ugly Twits, Worse than Dogs</title><link>http://blog.louisgray.com/2008/12/twitorfit-says-all-you-blokes-are-ugly.html#comment-4599030</link><description>Hi Louis,&lt;br&gt;&lt;br&gt;We will in the new year reveal some of the voting trends - but given that the ratio of men to women is very high - you can pretty much bet men were voting on other men. &lt;br&gt;&lt;br&gt;Main lesson we learnt from this is that until we get OAuth (come on twitter!) - we need a way to securely sign people up without taking twitter user/pass.&lt;br&gt;&lt;br&gt;Have a great christmas + new year,&lt;br&gt;&lt;br&gt;Nick</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Tue, 23 Dec 2008 19:12:39 -0000</pubDate></item><item><title>Re: louisgray.com: i.TV Hooks Up With TiVo for iPhone DVR Scheduling</title><link>http://blog.louisgray.com/2008/12/itv-hooks-up-with-tivo-for-iphone-dvr.html#comment-4568649</link><description>&lt;p&gt;Shame TIVO did not survive in the UK - just have to wait for the SKY+ equivalent makes it to the iPhone&lt;/p&gt;&lt;br&gt;&lt;br&gt;sent from: fav.or.it</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Mon, 22 Dec 2008 06:05:58 -0000</pubDate></item><item><title>Re: rizzn's personal blog: HuffPo’s Grubby Syndication Practices</title><link>http://rizzn.com/blog/2008/12/huffpos-grubby-syndication-practices.php#comment-4554493</link><description>hi Mark,&lt;br&gt;&lt;br&gt;Just for the record a few people have asked to have feeds removed - and once we spoke to those and explained they could change to a Creative Commons license (which our site abides by) they were then happy to leave the content in place. We have had a few 'ranters' who accused us of website scraping (they obviously not spotted their own RSS feed?) but here is the twist ... we get multiple requests to add new feeds every single day.&lt;br&gt;&lt;br&gt;The fact is that we attribute everything, we take account of license terms. And to give you a little insight into why this will all suddenly make sense. &lt;br&gt;&lt;br&gt;We have already quietly launched 'channels' - &lt;a href="http://fav.or.it/channels" rel="nofollow"&gt;http://fav.or.it/channels&lt;/a&gt; - these are content focused areas (a bit like Alltop subdomains) but these are filtered via Yahoo Pipe style rules - and most importantly each can look very very different. (e.g. &lt;a href="http://video.fav.or.it" rel="nofollow"&gt;http://video.fav.or.it&lt;/a&gt;)&lt;br&gt;&lt;br&gt;Why is this important? Well for a consumer its great to have a central location of content from thousands of feeds but on a niche subject. &lt;br&gt;&lt;br&gt;For the blogs? well very soon we launch &lt;a href="http://www.feedbroker.net/" rel="nofollow"&gt;http://www.feedbroker.net/&lt;/a&gt; - a way to micro-pay blogger per post - I wont go into how the model works - but suddenly bloggers will have a new way to monetize (that isnt fishy like payperreview) - and who is going to pay? businesses + brands -&amp;gt; these both want to engage with the blogosphere - and imagine building a channel around a brand that aggregates in lots of content + conversation around that brand, good for the brand to be involved in the conversation - and good for the blogs - because they are being paid to be involved.&lt;br&gt;&lt;br&gt;Have a great christmas,&lt;br&gt;&lt;br&gt;Nick</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nickhalstead</dc:creator><pubDate>Sun, 21 Dec 2008 06:40:44 -0000</pubDate></item></channel></rss>