rel-me: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
GRegorLove (talk | contribs) (→implementations: +Threads) |
||
| (37 intermediate revisions by 13 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:rel="me"}} | |||
;short URL | |||
:http://ufs.cc/w/relme | |||
[[XFN]] 1.1 introduced the "me" [[rel]] value which is used for | [[XFN]] 1.1 introduced the "me" [[rel]] value which is used to indicate profile equivalence and for [[identity-consolidation]]. | ||
< | == example == | ||
<code>rel="me"</code> is used on hyperlinks from one page about a person to other pages about that same person. | |||
For example, [[User:Tantek|Tantek]]'s [https://tantek.com/ home page] has (markup simplified) | |||
<syntaxhighlight lang="html"><a href="https://github.com/tantek" rel="me">@t</a></syntaxhighlight> | |||
And his GitHub profile itself has (markup simplified) | |||
<syntaxhighlight lang="html"><a href="https://tantek.com/" rel="me">https://tantek.com/</a></syntaxhighlight> | |||
Thus establishing a bi-directional rel-me link and confirming that the two URLs represent the same person. | |||
Publishers can use the [https://gmpg.org/xfn/creator XFN creator] form to create rel-me hyperlinks. | |||
== screencast and videos == | |||
Watch some short videos: | |||
* 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. (original: <nowiki>http://www.sixapart.com/static_news/opening_social_graph/xfn_links/xfn_links.html</nowiki>) | |||
* [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 --> | |||
Longer: | |||
* [https://www.youtube.com/watch?v=Q2WzVSVxrrI Gavin Bell on "What is your provenance?"] (40 minutes) - provides a much broader discussion of the problem statement of who is a person on the Web, and [https://youtu.be/Q2WzVSVxrrI?t=450 starting at about 0:07:30] explains how [[hCard]] + rel="me" helps solve this problem. | |||
== tutorials == | |||
[http://ungeekdapo.wordpress.com/2008/04/29/a-simple-data-portability-project-or-is-it/ A simple data portability project or is it] ([http://web.archive.org/web/20221110203949/https://ungeekdapo.wordpress.com/2008/04/29/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: | |||
* [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. | |||
* [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: | |||
* '''[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]]: | |||
* [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. | |||
=== 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 === | |||
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: | |||
* [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 of sites publishing rel=me support, e.g. on user profiles. | |||
See: | |||
* [[hcard-xfn-supporting-friends-lists#Services_with_XFN_rel.3D.22me.22_to_multiple_external_sites|services supporting XFN rel=me]] | |||
== articles == | |||
* 2018-04-26 [https://vanderven.se/martijn/ Martijn van der Ven]: [https://wiki.zegnat.net/media/the-real-deal-about-rel-me.html The Real Deal About <code>rel="me"</code>] | |||
== 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"]] | |||
* [[rel-me-faq]] | |||
* [[xfn]] | * [[xfn]] | ||
* [[rel]] | * [[rel]] | ||
* [[social network portability]] | * [[social network portability]] | ||
* [ | * [https://gmpg.org/xfn/11 XFN 1.1 profile] | ||
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:
- David Recordon's excellent *30 second* explanation of XFN rel="me"
- Archived page, though presentation requires Flash. (original: http://www.sixapart.com/static_news/opening_social_graph/xfn_links/xfn_links.html)
- Brad Fitzpatrick explains rel="me" and more XFN.
- Joseph Smarr's whiteboard explanation of rel="me" as implemented in the Plaxo online identity aggregator. (archived)
Longer:
- Gavin Bell on "What is your provenance?" (40 minutes) - provides a much broader discussion of the problem statement of who is a person on the Web, and starting at about 0:07:30 explains how hCard + rel="me" helps solve this problem.
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:
- Mastodon uses rel-me to support "verified" site links in a green box with a green checkmark next to the verified site.
- GitHub
- Wikipedia via MediaWiki Extension RealMe
- Threads announced rel-me support 2023-08-09 [1]
- ...
Services:
- 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 independent websites.
- Social Links Wordpress plugin - supports rel-me links to other services
- About Me plugin (on github) - supports creation of an About Me page with rel-me links to other profiles.
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:
- 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 of sites publishing rel=me support, e.g. on user profiles.
See:
articles
- 2018-04-26 Martijn van der Ven: The Real Deal About
rel="me"