<?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>E-Mail &#8211; notizBlog</title>
	<atom:link href="https://notiz.blog/tag/e-mail/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>Sun, 06 Jun 2021 16:05:26 +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>E-Mail &#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/e-mail/feed/"/>
<atom:link rel="search" type="application/opensearchdescription+xml" title="Search notizBlog" href="https://notiz.blog/wp-api/opensearch/1.1/document" />	<item>
		<title>OpenIDs sind wie Autos</title>
		<link>https://notiz.blog/2008/11/18/openids-sind-wie-autos/</link>
					<comments>https://notiz.blog/2008/11/18/openids-sind-wie-autos/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Tue, 18 Nov 2008 12:08:20 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[E-Mail]]></category>
		<category><![CDATA[EAUT]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[UX]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1292</guid>

					<description><![CDATA[’&#8230;it’s just proving hard to get people to understand that. Using horses is all they know and the user testing suggests that getting people to switch to something so foreign as an automobile will be near impossible. Maybe we could make some changes so that adoption is easier?’ own your identity mit einer Metapher zu [&#8230;]]]></description>
										<content:encoded><![CDATA[
<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>’&#8230;it’s just proving hard to get people to understand that. Using horses is all they know and the user testing suggests that getting people to switch to something so foreign as an automobile will be near impossible. Maybe we could make some changes so that adoption is easier?’</p></blockquote>



<p><em><a href="https://web.archive.org/web/*/http://www.ownyouridentity.com/">own your identity</a></em> mit einer <a href="https://web.archive.org/web/20090430225040/http://www.ownyouridentity.com:80/2008/11/17/using-email-for-openid-by-henry-ford/">Metapher</a> zu der <a href="http://openid.net/pipermail/specs/2008-April/thread.html#2267">Diskussion</a> die E-Mail &#8211; Adresse aus Usability-Gründen mit in den OpenID Standard aufzunehmen.</p>



<p>&#8230;immerhin haben unsere heutigen Autos ja auch keine Zügel 😉</p>



<p>(<a href="http://hackr.de/2008/11/17/opendau">via hackr</a>)</p>
<p>RSS readers like you are the unsung heroes of the internet. Keep up the good work!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/11/18/openids-sind-wie-autos/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Open Web Podcast: Nochmal OpenID</title>
		<link>https://notiz.blog/2008/11/16/open-web-podcast-nochmal-openid/</link>
					<comments>https://notiz.blog/2008/11/16/open-web-podcast-nochmal-openid/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Sun, 16 Nov 2008 20:59:47 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Directed Identity]]></category>
		<category><![CDATA[E-Mail]]></category>
		<category><![CDATA[EAUT]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[OpenWeb Podcast]]></category>
		<category><![CDATA[Yahoo]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1277</guid>

					<description><![CDATA[Diesmal mit Thomas Huhn, dem Mann hinter dem ersten deutschen OpenID-Provider MeinGuter.name und dem Mitbegründer von SpreadOpenID.org. Themen des Podcastes sind unter Anderem die neuen OpenID-Provider Google und Microsoft, Vor- und Nachteile des Directed Identity Protokolls und die E-Mail Adresse als bessere OpenID (?). Thomas hat sich nach dem Podcast übrigens noch ein paar interessante [&#8230;]]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image aligncenter"><img decoding="async" src="https://notiz.blog/wp-content/uploads/2008/11/open-web-podcast.png" alt="open-web-podcast.png" /></figure>



<p>Diesmal mit <a href="https://web.archive.org/web/20180329051705/http://thomashuhn.com/">Thomas Huhn</a>, dem Mann hinter dem ersten deutschen OpenID-Provider <em><a href="https://web.archive.org/web/20131231092548/http://meinguter.name/">MeinGuter.name</a></em> und dem Mitbegründer von <em><a href="https://web.archive.org/web/20080730205943/http://spreadopenid.org/">SpreadOpenID.org</a></em>.</p>



<p>Themen des <a href="https://openwebpodcast.de/33/episode-4-openid-fur-tekkies/">Podcastes</a> sind unter Anderem die neuen OpenID-Provider <a href="https://web.archive.org/web/20090225060125/http://pixelsebi.com/2008-10-31/google-openid-already-works-nearly-everywhere/">Google</a> und <a href="https://notiz.blog/2008/10/27/windows-live-id-wird-openid-provider/">Microsoft</a>, Vor- und Nachteile des <em>Directed Identity</em> Protokolls und die <a href="https://web.archive.org/web/20090204103711/http://eaut.org/">E-Mail Adresse als bessere OpenID</a> (?).</p>



<p>Thomas hat sich nach dem Podcast übrigens noch ein paar interessante Gedanken über <em><a href="https://web.archive.org/web/20110727185019/http://openidgermany.de:80/2008/11/14/openid-baut-sich-eine-brucke-zur-massenanwendung/">die Zukunft von OpenID</a></em> gemacht (<a href="https://web.archive.org/web/20080831111551/http://openidgermany.de/">OpenID Germany</a> ist übrigens auch ein Projekt von ihm).</p>



<p>Viel Spaß beim hören und lesen 🙂</p>



<p>Die Links zur Sendung gibt&#8217;s wie immer <a href="https://openwebpodcast.de/33/episode-4-openid-fur-tekkies/">hier</a>!</p>



<p><strong>Den Podcast abonnieren</strong>:</p>



<ul class="wp-block-list">
	<li><a href="http://openwebpodcast.de/mp3/openweb04.mp3">Download MP3</a></li>
	<li><a href="http://feeds.feedburner.com/openwebcast">RSS Feed</a></li>
	<li><a href="https://podcasts.apple.com/de/podcast/der-open-web-podcast/id294732929">iTunes</a></li>
</ul>
<p>Hey there, RSS reader! You’re cool. Keep being awesome! 😎</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/11/16/open-web-podcast-nochmal-openid/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		<enclosure url="http://openwebpodcast.de/mp3/openweb04.mp3" length="57735098" type="audio/mpeg" />

			</item>
		<item>
		<title>Email Address to URL Transformation</title>
		<link>https://notiz.blog/2008/07/27/email-address-to-url-transformation/</link>
					<comments>https://notiz.blog/2008/07/27/email-address-to-url-transformation/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Sun, 27 Jul 2008 17:13:53 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[E-Mail]]></category>
		<category><![CDATA[EAUT]]></category>
		<category><![CDATA[Email to ID]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[OpenID]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=986</guid>

					<description><![CDATA[Email to ID hat seine Spezifikation. Email Address to URL Translation (kurz EAUT) ist ein offenes Protokoll um E-Mail &#8211; Adressen zu URLs zu transformieren um sie für Services wie z.B. OpenID verwenden zu können. Email Address to URL Transformation (EAUT) defines a mechanism for transforming the &#8222;addr-spec&#8220; portion of an RFC2822 email address into [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><a href="https://web.archive.org/web/20080929085748/http://emailtoid.net/">Email <em>to</em> ID</a> hat seine <a href="https://notiz.blog/2008/07/03/openid-per-e-mail/">Spezifikation</a>. <strong><a href="https://web.archive.org/web/20090204103711/http://eaut.org/">Email Address to URL Translation</a></strong> (kurz <abbr title="Email Address to URL Translation">EAUT</abbr>) ist ein offenes Protokoll um E-Mail &#8211; Adressen zu URLs zu transformieren um sie für Services wie z.B. <a href="http://openid.net">OpenID</a> verwenden zu können.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Email Address to URL Transformation (EAUT) defines a mechanism for transforming the &#8222;addr-spec&#8220; portion of an RFC2822 email address into an associated URL. The transform options outlined in this document are designed to be flexible enough such that every DNS domain-owner can specify unlimited email address to URL transformations that services can easily discover and utilize in their URL-based transactions.</p>
</blockquote>



<p>Das Prinzip ist einfach:</p>



<ul class="wp-block-list">
	<li>Zuerst wird die <a href="https://web.archive.org/web/20080827081243/http://eaut.org/specs/1.0/#obtaining-discovery-endpoint">EAUT Discovery Endpoint URL</a> ermittelt. Bei der E-Mail &#8211; Adresse <code>matthias@pfefferle.org</code> wäre die URL <code>pfefferle.org</code>.</li>
	<li>Als nächstes wird unter der URL nach <a href="https://web.archive.org/web/20080906083104/http://eaut.org/specs/1.0/#discovered_info"><em>Discovered Information</em></a> (<a href="https://web.archive.org/web/20090227100639/http://xrds-simple.net/">XRDS-Simple</a>) gesucht.</li>
	<li>Sind Informationen verfügbar, wird die <a href="https://web.archive.org/web/20080906083104/http://eaut.org/specs/1.0/#anchor9">E-Mail &#8211; Adresse entsprechend der Vorgaben gemappt</a>.</li>
	<li>Gibt es keine passenden XRDS-Simple Daten, werden Mapper wie z.B. <a href="https://web.archive.org/web/20080929085748/http://emailtoid.net/">Email <em>to</em> ID</a> empfohlen.</li>
</ul>



<p>Wen interessiert welche Schritte genau durchgeführt werden oder ob der eigene E-Mail &#8211; Provider ein entsprechendes Mapping unterstützt, kann seine E-Mail &#8211; Adresse <a href="https://web.archive.org/web/20080823082010/http://eaut.org/example/">hier</a> testen (Beispiel: <a href="https://web.archive.org/web/20090321194351/http://eaut.org/example/?email=matthias@pfefferle.org">matthias@pfefferle.org</a>).</p>



<h2 class="wp-block-heading">Examples in the wild</h2>



<p>Der erste Service, der die <strong><a href="https://web.archive.org/web/20090204103711/http://eaut.org/">Email Address to URL Translation</a></strong> Spezifikation umgesetzt hat ist <a href="http://groups.google.com/group/eaut/browse_thread/thread/17018f869c9d3f4a">Ma.gnolia.com</a>:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Just wanted to let everyone know that we just deployed EAUT support over at Ma.gnolia (http://ma.gnolia.com). You can now type in your email address in the OpenID field and we&#8217;ll resolve using EAUT with https://web.archive.org/web/20080929085748/http://emailtoid.net/ as the default.</p>
</blockquote>



<figure class="wp-block-image aligncenter"><img decoding="async" src="https://notiz.blog/wp-content/uploads/2008/07/magnoliacom-find-web-sites-build-community-online-1.jpg" alt="Ma.gnolia.com - Email Address to URL Transformation" /></figure>



<p><a href="http://willnorris.com/">Will Norris</a> hat <abbr title="Email Address to URL Translation">EAUT</abbr> außerdem in sein <a href="http://willnorris.com/2008/07/wp-openid-220-released"><strong>OpenID WordPress Plugin</strong> (Version 2.2.0)</a> implementiert.</p>



<p>(via <a href="http://feeds.feedburner.com/CarstenPoetterSharedItems">Carsten Pötters Shared Items</a>)</p>
<p>RSS readers like you are the unsung heroes of the internet. Keep up the good work!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/07/27/email-address-to-url-transformation/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>OpenID per E-Mail</title>
		<link>https://notiz.blog/2008/07/03/openid-per-e-mail/</link>
					<comments>https://notiz.blog/2008/07/03/openid-per-e-mail/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Thu, 03 Jul 2008 17:57:23 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[E-Mail]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Mapper]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[XRDS]]></category>
		<category><![CDATA[XRDS-Simple]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=922</guid>

					<description><![CDATA[EMAIL to ID ist ein Service, der eine E-Mail &#8211; Adresse zu OpenIDs macht. Emailtoid is a simple mapping service that enables the use of email addresses as OpenID identifiers. EMAIL to ID will kein neuer Provider sein, sondern sieht sich selbst nur als Übergangslösung bis E-Mail Services (z.B. GMX oder GMail) selbst diesen Dienst [&#8230;]]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image alignright"><img decoding="async" src="https://notiz.blog/wp-content/uploads/2008/07/emailtoidlogo.png" alt="emailtoid.logo.png" /></figure>



<p><em><a href="https://web.archive.org/web/20080929085748/http://emailtoid.net/">EMAIL to ID</a></em> ist ein Service, der eine E-Mail &#8211; Adresse zu OpenIDs macht.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Emailtoid is a simple mapping service that enables the use of email addresses as OpenID identifiers.</p>
</blockquote>



<p><em>EMAIL to ID</em> will kein neuer Provider sein, sondern sieht sich selbst nur als Übergangslösung bis E-Mail Services (z.B. GMX oder GMail) selbst diesen Dienst anbieten.</p>



<p>Der Login-Prozess soll folgendermaßen ablaufen:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>When a user enters in an email address, there is an xrds discovery made on the top level domain (eg, gmail.com). If the XRDS document contains an Emailtoid mapper or email transformation template, use that. If not, then you make the same request on emailtoid.net to get the mapper document and send the email to there. <strong>Emailtoid is a fallback.</strong></p>
</blockquote>



<p>Wie genau das Mapping oder das <a href="https://web.archive.org/web/20090227100639/http://xrds-simple.net/">XRDS-Dokument</a> aussehen soll ist noch nicht spezifiziert, wird aber demnächst <a href="https://web.archive.org/web/20120526115554/http://emailtoid.net/developers/">hier</a> zu finden sein.</p>



<h4 class="wp-block-heading">Macht eine E-Mail &#8211; Adresse als OpenID Sinn?</h4>



<p>In Zukunft steht sicherlich die URL im Zentrum des Authentifizierungsprozesses, da sich über sie einfach mehr Informationen transportieren lassen (seien es Meta-Information oder Semantisches HTML). Auch das Semantische Web basiert auf <abbr title="Uniform Resource Identifier">URI</abbr>s, um verschiedene Informationen zu vernetzen. Aus diesen Gründen sollte man den User mal so langsam an diese neuen Umstände gewöhnen 😉</p>



<p>Mit <em>EMAIL to ID</em> kann der Nutzer seine bestehenden Gewohnheiten (Anmelden per E-Mail &#8211; Adresse) beibehalten und trotzdem die Vorteile von <a href="http://openid.net/">OpenID</a> nutzen (Simple Lösung für ein scheinbar schwieriges Problem&#8230; hat was vom Ei des Kolumbus).</p>



<h4 class="wp-block-heading">Warum kein eigener Standard?</h4>



<p>Ein neuer OpenID Standard auf Basis von E-Mail &#8211; Adressen (wie <a href="https://web.archive.org/web/20110914143933/http://www.sappenin.com:80/openid/ext/oet/openid-email-transform-extension-1_0.html">hier</a> angedacht) würde zusätzlichen und unnötigen Implementierungsaufwand bedeuten (nimmt man an, die <abbr title="Uniform Resource Locator">URL</abbr>s sind die Zukunft), den man sich bei <em>EMAIL to ID</em> sparen kann. <em>EMAIL to ID</em> mappt eigentlich <em>nur</em> eine E-Mail &#8211; Adresse auf eine <abbr title="Uniform Resource Locator">URL</abbr> <code>http://emailtoid.net/mapper?email=jane@example.com</code> und entspricht somit einer vollwertigen OpenID (keine Anpassungen am bisherigen Standard nötig).</p>



<p>(<a href="http://factoryjoe.com/blog/2008/06/22/announcing-emailtoid-mapping-email-addresses-to-openids/">via</a>)</p>
<p>RSS readers like you are the unsung heroes of the internet. Keep up the good work!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/07/03/openid-per-e-mail/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
