<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="https://notiz.blog/wp-content/plugins/pretty-feeds/pretty-feed-v4.xsl" type="text/xsl" media="screen" ?>


<!--

	Feeds whisper secrets,
	In the RSS Club's embrace,
	Knowledge blooms in grace.

-->

<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/"
	xmlns:source="http://source.scripting.com/"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>fatigue &#8211; notizBlog</title>
	<atom:link href="https://notiz.blog/tag/fatigue/feed/" rel="self" type="application/rss+xml" />
	<link>https://notiz.blog</link>
	<description>a weblog mainly about the open, portable, interoperable, small, social, synaptic, semantic, structured, distributed, (re-)decentralized, independent, microformatted and federated social web</description>
	<lastBuildDate>Wed, 01 Mar 2023 15:48:05 +0000</lastBuildDate>
	<language>de</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://notiz.blog/wp-content/uploads/2019/10/cropped-notizblog-icon-1-32x32.png</url>
	<title>fatigue &#8211; notizBlog</title>
	<link>https://notiz.blog</link>
	<width>32</width>
	<height>32</height>
</image> 
<source:blogroll>https://reader.pfefferle.org/i/?a=opml&amp;get=c_2</source:blogroll>
<creativeCommons:license>https://creativecommons.org/licenses/by-sa/4.0/</creativeCommons:license>
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com"/>
<atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com"/>
<atom:link rel="hub" href="https://switchboard.p3k.io/"/>
<atom:link rel="self" href="https://notiz.blog/tag/fatigue/feed/"/>
<atom:link rel="search" type="application/opensearchdescription+xml" title="Search notizBlog" href="https://notiz.blog/wp-api/opensearch/1.1/document" />	<item>
		<title>DataPortability Fatigue</title>
		<link>https://notiz.blog/2008/05/13/dataportability-fatigue/</link>
					<comments>https://notiz.blog/2008/05/13/dataportability-fatigue/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Tue, 13 May 2008 19:37:30 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Data Availability]]></category>
		<category><![CDATA[DataPortability]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[fatigue]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[myspace]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=859</guid>

					<description><![CDATA[Nach seinem Artikel über DataPortability und Chris Saads Antwort, äußert sich Chris Messina nochmals sehr kritisch zu dem Thema in der DP Google-Group. Gerade nach den Pressemeldungen über MySpaces &#8222;Data Availability&#8220;: [&#8230;] MySpace is announcing a broad ranging embrace of data portability standards today, along with data sharing partnerships with Yahoo, Ebay, Twitter and their [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Nach seinem <a href="http://factoryjoe.com/blog/2008/05/11/thoughts-on-dataportability/">Artikel über DataPortability</a> und <a href="http://chrissaad.wordpress.com/2008/05/12/responses-to-dataportability-questions/">Chris Saads Antwort</a>, äußert sich Chris Messina nochmals sehr kritisch zu dem Thema in der <a href="http://groups.google.com/group/dataportabilityactionsteering/browse_thread/thread/5102dd84d2ddec0d/3a8b31cae01dc294#3a8b31cae01dc294">DP Google-Group</a>.</p>



<p>Gerade nach den Pressemeldungen über MySpaces &#8222;Data Availability&#8220;:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>[&#8230;] MySpace is announcing a broad ranging embrace of data portability standards today, along with data sharing partnerships with Yahoo, Ebay, Twitter and their own Photobucket subsidiary. [&#8230;] <a href="http://www.techcrunch.com/2008/05/08/myspace-embraces-data-portability-partners-with-yahoo-ebay-and-twitter/">#</a></p>
</blockquote>



<p>&#8230;oder über Googles &#8222;Friend Connect&#8220;:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>As we reported on Friday, Google will be launching its own data portability effort called Friend Connect. [&#8230;] <a href="http://www.techcrunch.com/2008/05/12/google-confirms-friend-connect/">#</a></p>
</blockquote>



<p>&#8230;ist (meiner Meinung nach) einer der treffendsten Punkte in <a href="http://groups.google.com/group/dataportabilityactionsteering/browse_thread/thread/5102dd84d2ddec0d/3a8b31cae01dc294#3a8b31cae01dc294">Chris&#8216; Kommentar</a>:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>The behavior indicates [&#8230;] that the DP-PR machine is simply more effective at taking credit for big moves that they had nothing directly to do with than to promote smaller independent, more &#8222;grassroots&#8220; groups who are *actually* making moves towards effective data portability, like Dopplr, like TripIt, like Satisfaction and Twitter and the rest. I don&#8217;t believe I&#8217;ve seen any press releases go out about them, and yet I would consider them to be on the vanguard giving people access to their data in real-world, useful ways.</p>
</blockquote>



<p>Ich muss Chris Messina leider recht geben, keines der groß angekündigten (<strong>und mit DataPortability in Verbindung gebrachten</strong>) Systeme betreibt wirklich DataPortability (zumindest zum aktuellen Zeitpunkt). Sowohl MySpace als auch Google verwenden zwar offene Standards (Facebook nutzt sogar keinen der erwähnten Standards für &#8222;Facebook Connect&#8220;) wie <a href="http://oauth.net">OAuth</a> oder <a href="https://web.archive.org/web/20180217084508/http://openid.com:80/">OpenID</a>, aber bisher leider nur hinter ihren &#8222;<a href="https://en.wikipedia.org/wiki/Closed_platform">Walled Gardens</a>&#8222;.<br/> Was ist mit den wahren <abbr title="DataPortability">DP</abbr> &#8222;Helden&#8220; wie <a href="http://pixelsebi.com/2007-06-25/dopplr-importiert-social-network-auf-basis-von-microformats/">Dopplr</a>, <a href="https://web.archive.org/web/http://www.notsorelevant.com/2008-03-15/open-standards-magnolia-as-an-example/">Magnolia</a> oder <a href="https://web.archive.org/web/20080831104943/http://getsatisfaction.com/people/new">Satisfaction</a>, die wirkliche Anwendungsfälle schaffen und sich dem Ziel der portablen Daten Schritt für Schritt nähern?</p>



<p><a href="https://web.archive.org/web/http://www.notsorelevant.com/2008-05-11/data-portability-lets-get-rid-of-it/">Carsten Pötter</a> beschreibt das bestehende Problem auch noch einmal von einer etwas anderen Seite:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>DataPortability, Data Availability, Facebook Connect, Google Friend Connect, DiSo,&#8230; [&#8230;] All the mentioned initiatives just lead to confusion. We can’t be sure if we mean the same thing when talking about data portability anymore. It’s probably best to abandon that term and just focus on single issues. Can I export my profile or can it just be accessed by a third party?</p>
</blockquote>



<p>Man sollte in Zukunft vielleicht etwas sparsamer mit dem <em>Titel</em> DataPortability umgehen und ihn <a href="https://notiz.blog/2008/05/02/sind-eine-hcard-und-ein-wenig-xfn-jetzt-schon-dataportability/">nicht für jede &#8222;simple&#8220; hCard <em>vergeben</em></a>.</p>
<p>Congratulations on being an RSS reader! You are part of an elite group of people who know how to stay updated in style.</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/05/13/dataportability-fatigue/feed/</wfw:commentRss>
			<slash:comments>8</slash:comments>
		
		
			</item>
	</channel>
</rss>
