rel-me: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(+IA archive link, use <syntaxhighlight> tag instead of <source>, move To Be Updated section after reviewed content)
 
(4 intermediate revisions by 2 users not shown)
Line 23: Line 23:
Watch some short videos:
Watch some short videos:
* David Recordon's excellent *30 second* explanation of XFN rel="me"
* David Recordon's excellent *30 second* explanation of XFN rel="me"
** [http://web.archive.org/web/20090119054502/http://www.sixapart.com/static_news/opening_social_graph/xfn_links/xfn_links.html Archived page], though presentation requires Flash
** [http://web.archive.org/web/20090119054502/http://www.sixapart.com/static_news/opening_social_graph/xfn_links/xfn_links.html Archived page], though presentation requires Flash. (original: <nowiki>http://www.sixapart.com/static_news/opening_social_graph/xfn_links/xfn_links.html</nowiki>)
** Original: http://www.sixapart.com/static_news/opening_social_graph/xfn_links/xfn_links.html
* [https://www.youtube.com/watch?v=LabCylbapuM Brad Fitzpatrick explains rel="me" and more XFN].
* [https://www.youtube.com/watch?v=LabCylbapuM Brad Fitzpatrick explains rel="me" and more XFN].
* [https://connectedsocialmedia.com/423/plaxo-to-ship-online-identity-aggregator-based-on-microformats/ Joseph Smarr's whiteboard explanation] of rel="me" as implemented in the Plaxo online identity aggregator. ([http://web.archive.org/web/20220708203538/https://connectedsocialmedia.com/423/plaxo-to-ship-online-identity-aggregator-based-on-microformats/ archived]) <!-- original URL http://www.podtech.net/scobleshow/technology/1611/plaxo-to-ship-online-identity-aggregator-based-on-microformats does not redirect to new episode permalink -->
* [https://connectedsocialmedia.com/423/plaxo-to-ship-online-identity-aggregator-based-on-microformats/ Joseph Smarr's whiteboard explanation] of rel="me" as implemented in the Plaxo online identity aggregator. ([http://web.archive.org/web/20220708203538/https://connectedsocialmedia.com/423/plaxo-to-ship-online-identity-aggregator-based-on-microformats/ archived]) <!-- original URL http://www.podtech.net/scobleshow/technology/1611/plaxo-to-ship-online-identity-aggregator-based-on-microformats does not redirect to new episode permalink -->
Line 49: Line 48:


Read more about how to implement [[RelMeAuth]] and [[web sign-in]].
Read more about how to implement [[RelMeAuth]] and [[web sign-in]].
----
----
'''TO BE UPDATED'''
The sections below this need to be updated (e.g. links verified, and deadlinks replaced with Internet Archive versions)
----
----


== implementations ==
== implementations ==
Notable Sites:
Notable Sites:
* '''[https://support.google.com/webmasters/answer/1229920 Google]''' uses reciprocal rel=me links for domain verification, which it also uses for independent site [[rel-author]] support.
* [https://indieweb.org/Mastodon#rel-me_support Mastodon] uses rel-me to support "verified" site links in a green box with a green checkmark next to the verified site.
* '''[http://blog.app.net/2013/04/29/announcing-domain-verification/ App.net]''' implements rel-me for officially connecting your domain to your app.net account, as well as publishing rel-me on your site.
* [https://web.archive.org/web/20230314223136/https://hachyderm.io/@nova/109790530971147702 GitHub]
* [https://wikis.world/@wikipedia/110396865170645710 Wikipedia] via [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:RealMe MediaWiki Extension RealMe]
* [https://indieweb.org/rel-me#Threads Threads] announced rel-me support 2023-08-09 [https://www.threads.net/@mosseri/post/Cvu2eXurRbB]
* ...


Services:
Services:
* '''[https://indieauth.com/ IndieAuth]''' is perhaps the most comprehensive [[rel-me]] implementation, using it to implement [[RelMeAuth]] and a superset of [[web-sign-in]] that is focused on [http://indiewebcamp.com/ independent websites].
* '''[https://indielogin.com/ IndieLogin]''' is perhaps the most comprehensive [[rel-me]] implementation, using it to implement [[RelMeAuth]] and a superset of [[web-sign-in]] that is focused on [http://indiewebcamp.com/ independent websites].


[[wordpress-plugins|WordPress plugins]]:
[[wordpress-plugins|WordPress plugins]]:
* [http://blog.maybe5.com/?page_id=94 Social Links Wordpress plugin] - supports rel-me links to other services
* [http://blog.maybe5.com/?page_id=94 Social Links Wordpress plugin] - supports rel-me links to other services
* [http://code.l0g.in/about-me/ About Me plugin] (on github) - supports creation of an About Me page with rel-me links to other profiles.
* [http://code.l0g.in/about-me/ About Me plugin] (on github) - supports creation of an About Me page with rel-me links to other profiles.
=== past implementations ===
* '''[https://web.archive.org/web/20170826050132/https://support.google.com/webmasters/answer/1229920 Google]''' used reciprocal rel=me links for domain verification, which it also used for independent site [[rel-author]] support.
* '''[http://web.archive.org/web/20140117144124/http://blog.app.net/2013/04/29/announcing-domain-verification App.net]''' implemented rel-me for officially connecting your domain to your app.net account, as well as publishing rel-me on your site.


=== advocacy ===
=== advocacy ===
Line 79: Line 76:


Current requests:
Current requests:
* [https://github.com/gittip/www.gittip.com/issues/2477 Gittip: Add "website" profile field #2477] - requested 2014-06-07 by Aaron Parecki.
* [https://github.com/liberapay/liberapay.com/issues/1034#issuecomment-461898619 Liberapay:  Associate accounts with websites #1034: rel="me" link] - requested 2019-02-08 by https://github.com/Changaco
* ...
* ...
----
----
'''TO BE UPDATED'''
The sections below this need to be updated (e.g. links verified, and deadlinks replaced with Internet Archive versions)
----
----


== examples in the wild ==
== examples in the wild ==
Line 92: Line 100:


== see also ==
== see also ==
* https://indieweb.org/rel-me
* [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_multiple_external_sites|services that support rel="me"]]
* [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_multiple_external_sites|services that support rel="me"]]
* [[rel-me-faq]]
* [[rel-me-faq]]

Latest revision as of 19:51, 11 August 2023

short URL
http://ufs.cc/w/relme

XFN 1.1 introduced the "me" rel value which is used to indicate profile equivalence and for identity-consolidation.

example

rel="me" is used on hyperlinks from one page about a person to other pages about that same person.

For example, Tantek's home page has (markup simplified)

<a href="https://github.com/tantek" rel="me">@t</a>

And his GitHub profile itself has (markup simplified)

<a href="https://tantek.com/" rel="me">https://tantek.com/</a>

Thus establishing a bi-directional rel-me link and confirming that the two URLs represent the same person.

Publishers can use the XFN creator form to create rel-me hyperlinks.

screencast and videos

Watch some short videos:

Longer:

tutorials

A simple data portability project or is it (archived) rel=me summary by Bob Ngu

domain verification

rel=me is the standard way to check that a website belongs to a user on a 3rd party site.

  • read a user's website that they entered into their 3rd party site profile
  • check for a rel=me hyperlink from their website to their 3rd party site profile
  • if such a rel=me hyperlink is found, then the user has proven that they control that personal website sufficient to put a link back to their 3rd party site profile, and thus domain verification succeeds.

If you're the implementer of such a 3rd party site with user profiles, implement the above to implement a personal website domain verification feature.

rel-me-auth

RelMeAuth is a proposed open standard for using rel-me links to profiles on OAuth supporting services to authenticate via either those profiles or your own site.

In short it is a combination of domain verification as documented above, and OAuth authorization on the 3rd party site that the user's domain links to.

Read more about how to implement RelMeAuth and web sign-in.

implementations

Notable Sites:

Services:

WordPress plugins:

past implementations

  • Google used reciprocal rel=me links for domain verification, which it also used for independent site rel-author support.
  • App.net implemented rel-me for officially connecting your domain to your app.net account, as well as publishing rel-me on your site.

advocacy

Advocating rel=me support can be done a few ways, if a site has:

  • user profiles but no "website" field - ask them to add a "website" field and mark it up with rel=me.
  • a "website" field on profiles - ask it to support publishing rel=me
  • a notion of "verification" or "verified" profiles - ask it to do so via confirming reciprocal rel=me
  • login/sign-in - ask it to support RelMeAuth with a Web sign-in user interface.

Current requests:




TO BE UPDATED

The sections below this need to be updated (e.g. links verified, and deadlinks replaced with Internet Archive versions)



examples in the wild

Examples of sites publishing rel=me support, e.g. on user profiles.

See:

articles

see also