#microformats — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #microformats, aggregated by home.social.
-
I spent the weekend adding a bunch of microformat classes to my blog and registering it to https://webmention.io/.
I have no idea if I added the microformats correctly. They seem to be parsed fine, but I'm not sure I'm using them right "semantically". If anybody wants to check it out (https://sergiswriting.com) it is greatly appreciated!
I guess next weekend I'll have to start adding some JS (gasp!) to display comments and other stuff.
-
I spent the weekend adding a bunch of microformat classes to my blog and registering it to https://webmention.io/.
I have no idea if I added the microformats correctly. They seem to be parsed fine, but I'm not sure I'm using them right "semantically". If anybody wants to check it out (https://sergiswriting.com) it is greatly appreciated!
I guess next weekend I'll have to start adding some JS (gasp!) to display comments and other stuff.
-
I spent the weekend adding a bunch of microformat classes to my blog and registering it to https://webmention.io/.
I have no idea if I added the microformats correctly. They seem to be parsed fine, but I'm not sure I'm using them right "semantically". If anybody wants to check it out (https://sergiswriting.com) it is greatly appreciated!
I guess next weekend I'll have to start adding some JS (gasp!) to display comments and other stuff.
-
I spent the weekend adding a bunch of microformat classes to my blog and registering it to https://webmention.io/.
I have no idea if I added the microformats correctly. They seem to be parsed fine, but I'm not sure I'm using them right "semantically". If anybody wants to check it out (https://sergiswriting.com) it is greatly appreciated!
I guess next weekend I'll have to start adding some JS (gasp!) to display comments and other stuff.
-
I spent the weekend adding a bunch of microformat classes to my blog and registering it to https://webmention.io/.
I have no idea if I added the microformats correctly. They seem to be parsed fine, but I'm not sure I'm using them right "semantically". If anybody wants to check it out (https://sergiswriting.com) it is greatly appreciated!
I guess next weekend I'll have to start adding some JS (gasp!) to display comments and other stuff.
-
After Madblog, how many of you would like #ActivityPub and #Indieweb support to come to GPSTracker too?
This is an idea that I’ve been flirting with for a while.
Like many Millennials, 10-15 years ago I was into the Foursquare-mania. It was the age where pubs would offer discount to their Foursquare mayor and where people used to share their Foursquare stats and compete on how many badges they had collected.
Then Foursquare decided to pivot its platform towards the business-side instead, the check-in app was spun off into Swarm, it gradually lost users but it gained trackers, and by now I think only 1-2 of my contacts (out of >100 in the golden age) still use it.
By now I don’t think anyone has filled that gap; there isn’t any social media built around networks that share and recommend their check-ins.
#GPSTracker already supports a lot of tracking, timeline and check-in features, synchronization of geo events with mobile devices, and even stats with arbitrary aggregations (by country, time range, city, region etc.). Plus some features that Foursquare never implemented (like searching for checkins on the timeline by simply selecting an area on the map).
#Microformats already support location tags through the
h-adrclass, although they are rarely used. Both #Webmentions and ActivityPub could send check-in activities as permalinks to pages with those tags. And the #OpenStreetMap APIs could do the heavylifting of retrieving POIs in in a certain lat/long box.The only hurdle would be implementing the protocols under the hood, as both the Webmentions and Pubby libraries are in #Python while #GPSTracker is in #Typescript. But it could be a good chance to start writing multi-language bindings for those libraries.
Let me know if it’s something that you would use, or even self-host, and if you know if there’s anything in the Fediverse that already fills this niche.
-
After Madblog, how many of you would like #ActivityPub and #Indieweb support to come to GPSTracker too?
This is an idea that I’ve been flirting with for a while.
Like many Millennials, 10-15 years ago I was into the Foursquare-mania. It was the age where pubs would offer discount to their Foursquare mayor and where people used to share their Foursquare stats and compete on how many badges they had collected.
Then Foursquare decided to pivot its platform towards the business-side instead, the check-in app was spun off into Swarm, it gradually lost users but it gained trackers, and by now I think only 1-2 of my contacts (out of >100 in the golden age) still use it.
By now I don’t think anyone has filled that gap; there isn’t any social media built around networks that share and recommend their check-ins.
#GPSTracker already supports a lot of tracking, timeline and check-in features, synchronization of geo events with mobile devices, and even stats with arbitrary aggregations (by country, time range, city, region etc.). Plus some features that Foursquare never implemented (like searching for checkins on the timeline by simply selecting an area on the map).
#Microformats already support location tags through the
h-adrclass, although they are rarely used. Both #Webmentions and ActivityPub could send check-in activities as permalinks to pages with those tags. And the #OpenStreetMap APIs could do the heavylifting of retrieving POIs in in a certain lat/long box.The only hurdle would be implementing the protocols under the hood, as both the Webmentions and Pubby libraries are in #Python while #GPSTracker is in #Typescript. But it could be a good chance to start writing multi-language bindings for those libraries.
Let me know if it’s something that you would use, or even self-host, and if you know if there’s anything in the Fediverse that already fills this niche.
-
After Madblog, how many of you would like #ActivityPub and #Indieweb support to come to GPSTracker too?
This is an idea that I’ve been flirting with for a while.
Like many Millennials, 10-15 years ago I was into the Foursquare-mania. It was the age where pubs would offer discount to their Foursquare mayor and where people used to share their Foursquare stats and compete on how many badges they had collected.
Then Foursquare decided to pivot its platform towards the business-side instead, the check-in app was spun off into Swarm, it gradually lost users but it gained trackers, and by now I think only 1-2 of my contacts (out of >100 in the golden age) still use it.
By now I don’t think anyone has filled that gap; there isn’t any social media built around networks that share and recommend their check-ins.
#GPSTracker already supports a lot of tracking, timeline and check-in features, synchronization of geo events with mobile devices, and even stats with arbitrary aggregations (by country, time range, city, region etc.). Plus some features that Foursquare never implemented (like searching for checkins on the timeline by simply selecting an area on the map).
#Microformats already support location tags through the
h-adrclass, although they are rarely used. Both #Webmentions and ActivityPub could send check-in activities as permalinks to pages with those tags. And the #OpenStreetMap APIs could do the heavylifting of retrieving POIs in in a certain lat/long box.The only hurdle would be implementing the protocols under the hood, as both the Webmentions and Pubby libraries are in #Python while #GPSTracker is in #Typescript. But it could be a good chance to start writing multi-language bindings for those libraries.
Let me know if it’s something that you would use, or even self-host, and if you know if there’s anything in the Fediverse that already fills this niche.
-
After Madblog, how many of you would like #ActivityPub and #Indieweb support to come to GPSTracker too?
This is an idea that I’ve been flirting with for a while.
Like many Millennials, 10-15 years ago I was into the Foursquare-mania. It was the age where pubs would offer discount to their Foursquare mayor and where people used to share their Foursquare stats and compete on how many badges they had collected.
Then Foursquare decided to pivot its platform towards the business-side instead, the check-in app was spun off into Swarm, it gradually lost users but it gained trackers, and by now I think only 1-2 of my contacts (out of >100 in the golden age) still use it.
By now I don’t think anyone has filled that gap; there isn’t any social media built around networks that share and recommend their check-ins.
#GPSTracker already supports a lot of tracking, timeline and check-in features, synchronization of geo events with mobile devices, and even stats with arbitrary aggregations (by country, time range, city, region etc.). Plus some features that Foursquare never implemented (like searching for checkins on the timeline by simply selecting an area on the map).
#Microformats already support location tags through the
h-adrclass, although they are rarely used. Both #Webmentions and ActivityPub could send check-in activities as permalinks to pages with those tags. And the #OpenStreetMap APIs could do the heavylifting of retrieving POIs in in a certain lat/long box.The only hurdle would be implementing the protocols under the hood, as both the Webmentions and Pubby libraries are in #Python while #GPSTracker is in #Typescript. But it could be a good chance to start writing multi-language bindings for those libraries.
Let me know if it’s something that you would use, or even self-host, and if you know if there’s anything in the Fediverse that already fills this niche.
-
After Madblog, how many of you would like #ActivityPub and #Indieweb support to come to GPSTracker too?
This is an idea that I’ve been flirting with for a while.
Like many Millennials, 10-15 years ago I was into the Foursquare-mania. It was the age where pubs would offer discount to their Foursquare mayor and where people used to share their Foursquare stats and compete on how many badges they had collected.
Then Foursquare decided to pivot its platform towards the business-side instead, the check-in app was spun off into Swarm, it gradually lost users but it gained trackers, and by now I think only 1-2 of my contacts (out of >100 in the golden age) still use it.
By now I don’t think anyone has filled that gap; there isn’t any social media built around networks that share and recommend their check-ins.
#GPSTracker already supports a lot of tracking, timeline and check-in features, synchronization of geo events with mobile devices, and even stats with arbitrary aggregations (by country, time range, city, region etc.). Plus some features that Foursquare never implemented (like searching for checkins on the timeline by simply selecting an area on the map).
#Microformats already support location tags through the
h-adrclass, although they are rarely used. Both #Webmentions and ActivityPub could send check-in activities as permalinks to pages with those tags. And the #OpenStreetMap APIs could do the heavylifting of retrieving POIs in in a certain lat/long box.The only hurdle would be implementing the protocols under the hood, as both the Webmentions and Pubby libraries are in #Python while #GPSTracker is in #Typescript. But it could be a good chance to start writing multi-language bindings for those libraries.
Let me know if it’s something that you would use, or even self-host, and if you know if there’s anything in the Fediverse that already fills this niche.
-
I was hard at work this morning installing microformats onto my pureblog site. I still need to do the h-feeds, and I'm yet to come up with a way of doing tags given the way they are produced.
🔖 #indieweb #microformats #pureblog
https://prry.uk/2026-03-17-note -
I was hard at work this morning installing microformats onto my pureblog site. I still need to do the h-feeds, and I'm yet to come up with a way of doing tags given the way they are produced.
🔖 #indieweb #microformats #pureblog
https://prry.uk/2026-03-17-note -
I was hard at work this morning installing microformats onto my pureblog site. I still need to do the h-feeds, and I'm yet to come up with a way of doing tags given the way they are produced.
🔖 #indieweb #microformats #pureblog
https://prry.uk/2026-03-17-note -
I was hard at work this morning installing microformats onto my pureblog site. I still need to do the h-feeds, and I'm yet to come up with a way of doing tags given the way they are produced.
🔖 #indieweb #microformats #pureblog
https://prry.uk/2026-03-17-note -
I was hard at work this morning installing microformats onto my pureblog site. I still need to do the h-feeds, and I'm yet to come up with a way of doing tags given the way they are produced.
🔖 #indieweb #microformats #pureblog
https://prry.uk/2026-03-17-note -
Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.
I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.
Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?
I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.
-
Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.
I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.
Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?
I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.
-
Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.
I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.
Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?
I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.
-
Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.
I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.
Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?
I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.
-
Now that I have self-hosted Forgejo actions building this blog and transferring it to the host, almost everything is great. The one pebble in the shoe of my transition has been the tags.
I refactored them recently to take out the spaces and wordcase them in both views and pages to make it more friendly to pushing to the fediverse. The only problem with that is that in the process of Bridge Fed ... bridging to the fed all the tags would get congolomerated into one great big concatenated mess. I have been lamenting this.
Tonight I really dug down into my Eleventy templates. I realized that the "p-category" class was assigned to a div and that div wrapped all the tags. It was not being assigned one by one but only one was assigned and it encompassed all of them. So maybe garbage in garbage out?
I wrapped each individual tag with a span and gave each a "p-category" class. This is the first post being pushed since that change. If you see this on Mastodon or other fediverse clients and it has a bunch of individual tags, then succcess. If not, then I guess I will just start pulling my hair out.
-
I would use #microformats on my blog, but they're distressingly confusing
-
-
Is anyone still using #microformats or h-entry tags anymore?
-
Is anyone still using #microformats or h-entry tags anymore?
-
Is anyone still using #microformats or h-entry tags anymore?
-
Is anyone still using #microformats or h-entry tags anymore?
-
Slowly moving past the MVP phase. Replies now work in my AP implementation.
I have to work on the rendering, but you can see the replies as part of the thread since I added
inReplyToproperty to notes. -
Slowly moving past the MVP phase. Replies now work in my AP implementation.
I have to work on the rendering, but you can see the replies as part of the thread since I added
inReplyToproperty to notes. -
Slowly moving past the MVP phase. Replies now work in my AP implementation.
I have to work on the rendering, but you can see the replies as part of the thread since I added
inReplyToproperty to notes. -
Slowly moving past the MVP phase. Replies now work in my AP implementation.
I have to work on the rendering, but you can see the replies as part of the thread since I added
inReplyToproperty to notes. -
Slowly moving past the MVP phase. Replies now work in my AP implementation.
I have to work on the rendering, but you can see the replies as part of the thread since I added
inReplyToproperty to notes. -
Have a look at how my home-made rss-reader sees your website by appending your url to villepreux.net/lab/metadata/?url=xxxxxxxxx
Example with the excellent David Bushell @db website: https://villepreux.net/lab/metadata/?url=dbushell.comThe rss-reader in question: https://villepreux.net/web-feed
-
Have a look at how my home-made rss-reader sees your website by appending your url to villepreux.net/lab/metadata/?url=xxxxxxxxx
Example with the excellent David Bushell @db website: https://villepreux.net/lab/metadata/?url=dbushell.comThe rss-reader in question: https://villepreux.net/web-feed
-
Have a look at how my home-made rss-reader sees your website by appending your url to villepreux.net/lab/metadata/?url=xxxxxxxxx
Example with the excellent David Bushell @db website: https://villepreux.net/lab/metadata/?url=dbushell.comThe rss-reader in question: https://villepreux.net/web-feed
-
Have a look at how my home-made rss-reader sees your website by appending your url to villepreux.net/lab/metadata/?url=xxxxxxxxx
Example with the excellent David Bushell @db website: https://villepreux.net/lab/metadata/?url=dbushell.comThe rss-reader in question: https://villepreux.net/web-feed
-
Have a look at how my home-made rss-reader sees your website by appending your url to villepreux.net/lab/metadata/?url=xxxxxxxxx
Example with the excellent David Bushell @db website: https://villepreux.net/lab/metadata/?url=dbushell.comThe rss-reader in question: https://villepreux.net/web-feed
-
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 -
Trying to make my site more indieweb friendly, but this microformat business is doing my head in. I already use schema for structured data, which is much easier as the data doesn't rely on a particular markup structure. Like, I don't want to have to print the full permalink url for each blog post, or refactor my post header so that the author profile picture is inside of an element with the `p-author` class. Honestly, I don't want this extra cruft in my markup at all. #indieweb #microformats
-
Trying to make my site more indieweb friendly, but this microformat business is doing my head in. I already use schema for structured data, which is much easier as the data doesn't rely on a particular markup structure. Like, I don't want to have to print the full permalink url for each blog post, or refactor my post header so that the author profile picture is inside of an element with the `p-author` class. Honestly, I don't want this extra cruft in my markup at all. #indieweb #microformats
-
Trying to make my site more indieweb friendly, but this microformat business is doing my head in. I already use schema for structured data, which is much easier as the data doesn't rely on a particular markup structure. Like, I don't want to have to print the full permalink url for each blog post, or refactor my post header so that the author profile picture is inside of an element with the `p-author` class. Honestly, I don't want this extra cruft in my markup at all. #indieweb #microformats
-
Trying to make my site more indieweb friendly, but this microformat business is doing my head in. I already use schema for structured data, which is much easier as the data doesn't rely on a particular markup structure. Like, I don't want to have to print the full permalink url for each blog post, or refactor my post header so that the author profile picture is inside of an element with the `p-author` class. Honestly, I don't want this extra cruft in my markup at all. #indieweb #microformats
-
Trying to make my site more indieweb friendly, but this microformat business is doing my head in. I already use schema for structured data, which is much easier as the data doesn't rely on a particular markup structure. Like, I don't want to have to print the full permalink url for each blog post, or refactor my post header so that the author profile picture is inside of an element with the `p-author` class. Honestly, I don't want this extra cruft in my markup at all. #indieweb #microformats
-
Discussing implementation of microformats on my bearblog project.
#Article #Bearblog #IndieWeb #MicroformatsUsing Microformats with Bear - https://l.prry.uk/using-microformats-with-bear/
-
Discussing implementation of microformats on my bearblog project.
#Article #Bearblog #IndieWeb #MicroformatsUsing Microformats with Bear - https://l.prry.uk/using-microformats-with-bear/
-
Discussing implementation of microformats on my bearblog project.
#Article #Bearblog #IndieWeb #MicroformatsUsing Microformats with Bear - https://l.prry.uk/using-microformats-with-bear/
-
Discussing implementation of microformats on my bearblog project.
#Article #Bearblog #IndieWeb #MicroformatsUsing Microformats with Bear - https://l.prry.uk/using-microformats-with-bear/