{
    "type": "entry",
    "author": {
        "name": "@shellsharks",
        "url": "https://shellsharks.social/@shellsharks",
        "photo": null
    },
    "url": "https://shellsharks.social/@shellsharks/112281848799996931",
    "content": {
        "html": "<p>Basic-ish <a href=\"https://shellsharks.social/tags/jekyll\">#<span>jekyll</span></a> stuff but I just posted a new <a href=\"https://shellsharks.social/tags/devlog\">#<span>devlog</span></a> about using Jekyll's powerful \"collections\" feature.</p><p><a href=\"https://shellsharks.com/devlog/collection-all-the-things\"><span>https://</span><span>shellsharks.com/devlog/collect</span><span>ion-all-the-things</span></a></p><p>Using multiple collections and remembering to use collections whenever you can makes building new cool stuff for the site A LOT easier.</p><p>Also worth mentioning that in the <a href=\"https://shellsharks.social/tags/indieweb\">#<span>indieweb</span></a> world, having multiple \"types\" of posts (i.e. \"post\", \"note\", etc\u2026) is a valued characteristic (per <a href=\"https://shellsharks.social/tags/indiemark\">#<span>indiemark</span></a> at least <a href=\"https://indieweb.org/IndieMark#Level_2_posts\"><span>https://</span><span>indieweb.org/IndieMark#Level_2</span><span>_posts</span></a>)</p><p><a href=\"https://shellsharks.social/tags/blogging\">#<span>blogging</span></a></p>",
        "text": "Basic-ish #jekyll stuff but I just posted a new #devlog about using Jekyll's powerful \"collections\" feature.\n\nhttps://shellsharks.com/devlog/collection-all-the-things\n\nUsing multiple collections and remembering to use collections whenever you can makes building new cool stuff for the site A LOT easier.\n\nAlso worth mentioning that in the #indieweb world, having multiple \"types\" of posts (i.e. \"post\", \"note\", etc\u2026) is a valued characteristic (per #indiemark at least https://indieweb.org/IndieMark#Level_2_posts)\n\n#blogging"
    },
    "published": "2024-04-16T16:30:46+00:00",
    "post-type": "note",
    "_id": "40854606",
    "_source": "8007",
    "_is_read": false
}

The state of Indiekit

