#100postsofindieweb — Public Fediverse posts

Happy Twin Peaks day to those who celebrate!

In Agent Cooper’s first appearance in the show, he’s driving a car, right hand on the steering wheel, left hand holding a small black box (a microcassette recorder), that, if you don’t look too closely, could easily be mistaken for a regular sized black iPhone with a flush battery pack attached to its back.

You may search the web for a screen capture or video if you like, or continue with this plain text description.

He's keeping his eyes on the road, and dictating audio.

“Diane, 11:30 a.m., February 24th. Entering the town of Twin Peaks.”

In 1989 he’s dictating a log entry to his presumably human assistant, Diane, for her to transcribe after the fact.

In 2026 (notwithstanding safety and legal concerns while driving) it’s not a stretch to say he could (would likely) be dictating to his (perhaps renamed) digital assistant, Diane, or at least a speech-to-text feature in a note-taking application that would automatically transcribe his words in real time.

Those transcribed words could even be saved as a private post or draft, either locally on his device, or to his personal website, for him to review and clean-up if necessary before publishing to and notifying perhaps a limited audience.

Imagine capturing your thoughts without having to look at a screen. No scrolling to first see what others have said. No attention-distracting alerts or admintax prompts to update an application. Capture your thoughts as they occur, and continue onward, focused on your current task or project, uninterrupted.

Today’s technologies and standards should enable such an interaction, all the way through to storing your dictations in a location of your choice. I wonder if anyone has built this.

This is post 8 of #100PostsOfIndieWeb. #100Posts #IndieWeb #TwinPeaksDay

← https://tantek.com/2026/007/t3/wikipedia-edited-year-in-review
→ 🔮

Wikipedia “Edited” 2025 year in review, summarizing from Wikimedia XTools queries, and Wikipedia itself, curated manually for my personal site:

