because I forgot to put explicit categories (p-category markup) in the article post.
Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.
{
"type": "entry",
"published": "2023-09-24 18:33-0700",
"url": "https://tantek.com/2023/267/t1/summary-w3c-tpac-2023",
"category": [
"W3C",
"TPAC",
"hashtag",
"Sevilla",
"Seville",
"Spain",
"WICG",
"SocialCG",
"SWICG",
"Fediverse",
"SocialWeb",
"sustainability",
"IndieWeb",
"ActivityPub",
"BridgyFed",
"Mastodon",
"w3cTPAC"
],
"content": {
"text": "I recently wrote a high level summary blog post:\n\nW3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023\n\nhttps://tantek.com/2023/262/b1/w3c-technical-plenary-tpac\n\nof my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.\n\nPosting this note to explicitly #hashtag that article with topics mentioned therein:\n\n#Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub\n\nbecause I forgot to put explicit categories (p-category markup) in the article post.\n\nAdding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I\u2019ll be sure to include category markup before publishing and see if that works.\n\nPost glossary:\n\narticle post\n\u00a0 https://indieweb.org/article\nnote post\n\u00a0 https://indieweb.org/note\np-category\n\u00a0 https://indieweb.org/p-category\ntags\n\u00a0 https://indieweb.org/tags",
"html": "I recently wrote a high level summary blog post:<br /><br />W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023<br /><br /><a href=\"https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac\">https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac</a><br /><br />of my time at the #<span class=\"p-category\">W3C</span> (<a href=\"https://W3.org\">@W3.org</a>, <a href=\"https://w3c.social/@w3c\">@w3c@w3c.social</a>, <a class=\"h-cassis-username\" href=\"https://twitter.com/W3C\">@W3C</a>) #<span class=\"p-category\">TPAC</span> the week before.<br /><br />Posting this note to explicitly #<span class=\"p-category\">hashtag</span> that article with topics mentioned therein:<br /><br />#<span class=\"p-category\">Sevilla</span> #<span class=\"p-category\">Seville</span> #<span class=\"p-category\">Spain</span> #<span class=\"p-category\">WICG</span> #<span class=\"p-category\">SocialCG</span> #<span class=\"p-category\">SWICG</span> #<span class=\"p-category\">Fediverse</span> #<span class=\"p-category\">SocialWeb</span> #<span class=\"p-category\">sustainability</span> #<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">ActivityPub</span><br /><br />because I forgot to put explicit categories (p-category markup) in the article post.<br /><br />Adding that markup after publishing, and then sending an ActivityPub update (via #<span class=\"p-category\">BridgyFed</span>) is apparently not enough for #<span class=\"p-category\">Mastodon</span> to notice that the Update has new tags to display and aggregate on tag pages. In my next #<span class=\"p-category\">w3cTPAC</span> article post I\u2019ll be sure to include category markup before publishing and see if that works.<br /><br />Post glossary:<br /><br />article post<br />\u00a0 <a href=\"https://indieweb.org/article\">https://indieweb.org/article</a><br />note post<br />\u00a0 <a href=\"https://indieweb.org/note\">https://indieweb.org/note</a><br />p-category<br />\u00a0 <a href=\"https://indieweb.org/p-category\">https://indieweb.org/p-category</a><br />tags<br />\u00a0 <a href=\"https://indieweb.org/tags\">https://indieweb.org/tags</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "39003931",
"_source": "2460"
}
I spent most of the day working on Meetable, my event listing website that powers https://events.indieweb.org and a few other sites. Some great new features and bugfixes!
• Added passkeys for admin login • "Live Now" indicator is now aware of the actual Zoom meeting status • Zoom meeting updates if event time changes • Added tooltip to show local time on event pages
{
"type": "entry",
"published": "2023-09-23T19:24:00-07:00",
"url": "https://aaronparecki.com/2023/09/23/11/meetable",
"category": [
"meetable",
"events"
],
"content": {
"text": "I spent most of the day working on Meetable, my event listing website that powers https://events.indieweb.org and a few other sites. Some great new features and bugfixes! \n\n\u2022 Added passkeys for admin login \n\u2022 \"Live Now\" indicator is now aware of the actual Zoom meeting status \n\u2022 Zoom meeting updates if event time changes \n\u2022 Added tooltip to show local time on event pages",
"html": "I spent most of the day working on Meetable, my event listing website that powers <a href=\"https://events.indieweb.org\"><span>https://</span>events.indieweb.org</a> and a few other sites. Some great new features and bugfixes! <br /><br />\u2022 Added passkeys for admin login <br />\u2022 \"Live Now\" indicator is now aware of the actual Zoom meeting status <br />\u2022 Zoom meeting updates if event time changes <br />\u2022 Added tooltip to show local time on event pages"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "38996667",
"_source": "16"
}
Now that @1Password launched passkey support *and* it's integrated into iOS 17 with the 1Password app, I feel like I can finally actually take the plunge and set up passkeys everywhere!
No more passwords! and the login UX is so much better too!
{
"type": "entry",
"published": "2023-09-23T18:48:24-07:00",
"url": "https://aaronparecki.com/2023/09/23/9/passkeys",
"category": [
"security",
"passkey",
"password"
],
"content": {
"text": "Now that @1Password launched passkey support *and* it's integrated into iOS 17 with the 1Password app, I feel like I can finally actually take the plunge and set up passkeys everywhere! \n\nNo more passwords! and the login UX is so much better too!",
"html": "Now that <a href=\"https://twitter.com/1Password\">@1Password</a> launched passkey support *and* it's integrated into iOS 17 with the 1Password app, I feel like I can finally actually take the plunge and set up passkeys everywhere! <br /><br />No more passwords! and the login UX is so much better too!"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"post-type": "note",
"_id": "38996465",
"_source": "16"
}
{
"type": "entry",
"published": "2023-09-23T13:18:53-0400",
"url": "https://martymcgui.re/2023/09/23/this-map-is-made-for-you-and-me/",
"category": [
"site-update",
"maps",
"stadia",
"stamen",
"toner",
"check",
"checkins",
"swarm",
"foursquare",
"IndieWeb"
],
"name": "This map is made for you and me",
"content": {
"text": "Well, it's a rainy day and a good day for someday projects. Also, oops, here's a post about a tiny site update that accidentally sprawled into a post about 6 (or 14) years of my relationships with Foursquare and the whole idea of sharing \"check in\"s (not \ud83d\udc14s).\nOh no it's backstory time\nIn 2009 I was living in Pittsburgh, working as a research programmer at Carnegie Mellon, a proud member of the newly formed HackPGH hacker space, starting down the slippery slope of joining the 3D printing industry, and basically excited about technology and the future. It was in this context that I vaguely remember being talked into joining Foursquare, so friends and I could keep up with one another at our usual haunts around town.\nI'm not sure how much serendipity it really enabled, but checkins did lead to conversations and a nice general awareness of what folks in my social network were up to. Oh, and some competition for points and mayorships, of course, thanks to gamification.\nI made use of checkins pretty regularly, in town and on trips, across a move to Baltimore and starting a new job in the aforementioned 3D printing industry. And then in 2012 I stopped. I don't 100% remember making this a conscious choice, but I do recall that most of my friends who used the app regularly were far away in Pittsburgh, privacy and surveillance capital concerns were on the rise, and \u2014 heck \u2014 I probably changed phones or something and just plain didn't install it.\nFast-forward about 5 years to 2017 and I'm all-in on the IndieWeb community. After learning about it in ~2015, putting together my first blog since ~2003, and attending my first IndieWebCamp in NYC in 2016, I found myself in Portland, OR for the IndieWeb Summit.\nAnd goodness these folks liked checking in with Foursquare (now Swarm)! They were tagging one another in the app, maximizing points with photos, just documenting the heck out of where we were going and what we were doing.\nAaron Parecki, one of the co-founders of IndieWeb, had set up a service called OwnYourSwarm which you could set up to watch your Swarm account for new checkins, at which point it would send 'em off your your website. While I probably should have been paying more attention to the excellent IndieWeb Summit discussions, I hacked up some bits of my site to understand posts from OwnYourSwarm and posted my first checkin to my own site.\nOwnYourSwarm is still around and working well, despite some speedbumps over the years from Swarm API changes. Thanks, Aaron!\nOkay, but something about maps?\nSpeaking of Aaron, I was jealous of how good his checkin posts looked. Like this example checking in for IndieWeb Summit day 1. I specifically liked the little map at the top and wanted one for myself.\nScreenshot of the top of Aaron's post checking in at Mozilla Portland. A small map in wide aspect ratio has a blue pin indicating the location among the streets in downtown Portland.So, uh, almost a year later, I was inspired by this really great post on privacy-preserving, self-hosted maps by Sebastian Greger, to finally put together my own setup and promptly never blogged about it. I know this because I bookmarked his post and found the Git commit from June 25th, 2018 where I switch from Javascript-powered Mapbox (which I don't really recall setting up) to my own static map setup.\n(Would we be shocked to discover that, on June 25th, 2018, I was checking in for that year's IndieWeb Summit? We should not be.)\nBlack and white map image with a purple push pin at the corner of SW 2nd Ave and SW Pine St in downtown Portland, OR. Map tiles provided by Stamen, contributions by OpenStreetMap contributors, etc.The closest thing to a write-up on my own site I was able to find was this comment I had made on a great post by Jeremy Keith about a map project of his own:\n\n I use https://github.com/dfacts/staticmaplite on my site. It\u2019s no longer under development but, as long as you point it at a working tilemap server, it works fine! I switched out the URLs hardcoded in the PHP file for the Stamen \u201cToner\u201d tiles, using the tile server URL pattern on the Open Street Map wiki.\n\nstaticMapLite is a little PHP service you can self-host that creates plain old map images, of the locations you want at the sizes you want with overlays and pins if you want them, and caches them forever. It does so the same way as pretty much all map tools on the web: by asking bigger servers (called \"tile servers\", or \"raster tile servers\") for larger sets of \"tile\" images, then slicing up those tiles to make the image you want. The project is archived and hasn't seen updates since 2018, but it works fine! Raster tile server technology hasn't changed much since then.\n\n Assuming, that is, that you have a raster tile server! You can run your own, but they require a ton of storage for all the map data, need regular updates, and generally are considered a pain to maintain.\n \n\nWhen I set this up I remember looking over the list of raster tile servers on the Open Street Map wiki to find one that was free, didn't require signup, and produced map images that were aesthetic and minimal. With its dithered black and white look, Stamen's Toner definitely fit the bill. Stamen, those data visualization folks, right? I don't really remember thinking too hard about it!\nWe were promised a site update\nOkay, okay! As it turns out Stamen also didn't like being maintainers of map tile servers. Especially when so many folks were freeloading on them!\n\n To that end, this year Stamen announced a partnership with Stadia to begin hosting Stamen's many tile designs with Stadia, a map service with a business model, instead. The tile images remain shareable under their Creative Commons attribution license, I can keep all my existing cached images, and so on. They're offering a free tier of up to 200,000 tile images a month which is welllll below what I'll need for my few static images on rare times that I make checkin posts.\n \n\nStadia has their own page about the Stamen maps project, and a fairly straightforward migration guide to using Stamen map tiles served by Stadia tile servers.\nSo, I've updated my deployment of staticmaplite to pull tiles from Stadia. Steps largely followed their migration guide:\nMake a (free) Stadia account.\n Generate an API key.\n Update staticmap.php to replace the \"a.tile.stamen.com\" map URL with \"https://tiles.stadiamaps.com/tiles/stamen_toner/{Z}/{X}/{Y}.png?api_key=MY_API_KEY_HERE\".\n \n Update my post template with the new attribution requirements.\n \n\nI went hunting around the map cache on my server to find the most recent map image and delete the cached image so it would re-generate. It took me a couple of tries to get my tiles.stadiamaps.com URL correct, as Stadia's example used lowercase placeholders like \"{x}\" while staticmapslite requires uppercase like \"{X}\". Also, Stadia supports an optional \"{r}\" value \u2014 either an empty string \"\" or \"@2x\" if you want double-resolution images for Retina displays \u2014 that staticmaplite doesn't understand (and that I opted not to use).\nAnyway, here's that most recent checkin, using the new map image.\nMap image of Brooklyn, NY with a purple pin near the southeast corner of 5th Ave and 3rd St. Map tile courtesy Stadia and Stamen and OpenStreetMap contributors.Looks pretty much the same, which is the point!\nSo.\n\n Was this a site update? Perhaps one long overdue from 2017 or 2018? Or is this a post about a very specific kind of admin tax? Or something else? I'm interested in your thoughts!",
"html": "<p>Well, it's a rainy day and a good day for <a href=\"https://sebastiangreger.net/2018/05/self-hosting-maps-control-privacy-ux/\">someday projects</a>. Also, oops, here's a post about a tiny site update that accidentally sprawled into a post about 6 (or 14) years of my relationships with Foursquare and the whole idea of sharing \"<a href=\"https://indieweb.org/checkin\">check in</a>\"s (not <a href=\"https://indieweb.org/chicken\">\ud83d\udc14</a>s).</p>\n<h2>Oh no it's backstory time</h2>\n<p>In 2009 I was living in Pittsburgh, working as a research programmer at Carnegie Mellon, a proud member of the newly formed <a href=\"https://hackpgh.org/\">HackPGH</a> hacker space, <a href=\"https://www.flickr.com/photos/schmarty/albums/72157622010516117\">starting down the slippery slope of joining the 3D printing industry</a>, and basically excited about technology and the future. It was in this context that I<i> vaguely</i> remember being talked into joining Foursquare, so friends and I could keep up with one another at our usual haunts around town.</p>\n<p>I'm not sure how much serendipity it really enabled, but checkins did lead to conversations and a nice general awareness of what folks in my social network were up to. Oh, and some competition for points and mayorships, of course, thanks to gamification.</p>\n<p>I made use of checkins pretty regularly, in town and on trips, across a move to Baltimore and starting a new job in the aforementioned 3D printing industry. And then in 2012 I stopped. I don't 100% remember making this a conscious choice, but I do recall that most of my friends who used the app regularly were far away in Pittsburgh, privacy and surveillance capital concerns were on the rise, and \u2014 heck \u2014 I probably changed phones or something and just plain didn't install it.</p>\n<p>Fast-forward about 5 years to 2017 and I'm all-in on the <a href=\"https://indieweb.org/\">IndieWeb</a> community. After learning about it in ~2015, putting together my first blog since ~2003, and attending my first <a href=\"https://martymcgui.re/2016/08/31/indiewebcamp-nyc2-wrap-up/\">IndieWebCamp in NYC in 2016</a>, I found myself in Portland, OR for the IndieWeb Summit.</p>\n<p>And goodness these folks liked checking in with Foursquare (now Swarm)! They were tagging one another in the app, maximizing points with photos, just documenting the heck out of where we were going and what we were doing.</p>\n<p><a href=\"https://aaronparecki.com/\">Aaron Parecki</a>, one of the co-founders of IndieWeb, had set up a service called <a href=\"https://ownyourswarm.p3k.io/\">OwnYourSwarm</a> which you could set up to watch your Swarm account for new checkins, at which point it would send 'em off your your website. While I probably should have been paying more attention to the excellent IndieWeb Summit discussions, I hacked up some bits of my site to understand posts from OwnYourSwarm and posted <a href=\"https://martymcgui.re/2017/06/23/132159/\">my first checkin to my own site</a>.</p>\n<p>OwnYourSwarm is still around and working well, despite some speedbumps over the years from Swarm API changes. Thanks, Aaron!</p>\n<h2>Okay, but something about maps?</h2>\n<p>Speaking of Aaron, I was jealous of how good his checkin posts looked. Like <a href=\"https://aaronparecki.com/2017/06/24/10/\">this example checking in for IndieWeb Summit day 1</a>. I specifically liked the little map at the top and wanted one for myself.</p>\n<img src=\"https://media.martymcgui.re/c5/55/7c/f2/f44baa763afe90113429def0a443796eaed9b0e712f609985a0cfcaf.png\" alt=\"\" />Screenshot of the top of Aaron's post checking in at Mozilla Portland. A small map in wide aspect ratio has a blue pin indicating the location among the streets in downtown Portland.<p>So, uh, almost a year later, I was inspired by this <a href=\"https://sebastiangreger.net/2018/05/self-hosting-maps-control-privacy-ux/\">really great post on privacy-preserving, self-hosted maps by Sebastian Greger</a>, to finally put together my own setup and promptly <i>never blogged about it</i>. I know this because I <a href=\"https://martymcgui.re/2018/05/30/self-hosting-maps-taking-control-over-ux-and-users-privacy-/-sebastian-greger/\">bookmarked his post</a> and found the Git commit from June 25th, 2018 where I switch from Javascript-powered Mapbox (which I don't really recall setting up) to my own static map setup.</p>\n<p>(Would we be shocked to discover that, <a href=\"https://martymcgui.re/2018/06/25/201057/\">on June 25th, 2018, I was checking in for that year's IndieWeb Summit</a>? We should not be.)</p>\n<img src=\"https://media.martymcgui.re/19/f6/9e/ad/2fe6ae7a6b08b85f8837b2620448d0a6b3cbd2d3071842705dff803b.png\" alt=\"\" />Black and white map image with a purple push pin at the corner of SW 2nd Ave and SW Pine St in downtown Portland, OR. Map tiles provided by Stamen, contributions by OpenStreetMap contributors, etc.<p>The closest thing to a write-up on my own site I was able to find was <a href=\"https://martymcgui.re/2019/10/31/164228/\">this comment I had made</a> on a <a href=\"https://adactio.com/journal/16058\">great post by Jeremy Keith about a map project of his own</a>:</p>\n<blockquote>\n <p>I use <a href=\"https://github.com/dfacts/staticmaplite\">https://github.com/dfacts/staticmaplite</a> on my site. It\u2019s no longer under development but, as long as you point it at a working tilemap server, it works fine! I switched out the URLs hardcoded in the PHP file for the Stamen \u201cToner\u201d tiles, using the tile server URL pattern on the <a href=\"https://wiki.openstreetmap.org/wiki/Tile_servers\">Open Street Map wiki</a>.</p>\n</blockquote>\n<p><a href=\"https://github.com/dfacts/staticmaplite\">staticMapLite</a> is a little PHP service you can self-host that creates plain old map images, of the locations you want at the sizes you want with overlays and pins if you want them, and caches them forever. It does so the same way as pretty much all map tools on the web: by asking bigger servers (called \"tile servers\", or \"raster tile servers\") for larger sets of \"tile\" images, then slicing up those tiles to make the image you want. The project is archived and hasn't seen updates since 2018, but it works fine! Raster tile server technology hasn't changed much since then.</p>\n<p>\n Assuming, that is, that you have a raster tile server! You <i>can</i> run your own, but they require a ton of storage for all the map data, need regular updates, and generally are considered a pain to maintain.\n <br /></p>\n<p>When I set this up I remember looking over the list of <a href=\"https://wiki.openstreetmap.org/wiki/Raster_tile_providers\">raster tile servers on the Open Street Map wiki</a> to find one that was free, didn't require signup, and produced map images that were aesthetic and minimal. With its dithered black and white look, Stamen's Toner definitely fit the bill. <a href=\"https://stamen.com/\">Stamen</a>, those data visualization folks, right? I don't really remember thinking too hard about it!</p>\n<h2>We were promised a site update</h2>\n<p>Okay, okay! As it turns out Stamen also didn't like being maintainers of map tile servers. Especially when so many folks were freeloading on them!</p>\n<p>\n To that end, this year <a href=\"https://maps.stamen.com/stadia-partnership/\">Stamen announced a partnership with Stadia</a> to begin hosting Stamen's many tile designs with Stadia, a map service with a business model, instead. The tile images remain shareable under their Creative Commons attribution license, I can keep all my existing cached images, and so on. They're offering a free tier of up to 200,000 tile images a month which is <i>welllll</i> below what I'll need for my few static images on rare times that I make checkin posts.\n <br /></p>\n<p><a href=\"https://stadiamaps.com/stamen/\">Stadia has their own page about the Stamen maps project</a>, and a fairly straightforward migration guide to using <a href=\"https://docs.stadiamaps.com/guides/migrating-from-stamen-map-tiles/#url-based-migration-steps\">Stamen map tiles served by Stadia tile servers</a>.</p>\n<p>So, I've updated my deployment of staticmaplite to pull tiles from Stadia. Steps largely followed their migration guide:</p>\n<ul><li>Make a (free) Stadia account.</li>\n <li>Generate an API key.</li>\n <li>Update staticmap.php to replace the \"a.tile.stamen.com\" map URL with \"https://tiles.stadiamaps.com/tiles/stamen_toner/{Z}/{X}/{Y}.png?api_key=MY_API_KEY_HERE\".</li>\n <li>\n Update my post template with the new attribution requirements.\n <br /></li>\n</ul><p>I went hunting around the map cache on my server to find the most recent map image and delete the cached image so it would re-generate. It took me a couple of tries to get my tiles.stadiamaps.com URL correct, as Stadia's example used lowercase placeholders like \"{x}\" while staticmapslite requires uppercase like \"{X}\". Also, Stadia supports an optional \"{r}\" value \u2014 either an empty string \"\" or \"@2x\" if you want double-resolution images for Retina displays \u2014 that staticmaplite doesn't understand (and that I opted not to use).</p>\n<p>Anyway, here's <a href=\"https://martymcgui.re/2023/08/25/213212/\">that most recent checkin, using the new map image</a>.</p>\n<img src=\"https://media.martymcgui.re/46/36/d6/8e/0f040fd8e3220600c696c13d65ef7b67829dc1754a1e6f6c732e3fc0.png\" alt=\"\" />Map image of Brooklyn, NY with a purple pin near the southeast corner of 5th Ave and 3rd St. Map tile courtesy Stadia and Stamen and OpenStreetMap contributors.<p>Looks pretty much the same, which is the point!</p>\n<p>So.</p>\n<p>\n <i>Was</i> this a site update? Perhaps one long overdue from 2017 or 2018? Or is this a post about a very specific kind of <a href=\"https://indieweb.org/admintax\">admin tax</a>? Or something else? I'm interested in your thoughts!\n <br /></p>"
},
"author": {
"type": "card",
"name": "Marty McGuire",
"url": "https://martymcgui.re/",
"photo": "https://martymcgui.re/images/logo.jpg"
},
"post-type": "article",
"_id": "38993697",
"_source": "175"
}
{
"type": "entry",
"author": {
"name": null,
"url": "https://herestomwiththeweather.com/",
"photo": null
},
"url": "https://herestomwiththeweather.com/2023/09/22/webfinger-expectations/",
"published": "2023-09-22T14:34:49+00:00",
"content": {
"html": "<p>In an <a href=\"https://herestomwiththeweather.com/2023/01/08/correction-check_webfinger/\">earlier post</a> this year, I documented a problem I found and this post attempts to describe the issue a little more clearly and a plan to work around it.</p>\n\n<p>I have chosen <a href=\"https://herestomwiththeweather.com/.well-known/webfinger/?acct=tom@herestomwiththeweather.com\">@tom@herestomwiththeweather.com</a> as my personal identifier on the fediverse. If I decide I want to move from one activitypub server (e.g. Mastodon) to another, I would like to keep my same personal identifier. It follows that my activitypub server should not have to reside at the same domain as my personal identifier. I should be able to swap one activitypub server for another at any time. Certainly, I don\u2019t expect every activitypub server to support this but I\u2019m not obligated to use one that does not.</p>\n\n<p>Unfortunately, although my domain returns the chosen personal identifier in the subject field, because the JRD document returns a rel=self link to <a href=\"https://mastodon.social/users/herestomwiththeweather\">a Mastodon server</a> to provide my <a href=\"https://www.w3.org/TR/activitypub/#actor-objects\">actor document</a>, the mastodon servers do not seem to use my chosen personal identifier for anything other than resolving a search for my personal identifier to the mastodon profile to which it is currently associated. From that point forward, a completely new personal identifier with the domain component set to the domain of the mastodon server is used. In other words, a personal identifier that has been chosen for me by someone else is kept in a particular server\u2019s database table. I can later choose a different activitypub server but I may not be able to keep my preferred username because it may already be taken on the new server. In any case, choosing a new server means my personal identifier within the mastodon network also changes. Unless\u2026I don\u2019t use a mastodon server in the first place. Then, my personal identifier will be used as I would like by the mastodon network and I can potentially swap activitypub servers without ever having to change my personal identifier with my own domain.</p>\n\n<p>The two most relevant documents for understanding webfinger as it is currently used seem to be <a href=\"https://datatracker.ietf.org/doc/html/rfc7033\">RFC 7033: WebFinger</a> and <a href=\"https://docs.joinmastodon.org/spec/webfinger/\">Mastodon\u2019s documentation</a> and it is this mastodon documentation (in the section <a href=\"https://docs.joinmastodon.org/spec/webfinger/#mastodons-requirements-for-webfinger\">Mastodon\u2019s requirements for WebFinger</a>) that now describes the behavior (a problem for me) that I documented earlier. The new section explains</p>\n\n<pre><code>if the subject contains a different canonical account URI, then Mastodon will perform an additional Webfinger request for that canonical account URI in order to ensure that this new resource links to the same ActivityPub actor with the same criteria being checked.\n</code></pre>\n\n\n<p>This behavior makes sense if you assume that if you are using a mastodon server, then you inherit a personal identifier tied to that server. This makes validating a webfinger address simple for mastodon so advocating a change in this behavior in mastodon seems like it would be challenging. However, as I mentioned in the earlier post, instead of choosing mastodon as your activitypub server, your personal identifier with your own domain can be accepted by mastodon servers in a desirable way</p>\n\n<pre><code>as long as the fediverse node providing the actor document is smart enough to provide your personal domain in the subject when mastodon makes a webfinger call to it.\n</code></pre>\n\n\n<p>The problem here is that it seems that I would not be able to be \u201ctom\u201d on such an activitypub server if, for instance, tom@example.com was already pointing to that server unless the server could assign me a subdomain, for example.</p>",
"text": "In an earlier post this year, I documented a problem I found and this post attempts to describe the issue a little more clearly and a plan to work around it.\n\nI have chosen @tom@herestomwiththeweather.com as my personal identifier on the fediverse. If I decide I want to move from one activitypub server (e.g. Mastodon) to another, I would like to keep my same personal identifier. It follows that my activitypub server should not have to reside at the same domain as my personal identifier. I should be able to swap one activitypub server for another at any time. Certainly, I don\u2019t expect every activitypub server to support this but I\u2019m not obligated to use one that does not.\n\nUnfortunately, although my domain returns the chosen personal identifier in the subject field, because the JRD document returns a rel=self link to a Mastodon server to provide my actor document, the mastodon servers do not seem to use my chosen personal identifier for anything other than resolving a search for my personal identifier to the mastodon profile to which it is currently associated. From that point forward, a completely new personal identifier with the domain component set to the domain of the mastodon server is used. In other words, a personal identifier that has been chosen for me by someone else is kept in a particular server\u2019s database table. I can later choose a different activitypub server but I may not be able to keep my preferred username because it may already be taken on the new server. In any case, choosing a new server means my personal identifier within the mastodon network also changes. Unless\u2026I don\u2019t use a mastodon server in the first place. Then, my personal identifier will be used as I would like by the mastodon network and I can potentially swap activitypub servers without ever having to change my personal identifier with my own domain.\n\nThe two most relevant documents for understanding webfinger as it is currently used seem to be RFC 7033: WebFinger and Mastodon\u2019s documentation and it is this mastodon documentation (in the section Mastodon\u2019s requirements for WebFinger) that now describes the behavior (a problem for me) that I documented earlier. The new section explains\n\nif the subject contains a different canonical account URI, then Mastodon will perform an additional Webfinger request for that canonical account URI in order to ensure that this new resource links to the same ActivityPub actor with the same criteria being checked.\n\n\n\nThis behavior makes sense if you assume that if you are using a mastodon server, then you inherit a personal identifier tied to that server. This makes validating a webfinger address simple for mastodon so advocating a change in this behavior in mastodon seems like it would be challenging. However, as I mentioned in the earlier post, instead of choosing mastodon as your activitypub server, your personal identifier with your own domain can be accepted by mastodon servers in a desirable way\n\nas long as the fediverse node providing the actor document is smart enough to provide your personal domain in the subject when mastodon makes a webfinger call to it.\n\n\n\nThe problem here is that it seems that I would not be able to be \u201ctom\u201d on such an activitypub server if, for instance, tom@example.com was already pointing to that server unless the server could assign me a subdomain, for example."
},
"name": "Webfinger Expectations",
"post-type": "article",
"_id": "38990681",
"_source": "246"
}
{
"type": "entry",
"published": "2023-09-19 19:58-0700",
"url": "https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac",
"name": "W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023",
"content": {
"text": "Second IRL TPAC since 2019\nAs noted \n last \n year, \nthe \n W3C \nconvened its annual\n TPAC meetings\nin-person from \n 2001-2019 \n(full list). \nAfter a \n couple \nof \n virtual \nTPACs, last year W3C organized its \n first officially hybrid TPAC \nin Vancouver, British Columbia. \nI wrote \n one \n blog post about one session.\nLast week\u2019s second hybrid TPAC, held in Sevilla, Spain, felt very different in a number of positive ways. This post is a summary of impressions and varied types of meetings I participated in, each of which merits its own post.\n\n\nThis year\u2019s W3C TPAC (Technical Plenary and Advisory Committee) meetings felt denser in many ways, packed tighter with more topics, and more active participants. There were so many specific things in specific meetings, new connections, victories, new challenges, that in addition to capturing summary notes, I'm considering writing blog posts about each meeting or session.\n\n\nNearly all of them have public minutes that document both participants, and a good portion of what was discussed. I have my own notes, and combined with recollected details of what was minuted, I have my own observations to share. I encourage everyone who participated at TPAC (whether in-person or remote) to consider either writing a summary blog post about the experience, perhaps highlighting a few things that stood out, or if there were specific technical discussions that advanced something in a positive direction, or challenges blocking progress, those are worth their own blog posts as well.\n\n\n TPAC week 2023 \ntook place from Monday \n 2023-09-11 \n through Friday \n 2023-09-15, \nin \n Sevilla, \n Spain.\n\n\nHere is a summary outline of meetings, sessions, and discussions I participated in. Not listed: conversations at breakfasts, morning & afternoon breaks, lunches, dinners, and of course hallways. Unlinked for now, each of these has a calendar event with description, minutes, almost all of which are public.\n\nMonday\n\nWICG (Web Incubator Community Group)\n\nTuesday\nSocial Web Incubator CG (community group), AKA \n SocialCG or \n SWICG\n\n \nDID WG \n rechartering discussion\n \nAC meeting\n Vision TF\n\n Fediverse meetup\n\nWednesday \u2014 Breakouts day!\nChartering at W3C\n Technical Roadmap at W3C\n SocialWeb Test Suite Discussion\n SocialWeb Data Portability Discussion\n Introducing the Web Sustainability Guidelines (WSGs)\n Report to Members, Hearing from Members\n Technical Plenary reception\n\nThursday\n\nCSS WG, briefly\n Afternoon break: \n Solid \n charter discussions\n\nFriday\nSocial CG planning\n Departing conversations & reflections\n\n\nThose are the sessions & discussions that I found in my notes. \nI also met a lot of new people during meetings, meals, and discussions at breaks. \nAs I write up my notes on specific sessions and their minutes (and hyperlink the above list items), I expect to recall more context and details. If you were at TPAC, I encourage you to write-up your experiences as well, while the thoughts, feelings, and insights are fresh in your mind. By documenting our collective experiences, we can build upon them together.",
"html": "<h2>Second <abbr title=\"in real life\">IRL</abbr> TPAC since 2019</h2>\n<p>As noted \n <a href=\"https://tantek.com/2022/267/b1/w3c-tpac-sustainability-cg-meeting\">last \n year</a>, \nthe \n <abbr title=\"World Wide Web Consortium\">W3C</abbr> \nconvened its annual\n <abbr title=\"Technical Plenary and Advisory Committee\">TPAC</abbr> meetings\nin-person from \n <a href=\"https://www.w3.org/2001/02/allgroupoverview.html\">2001</a>-<a href=\"https://www.w3.org/wiki/TPAC/2019\">2019</a> \n(<a href=\"https://www.w3.org/wiki/TPAC\">full list</a>). \nAfter a \n <a href=\"https://www.w3.org/wiki/TPAC/2020\">couple</a> \nof \n <a href=\"https://www.w3.org/wiki/TPAC/2021\">virtual</a> \nTPACs, last year W3C organized its \n <a href=\"https://www.w3.org/wiki/TPAC/2022\">first officially <em>hybrid</em> TPAC</a> \nin Vancouver, British Columbia. \nI wrote \n <a href=\"https://tantek.com/2022/267/b1/w3c-tpac-sustainability-cg-meeting\">one \n blog post about one session</a>.\nLast week\u2019s second hybrid TPAC, held in Sevilla, Spain, felt very different in a number of positive ways. This post is a summary of impressions and varied types of meetings I participated in, each of which merits its own post.\n</p>\n<p>\nThis year\u2019s W3C TPAC (Technical Plenary and Advisory Committee) meetings felt denser in many ways, packed tighter with more topics, and more active participants. There were so many specific things in specific meetings, new connections, victories, new challenges, that in addition to capturing summary notes, I'm considering writing blog posts about each meeting or session.\n</p>\n<p>\nNearly all of them have public minutes that document both participants, and a good portion of what was discussed. I have my own notes, and combined with recollected details of what was minuted, I have my own observations to share. I encourage everyone who participated at TPAC (whether in-person or remote) to consider either writing a summary blog post about the experience, perhaps highlighting a few things that stood out, or if there were specific technical discussions that advanced something in a positive direction, or challenges blocking progress, those are worth their own blog posts as well.\n</p>\n<p class=\"h-event\">\n <a href=\"https://www.w3.org/wiki/TPAC/2023\" class=\"p-name u-url\">TPAC week 2023</a> \ntook place from Monday \n <time class=\"dt-start\">2023-09-11</time> \n through Friday \n <time class=\"dt-end\">2023-09-15</time>, \nin \n <span class=\"p-location h-adr\"><span class=\"p-locality\">Sevilla</span>, \n <span class=\"p-country-name\">Spain</span></span>.\n</p>\n<p>\nHere is a summary outline of meetings, sessions, and discussions I participated in. Not listed: conversations at breakfasts, morning & afternoon breaks, lunches, dinners, and of course hallways. Unlinked for now, each of these has a calendar event with description, minutes, almost all of which are public.\n</p>\n<ul><li>Monday\n<ul><li>\n<abbr>WICG</abbr> (Web Incubator Community Group)</li>\n</ul></li>\n<li>Tuesday\n<ul><li>Social Web Incubator CG (community group), AKA \n <abbr>SocialCG</abbr> or \n <abbr>SWICG</abbr>\n</li>\n <li>\n<abbr title=\"Decentrlized Identifiers Working Group\">DID WG</abbr> \n rechartering discussion</li>\n <li>\n<abbr title=\"Advisory Committee\">AC</abbr> meeting</li>\n <li>Vision <abbr title=\"task force\">TF</abbr>\n</li>\n <li>Fediverse meetup</li>\n</ul></li>\n<li>Wednesday \u2014 Breakouts day!\n<ul><li>Chartering at W3C</li>\n <li>Technical Roadmap at W3C</li>\n <li>SocialWeb Test Suite Discussion</li>\n <li>SocialWeb Data Portability Discussion</li>\n <li>Introducing the Web Sustainability Guidelines (WSGs)</li>\n <li>Report to Members, Hearing from Members</li>\n <li>Technical Plenary reception</li>\n</ul></li>\n<li>Thursday\n<ul><li>\n<abbr title=\"Cascading Style Sheets Working Group\">CSS WG</abbr>, briefly</li>\n <li>Afternoon break: \n <abbr title=\"Social Linked Data\">Solid</abbr> \n charter discussions</li>\n</ul></li>\n<li>Friday\n<ul><li>Social CG planning</li>\n <li>Departing conversations & reflections</li>\n</ul></li>\n</ul><p>\nThose are the sessions & discussions that I found in my notes. \nI also met a lot of new people during meetings, meals, and discussions at breaks. \nAs I write up my notes on specific sessions and their minutes (and hyperlink the above list items), I expect to recall more context and details. If you were at TPAC, I encourage you to write-up your experiences as well, while the thoughts, feelings, and insights are fresh in your mind. By documenting our collective experiences, we can build upon them together.\n</p>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "article",
"_id": "38961201",
"_source": "2460"
}
I have posted some “Music Monday” posts occasionally. It’s usually been when I’m particularly excited about a song or just when the mood strikes me. I was intrigued by Pablo’s idea and figured it could be a relatively easy task to listen to one distinct album each day(-ish), whether it’s new to me or not. I am always interested in finding good new music, so that will be part of the goal, but I think this will also help me go through the catalog of albums I haven’t listened to in ages and see how they hold up.
I’m keeping it simple for now, so not going to commit to 1000 albums or posting about each one I listen to, but I am sure I will share some of the high/lowlights.
Recommendations are always welcome! What are some of your favorite albums of 2023?
{
"type": "entry",
"published": "2023-09-14 13:23-0700",
"url": "https://gregorlove.com/2023/09/i-joined-the-virtual/",
"category": [
"music"
],
"content": {
"text": "I joined the virtual Homebrew Website Club meetup last night and Pablo shared the post about his plans to expand his music tastes, \u201c1000 Albums in 1000 Days.\u201d\n\nI have posted some \u201cMusic Monday\u201d posts occasionally. It\u2019s usually been when I\u2019m particularly excited about a song or just when the mood strikes me. I was intrigued by Pablo\u2019s idea and figured it could be a relatively easy task to listen to one distinct album each day(-ish), whether it\u2019s new to me or not. I am always interested in finding good new music, so that will be part of the goal, but I think this will also help me go through the catalog of albums I haven\u2019t listened to in ages and see how they hold up.\n\nI\u2019m keeping it simple for now, so not going to commit to 1000 albums or posting about each one I listen to, but I am sure I will share some of the high/lowlights.\n\nRecommendations are always welcome! What are some of your favorite albums of 2023?",
"html": "<p>I joined the virtual <a href=\"https://events.indieweb.org/2023/09/homebrew-website-club-pacific-0ZJleWIYDM3x\">Homebrew Website Club</a> meetup last night and <a class=\"h-card\" href=\"https://lifeofpablo.com/\">Pablo</a> shared the post about his plans to expand his music tastes, \u201c<a href=\"https://lifeofpablo.com/blog/one-thousand-albums-in-one-thousand-days\">1000 Albums in 1000 Days</a>.\u201d</p>\n\n<p>I have posted <a href=\"https://gregorlove.com/2021/11/music-monday-roundup/\">some</a> \u201c<a href=\"https://gregorlove.com/2020/03/music-monday-da-i-og-gagnamagni/\">Music Monday</a>\u201d <a href=\"https://gregorlove.com/2016/04/music-monday-young-ejecta/\">posts</a> occasionally. It\u2019s usually been when I\u2019m particularly excited about a song or just when the mood strikes me. I was intrigued by Pablo\u2019s idea and figured it could be a relatively easy task to listen to one distinct album each day(-ish), whether it\u2019s new to me or not. I am always interested in finding good new music, so that will be part of the goal, but I think this will also help me go through the catalog of albums I haven\u2019t listened to in ages and see how they hold up.</p>\n\n<p>I\u2019m keeping it simple for now, so not going to commit to 1000 albums or posting about each one I listen to, but I am sure I will share some of the high/lowlights.</p>\n\n<p>Recommendations are always welcome! What are some of your favorite albums of 2023?</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "38916294",
"_source": "95"
}