{
    "type": "entry",
    "author": {
        "name": "Paul Robert Lloyd",
        "url": "https://paulrobertlloyd.com",
        "photo": null
    },
    "url": "https://paulrobertlloyd.com/2024/107/a1/indiekit/",
    "published": "2024-04-16T12:07:35+00:00",
    "content": {
        "html": "<blockquote><p>This project will be a marathon, not a sprint.</p></blockquote><p>Those were my words when <a href=\"https://paulrobertlloyd.com/2019/041/a1/weeknotes_5/\">I first mentioned building a Micropub server</a> in February 2019. 5 years later, these words have never been truer.</p><p>That Micropub server became <a href=\"https://getindiekit.com/\">Indiekit</a>, a Node.js application that aims to provide all the parts needed to publish content to a staticlly-generated website and then share it on social media.</p><p>It\u2019s been a while since I <a href=\"https://paulrobertlloyd.com/2022/351/a1/indiekit/\">formally announced the project in December 2022</a>, so I thought I\u2019d provide a progress report covering what\u2019s been added, what\u2019s still missing and my longer term ambitions.</p><h2>New features</h2><p>Aside from fixing a good number of bugs, I\u2019ve added the following features:</p><ul><li>The ability to <a href=\"https://getindiekit.com/plugins/post-types\">add post types via plug-ins</a></li><li>The ability to upload and add media items to posts</li><li>A Markdown editor with a full screen interface and auto save</li><li>A service worker with enhanced support for progressive web apps</li><li>An S3-compatible content store plug-in</li><li>A publication preset plug-in for Eleventy</li><li>Swedish, Latin American Spanish and simplified Chinese localisations</li></ul><p>There\u2019s been a good deal of polish to the content management interface, plus improvements to the onboarding experience and overall robustness of the application. I also updated the 600+ tests to use Node\u2019s native test runner instead of AVA.</p><p>The project is reasonably well documented, both within the code and outside of it. Whenever I return to the project, I\u2019m able to pick up from where I left off and, importantly, not feel like I need to rip everything apart and start again.</p><p>I\u2019m really happy and proud with what I\u2019ve built so far.</p><img src=\"https://paulrobertlloyd.com/media/2024/107/a1/markdown_editor.png#screenshot\" alt=\"Screenshot of the Markdown editing interface in full screen mode.\" /><h2>The perpetual beta</h2><p>If there\u2019s one thing I\u2019ve learnt during the development of this project, it\u2019s that I\u2019m bad at version numbering. My hesitancy to call anything \u2018done\u2019 means that, over <a href=\"https://github.com/getindiekit/indiekit/releases\">67 individual releases</a>, I\u2019ve published the following versions:</p><ul><li><code>v0.0.1</code></li><li><code>v0.0.2</code></li><li><code>v0.0.3</code></li><li><code>v0.1.0.alpha.x</code> (23 releases)</li><li><code>v0.1.0.beta.x</code> (5 releases)</li><li><code>v0.2.0</code></li><li><code>v0.3.0</code></li><li><code>v1.0.0.alpha.x</code> (19 releases)</li><li><code>v1.0.0.beta.x</code> (15 releases)</li></ul><p>Maybe this is fine, but it\u2019s clear that I like the comfort of alpha and beta releases which allow me to make breaking changes.</p><p>When will v1.0.0 be released? Well, there are a few gnarly issues that are preventing me from calling it done.</p><ul><li><h3>Syncing with content stores</h3><p>This issue is firmly within the realm of fundamental architectural constraint. Indiekit saves posts to a database as well as writing files to a content store such as a GitHub repository. This allows deleted posts to be restored later, and makes it easier to update posts without parsing files where data may have gone missing.</p><p>However, it also means there are 2 separate stores of data. In most cases, this is not a problem. However, should you create a post and the content store returns an error, the post in the database will not reflect the unpublished state of the post in the content store (and therefore your website).</p><p>I think the solution is to have posts remain in a pending state until the content store has confirmed that the file has been published. Sounds simple, but last time I tried to tackle this, I had to take a break from the project.</p></li><li><h3>Syndicating content to social networks</h3><p>I originally created syndicator plug-ins for the Internet Archive, Mastodon and Twitter. I removed the Twitter syndicator in Beta 5 (I don\u2019t need to explain why) while the Internet Archive syndicator can cause Indiekit\u2019s syndication endpoint to time out. That means in effect, there is only one usable syndicator at present. And even that one can end up creating duplicate posts on Mastodon.</p><p>This is another hairy architectural challenge, the sort that makes me question the decision to build my own software. A complete rethink is needed \u2013 and partly the reason why I\u2019ve not written plug-ins for other social networks yet.</p><p>I\u2019ve been toying with the idea of adding an event model to Indiekit. This would allow syndicators (and possibly other plug-ins) to hook into certain points of the publishing flow.</p><p>The speed in which a syndicator can return a URL to its syndicated copy would dictate which event they should hook into.</p><p>For example, the Mastodon syndicator could respond to a <code>publish.before</code> event, syndicate a post, append the returned URL to post data prior to this being sent on to the content store. Meanwhile, the Internet Archive syndicator could respond to a <code>publish.after</code> event, where it would query the Internet Archive <abbr title=\"application programming interface\">API</abbr> and only update a post once an archived URL had been created.</p><p>I\u2019d also like syndicators to provide equivalent methods when a post is updated or deleted. This would allow syndicated copies to remain in sync with content published to a website.</p></li><li><h3>An independent Micropub client</h3><p>One of the most intriguing aspects of Micropub is that it allows you to manage content on your website using different clients.</p><p>While any Micropub client can post to an Indiekit-powered website, it\u2019s not possible for Indiekit to publish to other websites in the same way. It should be possible, for example, to post to a Micro.blog-hosted blog using your Indiekit server.</p><p>There are a few changes I need to make to enable this. Firstly, Indiekit\u2019s authentication endpoint needs the ability to perform endpoint discovery, and the posts endpoint needs to query a website\u2019s Micropub endpoint to know which post types it supports.</p></li><li><h3>Documentation and tutorials</h3><p>While I\u2019ve tried to provide adequate documentation, it\u2019s written from the perspective of someone who knows far too much about the project! <a href=\"https://ohhelloana.blog/iwc-brighton-2024/\">Helping Ana set up Indiekit at IndieWebCamp</a> last month really highlighted how badly placed I am to write useful documentation about how to get started.</p><p>That sounds like a cop-out, really it\u2019s an invitation for people to try Indiekit and let me know how and where they\u2019re getting stuck.</p></li></ul><h2>The future</h2><p>In the future I\u2019d like to support Webmention, Microsub and ActivityPub protocols, as well as support multi-tenancy (the ability to have one server support several different websites).</p><p>I\u2019ve also got one eye on (and several pounds invested in) <a href=\"https://www.kickstarter.com/projects/fontawesome/web-awesome\">Web Awesome</a>; being able to lean on a well-designed, well-documented component system would make it easier to create plug-ins that provide pages to the application interface.</p><p>Lastly, I\u2019m questioning my choice of MongoDB; an SQL-like database would mean Indiekit could support more platforms and perhaps even use a single SQLite file.</p><p>But as you can see, there are a few knotty problems that I need to untangle before I take on any more complexity.</p><h2>Thank you</h2><p>Finally, a big thank you to everyone who has supported this project so far. The GitHub repository currently shows Indiekit as having:</p><ul><li>6 sponsors</li><li>13 contributors</li><li>51 dependent projects</li><li>320 stars</li></ul><p>Meanwhile on Localazy, 26 people have contributed to <a href=\"https://localazy.com/p/indiekit\">11 available translations</a> (with a further 10 translations pending).</p><p>Nothing makes me happier than when somebody files a bug or makes a pull request, each small contribution supporting me as I continue along this marathon IndieWeb journey.</p><p>Reply via email</p>",
        "text": "This project will be a marathon, not a sprint.Those were my words when I first mentioned building a Micropub server in February 2019. 5 years later, these words have never been truer.\n\nThat Micropub server became Indiekit, a Node.js application that aims to provide all the parts needed to publish content to a staticlly-generated website and then share it on social media.\n\nIt\u2019s been a while since I formally announced the project in December 2022, so I thought I\u2019d provide a progress report covering what\u2019s been added, what\u2019s still missing and my longer term ambitions.New featuresAside from fixing a good number of bugs, I\u2019ve added the following features:The ability to add post types via plug-insThe ability to upload and add media items to postsA Markdown editor with a full screen interface and auto saveA service worker with enhanced support for progressive web appsAn S3-compatible content store plug-inA publication preset plug-in for EleventySwedish, Latin American Spanish and simplified Chinese localisationsThere\u2019s been a good deal of polish to the content management interface, plus improvements to the onboarding experience and overall robustness of the application. I also updated the 600+ tests to use Node\u2019s native test runner instead of AVA.\n\nThe project is reasonably well documented, both within the code and outside of it. Whenever I return to the project, I\u2019m able to pick up from where I left off and, importantly, not feel like I need to rip everything apart and start again.\n\nI\u2019m really happy and proud with what I\u2019ve built so far.The perpetual betaIf there\u2019s one thing I\u2019ve learnt during the development of this project, it\u2019s that I\u2019m bad at version numbering. My hesitancy to call anything \u2018done\u2019 means that, over 67 individual releases, I\u2019ve published the following versions:v0.0.1v0.0.2v0.0.3v0.1.0.alpha.x (23 releases)v0.1.0.beta.x (5 releases)v0.2.0v0.3.0v1.0.0.alpha.x (19 releases)v1.0.0.beta.x (15 releases)Maybe this is fine, but it\u2019s clear that I like the comfort of alpha and beta releases which allow me to make breaking changes.\n\nWhen will v1.0.0 be released? Well, there are a few gnarly issues that are preventing me from calling it done.Syncing with content storesThis issue is firmly within the realm of fundamental architectural constraint. Indiekit saves posts to a database as well as writing files to a content store such as a GitHub repository. This allows deleted posts to be restored later, and makes it easier to update posts without parsing files where data may have gone missing.\n\nHowever, it also means there are 2 separate stores of data. In most cases, this is not a problem. However, should you create a post and the content store returns an error, the post in the database will not reflect the unpublished state of the post in the content store (and therefore your website).\n\nI think the solution is to have posts remain in a pending state until the content store has confirmed that the file has been published. Sounds simple, but last time I tried to tackle this, I had to take a break from the project.Syndicating content to social networksI originally created syndicator plug-ins for the Internet Archive, Mastodon and Twitter. I removed the Twitter syndicator in Beta 5 (I don\u2019t need to explain why) while the Internet Archive syndicator can cause Indiekit\u2019s syndication endpoint to time out. That means in effect, there is only one usable syndicator at present. And even that one can end up creating duplicate posts on Mastodon.\n\nThis is another hairy architectural challenge, the sort that makes me question the decision to build my own software. A complete rethink is needed \u2013 and partly the reason why I\u2019ve not written plug-ins for other social networks yet.\n\nI\u2019ve been toying with the idea of adding an event model to Indiekit. This would allow syndicators (and possibly other plug-ins) to hook into certain points of the publishing flow.\n\nThe speed in which a syndicator can return a URL to its syndicated copy would dictate which event they should hook into.\n\nFor example, the Mastodon syndicator could respond to a publish.before event, syndicate a post, append the returned URL to post data prior to this being sent on to the content store. Meanwhile, the Internet Archive syndicator could respond to a publish.after event, where it would query the Internet Archive API and only update a post once an archived URL had been created.\n\nI\u2019d also like syndicators to provide equivalent methods when a post is updated or deleted. This would allow syndicated copies to remain in sync with content published to a website.An independent Micropub clientOne of the most intriguing aspects of Micropub is that it allows you to manage content on your website using different clients.\n\nWhile any Micropub client can post to an Indiekit-powered website, it\u2019s not possible for Indiekit to publish to other websites in the same way. It should be possible, for example, to post to a Micro.blog-hosted blog using your Indiekit server.\n\nThere are a few changes I need to make to enable this. Firstly, Indiekit\u2019s authentication endpoint needs the ability to perform endpoint discovery, and the posts endpoint needs to query a website\u2019s Micropub endpoint to know which post types it supports.Documentation and tutorialsWhile I\u2019ve tried to provide adequate documentation, it\u2019s written from the perspective of someone who knows far too much about the project! Helping Ana set up Indiekit at IndieWebCamp last month really highlighted how badly placed I am to write useful documentation about how to get started.\n\nThat sounds like a cop-out, really it\u2019s an invitation for people to try Indiekit and let me know how and where they\u2019re getting stuck.The futureIn the future I\u2019d like to support Webmention, Microsub and ActivityPub protocols, as well as support multi-tenancy (the ability to have one server support several different websites).\n\nI\u2019ve also got one eye on (and several pounds invested in) Web Awesome; being able to lean on a well-designed, well-documented component system would make it easier to create plug-ins that provide pages to the application interface.\n\nLastly, I\u2019m questioning my choice of MongoDB; an SQL-like database would mean Indiekit could support more platforms and perhaps even use a single SQLite file.\n\nBut as you can see, there are a few knotty problems that I need to untangle before I take on any more complexity.Thank youFinally, a big thank you to everyone who has supported this project so far. The GitHub repository currently shows Indiekit as having:6 sponsors13 contributors51 dependent projects320 starsMeanwhile on Localazy, 26 people have contributed to 11 available translations (with a further 10 translations pending).\n\nNothing makes me happier than when somebody files a bug or makes a pull request, each small contribution supporting me as I continue along this marathon IndieWeb journey.\n\nReply via email"
    },
    "name": "The state of Indiekit",
    "post-type": "article",
    "_id": "40853820",
    "_source": "3686",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@knowler",
        "url": "https://sunny.garden/@knowler",
        "photo": null
    },
    "url": "https://sunny.garden/@knowler/112281509757352871",
    "content": {
        "html": "<p>How and why I\u2019m self-hosting my code demos.<br /><a href=\"https://knowler.dev/blog/self-hosting-code-demos\"><span>https://</span><span>knowler.dev/blog/self-hosting-</span><span>code-demos</span></a></p><p><a href=\"https://sunny.garden/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "How and why I\u2019m self-hosting my code demos.\nhttps://knowler.dev/blog/self-hosting-code-demos\n\n#IndieWeb"
    },
    "published": "2024-04-16T15:04:33+00:00",
    "post-type": "note",
    "_id": "40853645",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@mms",
        "url": "https://emacs.ch/@mms",
        "photo": null
    },
    "url": "https://emacs.ch/@mms/112281445160069036",
    "content": {
        "html": "<p>New brain rot: Dune Part II</p><p>\"But I was very skeptical. The trailers seemed to indicate a train wreck. They were full of explosions, angry screaming guys and the taglines about war. Dune was never about war. War was in there, but it was never the point. But cinema, SciFi especially, loves special effects, and big-booms are amongst the most used. I dislike a lot of SciFi movies from the USA, as the (so called) spectacle is all there is.\"</p><p><a href=\"https://michal.sapka.me/brain-rot/dune/part-two-2024/\"><span>https://</span><span>michal.sapka.me/brain-rot/dune</span><span>/part-two-2024/</span></a></p><p><a href=\"https://emacs.ch/tags/dune\">#<span>dune</span></a> <a href=\"https://emacs.ch/tags/scifi\">#<span>scifi</span></a> <a href=\"https://emacs.ch/tags/100daystooffload\">#<span>100daystooffload</span></a> <a href=\"https://emacs.ch/tags/smallweb\">#<span>smallweb</span></a> <a href=\"https://emacs.ch/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "New brain rot: Dune Part II\n\n\"But I was very skeptical. The trailers seemed to indicate a train wreck. They were full of explosions, angry screaming guys and the taglines about war. Dune was never about war. War was in there, but it was never the point. But cinema, SciFi especially, loves special effects, and big-booms are amongst the most used. I dislike a lot of SciFi movies from the USA, as the (so called) spectacle is all there is.\"\n\nhttps://michal.sapka.me/brain-rot/dune/part-two-2024/\n\n#dune #scifi #100daystooffload #smallweb #indieweb"
    },
    "published": "2024-04-16T14:48:07+00:00",
    "post-type": "note",
    "_id": "40853493",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@GandalfDG",
        "url": "https://indieweb.social/@GandalfDG",
        "photo": null
    },
    "url": "https://indieweb.social/@GandalfDG/112281281321649906",
    "content": {
        "html": "<p>Added a <a href=\"https://indieweb.social/tags/now\">#<span>now</span></a> page to my personal site. Pretty bare-bones at the moment but it's a neat idea. <a href=\"https://www.jack-case.pro/now/\"><span>https://www.</span><span>jack-case.pro/now/</span><span></span></a></p><p><a href=\"https://indieweb.social/tags/PersonalSites\">#<span>PersonalSites</span></a> <a href=\"https://indieweb.social/tags/Website\">#<span>Website</span></a> <a href=\"https://indieweb.social/tags/Hugo\">#<span>Hugo</span></a> <a href=\"https://indieweb.social/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "Added a #now page to my personal site. Pretty bare-bones at the moment but it's a neat idea. https://www.jack-case.pro/now/\n\n#PersonalSites #Website #Hugo #indieweb"
    },
    "published": "2024-04-16T14:06:27+00:00",
    "post-type": "note",
    "_id": "40852983",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@weirdwriter",
        "url": "https://tweesecake.social/@weirdwriter",
        "photo": null
    },
    "url": "https://tweesecake.social/@weirdwriter/112281103270555752",
    "content": {
        "html": "<p>I love this exact kind of tech you describe! The <a href=\"https://tweesecake.social/tags/SmallTech\">#<span>SmallTech</span></a> and the <a href=\"https://tweesecake.social/tags/SmallWeb\">#<span>SmallWeb</span></a> and, by extension, the <a href=\"https://tweesecake.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <span class=\"h-card\"><a class=\"u-url\" href=\"https://hachyderm.io/@collinsworth\">@<span>collinsworth</span></a></span></p>\n<a class=\"u-mention\" href=\"https://hachyderm.io/@collinsworth\"></a>",
        "text": "I love this exact kind of tech you describe! The #SmallTech and the #SmallWeb and, by extension, the #IndieWeb @collinsworth"
    },
    "published": "2024-04-16T13:21:10+00:00",
    "post-type": "note",
    "_id": "40852984",
    "_source": "8007",
    "_is_read": false
}

