home.social

#dotio — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dotio, aggregated by home.social.

  1. Unless the IANA steps in and makes a change to standard policy, the .io domain will be retired starting very soon

    #domains #gaming #dotio #news #technews

    every.to/p/the-disappearance-of-an-internet-domain

  2. Unless the IANA steps in and makes a change to standard policy, the .io domain will be retired starting very soon

    #domains #gaming #dotio #news #technews

    every.to/p/the-disappearance-of-an-internet-domain

  3. Unless the IANA steps in and makes a change to standard policy, the .io domain will be retired starting very soon

    #domains #gaming #dotio #news #technews

    every.to/p/the-disappearance-of-an-internet-domain

  4. Unless the IANA steps in and makes a change to standard policy, the .io domain will be retired starting very soon

    #domains #gaming #dotio #news #technews

    every.to/p/the-disappearance-of-an-internet-domain

  5. Unless the IANA steps in and makes a change to standard policy, the .io domain will be retired starting very soon

    #domains #gaming #dotio #news #technews

    every.to/p/the-disappearance-of-an-internet-domain

  6. The .IO drama is just the latest in a long line of reasons why I stopped using ccTLDs. Domain hacks are fun, and I used to have a few, but ccTLDs are always playing with fire. Read why I think boring old .COM is still king: b10g.xyz/blog/2024/cctlds-are-
    #WebDev #ccTLD #dotIO

  7. The .IO drama is just the latest in a long line of reasons why I stopped using ccTLDs. Domain hacks are fun, and I used to have a few, but ccTLDs are always playing with fire. Read why I think boring old .COM is still king: b10g.xyz/blog/2024/cctlds-are-

  8. The .IO drama is just the latest in a long line of reasons why I stopped using ccTLDs. Domain hacks are fun, and I used to have a few, but ccTLDs are always playing with fire. Read why I think boring old .COM is still king: b10g.xyz/blog/2024/cctlds-are-
    #WebDev #ccTLD #dotIO

  9. The .IO drama is just the latest in a long line of reasons why I stopped using ccTLDs. Domain hacks are fun, and I used to have a few, but ccTLDs are always playing with fire. Read why I think boring old .COM is still king: b10g.xyz/blog/2024/cctlds-are-
    #WebDev #ccTLD #dotIO

  10. The .IO drama is just the latest in a long line of reasons why I stopped using ccTLDs. Domain hacks are fun, and I used to have a few, but ccTLDs are always playing with fire. Read why I think boring old .COM is still king: b10g.xyz/blog/2024/cctlds-are-
    #WebDev #ccTLD #dotIO

  11. ⚠️ .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

  12. ⚠️ .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

  13. ⚠️ .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

  14. ⚠️ .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

  15. ⚠️ .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

  16. Die Top-Level-Domain .io steht vor dem Aus. Politische Veränderungen im British Indian Ocean Territory könnten das Ende der bei #Startups beliebten Domain-Endung bedeuten. #TLD #ccTLD #dotIO #ChagosArchipel winfuture.de/news,145867.html?

  17. Die Top-Level-Domain .io steht vor dem Aus. Politische Veränderungen im British Indian Ocean Territory könnten das Ende der bei #Startups beliebten Domain-Endung bedeuten. #TLD #ccTLD #dotIO #ChagosArchipel winfuture.de/news,145867.html?

  18. Die Top-Level-Domain .io steht vor dem Aus. Politische Veränderungen im British Indian Ocean Territory könnten das Ende der bei #Startups beliebten Domain-Endung bedeuten. #TLD #ccTLD #dotIO #ChagosArchipel winfuture.de/news,145867.html?

  19. Die Top-Level-Domain .io steht vor dem Aus. Politische Veränderungen im British Indian Ocean Territory könnten das Ende der bei #Startups beliebten Domain-Endung bedeuten. #TLD #ccTLD #dotIO #ChagosArchipel winfuture.de/news,145867.html?

  20. Die Top-Level-Domain .io steht vor dem Aus. Politische Veränderungen im British Indian Ocean Territory könnten das Ende der bei #Startups beliebten Domain-Endung bedeuten. #TLD #ccTLD #dotIO #ChagosArchipel winfuture.de/news,145867.html?

  21. I was always weary of using the IO TLD because it was a ccTLD of a random island, but surely someone will just pick up the IO TLD commercially now that it's becoming not-a-ccTLD, no?

    It's not like we're actually going to just *let it get deprecated*?

    #dns #dotio

  22. I was always weary of using the IO TLD because it was a ccTLD of a random island, but surely someone will just pick up the IO TLD commercially now that it's becoming not-a-ccTLD, no?

    It's not like we're actually going to just *let it get deprecated*?

    #dns #dotio

  23. I created an issue in #GitLab to ask them what the plan is in the event that ICANN announces the retirement of the #dotIO subdomain.

    Please vote on it and share if you use GitLab Pages.

    gitlab.com/gitlab-org/gitlab-p

  24. I created an issue in #GitLab to ask them what the plan is in the event that ICANN announces the retirement of the #dotIO subdomain.

    Please vote on it and share if you use GitLab Pages.

    gitlab.com/gitlab-org/gitlab-p

  25. I created an issue in #GitLab to ask them what the plan is in the event that ICANN announces the retirement of the #dotIO subdomain.

    Please vote on it and share if you use GitLab Pages.

    gitlab.com/gitlab-org/gitlab-p

  26. I created an issue in #GitLab to ask them what the plan is in the event that ICANN announces the retirement of the #dotIO subdomain.

    Please vote on it and share if you use GitLab Pages.

    gitlab.com/gitlab-org/gitlab-p

  27. I created an issue in #GitLab to ask them what the plan is in the event that ICANN announces the retirement of the #dotIO subdomain.

    Please vote on it and share if you use GitLab Pages.

    gitlab.com/gitlab-org/gitlab-p

  28. Q: Qui bono?
    A: The Western colonials who have registered .io domains for their various Western whims.

    There’s no moral reason to consider their interests. They’re casual unthinking bad actors in this case. Like all those sad white folks in Kenya, Tanzania, and Zimbabwe (nee Rhodesia) still whining about losing the lands stolen by their grandparents. Registrants of .io domains don't even have an excuse of being born into trespass.

    #dotio #Chagos #io #domains mendeddrum.org/@fanf/113273818

  29. Q: Qui bono?
    A: The Western colonials who have registered .io domains for their various Western whims.

    There’s no moral reason to consider their interests. They’re casual unthinking bad actors in this case. Like all those sad white folks in Kenya, Tanzania, and Zimbabwe (nee Rhodesia) still whining about losing the lands stolen by their grandparents. Registrants of .io domains don't even have an excuse of being born into trespass.

    #dotio #Chagos #io #domains mendeddrum.org/@fanf/113273818

  30. Q: Qui bono?
    A: The Western colonials who have registered .io domains for their various Western whims.

    There’s no moral reason to consider their interests. They’re casual unthinking bad actors in this case. Like all those sad white folks in Kenya, Tanzania, and Zimbabwe (nee Rhodesia) still whining about losing the lands stolen by their grandparents. Registrants of .io domains don't even have an excuse of being born into trespass.

    #dotio #Chagos #io #domains mendeddrum.org/@fanf/113273818

  31. Q: Qui bono?
    A: The Western colonials who have registered .io domains for their various Western whims.

    There’s no moral reason to consider their interests. They’re casual unthinking bad actors in this case. Like all those sad white folks in Kenya, Tanzania, and Zimbabwe (nee Rhodesia) still whining about losing the lands stolen by their grandparents. Registrants of .io domains don't even have an excuse of being born into trespass.

    #dotio #Chagos #io #domains mendeddrum.org/@fanf/113273818

  32. I am contemplating holding back articles until ICANN announces what they're going to do about the .io top-level domain.

    #dotIO #IANA #ICANN

  33. I am contemplating holding back articles until ICANN announces what they're going to do about the .io top-level domain.

    #dotIO #IANA #ICANN

  34. I am contemplating holding back articles until ICANN announces what they're going to do about the .io top-level domain.

    #dotIO #IANA #ICANN

  35. I am contemplating holding back articles until ICANN announces what they're going to do about the .io top-level domain.

    #dotIO #IANA #ICANN

  36. I am contemplating holding back articles until ICANN announces what they're going to do about the .io top-level domain.

    #dotIO #IANA #ICANN

  37. Apparently by handing Chagos back to Mauritius, the UK has started the beginning of the end for the .io internet domain.

    every.to/p/the-disappearance-o

    #io #DotIO #Chagos #Mauritius

  38. Apparently by handing Chagos back to Mauritius, the UK has started the beginning of the end for the .io internet domain.

    every.to/p/the-disappearance-o

    #io #DotIO #Chagos #Mauritius

  39. Apparently by handing Chagos back to Mauritius, the UK has started the beginning of the end for the .io internet domain.

    every.to/p/the-disappearance-o

    #io #DotIO #Chagos #Mauritius

  40. Apparently by handing Chagos back to Mauritius, the UK has started the beginning of the end for the .io internet domain.

    every.to/p/the-disappearance-o

    #io #DotIO #Chagos #Mauritius

  41. Apparently by handing Chagos back to Mauritius, the UK has started the beginning of the end for the .io internet domain.

    every.to/p/the-disappearance-o

    #io #DotIO #Chagos #Mauritius