#100posts — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #100posts, aggregated by home.social.
-
Beyond aggregated and summarized stats, in 2025 I met a few amazing people (you know who you are), and started a few projects. Most of these projects started with an idea, or recognizing a problem, that inspired invention.
Sometimes the ideas came from observations, shared, questioned, distilled into insights, and sometimes new creations.
During one such conversation over coffee, James (https://jamesg.blog/) and I noticed that our Spotify “daylist” list names were often quite entertaining, despite their brevity.
We mused whether it was worth keeping track of the particularly fun or interesting names, even knowing they were automatically generated.
In September 2025, James created a page on his site, a simple HTML list of a few his fun daylists names, and shared it:
* https://jamesg.blog/daylists
With a single real world #indieweb example, it was enough to stub a wiki page:
* https://indieweb.org/daylists
A little over two months later, during the weekend of 2025 IndieWeb Black Friday Create Day: Build Don’t Buy, I followed James’s example and built my own daylists page with a similar list of names of daylists, adding the datetimes when I had taken screenshots of my daylists.
* https://tantek.com/daylists
Realizing it was a page of items listed in reverse chronological order with datetime stamps, it made sense to mark it up as an h-feed so a social reader could theoretically subscribe to it. The list items had the minimum viable information for h-entry markup: content and a datetime. Minimal information meant only minimal markup was necessary: one nested HTML time element, and a couple of class names.
The list item of just the daylist name I started with:
<!-- a daylist item -->
<li>
cyberpunk synthwave wednesday early morning
</li>
<!-- -->
The name’s coarse textual day and time of day was a handy bit of text to markup with the time element with a numerical date-time for parsers. That plus two h-entry class names:
<!-- minimal h-entry markup for a daylist item -->
<li class="h-entry">
cyberpunk synthwave
<time class="dt-published" datetime="2025-10-15 07:59">wednesday early morning</time>
</li>
<!-- -->
As linked on my daylists page, that plus a little h-feed wrapper is enough to make a web feed that a social reader like Monocle can parse and display:
* https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2Fdaylists
Minimal incremental markup added to an existing human readable HTML page.
No separate feed file needed. No XML, XSLT, or JavaScript either.
The HTML is the feed.
A feed that social readers, like Monocle, or Artemis (that James wrote) can directly follow.
Full circle.
And the year before that, James blogged about how publishing an h-feed is also a more efficient, and easier to maintain, method of supporting other formats:
* https://jamesg.blog/2024/06/06/publish-h-feed
This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed #microformats #microformats2 #hFeed #hEntry #socialReader #socialWeb
← https://tantek.com/2026/005/t1/year-movies-in-theaters
→ 🔮
Glossary:
Artemis
https://indieweb.org/Artemis
daylists
https://indieweb.org/daylists
h-entry
https://indieweb.org/h-entry
h-feed
https://indieweb.org/h-feed
IndieWeb Black Friday Create Day
https://indieweb.org/events/2025-black-friday-create-day
Monocle
https://indieweb.org/Monocle
social reader
https://indieweb.org/social_reader
time element
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/time -
Beyond aggregated and summarized stats, in 2025 I met a few amazing people (you know who you are), and started a few projects. Most of these projects started with an idea, or recognizing a problem, that inspired invention.
Sometimes the ideas came from observations, shared, questioned, distilled into insights, and sometimes new creations.
During one such conversation over coffee last year, James (https://jamesg.blog/) and I noticed that our Spotify “daylist” list names were often quite entertaining, despite their brevity.
We mused whether it was worth keeping track of the particularly fun or interesting names, even knowing they were automatically generated.
In September 2025, James created a page on his site, a simple HTML list of a few of his fun daylists names, and shared it:
* https://jamesg.blog/daylists
With a single real world #indieweb example, it was enough to stub a wiki page:
* https://indieweb.org/daylists
A little over two months later, during the weekend of 2025 IndieWeb Black Friday Create Day: Build Don’t Buy, I followed James’s example and built my own daylists page with a similar list of names of daylists, adding the datetimes when I had taken screenshots of my daylists.
* https://tantek.com/daylists
Realizing it was a page of items listed in reverse chronological order with datetime stamps, it made sense to mark it up as an h-feed so a social reader could theoretically subscribe to it. The list items had the minimum viable information for h-entry markup: content and a datetime. Minimal information meant only minimal markup was necessary: one nested HTML time element, and a couple of class names.
The list item of just the daylist name I started with:
<!-- a daylist item -->
<li>
cyberpunk synthwave wednesday early morning
</li>
<!-- -->
The name’s coarse textual day and time of day was a handy bit of text to markup with the time element with a numerical date-time for parsers. That plus two h-entry class names:
<!-- minimal h-entry markup for a daylist item -->
<li class="h-entry">
cyberpunk synthwave
<time class="dt-published" datetime="2025-10-15 07:59">wednesday early morning</time>
</li>
<!-- -->
As linked on my daylists page, that plus a little h-feed wrapper is enough to make a web feed that a social reader like Monocle can parse and display:
* https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2Fdaylists
Minimal incremental markup added to an existing human readable HTML page.
No separate feed file needed. No XML, XSLT, or JavaScript either.
The HTML is the feed.
A feed that social readers, like Monocle, or Artemis (that James wrote) can directly follow.
Full circle.
And the year before that, James blogged about how publishing an h-feed is also a more efficient, and easier to maintain, method of supporting other formats:
* https://jamesg.blog/2024/06/06/publish-h-feed
This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed #microformats #microformats2 #hFeed #hEntry #socialReader #socialWeb
← https://tantek.com/2026/005/t1/year-movies-in-theaters
→ 🔮
Glossary:
Artemis
https://indieweb.org/Artemis
daylists
https://indieweb.org/daylists
h-entry
https://indieweb.org/h-entry
h-feed
https://indieweb.org/h-feed
IndieWeb Black Friday Create Day
https://indieweb.org/events/2025-black-friday-create-day
Monocle
https://indieweb.org/Monocle
social reader
https://indieweb.org/social_reader
time element
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/time -
Beyond aggregated and summarized stats, in 2025 I met a few amazing people (you know who you are), and started a few projects. Most of these projects started with an idea, or recognizing a problem, that inspired invention.
Sometimes the ideas came from observations, shared, questioned, distilled into insights, and sometimes new creations.
During one such conversation over coffee last year, James (https://jamesg.blog/) and I noticed that our Spotify “daylist” list names were often quite entertaining, despite their brevity.
We mused whether it was worth keeping track of the particularly fun or interesting names, even knowing they were automatically generated.
In September 2025, James created a page on his site, a simple HTML list of a few of his fun daylists names, and shared it:
* https://jamesg.blog/daylists
With a single real world #indieweb example, it was enough to stub a wiki page:
* https://indieweb.org/daylists
A little over two months later, during the weekend of 2025 IndieWeb Black Friday Create Day: Build Don’t Buy, I followed James’s example and built my own daylists page with a similar list of names of daylists, adding the datetimes when I had taken screenshots of my daylists.
* https://tantek.com/daylists
Realizing it was a page of items listed in reverse chronological order with datetime stamps, it made sense to mark it up as an h-feed so a social reader could theoretically subscribe to it. The list items had the minimum viable information for h-entry markup: content and a datetime. Minimal information meant only minimal markup was necessary: one nested HTML time element, and a couple of class names.
The list item of just the daylist name I started with:
<!-- a daylist item -->
<li>
cyberpunk synthwave wednesday early morning
</li>
<!-- -->
The name’s coarse textual day and time of day was a handy bit of text to markup with the time element with a numerical date-time for parsers. That plus two h-entry class names:
<!-- minimal h-entry markup for a daylist item -->
<li class="h-entry">
cyberpunk synthwave
<time class="dt-published" datetime="2025-10-15 07:59">wednesday early morning</time>
</li>
<!-- -->
As linked on my daylists page, that plus a little h-feed wrapper is enough to make a web feed that a social reader like Monocle can parse and display:
* https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2Fdaylists
Minimal incremental markup added to an existing human readable HTML page.
No separate feed file needed. No XML, XSLT, or JavaScript either.
The HTML is the feed.
A feed that social readers, like Monocle, or Artemis (that James wrote) can directly follow.
Full circle.
And the year before that, James blogged about how publishing an h-feed is also a more efficient, and easier to maintain, method of supporting other formats:
* https://jamesg.blog/2024/06/06/publish-h-feed
This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed #microformats #microformats2 #hFeed #hEntry #socialReader #socialWeb
← https://tantek.com/2026/005/t1/year-movies-in-theaters
→ 🔮
Glossary:
Artemis
https://indieweb.org/Artemis
daylists
https://indieweb.org/daylists
h-entry
https://indieweb.org/h-entry
h-feed
https://indieweb.org/h-feed
IndieWeb Black Friday Create Day
https://indieweb.org/events/2025-black-friday-create-day
Monocle
https://indieweb.org/Monocle
social reader
https://indieweb.org/social_reader
time element
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/time -
Beyond aggregated and summarized stats, in 2025 I met a few amazing people (you know who you are), and started a few projects. Most of these projects started with an idea, or recognizing a problem, that inspired invention.
Sometimes the ideas came from observations, shared, questioned, distilled into insights, and sometimes new creations.
During one such conversation over coffee, James (https://jamesg.blog/) and I noticed that our Spotify “daylist” list names were often quite entertaining, despite their brevity.
We mused whether it was worth keeping track of the particularly fun or interesting names, even knowing they were automatically generated.
In September 2025, James created a page on his site, a simple HTML list of a few his fun daylists names, and shared it:
* https://jamesg.blog/daylists
With a single real world #indieweb example, it was enough to stub a wiki page:
* https://indieweb.org/daylists
A little over two months later, during the weekend of 2025 IndieWeb Black Friday Create Day: Build Don’t Buy, I followed James’s example and built my own daylists page with a similar list of names of daylists, adding the datetimes when I had taken screenshots of my daylists.
* https://tantek.com/daylists
Realizing it was a page of items listed in reverse chronological order with datetime stamps, it made sense to mark it up as an h-feed so a social reader could theoretically subscribe to it. The list items had the minimum viable information for h-entry markup: content and a datetime. Minimal information meant only minimal markup was necessary: one nested HTML time element, and a couple of class names.
The list item of just the daylist name I started with:
<!-- a daylist item -->
<li>
cyberpunk synthwave wednesday early morning
</li>
<!-- -->
The name’s coarse textual day and time of day was a handy bit of text to markup with the time element with a numerical date-time for parsers. That plus two h-entry class names:
<!-- minimal h-entry markup for a daylist item -->
<li class="h-entry">
cyberpunk synthwave
<time class="dt-published" datetime="2025-10-15 07:59">wednesday early morning</time>
</li>
<!-- -->
As linked on my daylists page, that plus a little h-feed wrapper is enough to make a web feed that a social reader like Monocle can parse and display:
* https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2Fdaylists
Minimal incremental markup added to an existing human readable HTML page.
No separate feed file needed. No XML, XSLT, or JavaScript either.
The HTML is the feed.
A feed that social readers, like Monocle, or Artemis (that James wrote) can directly follow.
Full circle.
And the year before that, James blogged about how publishing an h-feed is also a more efficient, and easier to maintain, method of supporting other formats:
* https://jamesg.blog/2024/06/06/publish-h-feed
This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed #microformats #microformats2 #hFeed #hEntry #socialReader #socialWeb
← https://tantek.com/2026/005/t1/year-movies-in-theaters
→ 🔮
Glossary:
Artemis
https://indieweb.org/Artemis
daylists
https://indieweb.org/daylists
h-entry
https://indieweb.org/h-entry
h-feed
https://indieweb.org/h-feed
IndieWeb Black Friday Create Day
https://indieweb.org/events/2025-black-friday-create-day
Monocle
https://indieweb.org/Monocle
social reader
https://indieweb.org/social_reader
time element
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/time -
Beyond aggregated and summarized stats, in 2025 I met a few amazing people (you know who you are), and started a few projects. Most of these projects started with an idea, or recognizing a problem, that inspired invention.
Sometimes the ideas came from observations, shared, questioned, distilled into insights, and sometimes new creations.
During one such conversation over coffee, James (https://jamesg.blog/) and I noticed that our Spotify “daylist” list names were often quite entertaining, despite their brevity.
We mused whether it was worth keeping track of the particularly fun or interesting names, even knowing they were automatically generated.
In September 2025, James created a page on his site, a simple HTML list of a few his fun daylists names, and shared it:
* https://jamesg.blog/daylists
With a single real world #indieweb example, it was enough to stub a wiki page:
* https://indieweb.org/daylists
A little over two months later, during the weekend of 2025 IndieWeb Black Friday Create Day: Build Don’t Buy, I followed James’s example and built my own daylists page with a similar list of names of daylists, adding the datetimes when I had taken screenshots of my daylists.
* https://tantek.com/daylists
Realizing it was a page of items listed in reverse chronological order with datetime stamps, it made sense to mark it up as an h-feed so a social reader could theoretically subscribe to it. The list items had the minimum viable information for h-entry markup: content and a datetime. Minimal information meant only minimal markup was necessary: one nested HTML time element, and a couple of class names.
The list item of just the daylist name I started with:
<!-- a daylist item -->
<li>
cyberpunk synthwave wednesday early morning
</li>
<!-- -->
The name’s coarse textual day and time of day was a handy bit of text to markup with the time element with a numerical date-time for parsers. That plus two h-entry class names:
<!-- minimal h-entry markup for a daylist item -->
<li class="h-entry">
cyberpunk synthwave
<time class="dt-published" datetime="2025-10-15 07:59">wednesday early morning</time>
</li>
<!-- -->
As linked on my daylists page, that plus a little h-feed wrapper is enough to make a web feed that a social reader like Monocle can parse and display:
* https://monocle.p3k.io/preview?url=https%3A%2F%2Ftantek.com%2Fdaylists
Minimal incremental markup added to an existing human readable HTML page.
No separate feed file needed. No XML, XSLT, or JavaScript either.
The HTML is the feed.
A feed that social readers, like Monocle, or Artemis (that James wrote) can directly follow.
Full circle.
And the year before that, James blogged about how publishing an h-feed is also a more efficient, and easier to maintain, method of supporting other formats:
* https://jamesg.blog/2024/06/06/publish-h-feed
This is post 6 of #100PostsOfIndieWeb. #100Posts #yearInReview #webFeed #microformats #microformats2 #hFeed #hEntry #socialReader #socialWeb
← https://tantek.com/2026/005/t1/year-movies-in-theaters
→ 🔮
Glossary:
Artemis
https://indieweb.org/Artemis
daylists
https://indieweb.org/daylists
h-entry
https://indieweb.org/h-entry
h-feed
https://indieweb.org/h-feed
IndieWeb Black Friday Create Day
https://indieweb.org/events/2025-black-friday-create-day
Monocle
https://indieweb.org/Monocle
social reader
https://indieweb.org/social_reader
time element
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/time -
Important #indieweb lesson in #modular website setup this morning:
Keep your DNS provider separate from your CDN separate from your webhost, so you can swap out any one of them as necessary, whether for economic or as it were today, reliability reasons. And make sure those services themselves don’t depend on each other.
This is of course regarding the #Cloudflare #outage:
* https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
* https://theguardian.com/technology/2025/nov/18/cloudflare-outage-causes-error-messages-across-the-internet
* https://the-independent.com/tech/cloudflare-down-twitter-not-working-outage-b2867367.html
* https://bbc.com/news/articles/c629pny4gl7o
* https://independent.co.uk/bulletin/news/nj-transit-down-app-cloudfare-outage-b2867457.html
#CloudflareOutage #NJTransit #ChatGPT #Shopify #Dropbox #Coinbase #Twitter/X #modularity #devops
This is post 17 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2025/311/t2/indieweb-sessions-btconf-berlin
→ 🔮 -
October is almost over! For all us procrastinators, still time to write a post or two to participate in #October blogging challenges like:
#Blogtober
#IndieWebMovieClub on #Hackers
#Inktober
#Mathober
#WeirdWebOctober
+ coding challenges:
#Hacktoberfest — https://blog.holopin.io/posts/hacktoberfest-2025
Many more at:
* https://indieweb.org/October
* https://indieweb.org/blog_carnival
🎃 And tomorrow is #Halloween so consider a holiday theme for your site as well! See #IndieWeb examples for inspiration:
* https://indieweb.org/Halloween
Last but not least, perhaps we’ll see some of you at #IndieWebCamp Berlin this weekend!
* https://indieweb.org/2025/Berlin
This is post 13 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2025/182/t1/movie-club-tomorrowland-submissions
→ 🔮 -
The team @micro.blog have done it again.
They soft-launched https://micro.one yesterday¹.
This may be the most accessible onramp to the open social web ever.
Cost: $1 a month. Yes you read correctly.
This is the simplest and cheapest (where you are the customer, not the product) way to own your identity and content online².
Stop posting in someone else’s garage³.
Time to export your Twitter, and migrate your Mastodon handle to your own home on the web.
Of course you can bring your own domain name. Additionally:
* blog posts, naturally, both articles and microblogging notes
* photos
* podcasting
* custom themes
* web-clients and native mobile posting clients
* WordPress, Tumblr, Mastodon, Medium import
More details (and alternatives) at https://micro.one/about/pricing
And yes, it interoperates with the open #socialWeb, including:
* #ActivityPub support, #Mastodon and #fediverse compatibility
* #IndieAuth to sign-in to third-party apps
* #microformats support in all built-in themes
* #Webmention for sending and receiving replies across websites
* #Micropub standard posting API, supporting dozens of clients
* #Microsub standard timeline API, supporting social readers
More #indieweb support details at https://micro.one/about/indieweb
Did I mention the the superb micro.blog (and micro.one) Community Guidelines?
* https://help.micro.blog/t/community-guidelines/39
Well done @manton.org and team.
This is post 6 of #100PostsOfIndieWeb. #100Posts #ownYourIdentity #ownYourData #openSocialWeb
← https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24
→ https://tantek.com/2025/012/t1/eight-years-webmention
Glossary
IndieAuth
https://indieweb.org/IndieAuth
microformats
https://microformats.org/wiki/microformats
Micropub
https://indieweb.org/Micropub
Microsub
https://indieweb.org/Microsub
Webmention
https://indieweb.org/Webmention
References
¹ https://www.manton.org/2025/01/03/microone-was-effectively-a-softlaunch.html
² https://tantek.com/2025/001/t1/15-years-notes-my-site-first
³ https://tantek.com/2023/022/t2/own-your-notes-domain-migration -
⚠️ .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