Jeremy Keith adactio.com

{
    "type": "entry",
    "published": "2024-04-16T10:43:56Z",
    "url": "https://adactio.com/links/21051",
    "category": [
        "writing",
        "blogging",
        "thinking",
        "sharing",
        "communication",
        "indieweb"
    ],
    "bookmark-of": [
        "https://robinrendle.com/notes/good-and-useful-writing-/"
    ],
    "content": {
        "text": "Robin Rendle \u2014 Good and useful writing\n\n\n\n\n  The most important lesson that blogging taught me is that writing is for thinking first, communication last.",
        "html": "<h3>\n<a class=\"p-name u-bookmark-of\" href=\"https://robinrendle.com/notes/good-and-useful-writing-/\">\nRobin Rendle \u2014 Good and useful writing\n</a>\n</h3>\n\n<blockquote>\n  <p>The most important lesson that blogging taught me is that writing is for thinking first, communication last.</p>\n</blockquote>"
    },
    "author": {
        "type": "card",
        "name": "Jeremy Keith",
        "url": "https://adactio.com/",
        "photo": "https://adactio.com/images/photo-150.jpg"
    },
    "post-type": "bookmark",
    "_id": "40851660",
    "_source": "2",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@inforflux",
        "url": "https://mastodon.social/@inforflux",
        "photo": null
    },
    "url": "https://mastodon.social/@inforflux/112279527027479645",
    "content": {
        "html": "<p>I've only just discovered the <a href=\"https://mastodon.social/tags/fediverse\">#<span>fediverse</span></a> and found out <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> and <a href=\"https://mastodon.social/tags/smallweb\">#<span>smallweb</span></a> are what you call those cool, fun, real websites I've missed so badly.</p><p>I feel like I've just opened a door that I've only ever heard muffled crys of joy from the other side. It's completely bonkers in here. So much creativity. Am I late to the party or is it just getting started?</p><p><a href=\"https://spyderooth.vercel.app//quick-posts/quick-post-2024-04-16-180205/\"><span>https://</span><span>spyderooth.vercel.app//quick-p</span><span>osts/quick-post-2024-04-16-180205/</span></a></p>",
        "text": "I've only just discovered the #fediverse and found out #indieweb and #smallweb are what you call those cool, fun, real websites I've missed so badly.\n\nI feel like I've just opened a door that I've only ever heard muffled crys of joy from the other side. It's completely bonkers in here. So much creativity. Am I late to the party or is it just getting started?\n\nhttps://spyderooth.vercel.app//quick-posts/quick-post-2024-04-16-180205/"
    },
    "published": "2024-04-16T06:40:18+00:00",
    "post-type": "note",
    "_id": "40850025",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@jcrabapple",
        "url": "https://dmv.community/@jcrabapple",
        "photo": null
    },
    "url": "https://dmv.community/@jcrabapple/112278396807126758",
    "content": {
        "html": "<p>Discover the <a href=\"https://dmv.community/tags/IndieWeb\">#<span>IndieWeb</span></a>, one blog post at a time.</p><p><a href=\"https://indieblog.page/\"><span>https://</span><span>indieblog.page/</span><span></span></a></p>",
        "text": "Discover the #IndieWeb, one blog post at a time.\n\nhttps://indieblog.page/"
    },
    "published": "2024-04-16T01:52:53+00:00",
    "post-type": "note",
    "_id": "40848677",
    "_source": "8007",
    "_is_read": false
}

