<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	>
<channel>
	<title>Kommentare zu: Neue Richtlinien für Anwendungen</title>
	<atom:link href="http://www.facebookbiz.de/artikel/neue-richtlinien-fur-anwendungen/%20/feed" rel="self" type="application/rss+xml" />
	<link>http://www.facebookbiz.de/artikel/neue-richtlinien-fur-anwendungen/ </link>
	<description>Ein Social Media Marketing Blog</description>
	<pubDate>Fri, 30 Jul 2010 14:04:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Von: Gregor</title>
		<link>http://www.facebookbiz.de/artikel/neue-richtlinien-fur-anwendungen//comment-page-1#comment-181</link>
		<dc:creator>Gregor</dc:creator>
		<pubDate>Mon, 30 Nov 2009 20:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.facebookbiz.de/?p=834#comment-181</guid>
		<description>Viel interessanter finde ich das folgendes, denn das beeinflußt Apps schon sehr:

V. Application Integration Points

   1. You must not incentivize users to grant additional permissions or use Application Integration Points.
   2. You must not provide users with rewards or gate content from users based on their number of friends who use your application.
   3. You must not require users to grant additional permissions or add Application Integration Points, and must only request extended permissions at reasonable times when the user engages with features that would require the use.
   4. You must not prompt users to send invitations, requests, generate notifications, or use other Facebook communication channels immediately after a user allows access or returns to your application.
   5. You must provide users with a "skip" button on any page where users are prompted to use a Facebook communication channel (e.g., invitations, requests, and notifications) that is adjacent to and the same size and design of the send option. If a user chooses to "skip" you must not present the user with a similar prompt during that user's visit to your application.
   6. You must not pre-select more than one person to receive information through a Facebook communication channel.
   7. You must only use one Facebook communication channel in response to a user's single action.
   8. You must not pre-fill the name, title, user_message parameter, or description of Photos, Videos, Notes, Links, Share, or Stream stories, unless the user generated the content earlier in the workflow.
   9. Your Application tab label must not contain a call to action (e.g., "Click Here").
  10. You must not prompt users to bookmark your application (e.g., by using a modal window or pop-up dialog). Instead, users must explicitly invoke any bookmark option you provide.</description>
		<content:encoded><![CDATA[<p>Viel interessanter finde ich das folgendes, denn das beeinflußt Apps schon sehr:</p>
<p>V. Application Integration Points</p>
<p>   1. You must not incentivize users to grant additional permissions or use Application Integration Points.<br />
   2. You must not provide users with rewards or gate content from users based on their number of friends who use your application.<br />
   3. You must not require users to grant additional permissions or add Application Integration Points, and must only request extended permissions at reasonable times when the user engages with features that would require the use.<br />
   4. You must not prompt users to send invitations, requests, generate notifications, or use other Facebook communication channels immediately after a user allows access or returns to your application.<br />
   5. You must provide users with a &#8220;skip&#8221; button on any page where users are prompted to use a Facebook communication channel (e.g., invitations, requests, and notifications) that is adjacent to and the same size and design of the send option. If a user chooses to &#8220;skip&#8221; you must not present the user with a similar prompt during that user&#8217;s visit to your application.<br />
   6. You must not pre-select more than one person to receive information through a Facebook communication channel.<br />
   7. You must only use one Facebook communication channel in response to a user&#8217;s single action.<br />
   8. You must not pre-fill the name, title, user_message parameter, or description of Photos, Videos, Notes, Links, Share, or Stream stories, unless the user generated the content earlier in the workflow.<br />
   9. Your Application tab label must not contain a call to action (e.g., &#8220;Click Here&#8221;).<br />
  10. You must not prompt users to bookmark your application (e.g., by using a modal window or pop-up dialog). Instead, users must explicitly invoke any bookmark option you provide.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
