You've likely ended up here because a website you're trying to sign in to uses IndieLogin.com to handle logging users in.
Instead of making a new account here, we'll take advantage of some accounts you may already have in order to authenticate you. You can always choose the services you use to log in, and the site you're logging in to won't have access to them.
If your website supports IndieAuth, then this site will use your IndieAuth server automatically! No further setup is needed, and you don't need to add any other social profiles to your site.
Micro.blog supports IndieAuth out of the box, no configuration is necessary. Try logging in using your Micro.blog address.
If your site is running WordPress, you can install the IndieAuth WordPress plugin.
If you would like to build IndieAuth support into your own website, the links below will help:
To use Twitter, link to your Twitter profile on your home page.
<a href="https://twitter.com/aaronpk" rel="me">twitter.com/aaronpk</a>
Make sure your Twitter account has your URL in your profile.
To use GitHub, link to your GitHub profile on your home page.
<a href="https://github.com/aaronpk" rel="me">github.com/aaronpk</a>
Make sure your GitHub account has your URL in your profile.
To use your email address to authenticate, you'll receive a short code you'll have to enter while signing in. Just link to your email address from your home page.
<a href="mailto:firstname.lastname@example.org" rel="me">email@example.com</a>
If you don't want to use any existing accounts to authenticate, you can use a PGP key and sign a challenge while logging in instead. You'll just need to link to your PGP key from your website.
<a href="/key.txt" rel="pgpkey authn">PGP Key</a>
If you have multiple domains, or want your Twitter URL to link to something that is not your main website, you can alternatively put one or more URLs in your "bio" field on Twitter and GitHub. This allows you to use one Twitter account to authenticate multiple domains.
If you don't want IndieLogin.com to consider all your
rel="me" links as possible authentication options, you can choose which ones specifically by using
rel="me authn" instead. This allows you to, for example, only use providers that support two-factor authorization, while still linking to your existing profiles using
<a href="https://twitter.com/aaronpk" rel="me">twitter.com/aaronpk</a> <a href="https://github.com/aaronpk" rel="me authn">github.com/aaronpk</a>
If any of your
rel="me" links also include
authn in the list of rels, then IndieLogin.com will only use the links with
authn, and will no longer consider your plain
rel="me" links as authentication options.