gRegor Morrill gregorlove.com

{
    "type": "entry",
    "published": "2024-04-15 12:16-0700",
    "url": "https://gregorlove.com/2024/04/have-questions-about-html/",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "Have questions about HTML/CSS? Join the Front End Study Hall hosted by @artlung@xoxo.zone on Zoom next Wednesday, April 24!",
        "html": "<p>Have questions about HTML/CSS? Join the <a href=\"https://events.indieweb.org/2024/04/front-end-study-hall-FHS5M2AofkU4\">Front End Study Hall</a> hosted by <a href=\"https://xoxo.zone/@artlung\">@artlung@xoxo.zone</a> on Zoom next Wednesday, April 24!</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": "40847910",
    "_source": "179",
    "_is_read": false
}

gRegor Morrill gregorlove.com

{
    "type": "entry",
    "published": "2024-04-15 12:16-0700",
    "url": "https://gregorlove.com/2024/04/have-questions-about-html/",
    "category": [
        "indieweb"
    ],
    "content": {
        "text": "Have questions about HTML/CSS? Join the Front End Study Hall hosted by @artlung@xoxo.zone on Zoom next Wednesday, April 24!",
        "html": "<p>Have questions about HTML/CSS? Join the <a href=\"https://events.indieweb.org/2024/04/front-end-study-hall-FHS5M2AofkU4\">Front End Study Hall</a> hosted by <a href=\"https://xoxo.zone/@artlung\">@artlung@xoxo.zone</a> on Zoom next Wednesday, April 24!</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": "40847715",
    "_source": "95",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@jcrabapple",
        "url": "https://dmv.community/@jcrabapple",
        "photo": null
    },
    "url": "https://dmv.community/@jcrabapple/112277706477163571",
    "content": {
        "html": "<p>Scribbles Categories</p><p><a href=\"https://cool-as-heck.blog/post/scribbles-categories\"><span>https://</span><span>cool-as-heck.blog/post/scribbl</span><span>es-categories</span></a></p><p><a href=\"https://dmv.community/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "Scribbles Categories\n\nhttps://cool-as-heck.blog/post/scribbles-categories\n\n#indieweb"
    },
    "published": "2024-04-15T22:57:19+00:00",
    "post-type": "note",
    "_id": "40847224",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@Zeronaut",
        "url": "https://fosstodon.org/@Zeronaut",
        "photo": null
    },
    "url": "https://fosstodon.org/@Zeronaut/112276908120556870",
    "content": {
        "html": "<p>Just posted a new article on my blog called Joyous Jazz about Trying a new jazz club and sharing the joy of music with my partner <br /><a href=\"https://fosstodon.org/tags/GoHugo\">#<span>GoHugo</span></a> <a href=\"https://fosstodon.org/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://fosstodon.org/tags/Blog\">#<span>Blog</span></a> </p><p><a href=\"https://allisthewave.com/posts/2024-04-09-joyous-jazz/\"><span>https://</span><span>allisthewave.com/posts/2024-04</span><span>-09-joyous-jazz/</span></a></p>",
        "text": "Just posted a new article on my blog called Joyous Jazz about Trying a new jazz club and sharing the joy of music with my partner \n#GoHugo #indieweb #Blog \n\nhttps://allisthewave.com/posts/2024-04-09-joyous-jazz/"
    },
    "published": "2024-04-15T19:34:17+00:00",
    "photo": [
        "https://files.mastodon.social/cache/media_attachments/files/112/276/922/840/822/370/original/3459aa734b6f0738.jpeg"
    ],
    "post-type": "photo",
    "_id": "40845780",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@artlung",
        "url": "https://xoxo.zone/@artlung",
        "photo": null
    },
    "url": "https://xoxo.zone/@artlung/112276558214913184",
    "content": {
        "html": "<p>Front End Study Hall next Wednesday. Zoom open format HTML+CSS <a href=\"https://xoxo.zone/tags/IndieWeb\">#<span>IndieWeb</span></a>. <a href=\"https://artlung.com/blog/2024/04/15/front-end-study-hall/\"><span>https://</span><span>artlung.com/blog/2024/04/15/fr</span><span>ont-end-study-hall/</span></a> <a href=\"https://xoxo.zone/tags/IndieWeb\">#<span>IndieWeb</span></a></p>",
        "text": "Front End Study Hall next Wednesday. Zoom open format HTML+CSS #IndieWeb. https://artlung.com/blog/2024/04/15/front-end-study-hall/ #IndieWeb"
    },
    "published": "2024-04-15T18:05:18+00:00",
    "post-type": "note",
    "_id": "40845065",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@brianb",
        "url": "https://fosstodon.org/@brianb",
        "photo": null
    },
    "url": "https://fosstodon.org/@brianb/112276602574167651",
    "content": {
        "html": "<p>I kind of miss having a search option on my blog.</p><p><a href=\"https://blog.ohheybrian.com/2024/04/i-kind-of-miss-search/\"><span>https://</span><span>blog.ohheybrian.com/2024/04/i-</span><span>kind-of-miss-search/</span></a></p><p><a href=\"https://fosstodon.org/tags/100DaysToOffload\">#<span>100DaysToOffload</span></a> <a href=\"https://fosstodon.org/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "I kind of miss having a search option on my blog.\n\nhttps://blog.ohheybrian.com/2024/04/i-kind-of-miss-search/\n\n#100DaysToOffload #indieweb"
    },
    "published": "2024-04-15T18:16:35+00:00",
    "post-type": "note",
    "_id": "40845066",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@anders",
        "url": "https://thoresson.social/@anders",
        "photo": null
    },
    "url": "https://thoresson.social/@anders/112276516034461979",
    "content": {
        "html": "<p>An observation: What started as a list with <a href=\"https://thoresson.social/tags/11ty\">#<span>11ty</span></a>-related account I follow here is slowly transforming into an <a href=\"https://thoresson.social/tags/indieweb\">#<span>indieweb</span></a>/ <a href=\"https://thoresson.social/tags/SmallWeb\">#<span>SmallWeb</span></a> list. Not surprisingly perhaps that there is a huge overlap between the two communities.</p>",
        "text": "An observation: What started as a list with #11ty-related account I follow here is slowly transforming into an #indieweb/ #SmallWeb list. Not surprisingly perhaps that there is a huge overlap between the two communities."
    },
    "published": "2024-04-15T17:54:34+00:00",
    "post-type": "note",
    "_id": "40844901",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "@jcrabapple",
        "url": "https://dmv.community/@jcrabapple",
        "photo": null
    },
    "url": "https://dmv.community/@jcrabapple/112276007258440068",
    "content": {
        "html": "<p>Finally, A Weekend We've Been Waiting For</p><p><a href=\"https://cool-as-heck.blog/post/finally-a-weekend-we-ve-been-waiting-for\"><span>https://</span><span>cool-as-heck.blog/post/finally</span><span>-a-weekend-we-ve-been-waiting-for</span></a></p><p><a href=\"https://dmv.community/tags/indieweb\">#<span>indieweb</span></a></p>",
        "text": "Finally, A Weekend We've Been Waiting For\n\nhttps://cool-as-heck.blog/post/finally-a-weekend-we-ve-been-waiting-for\n\n#indieweb"
    },
    "published": "2024-04-15T15:45:11+00:00",
    "post-type": "note",
    "_id": "40843547",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://makai.chaotic.ninja/notes/9s43f5vb6z",
    "content": {
        "html": "<p>I wonder if anyone has tested this <a href=\"https://makai.chaotic.ninja/tags/PullRequest\">#PullRequest</a> yet that adds <a href=\"https://makai.chaotic.ninja/tags/Micropub\">#Micropub</a> support to <a href=\"https://makai.chaotic.ninja/tags/Misskey\">#Misskey</a>? I kinda don't want this PR to get forcefully discarded because of too many merge conflicts with upstream... \u200b<img alt=\":sagume_think:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/719/992/original/b3534a887247c89a.webp\" title=\":sagume_think:\" width=\"16\" />\u200b<span><br /><br />I might try testing it out here in </span><a href=\"https://makai.chaotic.ninja/tags/Makai\">#Makai</a> later but I will have to find a good Micropub client on <a href=\"https://makai.chaotic.ninja/tags/Android\">#Android</a> and <a href=\"https://makai.chaotic.ninja/tags/Windows\">#Windows</a> first (feel free to suggest here I guess you <a href=\"https://makai.chaotic.ninja/tags/IndieWeb\">#IndieWeb</a> nerds \u200b<img alt=\":chuckling_okuu:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/733/807/original/cbd5a5333cabdb5c.gif\" title=\":chuckling_okuu:\" width=\"16\" />\u200b<span>)<br /><br />(Also for some reason my previous quote renote linking to this OP got lost, I don't remember deleting it... </span>\u200b<img alt=\":SanaeConfuzzled:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/802/037/original/8d0a99af8e4c9d11.webp\" title=\":SanaeConfuzzled:\" width=\"16\" />\u200b<span>)<br /><br />RE: </span><a href=\"https://p1.a9z.dev/notes/9p80jquq4o\">https://p1.a9z.dev/notes/9p80jquq4o</a></p>",
        "text": "I wonder if anyone has tested this #PullRequest yet that adds #Micropub support to #Misskey? I kinda don't want this PR to get forcefully discarded because of too many merge conflicts with upstream... \u200b\u200b\n\nI might try testing it out here in #Makai later but I will have to find a good Micropub client on #Android and #Windows first (feel free to suggest here I guess you #IndieWeb nerds \u200b\u200b)\n\n(Also for some reason my previous quote renote linking to this OP got lost, I don't remember deleting it... \u200b\u200b)\n\nRE: https://p1.a9z.dev/notes/9p80jquq4o"
    },
    "published": "2024-04-15T05:43:13+00:00",
    "post-type": "note",
    "_id": "40839150",
    "_source": "8007",
    "_is_read": false
}

