<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Twitter kills flash apps</title>
	<link>http://team.bkwld.com/2008/03/15/twitter-kills-flash-apps/</link>
	<description>Team BKWLD</description>
	<pubDate>Tue, 06 Jan 2009 09:46:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Zach</title>
		<link>http://team.bkwld.com/2008/03/15/twitter-kills-flash-apps/#comment-2305</link>
		<pubDate>Fri, 21 Mar 2008 06:26:05 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/03/15/twitter-kills-flash-apps/#comment-2305</guid>
					<description>Flickr also went through some of the same issues way back... which is why their API endpoint is api.flickr.com, and they moved the crossdomain to that domain and removed it from flickr.com. other APIs do OAuth and use yahooapis.com as the API end-point. 

The sad part is that adobe will be further tightening the security in Flash in their next update. But, remember you can always use a server-side proxy ;)</description>
		<content:encoded><![CDATA[<p>Flickr also went through some of the same issues way back&#8230; which is why their API endpoint is api.flickr.com, and they moved the crossdomain to that domain and removed it from flickr.com. other APIs do OAuth and use yahooapis.com as the API end-point. </p>
<p>The sad part is that adobe will be further tightening the security in Flash in their next update. But, remember you can always use a server-side proxy ;)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Robert</title>
		<link>http://team.bkwld.com/2008/03/15/twitter-kills-flash-apps/#comment-2266</link>
		<pubDate>Tue, 18 Mar 2008 14:44:03 +0000</pubDate>
		<guid>http://team.bkwld.com/2008/03/15/twitter-kills-flash-apps/#comment-2266</guid>
					<description>One of the suggestions from that link, interesting.
1. Move the Twitter API to api.twitter.com.  Use the completely permissive crossdomain.xml on api.twitter.com. 
2. Stop supporting HTTP Basic auth. on api.twitter.com.  Implement OAuth or some other kind of auth. token system. 
3. Require non-public API requests to include a valid user auth. token.</description>
		<content:encoded><![CDATA[<p>One of the suggestions from that link, interesting.<br />
1. Move the Twitter API to api.twitter.com.  Use the completely permissive crossdomain.xml on api.twitter.com.<br />
2. Stop supporting HTTP Basic auth. on api.twitter.com.  Implement OAuth or some other kind of auth. token system.<br />
3. Require non-public API requests to include a valid user auth. token.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
