#relmeauth — Public Fediverse posts

⚠️ .io domain¹ likely being phased-out² — seven suggested steps

Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), so here are my suggested steps to take depending on your usage of .io domains:

1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)
2. If you currently run a .io service⁴ (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)
3. If you have a personal site on a .io domain⁵ or subdomain, make your own transition plan, and perhaps post about how others should link to your posts
4. If you are using someone else’s .io domain to publish (like #GitHubPages⁶), make a transition plan to publish elsewhere and leave a forwarding note and link behind
5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain
6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5
7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive)

And of course, post about your #dotIO plans.

Glossary

Domain
 https://indieweb.org/domain
IndieAuth
 https://indieweb.org/IndieAuth
Internet Archive
 https://web.archive.org/
OpenID
 https://indieweb.org/OpenID
Redirect
 https://indieweb.org/redirect
RelMeAuth
 https://indieweb.org/RelMeAuth
Web sign-in
 https://indieweb.org/Web_sign-in


References:

¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
⁴ E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
⁵ E.g. https://indieweb.org/werd.io
⁶ https://indieweb.org/github.io


This is post 25 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
→ https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

⚠️ .io domain¹ likely being phased-out² — seven suggested steps

Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), so here are my suggested steps to take depending on your usage of .io domains:

1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)
2. If you currently run a .io service⁴ (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)
3. If you have a personal site on a .io domain⁵ or subdomain, make your own transition plan, and perhaps post about how others should link to your posts
4. If you are using someone else’s .io domain to publish (like #GitHubPages⁶), make a transition plan to publish elsewhere and leave a forwarding note and link behind
5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain
6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5
7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive)

And of course, post about your #dotIO plans.

Glossary

Domain
 https://indieweb.org/domain
IndieAuth
 https://indieweb.org/IndieAuth
Internet Archive
 https://web.archive.org/
OpenID
 https://indieweb.org/OpenID
Redirect
 https://indieweb.org/redirect
RelMeAuth
 https://indieweb.org/RelMeAuth
Web sign-in
 https://indieweb.org/Web_sign-in


References:

¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
⁴ E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
⁵ E.g. https://indieweb.org/werd.io
⁶ https://indieweb.org/github.io


This is post 25 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
→ https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

⚠️ .io domain¹ likely being phased-out² — seven suggested steps

Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), so here are my suggested steps to take depending on your usage of .io domains:

1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)
2. If you currently run a .io service⁴ (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)
3. If you have a personal site on a .io domain⁵ or subdomain, make your own transition plan, and perhaps post about how others should link to your posts
4. If you are using someone else’s .io domain to publish (like #GitHubPages⁶), make a transition plan to publish elsewhere and leave a forwarding note and link behind
5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain
6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5
7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive)

And of course, post about your #dotIO plans.

Glossary

Domain
 https://indieweb.org/domain
IndieAuth
 https://indieweb.org/IndieAuth
Internet Archive
 https://web.archive.org/
OpenID
 https://indieweb.org/OpenID
Redirect
 https://indieweb.org/redirect
RelMeAuth
 https://indieweb.org/RelMeAuth
Web sign-in
 https://indieweb.org/Web_sign-in


References:

¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
⁴ E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
⁵ E.g. https://indieweb.org/werd.io
⁶ https://indieweb.org/github.io


This is post 25 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
→ https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

⚠️ .io domain¹ likely being phased-out² — seven suggested steps

Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), so here are my suggested steps to take depending on your usage of .io domains:

1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)
2. If you currently run a .io service⁴ (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)
3. If you have a personal site on a .io domain⁵ or subdomain, make your own transition plan, and perhaps post about how others should link to your posts
4. If you are using someone else’s .io domain to publish (like #GitHubPages⁶), make a transition plan to publish elsewhere and leave a forwarding note and link behind
5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain
6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5
7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive)

And of course, post about your #dotIO plans.

Glossary

Domain
 https://indieweb.org/domain
IndieAuth
 https://indieweb.org/IndieAuth
Internet Archive
 https://web.archive.org/
OpenID
 https://indieweb.org/OpenID
Redirect
 https://indieweb.org/redirect
RelMeAuth
 https://indieweb.org/RelMeAuth