{
    "type": "entry",
    "author": {
        "name": "#indieweb",
        "url": "https://mastodon.social/tags/indieweb",
        "photo": null
    },
    "url": "https://fed.brid.gy/r/https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings",
    "content": {
        "html": "Last week I participated <a href=\"https://W3.org\">@W3.org</a> (<a href=\"https://w3c.social/@w3c\">@w3c@w3c.social</a>) <a href=\"https://indieweb.social/tags/w3cAC\">#<span class=\"p-category\">w3cAC</span></a> (W3C Advisory Committee<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-1\">\u00b9</a>), <a href=\"https://indieweb.social/tags/w3cAB\">#<span class=\"p-category\">w3cAB</span></a> (W3C Advisory Board<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-2\">\u00b2</a> <a href=\"https://w3c.social/@ab\">@ab@w3c.social</a>), and <a href=\"https://indieweb.social/tags/w3cBoard\">#<span class=\"p-category\">w3cBoard</span></a> (Board of the W3C Corporation<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-3\">\u00b3</a>) meetings in Hiroshima, Japan.<br /><br />The AC (Advisory Committee) meeting was two days, followed by two days of AB and Board meetings which started with a half-day joint session (including the <a href=\"https://indieweb.social/tags/w3cTAG\">#<span class=\"p-category\">w3cTAG</span></a>), then separate meetings to focus on their own tasks &amp; discussions.<br /><br />The W3C Process<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-4\">\u2074</a> describes the twice a year AC (Advisory Committee) Meetings<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-5\">\u2075</a>. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the W3C Board, the W3C TAG (W3C Technical Architecture Group<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-6\">\u2076</a> <a href=\"https://w3c.social/@tag\">@tag@w3c.social</a>), Working Group<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-7\">\u2077</a> chairs, Chapter<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-8\">\u2078</a> staff, and this time also a W3C Invited Expert designated observer<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-9\">\u2079</a>.<br /><br />The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual <a href=\"https://indieweb.social/tags/w3cTPAC\">#<span class=\"p-category\">w3cTPAC</span></a> (W3C Technical Plenary and Advisory Committee<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-10\">\u00b9\u2070</a> meetings). The existence, dates, and location of the event are public<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-11\">\u00b9\u00b9</a>, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery &amp; navigation (if you work for a W3C Member Organization<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-12\">\u00b9\u00b2</a>): <br /><br />* <a href=\"https://www.w3.org/wiki/AC/Meetings#2024_Spring\">https://www.w3.org/wiki/AC/Meetings#2024_Spring</a><br /><br />Most of the W3C meeting materials and discussions were also W3C Member-confidential, however many of the presentations are publicly viewable, and a few more may be shared publicly after the fact.<br /><br />Myself and others at <a href=\"https://indieweb.social/tags/W3C\">#<span class=\"p-category\">W3C</span></a> who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.<br /><br />Aside: I started the <a href=\"https://indieweb.social/tags/OpenAB\">#<span class=\"p-category\">OpenAB</span></a> project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: <a href=\"https://www.w3.org/wiki/AB#Open_AB\">https://www.w3.org/wiki/AB#Open_AB</a><br /><br />Like most conferences, I got as much out of side conversations at breaks (AKA hallway track<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-13\">\u00b9\u00b3</a>) and meals as I did from scheduled talks and panels.<br /><br />For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:<br />* \ud83d\udcc4 report: <a href=\"https://www.w3.org/reports/ai-web-impact/\">https://www.w3.org/reports/ai-web-impact/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/\">https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/exploration/\">https://www.w3.org/2024/Talks/ac-slides/exploration/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf\">https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf</a><br />* \u25b6\ufe0f video 5m42s: <a href=\"https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch\">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch</a><br />* \u25b6\ufe0f video 4m16s: <a href=\"https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch\">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch</a><br />* \ud83d\uddd3 event: <a href=\"https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/\">https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/\">https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/\">https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/\">https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/</a> (nice <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> mention)<br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf\">https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf</a><br />* \ud83d\uddbc slides: <a href=\"https://w3c.github.io/adapt/presentations/ac2024/\">https://w3c.github.io/adapt/presentations/ac2024/</a> Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-14\">\u00b9\u2074</a>), more complex to author (requires sidefiles<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-15\">\u00b9\u2075</a>), harder to publish (requires site admin root access), likely to become inaccurate (Ruby\u2019s postulate<a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_note-16\">\u00b9\u2076</a>), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.<br />* \ud83d\uddd3 event: <a href=\"https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/\">https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/</a><br /><br />I\u2019ll update this list with additional resources as they are made publicly viewable.<br /><br />If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: <a href=\"https://www.w3.org/2024/04/AC/ac-agenda.html#monday\">https://www.w3.org/2024/04/AC/ac-agenda.html#monday</a><br /><br />References:<br /><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-1\">\u00b9</a> <a href=\"https://w3.org/wiki/AC\">https://w3.org/wiki/AC</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-2\">\u00b2</a> <a href=\"https://w3.org/wiki/AB\">https://w3.org/wiki/AB</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-3\">\u00b3</a> <a href=\"https://w3.org/wiki/Board\">https://w3.org/wiki/Board</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-4\">\u2074</a> <a href=\"https://www.w3.org/Consortium/Process/\">https://www.w3.org/Consortium/Process/</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-5\">\u2075</a> <a href=\"https://www.w3.org/2023/Process-20231103/#ACMeetings\">https://www.w3.org/2023/Process-20231103/#ACMeetings</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-6\">\u2076</a> <a href=\"https://w3.org/tag\">https://w3.org/tag</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-7\">\u2077</a> <a href=\"https://www.w3.org/groups/wg/\">https://www.w3.org/groups/wg/</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-8\">\u2078</a> <a href=\"https://chapters.w3.org/\">https://chapters.w3.org/</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-9\">\u2079</a> <a href=\"https://www.w3.org/invited-experts/#ac-observer\">https://www.w3.org/invited-experts/#ac-observer</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-10\">\u00b9\u2070</a> <a href=\"https://www.w3.org/wiki/TPAC\">https://www.w3.org/wiki/TPAC</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-11\">\u00b9\u00b9</a> <a href=\"https://www.w3.org/events/ac/2024/ac-2024/\">https://www.w3.org/events/ac/2024/ac-2024/</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-12\">\u00b9\u00b2</a> <a href=\"https://www.w3.org/membership/list/\">https://www.w3.org/membership/list/</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-13\">\u00b9\u00b3</a> <a href=\"https://en.wiktionary.org/wiki/hallway_track\">https://en.wiktionary.org/wiki/hallway_track</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-14\">\u00b9\u2074</a> <a href=\"https://microformats.org/wiki/existing-rel-values\">https://microformats.org/wiki/existing-rel-values</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-15\">\u00b9\u2075</a> <a href=\"https://indieweb.org/sidefile-antipattern\">https://indieweb.org/sidefile-antipattern</a><br /><a href=\"https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings#t5WT1_ref-16\">\u00b9\u2076</a> <a href=\"https://intertwingly.net/slides/2004/devcon/68.html\">https://intertwingly.net/slides/2004/devcon/68.html</a>\n<a class=\"u-mention\" href=\"https://W3.org\"></a>\n<a class=\"u-mention\" href=\"https://w3c.social/@ab\"></a>\n<a class=\"u-mention\" href=\"https://w3c.social/@tag\"></a>\n<a class=\"u-mention\" href=\"https://w3c.social/@w3c\"></a>",
        "text": "Last week I participated @W3.org (@w3c@w3c.social) #w3cAC (W3C Advisory Committee\u00b9), #w3cAB (W3C Advisory Board\u00b2 @ab@w3c.social), and #w3cBoard (Board of the W3C Corporation\u00b3) meetings in Hiroshima, Japan.\n\nThe AC (Advisory Committee) meeting was two days, followed by two days of AB and Board meetings which started with a half-day joint session (including the #w3cTAG), then separate meetings to focus on their own tasks & discussions.\n\nThe W3C Process\u2074 describes the twice a year AC (Advisory Committee) Meetings\u2075. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the W3C Board, the W3C TAG (W3C Technical Architecture Group\u2076 @tag@w3c.social), Working Group\u2077 chairs, Chapter\u2078 staff, and this time also a W3C Invited Expert designated observer\u2079.\n\nThe AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #w3cTPAC (W3C Technical Plenary and Advisory Committee\u00b9\u2070 meetings). The existence, dates, and location of the event are public\u00b9\u00b9, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization\u00b9\u00b2): \n\n* https://www.w3.org/wiki/AC/Meetings#2024_Spring\n\nMost of the W3C meeting materials and discussions were also W3C Member-confidential, however many of the presentations are publicly viewable, and a few more may be shared publicly after the fact.\n\nMyself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.\n\nAside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB\n\nLike most conferences, I got as much out of side conversations at breaks (AKA hallway track\u00b9\u00b3) and meals as I did from scheduled talks and panels.\n\nFor now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:\n* \ud83d\udcc4 report: https://www.w3.org/reports/ai-web-impact/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/exploration/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf\n* \u25b6\ufe0f video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch\n* \u25b6\ufe0f video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch\n* \ud83d\uddd3 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf\n* \ud83d\uddbc slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values\u00b9\u2074), more complex to author (requires sidefiles\u00b9\u2075), harder to publish (requires site admin root access), likely to become inaccurate (Ruby\u2019s postulate\u00b9\u2076), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.\n* \ud83d\uddd3 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/\n\nI\u2019ll update this list with additional resources as they are made publicly viewable.\n\nIf you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday\n\nReferences:\n\n\u00b9 https://w3.org/wiki/AC\n\u00b2 https://w3.org/wiki/AB\n\u00b3 https://w3.org/wiki/Board\n\u2074 https://www.w3.org/Consortium/Process/\n\u2075 https://www.w3.org/2023/Process-20231103/#ACMeetings\n\u2076 https://w3.org/tag\n\u2077 https://www.w3.org/groups/wg/\n\u2078 https://chapters.w3.org/\n\u2079 https://www.w3.org/invited-experts/#ac-observer\n\u00b9\u2070 https://www.w3.org/wiki/TPAC\n\u00b9\u00b9 https://www.w3.org/events/ac/2024/ac-2024/\n\u00b9\u00b2 https://www.w3.org/membership/list/\n\u00b9\u00b3 https://en.wiktionary.org/wiki/hallway_track\n\u00b9\u2074 https://microformats.org/wiki/existing-rel-values\n\u00b9\u2075 https://indieweb.org/sidefile-antipattern\n\u00b9\u2076 https://intertwingly.net/slides/2004/devcon/68.html"
    },
    "published": "2024-04-15T02:00:00+00:00",
    "post-type": "note",
    "_id": "40838428",
    "_source": "8007",
    "_is_read": false
}

