<?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 yaniv</title><link>http://disqus.com/by/yaniv/</link><description></description><atom:link href="http://disqus.com/yaniv/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 31 Aug 2010 07:29:39 -0000</lastBuildDate><item><title>Re: AOL Answers Sees The Light Of Day, 3 Years After AOL’s Acquisition Of Yedda</title><link>http://techcrunch.com/2010/08/31/aol-answers/#comment-73482954</link><description>&lt;p&gt;Robin, you're very quick - it's been less than 2 hours since it quietly went up :)&lt;/p&gt;&lt;p&gt;Anyway, while I understand that yesterday's news are, well, yesterday's, you might want to refer to the old TechCrunch posts covering Yedda - I believe you'll find out that it actually compares pretty well against what you call next-generation Q&amp;amp;A services.&lt;/p&gt;&lt;p&gt;If you can't find the time to do that, I'd be more than happy to walk you through the comparison. Some key points we could look at together - semantic search and matching, proactive distribution of questions, tapping the social graph (both Facebook and Twitter), automatic categorization, and probably quite a few more.&lt;/p&gt;&lt;p&gt;This is not meant to disparage these newer services - some of them are pretty good. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Tue, 31 Aug 2010 07:29:39 -0000</pubDate></item><item><title>Re: Buzz, blogsphere and serial killers</title><link>http://pravdam.com/2010/02/18/buzz-blogsphere-and-serial-killers/#comment-37034979</link><description>&lt;p&gt;There is a very simple way to measure the maturity of a service.&lt;/p&gt;&lt;p&gt;If most of the posts you're seeing are about the service itself, or if such posts dominate the "most popular" lists, it's still in the Scoble phase. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Fri, 26 Feb 2010 16:16:36 -0000</pubDate></item><item><title>Re: How to add a tweet this button with auto TinyURL or Bit.ly shortening</title><link>https://www.ruhanirabin.com/how-to-add-a-twitthis-button-with-tinyurl-or-bitly-api/#comment-32276894</link><description>&lt;p&gt;Quick fix - the code breaks when the URL contains Unicode characters.&lt;/p&gt;&lt;p&gt;To fix that, use your favorite Unicode-compatible URL encoding function before sending the URL to &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt;, and when parsing the response, replace:&lt;/p&gt;&lt;p&gt;$bitlyurl = $bitlycontent["results"][$url]["shortUrl"];&lt;/p&gt;&lt;p&gt;with:&lt;/p&gt;&lt;p&gt;        $temp = array_values($bitlycontent["results"]);&lt;br&gt;        $bitlyurl = $temp[0]["shortUrl"];&lt;/p&gt;&lt;p&gt;This removes the dependency on both &lt;a href="http://bit.ly" rel="nofollow noopener" target="_blank" title="bit.ly"&gt;bit.ly&lt;/a&gt; and you encoding the URL the same way. &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Mon, 01 Feb 2010 07:38:57 -0000</pubDate></item><item><title>Re: Why today's Twitter is like Napster in Y2K. (Scripting News)</title><link>http://www.scripting.com/stories/2009/12/19/whyTodaysTwitterIsLikeNaps.html#comment-26726199</link><description>&lt;p&gt;Or, you could go the other way:&lt;/p&gt;&lt;p&gt;@username is the pointer to my personal stream in the current service&lt;/p&gt;&lt;p&gt;@username@domain.com is the pointer to my personal stream on a &lt;a href="http://domain.com" rel="nofollow noopener" target="_blank" title="domain.com"&gt;domain.com&lt;/a&gt;. To resolve the pointer, use some kind of discovery API on &lt;a href="http://domain.com" rel="nofollow noopener" target="_blank" title="domain.com"&gt;domain.com&lt;/a&gt;, which will return the URL to my actual stream&lt;/p&gt;&lt;p&gt;@username@domainalias is the same as @username@domain.com, only shorter :) requires my current service to support this specific alias. Right now, we'll probably all want to support @username@twitter, though later there will probably be other major players we'll want to support.&lt;/p&gt;&lt;p&gt;I don't want Twitter to be the central clearing house for my identity. I have ClaimID for that (e.g. &lt;a href="http://claimid.com/yanivg)" rel="nofollow noopener" target="_blank" title="http://claimid.com/yanivg)"&gt;http://claimid.com/yanivg)&lt;/a&gt;. I want my identity to be able to able to include references to my Twitter (and later, BranxX) conversation stream. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Sun, 20 Dec 2009 04:55:43 -0000</pubDate></item><item><title>Re: Yaniv Golan Calls Twitter &amp;#8220;The 140-characters Netscape&amp;#8221;</title><link>http://www.blonde2dot0.com/blog/2009/12/07/yaniv-golan-calls-twitter-the-140-characters-netscape/#comment-25263241</link><description>&lt;p&gt;Not necessarily.&lt;/p&gt;&lt;p&gt;Twitter has an impressive but still limited reach at this point - a few tens of millions, depending on who's counting and how.&lt;/p&gt;&lt;p&gt;If a competing microblogging platform could end up being installed as the default on all Nokia phones, or - more likely - Googlephones - it could surpass Twitter in reach even if it was an inferior service. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Wed, 09 Dec 2009 03:38:10 -0000</pubDate></item><item><title>Re: Yaniv Golan Calls Twitter &amp;#8220;The 140-characters Netscape&amp;#8221;</title><link>http://www.blonde2dot0.com/blog/2009/12/07/yaniv-golan-calls-twitter-the-140-characters-netscape/#comment-25263155</link><description>&lt;p&gt;Obviously, I am not a fortune teller, and if there is one thing you can always count on, it's surprises :)&lt;/p&gt;&lt;p&gt;However, to make things even worse, my view isn't even bipolar, it's uni-polar - I don't think Twitter will survive by becoming a giant.&lt;/p&gt;&lt;p&gt;I see a chance for Twitter to be around long term if it becomes the leader in establishing open standards that enable interoperability with its competitors. And no, this is not an oxymoron.&lt;/p&gt;&lt;p&gt;Based on observing the (admittedly somewhat short) history of the net, I don't think Twitter can survive long term if they insist on becoming the one and only funnel. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Wed, 09 Dec 2009 03:33:16 -0000</pubDate></item><item><title>Re: The chat room/forum problem (&amp;#038; an apology to @Technosailor)</title><link>http://scobleizer.com/2009/11/02/the-chat-roomforum-problem-an-apology-to-technosailor/#comment-21652288</link><description>&lt;p&gt;I agree with your analysis. But I think there is one more thing that makes FriendFeed a less-then-optimal conversation platform, and that is the user intent.&lt;/p&gt;&lt;p&gt;People talk(ed) on FriendFeed. They started meaningful discussions, and participated in meaningful discussions. And that was interesting.&lt;/p&gt;&lt;p&gt;But FriendFeed is also very much a lifestream platform. Which means that when viewing my FF stream, I could see these bits that people put their mind to ( = posted with the intent of posting them to FF), but also lots of automatic bits, that FF was kind enough to collect from their various other online "places" - Flickr photos, Delicious links, etc.&lt;/p&gt;&lt;p&gt;These bits were created without an *intent*, and are therefore boring. They are mostly noise.&lt;/p&gt;&lt;p&gt;As a person who consumes a lot of information during the day, this is useful. I get a quick summary of what's going on without having to go places. But being useful is not the same as being interesting. FF was useful, but it wasn't very interesting.&lt;/p&gt;&lt;p&gt;Contrast that with Twitter. Most of the tweets are posted with intent. People intend to say something. Hence, the stream is interesting.&lt;/p&gt;&lt;p&gt;Facebook suffers from the same problem.&lt;/p&gt;&lt;p&gt;The same problem though is slowly creeping into Twitter, with automatic tweets from authenticated apps like FourSquare, Spymaster and friends. It's great for you that you just unlocked the explorer-whatever at wherever, but obviously, it is not very interesting.&lt;/p&gt;&lt;p&gt;I wish Twitter would acquire apps to always present the tweets they tweet on behalf of a person to the person, in edit mode, before they get posted. That would make it an intentional act, and IMO would prevent the boring-automatic-noise issue.&lt;/p&gt;&lt;p&gt;Lifestream is useful for us mass-information-consumers, but it's boring. Plus, most of the people are not multi-service mass-information-consumers, they just want to engage. With other people. In a meaningful way. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Mon, 02 Nov 2009 03:03:55 -0000</pubDate></item><item><title>Re: The Internet abhors a funnel (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/17/theInternetAbhorsAFunnel.html#comment-20308835</link><description>&lt;p&gt;I agree. It does feel like a fundamental law of this medium, and I've never met a company that was able to resist its implications long term. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Sun, 18 Oct 2009 04:32:00 -0000</pubDate></item><item><title>Re: Flickr Lost Its Appeal</title><link>http://www.blonde2dot0.com/blog/2009/09/17/flickr-lost-its-appeal/#comment-17207980</link><description>&lt;p&gt;I share your pain, Ilan. You asked me on Twitter - what will I switch to. I don't have an answer yet,  but one thing I know is that I will not be so quick to switch to another service that holds that much power over my content *I've* created. Power corrupts :)&lt;/p&gt;&lt;p&gt;One thing though - while I appreciate the compliment, I do have to say that this is not doing Thomas justice :) in fact, when  I grow up, I want to be a Thomas Hawk. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Wed, 23 Sep 2009 03:56:07 -0000</pubDate></item><item><title>Re: How to fix URL-shorteners (Scripting News)</title><link>http://www.scripting.com/stories/2009/08/19/howToFixUrlshorteners.html#comment-15347212</link><description>&lt;p&gt;Oh, I agree re existing domain names being short enough and the value to the reader - that was my point, I guess it wasn't clear enough.&lt;/p&gt;&lt;p&gt;Re 3rd party tracking, yes, the value is the ego boost, and also the ability to understand how something spreads across the net and who are the real influencers. For companies like &lt;a href="http://tra.cx" rel="nofollow noopener" target="_blank" title="http://tra.cx"&gt;http://tra.cx&lt;/a&gt; this is invaluable information. It could be provided by the conversational media (e.g. Twitter) or by the publishing infrastructure (e.g. Wordpress).&lt;/p&gt;&lt;p&gt;And of course, once we have multiple stat-providers, there will be companies that will create services that will aggregate all these stats in one place, creating a new industry segment, and so the cycle continues... &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Tue, 25 Aug 2009 06:55:30 -0000</pubDate></item><item><title>Re: How to fix URL-shorteners (Scripting News)</title><link>http://www.scripting.com/stories/2009/08/19/howToFixUrlshorteners.html#comment-15345672</link><description>&lt;p&gt;Good point. Using the same domain name will improve performance, and reduce use confusion. It will also fix the incentives - the folks with the most incentive to keep links from rotting are the content publishers. See &lt;a href="http://yaniv.golan.name/blog/2009/08/18/of-breweries-and-url-shorteneres/" rel="nofollow noopener" target="_blank" title="http://yaniv.golan.name/blog/2009/08/18/of-breweries-and-url-shorteneres/"&gt;http://yaniv.golan.name/blo...&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;We'll be losing the "tracking" aspect of the current 3rd party short URLs, but this tracking is already quite unreliable given the non-unique nature of the short URLs. Perhaps it would be in the interest of Twitter etc to provide this click tracking capability. It'd still be unreliable, but would be far less damaging to the net infrastructure. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Tue, 25 Aug 2009 04:41:15 -0000</pubDate></item><item><title>Re: FasterWeb Gets Investment &amp;#8211; Pushed To Go Faster</title><link>http://www.blonde2dot0.com/blog/2009/07/19/fasterweb-gets-investment-pushed-to-go-faster/#comment-12942252</link><description>&lt;p&gt;This is exactly why I think that open source should have been a cornerstone of their strategy. And yes, without I do believe the biz model is at risk, and sale cycles will be long and hard.&lt;/p&gt;&lt;p&gt;Still, they provide a lot of value - and they are smart folks - I am sure they will find the right formula. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Mon, 20 Jul 2009 03:16:11 -0000</pubDate></item><item><title>Re: FasterWeb Gets Investment &amp;#8211; Pushed To Go Faster</title><link>http://www.blonde2dot0.com/blog/2009/07/19/fasterweb-gets-investment-pushed-to-go-faster/#comment-12941906</link><description>&lt;p&gt;Kfir,&lt;/p&gt;&lt;p&gt;FasterWeb is addressing the non-bandwidth issues actually - from latency to client-side render time issues.&lt;/p&gt;&lt;p&gt;Higher bandwidth will only further highlight the need for this kind of optimizations.&lt;/p&gt;&lt;p&gt;Check out this Yahoo! article - &lt;a href="http://developer.yahoo.com/performance/rules.html" rel="nofollow noopener" target="_blank" title="http://developer.yahoo.com/performance/rules.html"&gt;http://developer.yahoo.com/...&lt;/a&gt; - you will notice that many of the suggestions there have nothing to do with bandwidth-related issues. FasterWeb does some of this, as well as some more advanced optimizations made possible by its server-side components.&lt;/p&gt;&lt;p&gt;I am less comfortable with other elements in FasterWeb's strategy (as it was a few weeks ago when I participated in a due diligence process on FW) - I strongly believe it would have made sense for them to work more closely with the open source community for at least part oft their offering. &lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Mon, 20 Jul 2009 02:45:42 -0000</pubDate></item><item><title>Re: User data ownership on Facebook and why it doesn&amp;#8217;t matter</title><link>http://scobleizer.com/2009/02/17/ownership_facebook/#comment-9714928</link><description>&lt;p&gt;Robert,&lt;/p&gt;&lt;p&gt;At the risk of shooting my own foot, I for one would love stronger - much stronger - regulations on what companies can and cannot do with user accounts and user data, as well as an external "appeal" entity.&lt;/p&gt;&lt;p&gt;You read the TOS, and you know what you're signing up for. I don't think it's reasonable to expect everyone to be as savvy though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Tue, 17 Feb 2009 11:26:24 -0000</pubDate></item><item><title>Re: צרות במספר המשתמשים הפעילים באתרי התוכן</title><link>http://www.thecoils.com/2007/05/17/real_active_users/#comment-19714129</link><description>&lt;p&gt;שימו לב שלפחות במקרה של פליקר, חלק נכבד (הרוב?) של העלאות התמונות לא מתבצע דרך דף ה UPLOAD - שזה מה שנמדד פה - אלא דרך כלים אחרים - Uploadr, ווידג'טים למיניהם, אימייל ועוד. כך שכנראה שהמספר גדול משמעותית מ 0.2%.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Sat, 26 May 2007 12:24:26 -0000</pubDate></item><item><title>Re: אתגר המוגבלויות של Web2.0</title><link>http://www.thecoils.com/2006/03/19/web-20-accessibility/#comment-19713280</link><description>&lt;p&gt;שושנה,&lt;/p&gt;&lt;p&gt;זה לא תאוריה :)&lt;/p&gt;&lt;p&gt;תוספת שעוזרת, היא לאפשר את רוב הפעולות - מלבד באמצעות AJAX - גם בדרכים "נגישות". &lt;br&gt;יש מקרים שזה בלתי אפשרי (תלוי בסוג האתר), אבל ברוב המקרים זה בהחלט אפשרי...&lt;/p&gt;&lt;p&gt;לייצר גרסה נפרדת שהיא נגישה זה - לטעמי - מסובך יותר - קשה לדאוג שגרסה נפרדת תשאר מסנוכרנת ובאותה רמה כמו הגירסה הרגילה.&lt;/p&gt;&lt;p&gt;ואולי הידיד שלך ירצה לעזור לנו בבדיקות נגישות ב- &lt;a href="http://www.yedda.com" rel="nofollow noopener" target="_blank" title="http://www.yedda.com"&gt;Yedda&lt;/a&gt;?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Mon, 27 Mar 2006 08:23:49 -0000</pubDate></item><item><title>Re: אתגר המוגבלויות של Web2.0</title><link>http://www.thecoils.com/2006/03/19/web-20-accessibility/#comment-19713278</link><description>&lt;p&gt;פתרון יותר פשוט זה "graceful degradation" - תכונה של הישום, שעוברת אוטומטית למצב "פשוט" כאשר היא מזהה דפדפן שאינו תומך בכל הפיצ'קס. למשל, אם הדפדפן לא תומך ב- JavaScript, הישום חוזר להשתמש בהחלפת דפים מבוססת שרת פשוטה, ללא שימוש בטכנולוגיות AJAX למיניהם.&lt;/p&gt;&lt;p&gt;טכניקה זו אינה טריוואלית ודורשת תכנון והשקעה, אולם לדעתי היא מביאה - מעבר ליתרונותיה למשתמשים בעלי המוגבלויות - גם לישומים טובים יותר ונכונים יותר באופן כללי.&lt;/p&gt;&lt;p&gt;קל יותר ליישם את הטכניקה הזאת אם מתחילים את תכנון היישום ללא הנחות לגבי יכולות AJAX ודואגים שהכל יעבוד קודם כל ללא AJAX, ורק אז מוסיפים AJAX אופציונלי איפה שבאמת צריך.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaniv Golan</dc:creator><pubDate>Mon, 20 Mar 2006 10:41:07 -0000</pubDate></item></channel></rss>