<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for DavidBerind</title><link>http://disqus.com/by/DavidBerind/</link><description></description><atom:link href="http://disqus.com/DavidBerind/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 30 Dec 2008 12:24:33 -0000</lastBuildDate><item><title>Re: Joe Strummer &amp;#8211; Johnny Appleseed</title><link>http://staires.org/audio/102#comment-4783159</link><description>&lt;p&gt;I think you can strike a balance in terms of commerce links that you put on your site. For me, you're taking the friction out of acquiring the songs you recommend. So, if I like the song, I don't have to go to the trouble of searching it out on Amazon. You could even go one step further and list the last 10 songs you recommended in a sidebar with buy links.  But I wouldn't go much beyond that. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Berlind</dc:creator><pubDate>Tue, 30 Dec 2008 12:24:33 -0000</pubDate></item><item><title>Re: Twitter federates with Google? (Scripting News)</title><link>http://www.scripting.com/stories/2008/12/15/twitterFederatesWithGoogle.html#comment-4417584</link><description>&lt;p&gt;Dave's blog said "Twitter-like service" without mentioning Jaiku. Just struck me as sort of odd that he didn't mention it. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Berlind</dc:creator><pubDate>Mon, 15 Dec 2008 18:02:38 -0000</pubDate></item><item><title>Re: Twitter federates with Google? (Scripting News)</title><link>http://www.scripting.com/stories/2008/12/15/twitterFederatesWithGoogle.html#comment-4417423</link><description>&lt;p&gt;Google owns Jaiku, right? &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Berlind</dc:creator><pubDate>Mon, 15 Dec 2008 17:53:54 -0000</pubDate></item><item><title>Re: TwitterCards: Grabbing Contact Data from Twitter with Microformats</title><link>http://www.windley.com/archives/2008/12/twittercards_grabbing_contact_data_from_twitter_with_microformats.shtml#comment-4113950</link><description>&lt;p&gt;Kevin, it's sort of a catch-22, I understand the pitfalls of the idea but at the same time, understand the pitfalls of the choices made by the Twitter folks... to be hCard minimalists. So, the question is how do we solve the problem which is essentially to build and browse a relatively robust directory of followers/followees.&lt;/p&gt;&lt;p&gt;The choices as best as I can tell are:&lt;/p&gt;&lt;p&gt;a) Twitter gives us a way to create a more robust hCard than the one that's there.&lt;br&gt;b) Put a URL in one of the fields.&lt;/p&gt;&lt;p&gt;I acknowledge that putting URL in one of the fields will get you a WTF. But hashtags sort of get you the same thing if you're looking at them outside of &lt;a href="http://search.twitter.com" rel="nofollow noopener" target="_blank" title="search.twitter.com"&gt;search.twitter.com&lt;/a&gt;. Hashtags are somewhat of a power user thing and I think that if power users took the lead here by including a reference to a full blown hCard in their bio, that it would catch on, and be relatively viral.&lt;/p&gt;&lt;p&gt;Either approach involves a sacrafice, eh?&lt;/p&gt;&lt;p&gt;What would be cool is if some other 3rd party service (eg: Plaxo, LinkedIn, etc.) could offer some robust hCard hosting that's easy for all to use. Real 1-2-3.  If you're a Twitter user, folllow these 5 steps which include using a nice short URI to point to the hCard, but one that would be somewhat recognizable and one that when clicked on, would be human readable.&lt;/p&gt;&lt;p&gt;This cannot be that difficult and it only takes a kernel of users to make something happen on Twitter.&lt;/p&gt;&lt;p&gt;David&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Berlind</dc:creator><pubDate>Mon, 01 Dec 2008 21:01:20 -0000</pubDate></item><item><title>Re: TwitterCards: Grabbing Contact Data from Twitter with Microformats</title><link>http://www.windley.com/archives/2008/12/twittercards_grabbing_contact_data_from_twitter_with_microformats.shtml#comment-4111399</link><description>&lt;p&gt;Hey Phil:&lt;/p&gt;&lt;p&gt;Thanks for the first earnest "Hmm, this is a neat idea" follow up to my Twitter card idea. This is cool and it has caused me to install the plug-in in Firefox (I still have to restart). But based on what Twitter collects from users at sign-in, what I really wish Twitter would do is offer a bit more hCard depth. As it stands now, the amount of data is too lacking for anyone to do decent searches across their followers/followees. For example, what if I just want an alphabetized list with first name, last name, company and title, sorted by company name.  It's not doable. What if people change jobs and or companies.&lt;/p&gt;&lt;p&gt;So, what if we came up with more robust "TwitterCards" and simply referred to them (their URL) from one of the two "bio fields".. .either BIO or Web?  For example, if you look at my profile, both fields contain the following URL&lt;/p&gt;&lt;p&gt;&lt;a href="http://blogs.techweb.com/berlind/wp-content/uploads/berlind/twittercard.xml" rel="nofollow noopener" target="_blank" title="http://blogs.techweb.com/berlind/wp-content/uploads/berlind/twittercard.xml"&gt;http://blogs.techweb.com/be...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;which points to an XML document that contains my RDF-compliant vCard (hey, might as well prepare for the future). Other people get worried about how noisy RDF is, but who cares? All I need to be able to do is go into some editor, edit the card and all it's fields, save it and point to it.  And what noise can't be solve with XLST?&lt;/p&gt;&lt;p&gt;David&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Berlind</dc:creator><pubDate>Mon, 01 Dec 2008 18:55:54 -0000</pubDate></item><item><title>Re: http://blog.jamesurquhart.com/2008/11/in-cloud-computing-good-network-gives.html</title><link>http://blog.jamesurquhart.com/2008/11/in-cloud-computing-good-network-gives.html#comment-3759886</link><description>&lt;p&gt;There's another angle on the intersection of networking and cloud that's also worth pointing out. This point was made by one of the CIOs on stage at Evening in the Cloud at the Enterprise 2.0 conference in June. She worked for an ad agency and they have a strong interest in gaining the benefits of the cloud. But most of the collaboration at her company takes place around bandwidth intensive intellectual property (graphics, videos, etc.). Speed is of the essence and their networks are designed to move that material between end points without delay. It was suggested that a lot of the rendering of that material could take place in the cloud. But her concern was that her users wouldn't be able to retrieve that material out of the cloud nearly as quickly as they can pass it around their own networks.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Berlind</dc:creator><pubDate>Thu, 13 Nov 2008 15:52:51 -0000</pubDate></item><item><title>Re: $99 netbooks (Scripting News)</title><link>http://www.scripting.com/stories/2008/11/03/99Netbooks.html#comment-3456796</link><description>&lt;p&gt;Better model: Instead of $99, I'd prefer the model that Comcast takes with my PVR.... $15 per month (in other words, a monthly rate). Last year, our PVR shit the bucket. Comcast was here the next day, took the broken one and installed the new one. If the service provider can deliver the replacement to me with all my stuff on it (because the service provider happens to run some sort of netbook back up service in the cloud too), I'd be completely sold.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Berlind</dc:creator><pubDate>Mon, 03 Nov 2008 11:27:26 -0000</pubDate></item></channel></rss>