Tantek Çelik tantek.com

{
    "type": "entry",
    "published": "2024-04-14 18:41-0700",
    "url": "http://tantek.com/2024/105/t1/w3c-advisory-committee-meetings",
    "category": [
        "W3CAC",
        "W3CAB",
        "W3CBoard",
        "w3cTAG",
        "W3CTPAC",
        "W3C",
        "OpenAB",
        "IndieWeb"
    ],
    "content": {
        "text": "Last week I participated @W3.org (@w3c@w3c.social) #W3CAC (W3C Advisory Committee\u00b9), #W3CAB (W3C Advisory Board\u00b2 @ab@w3c.social), and #W3CBoard (Board of the W3C Corporation\u00b3) meetings in Hiroshima, Japan.\n\nThe W3C Process\u2074 describes the twice a year AC (Advisory Committee) Meetings\u2075. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the W3C Board, the #w3cTAG (W3C Technical Architecture Group\u2076 @tag@w3c.social), Working Group\u2077 chairs, Chapter\u2078 staff, and this time also a W3C Invited Expert designated observer\u2079.\n\nThe AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #W3CTPAC (W3C Technical Plenary and Advisory Committee\u00b9\u2070 meetings). The existence, dates, and location of the event are public\u00b9\u00b9, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery & navigation (if you work for a W3C Member Organization\u00b9\u00b2): \n\n* https://www.w3.org/wiki/AC/Meetings#2024_Spring\n\nMost of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact.\n\nMyself and others at #W3C who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.\n\nAside: I started the #OpenAB project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: https://www.w3.org/wiki/AB#Open_AB\n\nLike most conferences, I got as much out of side conversations at breaks (AKA hallway track\u00b9\u00b3) and meals as I did from scheduled talks and panels.\n\nFor now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:\n* \ud83d\udcc4 report: https://www.w3.org/reports/ai-web-impact/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/exploration/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf\n* \u25b6\ufe0f video 5m42s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch\n* \u25b6\ufe0f video 4m16s: https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch\n* \ud83d\uddd3 event: https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/ (nice #IndieWeb mention)\n* \ud83d\uddbc slides: https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf\n* \ud83d\uddbc slides: https://w3c.github.io/adapt/presentations/ac2024/ Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values\u00b9\u2074), more complex to author (requires sidefiles\u00b9\u2075), harder to publish (requires site admin root access), likely to become inaccurate (Ruby\u2019s postulate\u00b9\u2076), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.\n* \ud83d\uddd3 event: https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/\n\nI\u2019ll update this list with additional resources as they are made publicly viewable.\n\nIf you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: https://www.w3.org/2024/04/AC/ac-agenda.html#monday\n\nReferences:\n\n\u00b9 https://w3.org/wiki/AC\n\u00b2 https://w3.org/wiki/AB\n\u00b3 https://w3.org/wiki/Board\n\u2074 https://www.w3.org/Consortium/Process/\n\u2075 https://www.w3.org/2023/Process-20231103/#ACMeetings\n\u2076 https://w3.org/tag\n\u2077 https://www.w3.org/groups/wg/\n\u2078 https://chapters.w3.org/\n\u2079 https://www.w3.org/invited-experts/#ac-observer\n\u00b9\u2070 https://www.w3.org/wiki/TPAC\n\u00b9\u00b9 https://www.w3.org/events/ac/2024/ac-2024/\n\u00b9\u00b2 https://www.w3.org/membership/list/\n\u00b9\u00b3 https://en.wiktionary.org/wiki/hallway_track\n\u00b9\u2074 https://microformats.org/wiki/existing-rel-values\n\u00b9\u2075 https://indieweb.org/sidefile-antipattern\n\u00b9\u2076 https://intertwingly.net/slides/2004/devcon/68.html",
        "html": "Last week I participated <a href=\"https://W3.org\">@W3.org</a> (<a href=\"https://w3c.social/@w3c\">@w3c@w3c.social</a>) #<span class=\"p-category\">W3CAC</span> (W3C Advisory Committee<a href=\"http://tantek.com/#t5WT1_note-1\">\u00b9</a>), #<span class=\"p-category\">W3CAB</span> (W3C Advisory Board<a href=\"http://tantek.com/#t5WT1_note-2\">\u00b2</a> <a href=\"https://w3c.social/@ab\">@ab@w3c.social</a>), and #<span class=\"p-category\">W3CBoard</span> (Board of the W3C Corporation<a href=\"http://tantek.com/#t5WT1_note-3\">\u00b3</a>) meetings in Hiroshima, Japan.<br /><br />The W3C Process<a href=\"http://tantek.com/#t5WT1_note-4\">\u2074</a> describes the twice a year AC (Advisory Committee) Meetings<a href=\"http://tantek.com/#t5WT1_note-5\">\u2075</a>. In addition to members of the AC (one primary and one alternate per W3C Member Organization), the meetings are open to the AB (Advisory Board), the W3C Board, the #<span class=\"p-category\">w3cTAG</span> (W3C Technical Architecture Group<a href=\"http://tantek.com/#t5WT1_note-6\">\u2076</a> <a href=\"https://w3c.social/@tag\">@tag@w3c.social</a>), Working Group<a href=\"http://tantek.com/#t5WT1_note-7\">\u2077</a> chairs, Chapter<a href=\"http://tantek.com/#t5WT1_note-8\">\u2078</a> staff, and this time also a W3C Invited Expert designated observer<a href=\"http://tantek.com/#t5WT1_note-9\">\u2079</a>.<br /><br />The AC currently meets in the Spring on its own and a shorter meeting in the Fall as part of the annual #<span class=\"p-category\">W3CTPAC</span> (W3C Technical Plenary and Advisory Committee<a href=\"http://tantek.com/#t5WT1_note-10\">\u00b9\u2070</a> meetings). The existence, dates, and location of the event are public<a href=\"http://tantek.com/#t5WT1_note-11\">\u00b9\u00b9</a>, however the agenda, minutes, and registrants are generally Member-confidential. Since those individual links have their own access controls, I collected them on a publicly-viewable wiki page for easier discovery &amp; navigation (if you work for a W3C Member Organization<a href=\"http://tantek.com/#t5WT1_note-12\">\u00b9\u00b2</a>): <br /><br />* <a href=\"https://www.w3.org/wiki/AC/Meetings#2024_Spring\">https://www.w3.org/wiki/AC/Meetings#2024_Spring</a><br /><br />Most of the W3C meeting materials and discussions were also W3C Member-confidential, however a several of the presentations are publicly viewable, and a few more may be shared publicly after the fact.<br /><br />Myself and others at #<span class=\"p-category\">W3C</span> who believe in pushing for more openness and transparency in standards work, even (or especially) governance of said work, will be doing our best to work with others at W3C to continue shifting our work accordingly.<br /><br />Aside: I started the #<span class=\"p-category\">OpenAB</span> project when I was first elected to the AB (Advisory Board) in 2013, documenting it on the publicly viewable W3C Wiki, and updated it with the help of others since: <a href=\"https://www.w3.org/wiki/AB#Open_AB\">https://www.w3.org/wiki/AB#Open_AB</a><br /><br />Like most conferences, I got as much out of side conversations at breaks (AKA hallway track<a href=\"http://tantek.com/#t5WT1_note-13\">\u00b9\u00b3</a>) and meals as I did from scheduled talks and panels.<br /><br />For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed:<br />* \ud83d\udcc4 report: <a href=\"https://www.w3.org/reports/ai-web-impact/\">https://www.w3.org/reports/ai-web-impact/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/\">https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/exploration/\">https://www.w3.org/2024/Talks/ac-slides/exploration/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf\">https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf</a><br />* \u25b6\ufe0f video 5m42s: <a href=\"https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch\">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch</a><br />* \u25b6\ufe0f video 4m16s: <a href=\"https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch\">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch</a><br />* \ud83d\uddd3 event: <a href=\"https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/\">https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/\">https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/\">https://www.w3.org/2024/Talks/ac-slides/lt-accessing-llms-data/</a><br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/\">https://www.w3.org/2024/Talks/ac-slides/pac-data-sovereignty/</a> (nice #<span class=\"p-category\">IndieWeb</span> mention)<br />* \ud83d\uddbc slides: <a href=\"https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf\">https://www.w3.org/2024/Talks/ac-slides/intro-content-credentials.pdf</a><br />* \ud83d\uddbc slides: <a href=\"https://w3c.github.io/adapt/presentations/ac2024/\">https://w3c.github.io/adapt/presentations/ac2024/</a> Warning: the proposed use of .well-known therein is IMO a bad mistake. Unnecessary reinvention (most handled by existing rel values<a href=\"http://tantek.com/#t5WT1_note-14\">\u00b9\u2074</a>), more complex to author (requires sidefiles<a href=\"http://tantek.com/#t5WT1_note-15\">\u00b9\u2075</a>), harder to publish (requires site admin root access), likely to become inaccurate (Ruby\u2019s postulate<a href=\"http://tantek.com/#t5WT1_note-16\">\u00b9\u2076</a>), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post.<br />* \ud83d\uddd3 event: <a href=\"https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/\">https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/</a><br /><br />I\u2019ll update this list with additional resources as they are made publicly viewable.<br /><br />If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: <a href=\"https://www.w3.org/2024/04/AC/ac-agenda.html#monday\">https://www.w3.org/2024/04/AC/ac-agenda.html#monday</a><br /><br />References:<br /><br /><a href=\"http://tantek.com/#t5WT1_ref-1\">\u00b9</a> <a href=\"https://w3.org/wiki/AC\">https://w3.org/wiki/AC</a><br /><a href=\"http://tantek.com/#t5WT1_ref-2\">\u00b2</a> <a href=\"https://w3.org/wiki/AB\">https://w3.org/wiki/AB</a><br /><a href=\"http://tantek.com/#t5WT1_ref-3\">\u00b3</a> <a href=\"https://w3.org/wiki/Board\">https://w3.org/wiki/Board</a><br /><a href=\"http://tantek.com/#t5WT1_ref-4\">\u2074</a> <a href=\"https://www.w3.org/Consortium/Process/\">https://www.w3.org/Consortium/Process/</a><br /><a href=\"http://tantek.com/#t5WT1_ref-5\">\u2075</a> <a href=\"https://www.w3.org/2023/Process-20231103/#ACMeetings\">https://www.w3.org/2023/Process-20231103/#ACMeetings</a><br /><a href=\"http://tantek.com/#t5WT1_ref-6\">\u2076</a> <a href=\"https://w3.org/tag\">https://w3.org/tag</a><br /><a href=\"http://tantek.com/#t5WT1_ref-7\">\u2077</a> <a href=\"https://www.w3.org/groups/wg/\">https://www.w3.org/groups/wg/</a><br /><a href=\"http://tantek.com/#t5WT1_ref-8\">\u2078</a> <a href=\"https://chapters.w3.org/\">https://chapters.w3.org/</a><br /><a href=\"http://tantek.com/#t5WT1_ref-9\">\u2079</a> <a href=\"https://www.w3.org/invited-experts/#ac-observer\">https://www.w3.org/invited-experts/#ac-observer</a><br /><a href=\"http://tantek.com/#t5WT1_ref-10\">\u00b9\u2070</a> <a href=\"https://www.w3.org/wiki/TPAC\">https://www.w3.org/wiki/TPAC</a><br /><a href=\"http://tantek.com/#t5WT1_ref-11\">\u00b9\u00b9</a> <a href=\"https://www.w3.org/events/ac/2024/ac-2024/\">https://www.w3.org/events/ac/2024/ac-2024/</a><br /><a href=\"http://tantek.com/#t5WT1_ref-12\">\u00b9\u00b2</a> <a href=\"https://www.w3.org/membership/list/\">https://www.w3.org/membership/list/</a><br /><a href=\"http://tantek.com/#t5WT1_ref-13\">\u00b9\u00b3</a> <a href=\"https://en.wiktionary.org/wiki/hallway_track\">https://en.wiktionary.org/wiki/hallway_track</a><br /><a href=\"http://tantek.com/#t5WT1_ref-14\">\u00b9\u2074</a> <a href=\"https://microformats.org/wiki/existing-rel-values\">https://microformats.org/wiki/existing-rel-values</a><br /><a href=\"http://tantek.com/#t5WT1_ref-15\">\u00b9\u2075</a> <a href=\"https://indieweb.org/sidefile-antipattern\">https://indieweb.org/sidefile-antipattern</a><br /><a href=\"http://tantek.com/#t5WT1_ref-16\">\u00b9\u2076</a> <a href=\"https://intertwingly.net/slides/2004/devcon/68.html\">https://intertwingly.net/slides/2004/devcon/68.html</a>"
    },
    "author": {
        "type": "card",
        "name": "Tantek \u00c7elik",
        "url": "http://tantek.com/",
        "photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
    },
    "post-type": "note",
    "_id": "40838241",
    "_source": "1",
    "_is_read": false
}