* 7 articles created (new personal best), with several firsts for me. In creation order:
  * "Take California" (https://en.wikipedia.org/wiki/Take_California) — first music related
  * "West Coast Health Alliance" (https://en.wikipedia.org/wiki/West_Coast_Health_Alliance) — first health related
  * "Northeast Public Health Collaborative" (https://en.wikipedia.org/wiki/Northeast_Public_Health_Collaborative)
  * "RaptureTok" (https://en.wikipedia.org/wiki/RaptureTok) — first hashtag article
  * "Governors Public Health Alliance" (https://en.wikipedia.org/wiki/Governors_Public_Health_Alliance)
  * "Stephanie D'Agostini" (https://en.wikipedia.org/wiki/Stephanie_D%27Agostini) — first comedian
  * "Mic Drop Comedy" (https://en.wikipedia.org/wiki/Mic_Drop_Comedy) — first comedy club

* 2 Category: articles created — first ever for me. In creation order:
  * https://en.wikipedia.org/wiki/Category:2025_establishments_in_Hawaii
  * https://en.wikipedia.org/wiki/Category:2025_establishments_in_Maryland

* 28 redirects created: https://xtools.wmcloud.org/pages/en.wikipedia.org/Tantek/all/onlyredirects

and

* 1 image uploaded to Wikimedia Commons: https://commons.wikimedia.org/wiki/File:2025-12-11-stefdag.jpg?photo

In total:

* 272 edits (not counting User: page edits) across Wikipedia and Wikimedia commons
  * 229 main Wikipedia articles edits
  * 39 Talk: page edits
  * 2 Category: page edits (above-mentioned articles created)
  * 2 Wikipedia Commons edits
 
* 329 edits and contributions counting User: page edits: https://xtools.wmcloud.org/globalcontribs/Tantek/all///2025-12-31T01:36:35Z?limit=330

This is my first time posting a Wikipedia “Edited” year in review, despite having edited Wikipedia for 20+ years (https://tantek.com/2025/300/t20/wikipedia-editing-anniversary).

While this #indieweb version of a year in review was fun to make and look back on, since all the data is public, there’s an opportunity here for a service (perhaps another XTool) or open source project to create such a summary for any Wikipedia editor.

Beyond a nicer presentation than plain text lists and numbers, such a summary could include visuals like a graphs of some of these stats over time, like Wikipedia pages created or edits of various kinds each year.

Until then, I encourage everyone editing Wikipedia to make their own “Edited” (I made that up, feel free to pick a better term) year in review and post it on your personal site! Feel free to re-use any of the design or separation of numbers that I chose, or make up your own.


This is post 7 of #100PostsOfIndieWeb. #100Posts #yearInReview #Wikipedia #WikipediaEdited #Wikimedia #WikimediaCommons #XTools

← https://tantek.com/2026/006/t1/2025-people-projects-insights-creations
→ 🔮

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

My year in movies in theaters, using Fandango > My Orders > History, my Swarm Timeline, and personal recollection, to aggregate a few lists and stats:

I saw 9 new movies in theaters in 2025, two of them multiple times (dates are first viewing)
* 2025-02-20 👹 Captain America: Brave New World
* 2025-05-22 ℹ️ Mission: Impossible - The Final Reckoning
* 2025-07-20 🦸🏻‍♂️ Superman (2025)
* 2025-07-26 ⓸ The Fantastic Four: First Steps (2025)
* 2025-10-09 🔺 Tron: Ares
* 2025-11-15 🏃🏻‍♂️ The Running Man (2025)
* 2025-11-19 🧌 Predator: Badlands
* 2025-12-03 🪄 Now You See Me: Now You Don’t
* 2025-12-14 🧹 Wicked: For Good

In these cities:
* 11x San Francisco
* Berlin
* Boston
* San Diego

At the following movie theaters:
* 6x AMC Metreon Dolby
* 2x AMC Metreon IMAX
* Zoo Palast
* Alamo Drafthouse SF HDR BARCO
* AMC Boston Common IMAX
* Regal Stonestown Galleria ScreenX
* Regal Stonestown Galleria
* AMC Mission Valley 20

In the following formats, in rough order of frequency then features/quality:
* 5x Dolby
* 2x IMAX
* 2x Standard
* 3D IMAX
* 3D Dolby
* HDR BARCO
* ScreenX
* Standard German dub

The latter three were new formats for me this year: HDR BARCO, ScreenX, and Standard German dub.

My preferred movie format is still Dolby, in particular in the Metreon Dolby theater. I’ve been other “Dolby” theaters (including other AMC Dolby) and none have measured up. Dolby theater audio quality is significantly better than any IMAX theater I have been in.

3D IMAX can look amazing for the right film (e.g. Tron: Ares). In comparison, I was not impressed by 3D Dolby, or any other 3D projection+glasses technologies over the years.

HDR BARCO was very high quality, however, having seen the same film (Tron: Ares, with lots of dark scenes) in both HDR BARCO and Metreon Dolby, I could not see a discernible difference in the visual quality. Perhaps the light pollution from the Alamo Drafthouse's under-table lights interfered with the quality of the HDR BARCO experience.

I archived the page that Alamo Drafthouse had setup for the HDR BARCO Tron: Ares showing:
* https://web.archive.org/web/20251011173709/https://drafthouse.com/sf/event/special-event-tron-ares-hdr-by-barco?cinemaId=0801&sessionId=74102
Unclear why they took the page down.

ScreenX was an entertaining gimmick for the landscapes of Predator: Badlands. I would consider seeing another suitable movie in the format.

Watching a film dubbed in German was an interesting challenge that pushed and exceeded my German speech comprehension skills. I had to use contextual cues, on screen, sci-fi terminology, and the Fantastic Four subject matter to interpret much of it.

I constructed these summary lists by hand, and having completed them, I think next time it might work better to incorporate the raw data into a table with various columns for date, time, film name, theater, auditorium, format, and perhaps more like seat number(s) and the set of us at the viewing. I would not include classic "IMDB" fields like genre, director, writer etc. because all of those are independent of the particular theater/viewing and can easily be looked up on Wikipedia. Duplicating that info in my own personal notes would merely add noise to the signal of each specific movie theater experience.

I’m curious if anyone else has done something like this / is doing this to keep track of the movies they see in theaters, what info to capture about the viewing, what to note about the particular experience, and what to publish on their #indieweb site.

This is post 5 of #100PostsOfIndieWeb. #100Posts #yearInReview #yearInMovies #yearInTheaters

← https://tantek.com/2026/004/t1/year-in-sport
→ 🔮

My Year in Sport, using data from my Strava, Swarm, and personal notes & recollections, assembled into a simpler summary on my personal site.

2025 activities according to Strava:
🏃🏻‍♂️1354mi + 160,077' hiking+running
 👟 823mi + 119,453' running
  ⛰ 485mi trail running
  🛣 337mi road running
 🥾 526mi + 40,624' hiking
🧘🏻‍♂️ 8h27m yoga
💪🏻 some number of weight-lifting sessions (less than one a week)
🚲 4.6mi + 413' bicycling — only one ride all year somehow(?)
🪨 1 bouldering session (at Movement)

Races:
🏁 3 races, finished 2
🌳 12k Bay to Breakers 1:55:31 https://tantek.com/t5c61
⛰ 50k Skyline: 9:34:51 https://tantek.com/t5dQ1

2025 was a more difficult year than expected, in many ways, and it cut both the hours and frequencies of many physical activities.

My hours and frequency of yoga, weight-lifting, bicycling, and bouldering all dropped from 2024 to 2025. My goals for 2026 are to find sustainable regular rhythms for each of those, either by myself or with friends.

Despite that, I made several improvements in 2025 over 2024:
* Overall: 160,077' climbed, +9.4k' over 150,676' in 2024
* Running: 823mi + 119,453', +20mi +8.3k' over 803mi + 111,155' in 2024
* Hiking: 526mi just barely (+6mi) over 520mi in 2024
* Finished a 50k! First since mid-2023.

I have a few running goals for 2026:
* incrementally faster Bay to Breakers over 2025
* Broken Arrow 23k Skyrace, finish and ideally beat my 2024 time (6h52m)
* finish a 50k trail race, my fifth 50k

I don't have specific metrics goals, like total distance, or feet climbed, or any specific race times (other than beating last year’s times). Those are all secondary to my goals.

Based on how the past few years have gone, I believe these are reasonable goals, yet will take focus and hard work to achieve them.

Lastly, this personalized, #indieweb “year in sport”, reflects much more of what matters to me than any summary from an online service. It’s not perfect and doesn’t need to be. It’s a start and I expect to iterate and improve it next year.

This is post 4 of #100PostsOfIndieWeb. #100Posts #yearInReview #yearInSport

← https://tantek.com/2026/003/t1/seek-2025-year-in-review
→ 🔮


Glossary:

Year in Review:
  https://indieweb.org/year_in_review

My Seek 2025 Year in Review:

* 101 new species observed (down from 141 last year)

Top three kinds:
  * 64 new plants (down from 79)
  * 14 new insects (down from 20)
  * 8 new fungi
* 4 new challenge badges earned (down from 56)

July, June, February were the months I observed the most new species.
Last year: June, March, July.

Seek also gave me a graph of observations per month, and also a map of where I made my discoveries.

As noted last year: https://tantek.com/2025/020/t1/seek-2024-year-in-review

Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species.

Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works:
1. works without creating an account
2. works completely offline to identify species
3. adds new species to your local collection on your device

Those first two capabilities (no login wall, offline first) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends.

This is post 3 of #100PostsOfIndieWeb. #100Posts #yearInReview #iNaturalist #SeekApp

← https://tantek.com/2026/002/t1/find-export-strava-year-in-sport
→ https://tantek.com/2026/004/t1/year-in-sport


Glossary:

login wall
  https://indieweb.org/login_wall
offline first
  https://indieweb.org/offline_first

I checked my Strava: Year in Sport 2025 after I did my last run on the 31st, and it felt a bit light. When I checked my saved images/videos from last year’s Strava Year in Sport, it was clear they had dropped several things from 2024 to 2025.


First, here’s updated instructions for finding and exporting your Strava Year in Sport 2025:

The Strava Year in Sport 2025 is once again only available on the native mobile app (iOS and presumably Android) and not accessible via the website.

From the mobile app home screen, tap the "📋 You" button in the lower right corner.

Near the top you should see an orange header with white text:

STRAVA
YEAR IN SPORT

and a black triangle play button on a white disc background.



Tap that ▶️ play button.


Saving Summary Segments

You should fairly quickly see an animation start playing, with nine "segments" (like Instagram stories) at the top, gradually filling-in as progress indicators one at a time.

The first "segment" is purely intro animation. You can skip it.

Every subsequent "segment" you can screenshot using the respective button pressing on your mobile (e.g. volume-up + power on iPhone 14). In addition to taking a screenshot it will put you in a "share" screen with one or more videos or still images to share in a carousel format.

For each item in the carousel (if there is more than one)
1. tap the item in the carousel
2. tap the "[↓] Save" button at the bottom to store it locally on your mobile

Then tap "Cancel" in the top right to go back to the "segments".

Either wait for that current "segment" to finish playing or tap the video near the right edge of the screen to skip to the next "segment" and repeat the two steps above.

The ninth "segment" is your overall summary, and shows all your sports combined.

Save it (using the "[↓] Save" button as noted above), then
* tap the "✏️  Customize" button
* choose an individual sport (e.g. "👟 Run")
* tap "Save changes"
* save that image (with the "[↓] Save" button as above)
* tap customize again
* choose the next sport (e.g. "🚲 Ride")
* "Save changes" again
* "[↓] Save" button again

Strava seemingly only reports summaries of (up to?) two of your sports. Those were Run (presumably all running, street and trail) and Ride for me.


Cleanup Your Screenshots

After having saved all the videos/images for each "segment", you can:
* go back to your mobile’s top level Photos app/stream
* delete the screenshots

You should see all the images you've saved (no videos this year). If anything is missing, go back to the previous steps and save them again, then remove any duplicates as necessary.


I have saved all the images from my own Strava Year In Sport, and as I assemble the pieces into my own Year in Sport post, I’ll take more notes, and add to the IndieWeb year in review page accordingly: https://indieweb.org/year_in_review

Previously: https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save

#Strava #yearInSport #yearInReview #ownYourYearInReview

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

← https://tantek.com/2026/001/t1/no-socials-january
→ https://tantek.com/2026/003/t1/seek-2025-year-in-review

2026 goals I’ve heard:
* Dry January — avoid alcohol
* Meatless January — avoid meat

If you have a personal website, how about also:

* No Socials January — avoid #socialMedia silos

No posting on social media, just for a month (not counting DMs).

Instead, since you have your own website, post there, and see how that feels.

If you don’t have a personal website, make it your goal for the month to set one up. The #IndieWeb folks https://indieweb.org/ can help! Join https://chat.indieweb.org/

Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year.

This is post 1.

Previously:
* https://tantek.com/2025/001/t1/15-years-notes-my-site-first

← ✨
→ 🔮

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
→ 🔮

Great #indieweb sessions at #btconf #Berlin!

Yesterday, Sacha Judd (@sachajudd.com) reminded us to “teach someone …. something about building for the web”, and to “take back control of your feeds, your attention, and … go exploring again”. She encouraged us to “build healthy online neighborhoods”. That’s a great metaphor and very complementary to rebuilding your own home(page) on the web with perhaps a digital garden as well!

Today, Ana Rodrigues (@anarodrigu.es @ohhelloana.blog) connected the dots from Sacha’s reminders to encouraging everyone to join burgeoning healthy online neighborhoods like:
* 32-Bit Cafe (@32bit.cafe and see their Discord & Discourse)
* IndieWeb Community (@indieweb.org and see @chat.indieweb.org for Discord, IRC, Slack)

Both are filled with online neighbors helping and teaching each other how to make what people want to express on and for their personal sites!

Know of other healthy online neighborhoods? Let me know and I’ll add them to the IndieWeb communities page!

Want to connect your online home with online neighbors?
* Join the IndieWeb #webring: https://indieweb.org/IndieWeb_Webring

Prefer events? Join a virtual Frontend Study Hall, Homebrew Website Club meetup, or the next #IndieWebCamp!


Glossary and links:

btconf (Beyond Tellerrand conference) Berlin 2025
  https://beyondtellerrand.com/events/berlin-2025
communities (IndieWeb)
  https://indieweb.org/communities
digital gardens
    https://indieweb.org/digital_garden
home (page) on the web
  https://indieweb.org/homepage
Homebrew Website Club (HWC) online and in-person:
  https://events.indieweb.org/tag/hwc
Front End Study Hall (FrESH)
  https://indieweb.org/fresh
IndieWebCamps - in-person and hybrid!
  https://events.indieweb.org/tag/indiewebcamp


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

← https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos
→ https://tantek.com/2025/322/t1/modular-website-dns-cdn-webhost

IndieWebCamp Berlin was great! Participants facilitated inspiring sessions, and everyone made something on or for their personal site on our Create Day #Hackathon.

Session notes are up from day 1, recordings to follow:
* https://indieweb.org/2025/Berlin/Schedule

Demos notes also up, recording to follow:
* https://indieweb.org/2025/Berlin/Demos

Want to keep up with #IndieWebCamp #Berlin participants? Volunteer Daniel has updated the IndieWebCamp Berlin feed:
* https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My

Questions about sessions or demos? Ask in #IndieWeb chat!
* https://chat.indieweb.org/


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

← https://tantek.com/2025/304/t1/night-before-indiewebcamp-berlin
→ https://tantek.com/2025/311/t2/indieweb-sessions-btconf-berlin

🎃 Night before IndieWebCamp Berlin! Participants are (hopefully, mostly) all tucked into their beds, dreaming of what wonderful things they can brainstorm for their personal sites Saturday, and #HackTheirPlanet on Sunday.

Want to keep up with #IndieWebCamp #Berlin participants?

Follow their feeds and a Bluesky starter pack (happy to include more for any other formats, protocols, or platforms)
* https://indieweb.org/2025/Berlin#Feeds_Lists_Starter_Packs_Oh_My

We’ll add more as folks sign-in at the camp!

This is post 14 of #100PostsOfIndieWeb. #100Posts #IndieWeb #Blogtober #IndieWebMovieClub #HackThePlanet 📟

← https://tantek.com/2025/303/t1/october-blogging-challenges
→ https://tantek.com/2025/311/t1/indiewebcamp-berlin-sessions-demos

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
→ 🔮

I really enjoyed the IndieWeb Movie Club May 2025 submissions about the film “Tomorrowland”. Ordered from earliest to most recent:

* Paolo Feadin: https://www.feadin.eu/en/posts/tomorrowland
* Thomas Vander Wal: https://vanderwal.net/random/entrysel.php?blog=2119
* gRegor Morrill: https://gregorlove.com/2025/05/tomorrowland/
* Benji: https://www.benji.dog/watched/1748757918-tomorrowland-2015/
* James: https://jamesg.blog/2025/07/01/tomorrowland-indieweb-movie-club

As promised in my welcome post, here are my past posts regarding or related to Tomorrowland the film, Before Tomorrowland the book, and the themes and messages therein:
* https://tantek.com/2016/042/t1/the-problem-to-solve-negative-news
* https://tantek.com/2016/145/b1/tomorrowland-misjudging-by-name-association
* https://tantek.com/2016/150/b1/tomorrowland-change-perspective-flight-paris
* https://tantek.com/2016/279/t2/finished-reading-before-tomorrowland

I rewatched the film in May, and had a mix of remembering my past impressions as well as forming new impressions in the context of 2025. A lot has changed in the past 10 years. Worth a separate blog post.
 
Previously: https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland

#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub

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

← https://tantek.com/2025/120/t1/indieweb-movie-club-tomorrowland
→ https://tantek.com/2025/303/t1/october-blogging-challenges

Welcome to the May 2025 edition of IndieWeb Movie Club!

As your host for this month¹, I invite you to (re)watch the film “Tomorrowland” (https://movies.disney.com/tomorrowland), with an optional prequel book reading assignment!

“Before Tomorrowland” (https://books.disney.com/book/before-tomorrowland/) was released about a month before the film, so it’s fine to read before watching.

#Tomorrowland is available in various physical media formats, and via streaming on DisneyPlus². 130 minutes, rated PG.

This month is the 10th anniversary of Tomorrowland’s release.

The world was quite different in 2015.

I had my own impressions of Tomorrowland when I first heard about it and then watched it much later (which I won’t link to yet to avoid spoilers or biasing your opinions). The film made such a strong impression on me that I held a group film viewing and discussion party in 2015!

I’m curious how both first time viewers in 2025 and folks watching a second (or more) time think of Tomorrowland.

If you would like to participate in this month’s IndieWeb Movie Club:
* optional: read the prequel book
* watch the film
* blog a read³ (for the book), watch⁴, review⁵, or even a simple note⁶ post of your impressions, or some or all the above and link to this post

If you want your post(s) to be included in the May 2025 IndieWeb Movie Club roundup, notify me with a Webmention⁷ from your post, or drop a link in the IndieWeb chat discussion channel⁸ and @-mention me.

Since this is an IndieWeb community activity, please both follow the Code of Conduct⁹, and also keep your post within the same rating (PG) as the movie. I may curate the roundup accordingly.

Happy reading, watching, and dreaming!

#TomorrowlandFilm #BeforeTomorrowland #IndieWeb #IndieWebMovieClub

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

← https://tantek.com/2025/077/t1/what-are-words-for-blogging
→ 🔮


References:

¹ https://indieweb.org/IndieWeb_Movie_Club#2025
² https://www.disneyplus.com/en-gb/browse/entity-3355a91d-addb-4c66-91a6-136325e6ecf7
³ https://indieweb.org/read
⁴ https://indieweb.org/watch
⁵ https://indieweb.org/review
⁶ https://indieweb.org/note
⁷ https://indieweb.org/Webmention
⁸ https://indieweb.org/discuss#indieweb
⁹ https://indieweb.org/code-of-conduct

“Tell me, what are words for?” They are for blogging!

Earlier today during an informal espresso live stream in the #indieweb cafe, Spotify was playing an auto-generated daylist, something like “romantic 80s tuesday morning”, and the 1982 song “Words”¹ by the band Missing Persons came on.

When we heard this lyric:

🎶 What are words for when no one listens? 🎶

I remarked half-jokingly in response:

Words are for blogging, whether anyone is listening, reading, or not.

Another participant noted that blogging sometimes feels like screaming into the void.

I noted it doesn’t matter if anyone is reading (or listening), it’s fine to blog for an audience of one, yourself, even just to have something to refer to or reference in the future.

When I write a post it’s often directed at only a small number of people, who may be part of a larger conversation. The point of publishing it publicly is to assert a level of confidence and credibility by the act of “putting it on the permanent record” (since nearly everything blogged is promptly indexed and archived.) with a permalink.

The lyrics have some quite prescient bits, like this:

“No one notices, I think I'll dye my hair blue
 Media overload bombarding you with action
 It’s getting near impossible to cause distraction”

Written and sung more than forty years ago. Long before the web (or #socialWeb) was a thing.

Rewriting the lyrics as a parody could be a fun project, e.g.:

🎶 What are blogs for when no one reads them? 🎶

some existing lyrics barely need any edits, like:

“It’s like the feeling at the end of the page
 When you realize you don't know what you just read”

perhaps an exercise for the reader for now.

Previously: “Inbox Zero” (parody of The Fixx “Saved by Zero”²)
* https://tantek.com/w/InboxZero (2009-01-29 https://tantek.com/twttr/status/1160324190)


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

← https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity
→ 🔮


Glossary

blog
  https://indieweb.org/blog
blogging
  https://indieweb.org/blogging
permalink
  https://indieweb.org/permalink
why blog
  https://indieweb.org/why_post


References

¹ https://libre.fm/artist/Missing+Persons/track/Words (YouTube link inside)
² https://libre.fm/artist/The+Fixx/track/Saved+by+Zero (YouTube link inside)

Last week I published my first Cybersecurity Friday post with three key steps for indieweb cybersecurity. In summary:

1. Email MFA/2FA. Add multi-factor authentication (sometimes called two-factor authentication) to everywhere you store or check email. Do not use phone/cell numbers.
2. Domain Registrar MFA. Add multi-factor authentication to your domain registrar account.
3. Web Host MFA. Same for your web host and any intermediate name servers (DNS) or content delivery network (CDN) service accounts.

Full post: https://tantek.com/2025/052/b1/steps-indieweb-cybersecurity

Next time: entropy is your friend in security.

If you want my #Cybersecurity Friday posts as soon as I publish them, follow my site https://tantek.com/ directly in your reader rather than using #socialMedia or #Mastodon or some other notes-centric #fediverse client.

You can subscribe to my site directly with an h-feed supporting #indieweb Social Reader, or if you use a classic feed reader, it can auto-discover my Atom feed from my home page.

You can also read my article blog posts and those from other Mozillians on the Mozilla Planet:
* https://planet.mozilla.org/
If you look closely you might even find my not-so-secret articles-only Atom feed linked there if you prefer.


This is post 9 of #100PostsOfIndieWeb. #100Posts #cyber #security

← https://tantek.com/2025/020/t1/seek-2024-year-in-review
→ 🔮


Glossary

article post
  https://indieweb.org/article
Atom
  https://indieweb.org/Atom
content delivery network
  https://indieweb.org/content_delivery_network
cybersecurity
  https://en.wikipedia.org/wiki/cybersecurity
DNS
  https://indieweb.org/DNS
domain registrar
  https://indieweb.org/domain_registrar
entropy
  https://en.wikipedia.org/wiki/Entropy_(information_theory)
feed reader
  https://indieweb.org/feed_reader
h-feed
  https://indieweb.org/h-feed
MFA / 2FA
  https://indieweb.org/multi-factor_authentication sometimes called Two Factor Authentication or Second Factor Authentication
mobile number for MFA
  https://indieweb.org/SMS#Criticism
note post
  https://indieweb.org/note
social reader
  https://indieweb.org/social_reader
web host
  https://indieweb.org/web_hosting

My Seek 2024 Year in Review:

* 141 new species observed, of those, the top three kinds:
  * 79 plants
  * 20 insects
  * 16 fungi
* 56 challenge badges earned

June was the month I observed the most new species in 2024, followed by March, and then July.

Seek also gave me a graph of observations per month, and also a map of where I made my discoveries.

Rather than posting screenshots of the Year in Review that Seek provided me in the app, I am posting the relevant content here in a post on my personal site, which I know I’ll be able to search and look up in the future.

Seek is a delightful free (like actually free, free of tracking, free of surveillance) native mobile application for identifying species.

Made by the iNaturalist folks (https://www.inaturalist.org/pages/seek_app), Seek works without creating an account, and is able to work completely offline to identify species out in the wild (and add them to your local collection).

Seek awards you Species Badges when you discover a number of species of a particular grouping, as well as Challenge Badges when you complete one or more of their monthly challenges that they post.

In some ways it’s like Pokemon Go, except based on finding and collecting observations of real living things.

I have found it quite useful especially when traveling, and wondering is that plant (or animal) the same as one I’ve seen elsewhere, perhaps around home, or is it a slightly different species?

I also really like the good example that Seek provides for how an app can be immediately useful without requiring extra labor (like creating an account, or logging on) on behalf of the person using it.

Lastly, Seek is an excellent example of a truly offline capable app where nearly all of its functionality works just fine without a network connection.

Both of these capabilities (offline first, no login wall) are what we should aspire to when we build #indieweb apps or websites for ourselves and our friends.


This is post 8 of #100PostsOfIndieWeb. #100Posts #yearInReview #iNaturalist #SeekApp

← https://tantek.com/2025/012/t1/eight-years-webmention
→ https://tantek.com/2025/055/t1/three-steps-indieweb-cybersecurity


Glossary:

login wall
  https://indieweb.org/login_wall
offline first
  https://indieweb.org/offline_first

🎉 Eight years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/

As a social web building block, #Webmention was designed to work with various other building blocks. Small pieces, loosely joined. Every year developers find new ways to work with Webmention, and new subtleties when combined with other building blocks.

The primary uses of Webmention, peer-to-peer comments, likes, and other responses across web sites, have long presented an interesting challenge with the incorporation and display of external content originally from one site (the Webmention sender), on another site (the Webmention receiver).

There are multiple considerations to keep in mind when displaying such external content.

Two examples of external content are images (e.g. people’s icons or profile images from the author of a comment) and text (e.g. people’s names or the text of their comments).

For external images, rather than displaying them in full fidelity, you may want to compress them into a smaller resolution for how your site displays the profile images of comment authors.

If you accept Webmentions from arbitrary sources, there’s no telling what might show up in author images. You may want to pixelate images from unknown or novel sources into say 3x3 pixel grids of color (or grayscale) averages to make them uniquely identifiable while blurring any undesirable graphics beyond recognition.

For external text, one thing we discovered in recent IndieWeb chat¹ is that someone’s comment (or in this case their name) can contain Unicode directional formatting characters, e.g. for displaying an Arabic or Hebrew name right-to-left. Text with such formatting characters can errantly impact the direction of adjacent text.

Fortunately there is a CSS property, 'unicode-bidi', that can be used to directionally isolate such external text. Thus when you embed text that was parsed from a received Webmention, possibly with formatting characters, you have to wrap it in an HTML element (a span will do if you have not already wrapped it) with that CSS property. E.g.:

<span style="unicode-bidi: isolate;">parsed text here</span>

Though even better would be use of a generic HTML class name indicating the semantic:

<span class="external-text">parsed text here</span>

and then a CSS rule in your style sheet to add that property (and any others you want for external text)

.external-text { unicode-bidi: isolate; }

Previously: https://tantek.com/2023/012/t1/six-years-webmention-w3c


This is post 7 of #100PostsOfIndieWeb. #100Posts #socialWeb #openSocialWeb

← https://tantek.com/2025/004/t1/micro-one-onramp-open-social-web
→ 🔮


Glossary

HTML class name
  https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors
IndieWeb chat
  https://indieweb.org/discuss
pixelate
  https://indieweb.org/pixelated
small pieces, loosely joined
  https://www.smallpieces.com/
Unicode directional formatting characters
  https://en.wikipedia.org/wiki/Bidirectional_text#Explicit_formatting
unicode-bidi CSS property
  https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi  


References

¹ https://chat.indieweb.org/dev/2025-01-05#t1736092889120900

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

Yesterday https://last.fm/ (@lastfm) emailed their year in review reports, which they called #Playback24 and Last.Year.

Kudos to them for waiting until the new year to do so, and breaking with the pattern of services prematurely posting year in review summaries.¹

They’re also available on the web, without requiring a native mobile app to view.

Mine is here: https://www.last.fm/user/tantekc/listening-report/year

You can find yours (if you’re a last.fm user) by going here:
* https://www.last.fm/user/_/listening-report/year

The page title calls it your #YearInMusic, and the URL your #ListeningReport.

It has many interesting elements, from various top listened lists (artist, album, track), to what percent of 2024 listens (which they call scrobbles) were new artists, albums, and tracks.

Their “Top Tags” time chart is quite cool. Fascinating to see the differences in music listening over the seasons and the whole year.

The report has many interactive features, so it will take me some time to figure out how to save, export, and/or republish my listening report on my personal #indieweb site.

For now I used Firefox to save the page as an .html page to my laptop, and was quite impressed with how much of the information was available in that one file. Much more than #Spotify’s #Wrapped.

That’s step 1. Step 2 is figuring out a good way to blog at least some of it.

This is post 5 of #100PostsOfIndieWeb. #100Posts #LastFM #YearInReview

← https://tantek.com/2025/002/t1/indieweb-third-place-community
→ 🔮


Glossary:

scrobble
  https://indieweb.org/scrobble
year in review
  https://indieweb.org/year_in_review


¹ https://tantek.com/2025/001/t2/first-new-year-review-prior

The #indieweb is more than #independence. It’s also a web, of both personal sites and “third place” sites like aggregators, bridges, proxies, directories, indexes, and other community sites.

Broadly speaking, such “third place” sites include places we collectively contribute to, and which license our contributions for free use by others. While open source projects come to mind, perhaps a more obvious example is Wikipedia.

Similarly, the most obvious “third place” in the #IndieWeb community is our community site and wiki https://indieweb.org/ as well as the heterogeneous chat https://chat.indieweb.org/.

We also have many services run by individuals (or small teams) in the community, for the benefit of the community, like:
* @snarfed.org’s https://brid.gy/ and https://fed.brid.gy/
* @aaronparecki.com’s https://webmention.io/ and many others
* @martymcgui.re’s https://xn--sr8hvo.ws/ (IndieWeb Webring)
* @gregorlove.com’s https://indiebookclub.biz/
* @mat.tl’s https://libre.fm/
and I’m sure many more I’m forgetting.

All these services respect your data and your ownership of it. #ownYourData

All these services are swappable. Many (most?) are open source and self-hostable in case you want to run your own personal instance or another shared instance.

The web part of the indieweb complements, connects, and strengthens the indie part.

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

← https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save
→ https://tantek.com/2025/003/t1/lastfm-year-in-review-playback24

When we say #ownYourData we mean whatever data is important to you, like the data services aggregate about you and present back to you. Owning that data means extracting it into a form you can hang onto regardless of what the service does in the future (or disappears), and publishing whatever aspects of it you wish to, on your personal #indieweb site.

Speaking of year in reviews¹ and #Strava Year in Sport in particular, here are my brief notes for how to get the info from it (before it disappears on the 5th!²) and save it locally so you can write and publish your own year in sport.


How to find your Strava: Year in Sport 2024

For 2024, the Strava Year in Sport 2024 is only available on the native mobile app (iOS and presumably Android) and not accessible via the website. Prior years which were available on the website e.g. 2018(.)strava(.)com and 2017(.)strava(.)com are long gone.

From the mobile app home screen, tap the "📋 You" button in the lower right corner.

At the top you should see:

"Play back your 2024" heading with an orange button:

[ See your Year in Sport ]

Tap that button.


Saving Seven Summary Segments

You should immediately see an animation start playing, with seven "segments" (like Instagram stories) at the top, gradually filling-in as progress indicators one at a time.

For each "segment" if you press the screenshot combination of buttons on your mobile (e.g. volume-up + power on iPhone 14), in addition to taking a screenshot it will put you in a "share" screen with one or more videos or still images to share in a carousel format.

For each item in the carousel (if there is more than one)
* tap the item in the carousel
* tap the "[↑] More" button at the bottom.
* scroll down the list of options up a bit
* tap "Save Video [↓]" or "Save Image [↓]" option to store it locally on your mobile.

The seventh "segment" is your overall summary, and shows all your sports combined.

Save it (as an image as noted above), then
* tap the "✏️  Customize" button
* choose an individual sport (e.g. "👟 Run")
* tap "Save changes"
* save that image (as above)
* tap customize again
* choose the next sport (e.g. "🚲  Ride")
* save changes again
* save image again

Strava seemingly only reports summaries of (up to?) two or your sports it appears. Those were Run (presumably all running, street and trail) and Ride for me.


Cleanup Your Screenshots

After having saved all the videos/images for each "segment", you can:
* go back to your mobile’s top level Photos app/stream
* delete the screenshots

You should see all the videos/images you've saved. If anything is missing, go back to the previous steps and save them again, then remove any duplicates as necessary.


Post Your Year In Sport

Go through your saved videos/images, and either post on your own site as-is, or use your mobile’s built-in image OCR to copy the text bits into a plain personal year in sport note summary post on your own site. Or some combination of both if you prefer.

Add other summaries of your activities and sports as you see fit, like:
* info on other sports (beyond running and biking), e.g. yoga, weight-lifting, bouldering etc.
  * total days active (of 366)
  * total distance (if applicable)
  * total elevation (if applicable)
  * total time
* number of races you ran, biked etc. (and finished, if not the same)
* number of miles (or km) you raced (per sport and/or total overall)
* number of (or full set of) awards or trophies you earned at races
* any other stats that you think of that seem interesting to you

For each of these annual numbers, you could also compute (optionally display) the percentage change from 2023, if you happen to have those numbers around.

This is also a good reason to at least total up these numbers for 2024, whether you publish them or not, for figuring out the percentage change in 2025 next year.

When you publish your own year in sport post, might as well re-use the existing #YearInSport hashtag too.

I have already saved all the videos/images from my own Strava Year In Sport, and as I assemble the pieces into my own post, I’ll take more notes, and add to the IndieWeb year in review page³ accordingly.

This post could also be improved with a few screenshots for a few of the steps above. I figured I’d publish my notes first to hopefully help some people sooner (since the Strava Year In Sport will disappear on January 5th as mentioned!). I might upload a few screenshots to the IndieWeb wiki later as well.

#yearInReview #ownYourYearInReview

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

← https://tantek.com/2025/001/t2/first-new-year-review-prior
→ 🔮


Glossary:

hashtag
  https://indieweb.org/hashtag
own your data
  https://indieweb.org/own_your_data


¹ https://tantek.com/2025/001/t2/first-new-year-review-prior
² https://support.strava.com/hc/en-us/articles/22067973274509-Your-Year-in-Sport#h_01HH5VW132BPDTEZJZDHBGJ6KM
³ https://indieweb.org/year_in_review

The first of a new year seems like a good day to assemble, aggregate, summarize and publish various year in review posts for the prior year.

When various online services create a year in review for you many weeks before the end of the year (whether #Spotify #Unwrapped or #Strava #YearInSport), it seems they are short-changing you.

No one asks for an 11 months in review (except HR departments, which is a different problem).

So why do people accept only an ~11 months summary when services provide such a premature “year” in review?

When people say things like “Make every day count” do they not also believe you should “Count every day”?

In this case, 2024 had 366 days. You should count every one of them, and every thing from every one of them.

Rather than “sharing” a premature year in review, request your “year in review” today on the 1st of the year from various services, extract the data you want, fill in any gaps, and post your year in reviews on your own site¹.

#yearInReview #ownYourYearInReview

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

← https://tantek.com/2025/001/t1/15-years-notes-my-site-first
→ https://tantek.com/2025/001/t3/strava-year-in-sport-how-to-get-info-save


Glossary:

year in review
  https://indieweb.org/year_in_review
 

¹ https://indieweb.org/year_in_review#IndieWeb_Examples

Welcome to 2025!

15 years ago today I began posting notes on my own #indieweb site first, and only later on #socialMedia: https://tantek.com/2010/001/t1/declaring-independence-building-it

You can too.

I am once again encouraging you start the year with:
1. Getting a personal domain name
2. Posting on your own site first, then syndicating elsewhere: #POSSE

In 2025 there are even more neighborhoods with other people’s garages¹ to post into. Companies, servers, services, disappear all the time, taking all their posts and permalinks with them to graveyard 404².

This is your annual reminder to embrace #independent ownership of your online self, your creations, and their #longevity:
* Own your domain -> own your online identity
* Own your permalinks -> own your posts

Want help? Just ask: https://chat.indieweb.org/

#ownYourContent #ownYourData

Once again I am restarting a #100PostsOfIndieWeb #100Posts project for the year.

This is post 1.

Previously, previously, previously:
* https://tantek.com/2024/001/t1/restarting-100days-indieweb-gift-calendar
* https://tantek.com/2023/001/t1/own-your-notes
* https://tantek.com/2022/001/t1/12-years-notes-my-site
* https://tantek.com/2020/001/t1/10-years-notes-my-site
* https://tantek.com/2015/002/t1/notes-replies-faves-before-twitter-ownyourdata

← ✨
→ https://tantek.com/2025/001/t2/first-new-year-review-prior


Glossary:

IndieWeb
  https://indieweb.org/
longevity
  https://indieweb.org/longevity
post
  https://indieweb.org/post
permalink
  https://indieweb.org/permalink
personal domain name
  https://indieweb.org/personal-domain
POSSE
  https://indieweb.org/POSSE
syndicate
  https://indieweb.org/syndicate

¹ https://tantek.com/2023/022/t2/own-your-notes-domain-migration
² https://indieweb.org/site-deaths

This is a summary curation of prior posts of mine on why post, what to post, and how to post, as well as some bits I wrote on the #IndieWeb wiki. This post assumes you already have a blog — if you don’t have one and wonder why you should, that’s a different blog post.

If you have a blog and ever feel stuck about why you should post, what to post next, or how to write your post, hopefully this post will help get you unstuck.

These reasons, topics, and techniques help me create, expand, edit, publish, and update more posts, sooner. Choose the ones that resonate for you, ignore the rest, and publish what else works for you on your personal site!


Why Post

There is a whole wiki page on the topic:
* https://indieweb.org/why_post — which could use some gardening

Here are a few specific reasons why you should post:

* Wean yourself off social media. Post to your own site instead of social media. If you already post on social media, into someone else’s garage¹, then you already have reason enough to post. So post on your own site first, and optionally syndicate² to that silo, only if you have friends who still use it to read posts.
* Search everything you write. Do you post long comments or issues on GitHub? Do you post on public mailing lists? Post such things to your own site, so you can more easily search everything you’ve written on a topic. Then post a copy to those external destinations.
* All the reasons to own your data: https://indieweb.org/own_your_data


What to Post

There are so many things to post about! This is obviously highly personal. Here are a few that I use myself:

* Post positive things promptly: https://tantek.com/2018/357/t3
  * … from that day first: https://tantek.com/2018/364/t1
  * … in time order: https://tantek.com/2018/364/t5
* Make and share lists. People like lists
* Post to learn in public, and pass on what you learn


How to Post

I have spent a lot of time thinking about, trying, and iterating on different methods and techniques for starting, expanding, completing, publishing, and updating posts. These are a few of the techniques I use:

* Use a local text editor
* Capture first, edit & publish later: https://tantek.com/2023/365/t1/
* Do something positive (in-person), then post about it: https://tantek.com/2018/002/t1
* Single topic post
* Short and to the point. Edit and remove anything distracting from the main point.
* Quotable post title
* Summary opening paragraph
* Put tangents aside
* Quotable sentences and multi-sentence paragraphs
* Subheadings help cluster related paragraphs
* Use a footer for updates, terminology, previous posts, additional reading, and citations.
  * Move definitions, citations, etc. to the footer unless including them inline either provides little risk of distraction or significantly helps reading flow
  * Use footer sections: Previously, Post Glossary, References, Additional Reading
* Check your references


Each of these points could be its own blog post. There are many more whys, whats, and hows. See more on these pages on the IndieWeb community site:

* https://indieweb.org/why_post
* https://indieweb.org/what_to_post
* https://indieweb.org/how_to_post

Add your own to each, and/or help organize them!


Glossary

mailing list
  https://indieweb.org/mailing_list
own your data
  https://indieweb.org/own_your_data
post footer
  https://indieweb.org/posts#Footer_sections
silo
  https://indieweb.org/silo
social media
  https://indieweb.org/social_media


References

¹ https://tantek.com/2023/001/t1/own-your-notes
² https://indieweb.org/POSSE


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

← https://tantek.com/2024/306/t1/simple-embeds
→ 🔮

Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended!
* 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22).
* 18 introduced themselves² and their personal sites or aspirations for one

Collectively we proposed and facilitated 11 breakout sessions³ on many timely topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends.

Session titles (and hashtags)
* How to #POSSE
* How to make the web queerer / stranger. #queer
* Online presence after our #death
* Threat modeling #threatmodeling
* Non-technical collaboration on the internet. #collab
* Locations and #places check-in
* Writing with images. #imagewriting
* Text authoring UX. #textUX
* #SSR, organizing CSS/JS
* Website design without being a designer. #designfordummies
* Timeline algorithms. #timelines

Etherpad notes from sessions have been archived to the wiki, with session recordings to follow!

Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants.


References
 
¹ https://indieweb.org/2024
² https://indieweb.org/2024/Berlin/Intros
³ https://indieweb.org/2024/Berlin/Schedule#Saturday


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

← https://tantek.com/2024/306/t1/simple-embeds
→ 🔮

Last week at a #HomebrewWebsiteClub session¹ I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots.

I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things:

1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe.
2. A way to “Follow Your Nose” discover that separate embed version
3. A way to discover the original post from the embedded version

For (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice.

For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly².

For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink.


Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service!

https://indieweb.org/embed#IndieWeb_Examples

I have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together.

Got other ideas for simple embeds? Want to implement them on your own site?

Join us in the #indiewebdev chat: https://chat.indieweb.org/dev


UPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages).

A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2


Glossary

embed
  https://indieweb.org/embed
Follow Your Nose
  https://indieweb.org/follow_your_nose
h-entry
  https://microformats.org/wiki/h-entry
oEmbed
  https://indieweb.org/oEmbed
rel-canonical
  https://indieweb.org/rel-canonical
static site hosting
  https://indieweb.org/static_web_hosting


References
 
¹ https://indieweb.org/events/2024-10-23-hwc-europe#embedding
² https://indieweb.org/rel-embed


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

← https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug
→ 🔮

No I did not block you on the #fediverse / #Mastodon / #Misskey etc.

If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below).

No it’s absolutely not your fault, you did nothing wrong.

We need a variant of Hanlon’s Razor¹ like:

“Never attribute to malice that which is adequately explained by a software bug.”

Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!

Also no worries if you ever unfollow/refollow for any reason. I mean that.

I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.

Bug details:

This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!

The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴.

Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).

Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.

Bugs happen, yes even in production code, so please do not post/send any hate.

I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter.

This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check).

To be clear, I’m still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services.

All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first.

References:

¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor
² https://github.com/snarfed/bridgy-fed/issues/1379
³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be
⁴ https://chat.indieweb.org/dev/2024-09-22#t1727028174623700

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

← https://tantek.com/2024/285/t1/io-domain-suggested-steps
→ https://tantek.com/2024/306/t1/simple-embeds

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