Web sign-in
 https://indieweb.org/Web_sign-in


References:

¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
⁴ E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
⁵ E.g. https://indieweb.org/werd.io
⁶ https://indieweb.org/github.io


This is post 25 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
→ https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

⚠️ .io domain¹ likely being phased-out² — seven suggested steps

Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
* https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), so here are my suggested steps to take depending on your usage of .io domains:

1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)
2. If you currently run a .io service⁴ (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)
3. If you have a personal site on a .io domain⁵ or subdomain, make your own transition plan, and perhaps post about how others should link to your posts
4. If you are using someone else’s .io domain to publish (like #GitHubPages⁶), make a transition plan to publish elsewhere and leave a forwarding note and link behind
5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain
6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5
7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive)

And of course, post about your #dotIO plans.

Glossary

Domain
 https://indieweb.org/domain
IndieAuth
 https://indieweb.org/IndieAuth
Internet Archive
 https://web.archive.org/
OpenID
 https://indieweb.org/OpenID
Redirect
 https://indieweb.org/redirect
RelMeAuth
 https://indieweb.org/RelMeAuth
Web sign-in
 https://indieweb.org/Web_sign-in


References:

¹ https://indieweb.org/.io
² https://en.wikipedia.org/wiki/.io#Phasing_Out
³ https://en.wikipedia.org/wiki/.cs
⁴ E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
⁵ E.g. https://indieweb.org/werd.io
⁶ https://indieweb.org/github.io


This is post 25 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
→ https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

@aaronpk

☝🏻 Apologies for the tag-in, but you might be the only person I know on here who has any ideas on my post above.

#IndieAuth #RelMeAuth

@aaronpk

☝🏻 Apologies for the tag-in, but you might be the only person I know on here who has any ideas on my post above.

#IndieAuth #RelMeAuth

In an #IndieAuth flow, what are some authorization endpoint strategies (besides #RelMeAuth) for attesting that a person "owns" the domain they're authenticating with?

Some ideas in decreasing order of complexity: TXT DNS record, an HTTP header, a `<link>` element of some kind…

• https://indieauth.spec.indieweb.org
• https://microformats.org/wiki/RelMeAuth

In an #IndieAuth flow, what are some authorization endpoint strategies (besides #RelMeAuth) for attesting that a person "owns" the domain they're authenticating with?

Some ideas in decreasing order of complexity: TXT DNS record, an HTTP header, a `<link>` element of some kind…

• https://indieauth.spec.indieweb.org
• https://microformats.org/wiki/RelMeAuth

Interested in #RelMeAuth or #IndieAuth?
You can add this to your @getkirby install quite easily.
You could even add a structure to have all of your sites and accounts listed in your head tag:

https://getkirby.com/docs/cookbook/integrations/indieauth
Thanks, @lukasbestle !

#getkirby #IndieWeb #blogging

Interested in #RelMeAuth or #IndieAuth?
You can add this to your @getkirby install quite easily.
You could even add a structure to have all of your sites and accounts listed in your head tag:

https://getkirby.com/docs/cookbook/integrations/indieauth
Thanks, @lukasbestle !

#getkirby #IndieWeb #blogging

Interested in #RelMeAuth or #IndieAuth?
You can add this to your @getkirby install quite easily.
You could even add a structure to have all of your sites and accounts listed in your head tag:

https://getkirby.com/docs/cookbook/integrations/indieauth
Thanks, @lukasbestle !

#getkirby #IndieWeb #blogging

Virtuoso 08.03.3339 PAGO edition for the Microsoft Azure cloud is now live.

Highlights include:
* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/openlinkswcom-pago.openlink-virtuoso-azure-pago-offer-20201019?tab=Overview

#KnowledgeGraph #VirtuosoRDBMS #SQL #SPARQL #LinkedData #DBMS #GraphDatabase

Virtuoso 08.03.3339 PAGO edition for the Microsoft Azure cloud is now live.

Highlights include:
* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/openlinkswcom-pago.openlink-virtuoso-azure-pago-offer-20201019?tab=Overview

#KnowledgeGraph #VirtuosoRDBMS #SQL #SPARQL #LinkedData #DBMS #GraphDatabase

Virtuoso 08.03.3339 PAGO edition for the Microsoft Azure cloud is now live.

