<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Zingaya Blog</title>
	<atom:link href="http://blog.zingaya.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.zingaya.com</link>
	<description>latest news about Zingaya service</description>
	<lastBuildDate>Wed, 15 Feb 2012 20:12:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Web-Browsing from the Couch or the Patio</title>
		<link>http://blog.zingaya.com/2012/02/13/web-browsing-from-the-couch-or-the-patio/</link>
		<comments>http://blog.zingaya.com/2012/02/13/web-browsing-from-the-couch-or-the-patio/#comments</comments>
		<pubDate>Mon, 13 Feb 2012 21:17:26 +0000</pubDate>
		<dc:creator>mschwab</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Useful Tips]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=394</guid>
		<description><![CDATA[If the underlying assumptions behind certain business decisions are no longer true, intelligent companies revisit those decisions. For more than a decade, companies could safely assume that nearly all web-browsing was taking place on the desktop or the tabletop. The screen and the keyboard were large and hands were generally free to perform functions like [...]]]></description>
			<content:encoded><![CDATA[<link type="text/css" rel="stylesheet" href="http://blog.zingaya.com/wp-content/plugins/advanced-iframe/css/ai.css" />
<p>If the underlying assumptions behind certain business decisions are no longer true, intelligent companies revisit those decisions. For more than a decade, companies could safely assume that nearly all web-browsing was taking place on the desktop or the tabletop.<a href="http://blog.zingaya.com/wp-content/uploads/2012/02/6317978_s.jpg"><img class="alignright size-full wp-image-415" style="margin-top: 10px;margin-bottom: 10px" src="http://blog.zingaya.com/wp-content/uploads/2012/02/6317978_s.jpg" alt="" width="282" height="400" /></a> The screen and the keyboard were large and hands were generally free to perform functions like holding and dialing a telephone without impeding simultaneous web-browsing. The emergence of more mobile and portable devices is changing all that. Web-browsing, especially consumer web-browsing, is migrating away from the desktop and the tabletop to places like the couch and the patio. Companies that depend upon their website to drive significant revenues need to assess the impact this migration has on their business and develop new strategies that address the changing medium and venue of web-browsing.</p>
<p>Fortunately, most aspects of web-browsing remain the same. Consumers still visit websites and browse from page to page conducting research and performing self-service. But there are three key differences to consider.</p>
<ul style="margin-left: 50px;font-family: 'Aller';font-size: 15px;color: #6a6e72">
<li>The screen is often smaller.</li>
<li>The keyboard is often smaller and more awkward to use.</li>
<li>Hands are no longer free because they must hold or steady the device.</li>
</ul>
<p>All three of these key differences have a particularly high impact on the website visitor’s ability to interact with a contact center. For many companies, this should raise a big red flag. For them, access to the contact center from the website delivers a significant ROI. For these companies, the contact center augments the website to:</p>
<ul style="margin-left: 50px;font-family: 'Aller';font-size: 15px;color: #6a6e72">
<li>Enhance overall customer experience;</li>
<li>accelerate resolutions;</li>
<li>improve conversion rates; and</li>
<li>increase average order values.</li>
</ul>
<p><a href="http://blog.zingaya.com/wp-content/uploads/2012/02/Forrester-Tablet-540x3291.jpg"><img class="alignleft size-full wp-image-430" src="http://blog.zingaya.com/wp-content/uploads/2012/02/Forrester-Tablet-540x3291.jpg" alt="" width="425" height="296" /></a>Once away from the desktop or the tabletop, interacting with a contact center using conventional means is less appealing and less effective. With hands less free to hold and dial a telephone, toll-free numbers and request-for-callback options are no longer easy or convenient. Those website visitors who do use the telephone find simultaneously interacting with the website difficult. Likewise, a smaller and more awkward keyboard makes click-to-text-chat less attractive. Those website visitors who still initiate click-to-text-chat sessions find their smaller screens offer limited space for both website content and the chat dialog.</p>
<p>Zingaya’s click-to-call solution makes the contact center more accessible to website visitors in this new age when web-browsing takes place on the coach, the patio or just about anywhere. No phone or download is required. Website operators simply embed Zingaya’s click-to-call button next to their other contact options. A single click initiates a call directly to the contact center. The Zingaya call button is easy to create and deploy because it is just a few lines of auto-generated HTML code. Small businesses can sign up directly from our website for as little as $15 per month. Larger businesses, including the most demanding enterprises, can work with our sales and service team to craft a competitive package that will deliver a significant ROI.</p>
<p>Check out our small business plans <a href="http://zingaya.com/plans">here</a>. Alternatively, use one of the contact options below to connect with our sales and service team. You can even use Zingaya’s click-to-call button to reach us from your browser. Perhaps best of all … you can make the call while web-browsing from the couch or the patio!</p>
<p><span style="color: #000000">Matthew Schwab<br />
+1 (650) 520-4165</span><br />
<a href="mailto:mschwab@zingaya.com">mschwab@zingaya.com</a><br />
<iframe id='advanced_iframe' src='http://zingaya.com/buttons/907d3e1148825364e64f5624a9007ec6_1329166647286?width=127&amp;height=54' width='127' height='54' scrolling='no'  frameborder='0'  allowtransparency='true' ></iframe>
 </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2012/02/13/web-browsing-from-the-couch-or-the-patio/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WebRTC version of Zingaya</title>
		<link>http://blog.zingaya.com/2012/01/31/webrtc-version-of-zingaya/</link>
		<comments>http://blog.zingaya.com/2012/01/31/webrtc-version-of-zingaya/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 03:36:54 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Useful Tips]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[pstn]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[web call]]></category>
		<category><![CDATA[WebRTC]]></category>
		<category><![CDATA[Zingaya]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=373</guid>
		<description><![CDATA[DEMO DOESN&#8217;T WORK WITH THE LATEST DEV BUILD OF CHROME, WE WILL FIX IT LATER AND LET YOU KNOW As we mentioned in our previous post Google is working on Google Chrome dev build to let developers play with some first implementation of WebRTC technology. We&#8217;ve prepared a demo to let you try WebRTC right [...]]]></description>
			<content:encoded><![CDATA[<p><strong>DEMO DOESN&#8217;T WORK WITH THE LATEST DEV BUILD OF CHROME, WE WILL FIX IT LATER AND LET YOU KNOW</strong></p>
<p>As we mentioned in our previous post Google is working on Google Chrome dev build to let developers play with some first implementation of WebRTC technology. We&#8217;ve prepared a demo to let you try WebRTC right now, you can check it using this URL <a href="http://demos.zingaya.com/webrtc/" title="Zingaya WebRTC demo" target="_blank">http://demos.zingaya.com/webrtc/</a></p>
<p>There are some useful tips:</p>
<ul style="margin-left: 50px">
<li>You can get Chrome dev build from <a href="http://dev.chromium.org/getting-involved/dev-channel" title="Chrome Dev Build">http://dev.chromium.org/getting-involved/dev-channel</a></li>
<li>To enable WebRTC you need to open <a href="chrome://flags" title="Chrome Flags" target="_blank">chrome://flags</a> in your Chrome dev build and click enable under <strong>&#8220;Enable MediaStream&#8221;</strong> option.</li>
</ul>
<p>Zingaya is always on the edge, and we are proud to be the first company in the world which enabled calls from WebRTC to real phone numbers through our cloud platform. There is still a lot of work to be done for WebRTC community, but current progress is already very impressive!</p>
<p>P.S. you can get the latest info about WebRTC progress at <a href="http://www.webrtc.org/" title="WebRTC" target="_blank">http://www.webrtc.org/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2012/01/31/webrtc-version-of-zingaya/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Great news about WebRTC</title>
		<link>http://blog.zingaya.com/2012/01/19/great-news-about-webrtc/</link>
		<comments>http://blog.zingaya.com/2012/01/19/great-news-about-webrtc/#comments</comments>
		<pubDate>Thu, 19 Jan 2012 08:30:56 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Ericsson]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[Voxeo]]></category>
		<category><![CDATA[web]]></category>
		<category><![CDATA[WebRTC]]></category>
		<category><![CDATA[Zingaya]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=359</guid>
		<description><![CDATA[Today WebRTC became available in the Chrome dev channel, it means that release version of the Chrome browser with WebRTC support will become available soon. Zingaya will use new exciting capabilities of WebRTC to provide our customers and users with the best possible experience. Thanks to Google, Ericsson, Voxeo, Cisco and Mozilla for their work, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.zingaya.com/wp-content/uploads/2012/01/customLogo.png"><img class="alignleft size-full wp-image-363" title="customLogo" src="http://blog.zingaya.com/wp-content/uploads/2012/01/customLogo.png" alt="WebRTC" width="243" height="41" /></a>Today <a title="WebRTC" href="http://www.webrtc.org/blog/webrtcnowavailableinthechromedevchannel">WebRTC became available</a> in the Chrome dev channel, it means that release version of the Chrome browser with WebRTC support will become available soon. Zingaya will use new exciting capabilities of WebRTC to provide our customers and users with the best possible experience. Thanks to Google, Ericsson, Voxeo, Cisco and Mozilla for their work, web-based audio and video calling within the browser will bring new exciting opportunities for all of us!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2012/01/19/great-news-about-webrtc/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Robert Scoble reviews Zingaya</title>
		<link>http://blog.zingaya.com/2012/01/06/robert-scoble-reviews-zingaya/</link>
		<comments>http://blog.zingaya.com/2012/01/06/robert-scoble-reviews-zingaya/#comments</comments>
		<pubDate>Fri, 06 Jan 2012 02:52:30 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Rackspace]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[Robert Scoble]]></category>
		<category><![CDATA[Scobleizer]]></category>
		<category><![CDATA[webcall]]></category>
		<category><![CDATA[Zingaya]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=348</guid>
		<description><![CDATA[It was very exciting to meet with Robert personally in Rackspace HQ today, I want to say BIG thanks to him again for his review of Zingaya. He posted it in Google Plus/FB/Twitter and a lot of people commented and shared it, asked their questions, I tried to answer all of them, sorry if I [...]]]></description>
			<content:encoded><![CDATA[<p>It was very exciting to meet with Robert personally in Rackspace HQ today, I want to say BIG thanks to him again for his review of Zingaya. He posted it in Google Plus/FB/Twitter and a lot of people commented and shared it, asked their questions, I tried to answer all of them, sorry if I missed something. Hopefully I will meet him again after some time and we will discuss Zingaya&#8217;s progress on US market. People are really ready to stay connected (using voice) with businesses online without a phone and we want to bring this capability to as many websites as possible.</p>
<p><strong style="color: black; font-size: 17px; margin: 10px 0px">Robert Scoble: Zingaya is a useful service for companies trying to offer better customer service</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2012/01/06/robert-scoble-reviews-zingaya/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Happy New Year!</title>
		<link>http://blog.zingaya.com/2012/01/01/happy-new-year/</link>
		<comments>http://blog.zingaya.com/2012/01/01/happy-new-year/#comments</comments>
		<pubDate>Sun, 01 Jan 2012 20:01:59 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[2012]]></category>
		<category><![CDATA[happy new year]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=337</guid>
		<description><![CDATA[Thanks to everyone who supported us in the previous year and to all our dear clients! We promise to continue improvement of Zingaya to make it better and add very exciting and useful features in 2012. Stay tuned!]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.zingaya.com/wp-content/uploads/2012/01/zingaya_ny.png"><img class="alignleft size-full wp-image-338" title="zingaya_ny" src="http://blog.zingaya.com/wp-content/uploads/2012/01/zingaya_ny.png" alt="" width="240" height="85" /></a>Thanks to everyone who supported us in the previous year and to all our dear clients! We promise to continue improvement of Zingaya to make it better and add very exciting and useful features in 2012. Stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2012/01/01/happy-new-year/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New improvements in the Control Panel</title>
		<link>http://blog.zingaya.com/2011/12/14/new-improvements-in-the-control-panel/</link>
		<comments>http://blog.zingaya.com/2011/12/14/new-improvements-in-the-control-panel/#comments</comments>
		<pubDate>Wed, 14 Dec 2011 18:49:54 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Useful Tips]]></category>
		<category><![CDATA[improvement]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=325</guid>
		<description><![CDATA[When we were working on the design of our Control Panel we tried to keep menu as simple as possible and that&#8217;s why we had only 1 level menu so far. But when we decided to add some new features it appeared that we couldn&#8217;t do that without adding 2nd level, so this post is [...]]]></description>
			<content:encoded><![CDATA[<p>When we were working on the design of our Control Panel we tried to keep menu as simple as possible and that&#8217;s why we had only 1 level menu so far. But when we decided to add some new features it appeared that we couldn&#8217;t do that without adding 2nd level, so this post is about the latest changes in our menu structure. Hopefully it will help all our existing users to find few sections of the menu which were moved to the second level easily. First of all we prepared the following image with highlighted 2 new menu options:</p>
<p><a href="http://blog.zingaya.com/wp-content/uploads/2011/12/menu_changes_highlighted.png"><img class="alignnone size-full wp-image-326" title="menu_changes_highlighted" src="http://blog.zingaya.com/wp-content/uploads/2011/12/menu_changes_highlighted.png" alt="" width="527" height="45" /></a></p>
<p>Now everything related to payments and billing (Billing Information and Transactions) will appear in the Accounting menu section and you can setup different features (Voicemail, SIP, etc.) by selecting appropriate items in the Features menu section.</p>
<p>P.S. If you have any problems with the new menu it&#8217;s a good idea to clear your browser&#8217;s cache</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2011/12/14/new-improvements-in-the-control-panel/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Chrome with WebRTC support to be released in early 2012</title>
		<link>http://blog.zingaya.com/2011/12/07/chrome-with-webrtc-support-to-be-released-in-early-2012/</link>
		<comments>http://blog.zingaya.com/2011/12/07/chrome-with-webrtc-support-to-be-released-in-early-2012/#comments</comments>
		<pubDate>Wed, 07 Dec 2011 20:01:09 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=307</guid>
		<description><![CDATA[According to the latest news from Google their Chrome browser will get WebRTC support soon. We are waiting eagerly, because Zingaya platform already supports WebRTC and we would like to offer the new level of sound quality and user experience with its amazing capabilities. Hopefully we will be able to get some first working version [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.zingaya.com/wp-content/uploads/2011/12/webrtc.png"><img class="alignright size-full wp-image-308" title="webrtc" src="http://blog.zingaya.com/wp-content/uploads/2011/12/webrtc.png" alt="" width="237" height="43" /></a>According to the latest news from Google their Chrome browser will get WebRTC support soon. We are waiting eagerly, because Zingaya platform already supports WebRTC and we would like to offer the new level of sound quality and user experience with its amazing capabilities. Hopefully we will be able to get some first working version built from trunk before it goes to release and check if we are ready to offer this functionality in our widget. Our first tests were very impressive, although we didn&#8217;t use a lot of cool features Chrome would offer in the release (like audio codecs from GIPS).</p>
<p><strong>P.S. We are going to post the video of Zingaya powered by WebRTC soon, stay tuned!</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2011/12/07/chrome-with-webrtc-support-to-be-released-in-early-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Speeding up Zingaya with Amazon CloudFront</title>
		<link>http://blog.zingaya.com/2011/11/14/speeding-up-zingaya-with-amazon-cloudfront/</link>
		<comments>http://blog.zingaya.com/2011/11/14/speeding-up-zingaya-with-amazon-cloudfront/#comments</comments>
		<pubDate>Mon, 14 Nov 2011 19:19:02 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Amazon]]></category>
		<category><![CDATA[cloud]]></category>
		<category><![CDATA[CloudFront]]></category>
		<category><![CDATA[speed]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[Zingaya]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=291</guid>
		<description><![CDATA[Today we&#8217;ve upgraded Zingaya to use Amazon CloudFront and it increased speed a lot, especially in Europe and Russia (because Zingaya&#8217;s core is situated in US). Amazon&#8217;s Edge servers are located in all parts of the world and used to send the static content (including Zingaya button images and Zingaya widget images) to the end [...]]]></description>
			<content:encoded><![CDATA[<p>Today we&#8217;ve upgraded Zingaya to use Amazon CloudFront and it increased speed a lot, especially in Europe and Russia (because Zingaya&#8217;s core is situated in US). Amazon&#8217;s Edge servers are located in all parts of the world and used to send the static content (including Zingaya button images and Zingaya widget images) to the end users. We recommend to change zingaya.com to cdn.zingaya.com in CSS code of the button, or you can generate the HTML code again to get updated version.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2011/11/14/speeding-up-zingaya-with-amazon-cloudfront/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Zingaya upgraded, new features include bandwidth check and better sound quality with Flash 11</title>
		<link>http://blog.zingaya.com/2011/11/10/zingaya-upgraded-new-features-include-bandwidth-check-and-native-g-711-support-for-flash-11/</link>
		<comments>http://blog.zingaya.com/2011/11/10/zingaya-upgraded-new-features-include-bandwidth-check-and-native-g-711-support-for-flash-11/#comments</comments>
		<pubDate>Thu, 10 Nov 2011 16:49:27 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[bandwidth]]></category>
		<category><![CDATA[check]]></category>
		<category><![CDATA[Flash 11]]></category>
		<category><![CDATA[G.711]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[sound]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[Zingaya]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=268</guid>
		<description><![CDATA[We continue improving Zingaya to provide with the best possible sound quality. New version of the widget uses special bandwidth check feature that helps to detect the audio codec which will be used for the call and check if call is possible with currently available bandwidth and ping. If detected bandwidth or ping isn&#8217;t good [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.zingaya.com/wp-content/uploads/2011/11/audio.jpg"><img class="size-full wp-image-273 alignleft" title="audio" src="http://blog.zingaya.com/wp-content/uploads/2011/11/audio.jpg" alt="" width="208" height="208" /></a>We continue improving Zingaya to provide with the best possible sound quality. New version of the widget uses special bandwidth check feature that helps to detect the audio codec which will be used for the call and check if call is possible with currently available bandwidth and ping. If detected bandwidth or ping isn&#8217;t good enough for a good call quality system will notify about that and will ask to call again later [when network connection is good enough].</p>
<p>We are working on another few updates for significant increase in speed and performance of our website and widget in Europe and Russia. Stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2011/11/10/zingaya-upgraded-new-features-include-bandwidth-check-and-native-g-711-support-for-flash-11/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>What to do if Adobe Flash 11 crashes in Mac OS X</title>
		<link>http://blog.zingaya.com/2011/10/27/what-to-do-if-adobe-flash-11-crashes-in-mac-os-x/</link>
		<comments>http://blog.zingaya.com/2011/10/27/what-to-do-if-adobe-flash-11-crashes-in-mac-os-x/#comments</comments>
		<pubDate>Thu, 27 Oct 2011 20:01:08 +0000</pubDate>
		<dc:creator>Alexey</dc:creator>
				<category><![CDATA[Useful Tips]]></category>
		<category><![CDATA[Adobe]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[crash]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[Flash 11]]></category>
		<category><![CDATA[Fonts]]></category>

		<guid isPermaLink="false">http://blog.zingaya.com/?p=254</guid>
		<description><![CDATA[Unfortunately on many Macs Adobe Flash crashes all the time (in all browsers) after an upgrade to the new version. After some investigation Adobe informed that the reason is in some 3rd party Fonts you could install, we are posting the solution for those who have this problem and hope that Adobe will fix it [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.zingaya.com/wp-content/uploads/2011/10/flashcrash.jpg"><img class="alignright size-full wp-image-255" title="flashcrash" src="http://blog.zingaya.com/wp-content/uploads/2011/10/flashcrash.jpg" alt="" width="130" height="110" /></a>Unfortunately on many Macs Adobe Flash crashes all the time (in all browsers) after an upgrade to the new version. After some investigation Adobe informed that the reason is in some 3rd party Fonts you could install, we are posting the solution for those who have this problem and hope that Adobe will fix it in the next release (ASAP).</p>
<p>The steps are:<br />
1. exit out of all applications<br />
2. launch terminal<br />
3. type the following and hit return: sudo fs_usage -f pathname | grep Font<br />
4. launch firefox and navigate to youtube<br />
5. view the output in terminal for the font that is causing the crash<br />
6. move the font outside of the font directory (save it somewhere else if you need it for other work)<br />
7. refresh the browser window with youtube<br />
8. view the output in terminal again and repeat moving the questional font outside to another location<br />
9. keep repeating until you no longer get errors<br />
10. if it turns out ok, after the final refresh&#8230; content should disply</p>
<p>P.S. you can get more info in Adobe Forums <a href="http://forums.adobe.com/message/3960342?tstart=0" title="Adobe Forums">http://forums.adobe.com/message/3960342?tstart=0</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.zingaya.com/2011/10/27/what-to-do-if-adobe-flash-11-crashes-in-mac-os-x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