Highlights include:
* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD

https://azuremarketplace.microsoft.com/en-us/marketplace/apps/openlinkswcom-pago.openlink-virtuoso-azure-pago-offer-20201019?tab=Overview

#KnowledgeGraph #VirtuosoRDBMS #SQL #SPARQL #LinkedData #DBMS #GraphDatabase

Virtuoso 08.03.3339 PAGO edition for the Amazon Web Services (#AWS) cloud is now live.

Highlights include:

* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD

Product Page: https://aws.amazon.com/marketplace/pp/prodview-idujw25jbgpn4?sr=0-2&ref_=beagle&applicationId=AWSMPContessa

#KnowledgeGraph #VirtuosoRDBMS #SQL #SPARQL #LinkedData #DBMS #GraphDatabase #SemanticWeb

Virtuoso 08.03.3339 PAGO edition for the Amazon Web Services (#AWS) cloud is now live.

Highlights include:

* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD

Product Page: https://aws.amazon.com/marketplace/pp/prodview-idujw25jbgpn4?sr=0-2&ref_=beagle&applicationId=AWSMPContessa

#KnowledgeGraph #VirtuosoRDBMS #SQL #SPARQL #LinkedData #DBMS #GraphDatabase #SemanticWeb

Virtuoso 08.03.3339 PAGO edition for the Amazon Web Services (#AWS) cloud is now live.

Highlights include:

* #IndieAuth & #RelMeAuth auth protocols support for self-sovereign identity (#SSI)
* #ActivityPub & #ActivityStreams Support
* #OpenAI Web Service import and export
* Enhanced native support of both #JSON and #JSONLD

Product Page: https://aws.amazon.com/marketplace/pp/prodview-idujw25jbgpn4?sr=0-2&ref_=beagle&applicationId=AWSMPContessa

#KnowledgeGraph #VirtuosoRDBMS #SQL #SPARQL #LinkedData #DBMS #GraphDatabase #SemanticWeb

@chrismessina @dontpanic @Mastodon,

Finally cracked it. Here's how.

Over here I was pointing to https://www.threads.net/@kidehen (which does resolve) rather than https://threads.net/@kidehen.

That was it, bar confusion introduced by caching in my particular #Chrome instance.

This is a big move by #Threads re #identity authenticity, especially in regards to the burgeoning #CreatorEconomy (where the next major battle for curators is about to break out).

#RelMeAuth #OpenWeb #SSI #YouID

@chrismessina @dontpanic @Mastodon,

Finally cracked it. Here's how.

Over here I was pointing to https://www.threads.net/@kidehen (which does resolve) rather than https://threads.net/@kidehen.

That was it, bar confusion introduced by caching in my particular #Chrome instance.

This is a big move by #Threads re #identity authenticity, especially in regards to the burgeoning #CreatorEconomy (where the next major battle for curators is about to break out).

#RelMeAuth #OpenWeb #SSI #YouID

@chrismessina @dontpanic @Mastodon,

Finally cracked it. Here's how.

Over here I was pointing to https://www.threads.net/@kidehen (which does resolve) rather than https://threads.net/@kidehen.

That was it, bar confusion introduced by caching in my particular #Chrome instance.

This is a big move by #Threads re #identity authenticity, especially in regards to the burgeoning #CreatorEconomy (where the next major battle for curators is about to break out).

#RelMeAuth #OpenWeb #SSI #YouID

@lukasmueller @mysk Yeah, I personally prefer to never store passwords in the sites I build.

An alternative is to do #RelMeAuth: https://indieweb.org/RelMeAuth

@lukasmueller @mysk Yeah, I personally prefer to never store passwords in the sites I build.

An alternative is to do #RelMeAuth: https://indieweb.org/RelMeAuth

@lukasmueller @mysk Yeah, I personally prefer to never store passwords in the sites I build.

An alternative is to do #RelMeAuth: https://indieweb.org/RelMeAuth

:ablobcatcoffee: After a little over half a year, I've started the transition to a #selfdogfood diet: my own #IndieAuth instance is now an MVP running in production.

Over time, I'll be fixing problems found in the process, in addition to implementing improvements. Like #RelMeAuth, which would be nice to have in the near future.