FEED Validator

for Atom and RSS and KML

Congratulations!

This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 179, column 4: Use of unknown namespace: http://activitystrea.ms/spec/1.0/ (11 occurrences) [help]

    <object-type xmlns="http://activitystrea.ms/spec/1.0/">article</object-type>
    ^

line 184, column 125: The title attribute of link should not be blank (10 occurrences) [help]

... ="alternate" title="" type="text/html"/>
                                             ^

line 242, column 1559: div should not contain iframe tag [help]

... www.youtube.com/watch?v=qBLob0ObHMw</a> <iframe class="youtube-player au ...
                                             ^

Source: http://tantek.com/log/posts.atom

<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US">
<title>Tantek Çelik</title>
<link href="https://tantek.com/" rel="alternate" title="Tantek Çelik" type="text/html"/>
<link href="https://tantek.com/updates.atom" rel="self"/>
<link rel="hub" href="https://pubsubhubbub.superfeedr.com/"/>
<id>https://tantek.com/updates.atom</id>
<author>
<name>Tantek</name>
<uri>https://tantek.com/</uri>
</author>
<updated>2024-07-08T16:03:00-07:00</updated>
<entry>
<updated>2024-06-28T08:50:00-07:00</updated>
<published>2024-06-28T08:50:00-07:00</published>
<link href="https://tantek.com/2024/180/b1/responsible-inventing" rel="alternate" title="Responsible Inventing" type="text/html"/>
<id>https://tantek.com/2024/180/b1/responsible-inventing</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14">Responsible Inventing</div>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">
<div class="entry-content e-content">

I finally understand why
<a href="https://en.wikipedia.org/wiki/Milo_Rambaldi">Rambaldi</a>
may have hidden so many inventions.

<h2 id="ri-forecast">Forecast</h2>

When you invent something, you should forecast the impact of your invention in the current cultural (social, political, economic, belief systems) context, and if it
<ul>
<li> poses non trivial existential risk</li>
<li> or is likely to cause more harm than good</li>
</ul>
<h2 id="ri-shoulds">Shoulds</h2>

Then you should stop, and:

<ol>
<li id="ri-should-encrypt"> encrypt your work for a potentially better future context</li>
<li id="ri-should-shred"> or destroy your notes, ideally in a way that minimizes risk of detection of their deliberate destruction</li>
<li id="ri-should-avoid-detection"> and avoid any or any detectable use of your invention, because even the mere use of it may provide enough information for someone else to reinvent it who may not be as responsible. </li>
</ol>
<h2 id="ri-in-addition">In Addition</h2>

Insights and new knowledge are included in this meaning of “invention” and the guidance above.

Forecasting should consider both whether your invention could directly cause risk or more harm, or if it could be incorporated as a building block with other (perhaps yet to be invented) technologies to create risk or more harm.

<h2 id="ri-instead">Instead</h2>

Instead of continuing work on such inventions, shift your focus to:

<ol>
<li> work on other inventions</li>
<li> and document & understand how & why that current cultural context would contribute to existential risk or more harm than good</li>
<li> and work to improve, evolve that cultural context to reduce or eliminate its contribution to existential risk, and or its aspects that would (or already do) cause more harm than good</li>
</ol>
<h2 id="ri-da-vinci">Da Vinci</h2>

The
<a href="#ri-should-encrypt">Should (1)</a>
provides a plausible explanation for why
<a href="https://en.wikipedia.org/wiki/Leonardo_da_Vinci">Da Vinci</a>
“encrypted” his writings in
<a href="https://en.wikipedia.org/wiki/Mirror_writing#Notable_examples">mirror script</a>,
deliberately making it difficult for others to read (and thus remember or reproduce).
Per
<a href="ri-should-shred">Should (2)</a>
he also wrote in paper mediums of the time that were all destroyable,
and he may have been successful in destroying without detection,
since no one has found any evidence thereof, although such a lack of evidence is purely circumstantial and he may just as likely never destroyed any invention notes.

<h2 id="ri-precautions">Methods & Precautions</h2>

Learning from Da Vinci’s example within the context of the
<a href="#ri-shoulds">Shoulds</a>, we can infer additional methods and precautions to take when developing inventions:

<ul>
<li> do not write initial invention notes where others (people or bots) may read them (e.g. most online services) because their ability to transcribe or make copies prevents
<a href="ri-should-shred">Should (2)</a>.
Instead use something like paper notes which can presumably be shredded or burned if necessary, or keep your notes in your head.</li>
<li> do not use bound notebooks for initial invention notes because tearing out a page to destroy may be detectable by the bound remains left behind.
instead use individual sheets of paper organized into folders. perhaps eventually bind your papers into a notebook. Which apparently
<a href="https://en.wikipedia.org/wiki/Leonardo_da_Vinci#Journals_and_notes">Da Vinci did!</a>
<blockquote>“These notebooks – originally loose papers of different types and sizes…”</blockquote>
</li>
<li> consider developing a simple unique cipher you can actively use when writing which will at least inconvenience, reduce, or slow the readability of your notes. even better if you can develop a
<a href="https://en.wikipedia.org/wiki/Steganography">steganographic</a>
cipher, where an obvious reading of your invention writings provides a plausible but alternative meaning, thus hiding your actual invention writings in plain sight.
</li>
</ul>
<h2 id="ri-dream">Dream</h2>

Many of these insights came to me in a dream this morning, so clearly that I immediately wrote them down upon waking up, and continued writing extrapolations from the initial insights.

<h2 id="id-other-reading">Additional Reading</h2>

After writing down the above while it (and subsequent thoughts & deductions) were fresh in mind, and typing it up, I did a web search for “responsible inventing” for prior similar, related, or possibly of interest works and found:

<ul>
<li> IEEE Spectrum:
<a href="https://spectrum.ieee.org/what-does-responsible-innovation-mean">What Does “Responsible Innovation” Mean?</a></li>
<li> ResearchGate paper:
<a href="https://www.researchgate.net/publication/262864436_What_Is_Responsible_about_Responsible_Innovation_Understanding_the_Ethical_Issues">What Is “Responsible” about Responsible Innovation? Understanding the Ethical Issues</a></li>
<li> ScienceDirect paper:
<a href="https://www.sciencedirect.com/science/article/pii/S0048733313000930">Developing a framework for responsible innovation</a></li>
</ul>
<h2 id="ri-invent-future">Invent The Future</h2>

While this post encourages forecasting and other methods for avoiding unintended harmful impacts of inventions, I want to close by placing those precautions within an active positive context.


I believe it is the ultimate responsibility of an inventor to contribute, encourage, and actively create a positive vision of the future through their inventions. As
<a href="https://en.wikiquote.org/wiki/Alan_Kay#1970s">Alan Kay said</a>:

<blockquote>
“The best way to predict the future is to invent it.”
</blockquote>
<h2 id="responsible-inventing-comments" style="margin-top:1.5em">Comments</h2>
Comments curated from
<a href="https://indieweb.org/reply">replies on personal sites</a>
and
<a href="https://fed.brid.gy/web/tantek.com/notifications">federated replies</a>
that include thoughts, questions, and related reading
that contribute to the primary topic of the article.

<ol>
<li class="u-comment h-cite">
<a class="u-author h-card" href="https://paquita.masto.host/@crul">Crul</a>
at
<a class="u-url" href="https://paquita.masto.host/@crul/112698695985056254"><time class="dt-published">2024-06-29 00:20-07:00</time></a>:
<div class="p-content p-name">
Also related: Paul Virilio's concept of "The integral accident":
<a href="https://en.wikipedia.org/wiki/Paul_Virilio#The_integral_accident">en.wikipedia.org/wiki/Paul_Virilio#The_integral_accident</a>
</div>
</li>
<li class="u-comment h-cite">
<a class="u-author h-card" href="https://front-end.social/@kizu">Roma Komarov</a>
at
<a class="u-url" href="https://front-end.social/@kizu/112698823224979332"><time class="dt-published">2024-06-29 00:52-07:00</time></a>:
<div class="p-content p-name">
If some invention can pose a risk, should it be treated as a vulnerability?

Destroying/delaying an invention, in this case, could lead to it being re-invented and exploited in a different, less responsible, place.

Obviously, it doesn't mean that invention should be unleashed. But if it poses a risk, wouldn't it be more responsible to work on finding a way to minimize it, and, ideally, not alone?

There is probably no one good answer, and each case will be different.
</div>
</li>
<li class="u-comment h-cite">
<a class="u-author h-card" href="https://phpc.social/@lewiscowles1986">Lewis Cowles</a>
at
<a class="u-url" href="https://phpc.social/@lewiscowles1986/112700783578377159"><time class="dt-published">2024-06-29 09:11-07:00</time></a>:
<div class="p-content p-name">
I am unsure if it is always practical or possible, for an inventor to understand all the characteristics of their inventions and their impact beyond a very slim set of hops.

If things go well, I believe inventors can "believe their own hype", because they are human.

Questions: 
Is it a free pass if you make something awful and can't take it back? 
Would that make Ignorance a virtue?

This opens up many more problems, for both creators, and broader society.
</div>
</li>
</ol>
</div>
</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">article</object-type>
</entry>
<entry>
<updated>2024-06-24T21:31:00-07:00</updated>
<published>2024-06-24T21:31:00-07:00</published>
<link href="https://tantek.com/2024/176/t1/finished-broken-arrow-skyrace-23k" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/176/t1/finished-broken-arrow-skyrace-23k</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Finished my second Broken Arrow #Skyrace 23k<a id="t5Xd1_ref-1" href="#t5Xd1_note-1">¹</a> yesterday in 6:52:44! #RingDasBell This year’s #BrokenArrowSkyrace<a id="t5Xd1_ref-2" href="#t5Xd1_note-2">²</a> 23k was actually that distance! I ran 23.3km with 4557' vertical climb! In contrast, last year’s "23k" race<a id="t5Xd1_ref-3" href="#t5Xd1_note-3">³</a> was rerouted (due to weather conditions) last minute to two laps of the 11k course, where my actual distance was 18.87km with 4905' vert. I have been looking forward to this all year, to climbing the infamous "Stairway to Heaven" ladder to the top of Washeshu Peak (8885'/2692m elevation) for the first time (since last years’s race had to skip it). This year’s Broken Arrow is the start of the Mountain Running World Cup<a id="t5Xd1_ref-4" href="#t5Xd1_note-4">⁴</a>. It’s a rare sports event opportunity to compete with the best in the sport, to literally run the same trails they do, on the same day, with the same start (there are no waves), and finish line. Lots to write-up, for now, I’m grateful for the experience and accomplishment. Super grateful for everyone who came out to cheer and especially my coach whose training and guidance got me here. A few notes: Great lining up with so many friends. Hot day. Filled my ice bandana at the first aid station (Snow King) which made the rest possible. Steady hydration & fueling. Fueling timeline notes (times are my H:MM race clock times from the start) 0:00 start 1:45 ate Picky Bar 2:00 finished Tailwind in 500ml bottle 2:08 Snow King aid station, refilled bottles one with water and the other with mandarin Tailwind, filled ice bandana with ice, picked up a few Spring Energy gels 3:15 ate Awesome Sauce gel 3:45 ate Awesome Sauce gel ~4:30 left Siberia aid station with refilled ice bandana, bottles, a few Spring Snacks, ate potato chips, a watermelon slice, salt+nuun add to one water bottle, mandarin Tailwind in the other 5:05 ate Awesome Sauce gel 5:35 (-13:39) left Julia aid station with another Spring Energy gel 6:03 ate Awesome Sauce gel 6:52:44 finish Lots of incredible views along the way. The air was clean and quite breathable even nearing 9000'. Felt a bit slower but kept going within my capacity. Kept an eye on the time remaining before cut-off compared to my distance and vert climbing remaining and pushed steadily when I could. Finished with just over 7 minutes to spare before the official cut-off, to friends cheering on all sides. Saw and hugged my coach after ringing the bell at the finish. What an experience. #BrokenArrowSkyrace #trailRace #trailRun #trailRunner #runner #running #trailRunning <a id="t5Xd1_note-1" href="#t5Xd1_ref-1">¹</a> <a class="auto-link" href="https://www.brokenarrowskyrace.com/23k">https://www.brokenarrowskyrace.com/23k</a> <a id="t5Xd1_note-2" href="#t5Xd1_ref-2">²</a> <a class="auto-link" href="https://ultrasignup.com/register.aspx?did=106489">https://ultrasignup.com/register.aspx?did=106489</a> <a id="t5Xd1_note-3" href="#t5Xd1_ref-3">³</a> <a class="auto-link" href="https://tantek.com/2023/178/t1/june-trailrunner-ultrarunner">https://tantek.com/2023/178/t1/june-trailrunner-ultrarunner</a> <a id="t5Xd1_note-4" href="#t5Xd1_ref-4">⁴</a> <a class="auto-link" href="https://worldathletics.org/news/preview/mountain-running-world-cup-2024-opens-broken-arrow">https://worldathletics.org/news/preview/mountain-running-world-cup-2024-opens-broken-arrow</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-06-21T22:02:00-07:00</updated>
<published>2024-06-21T22:02:00-07:00</published>
<link href="https://tantek.com/2024/173/t1/years-posse-microformats-adoption" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/173/t1/years-posse-microformats-adoption</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Happy 12 years of <a class="auto-link" href="https://indieweb.org/POSSE">https://indieweb.org/POSSE</a> #POSSE and 19 years of <a class="auto-link" href="https://microformats.org/">https://microformats.org/</a> #microformats! (as of yesterday, the 20th) A few highlights from the past year: POSSE (Publish on your Own Site, Syndicate Elsewhere) has grown steadily as a common practice in the #IndieWeb community, personal sites, CMSs (like Withknown, which itself reached 10 years in May!), and services (like <a class="auto-link" href="https://micro.blog">https://micro.blog</a>) for over a decade. In its 12th year, POSSE broke through to broader technology press and adoption beyond the community. For example: * David Pierce’s (<a class="auto-link" href="https://mas.to/@pierce">@pierce@mas.to</a>) excellent article <a class="auto-link" href="https://TheVerge.com">@TheVerge.com</a> (<a class="auto-link" href="https://mastodon.social/@verge">@verge@mastodon.social</a>): “The poster’s guide to the internet of the future” (<a class="auto-link" href="https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon">https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon</a>): “Your post appears natively on all of those platforms, typically with some kind of link back to your blog. And your blog becomes the hub for everything, your main home on the internet. Done right, POSSE is the best of all posting worlds.” * David also recorded a 29 minute podcast on POSSE with some great interviews: <a class="auto-link" href="https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014">https://podcasts.apple.com/us/podcast/the-posters-guide-to-the-new-internet/id430333725?i=1000632256014</a> * Cory Doctorow (<a class="auto-link" href="https://craphound.com">@craphound.com</a> <a class="auto-link" href="https://mamot.fr/@doctorow">@doctorow@mamot.fr</a>) declared in his Pluralistic blog (<a class="auto-link" href="https://pluralisticmamot.fr">@pluralisticmamot.fr</a>) post: “Vice surrenders” (<a class="auto-link" href="https://pluralistic.net/2024/02/24/anti-posse/">https://pluralistic.net/2024/02/24/anti-posse/</a>): “This is the moment for POSSE (Post Own Site, Share Everywhere [sic]), a strategy that sees social media as a strategy for bringing readers to channels that you control” * And none other than Molly White (<a class="auto-link" href="https://mollywhite.net">@mollywhite.net</a> <a class="auto-link" href="https://hachyderm.io/@molly0xfff">@molly0xfff@hachyderm.io</a>) of <a class="auto-link" href="https://web3isgoinggreat.com">@web3isgoinggreat.com</a> (<a class="auto-link" href="https://indieweb.social/@web3isgreat">@web3isgreat@indieweb.social</a>) built, deployed, and started actively using her own POSSE setup as described in her post titled “POSSE” (<a class="auto-link" href="https://www.mollywhite.net/micro/entry/202403091817">https://www.mollywhite.net/micro/entry/202403091817</a>) to: "… write posts in the microblog and automatically crosspost them to Twitter/Mastodon/Bluesky, while keeping the original post on my site." Congrats Molly and well done! In its 19th year, the microformats formal #microformats2 syntax and popular vocabularies h-card, h-entry, and h-feed, kept growing across IndieWeb (micro)blogging services and software like CMSs & SSGs both for publishing, and richer peer-to-peer social web interactions via #Webmention. Beyond the IndieWeb, the rel=me microformat, AKA #relMe, continues to be adopted by services to support #distributed #verification, such as these in the past year: * Meta Platforms #Threads user profile "Link" field<a id="t5Xa1_ref-1" href="#t5Xa1_note-1">¹</a> * #Letterboxd user profile website field<a id="t5Xa1_ref-2" href="#t5Xa1_note-2">²</a> For both POSSE and microformats, there is always more we can do to improve their techniques, technologies, and tools to help people own their content and identities online, while staying connected to friends across the web. Got suggestions for this coming year? Join us in chat: * <a class="auto-link" href="https://chat.indieweb.org/dev">https://chat.indieweb.org/dev</a> * <a class="auto-link" href="https://chat.indieweb.org/microformats">https://chat.indieweb.org/microformats</a> for discussions about POSSE and microformats, respectively. Previously: <a class="auto-link" href="https://tantek.com/2023/171/t1/anniversaries-microformats-posse">https://tantek.com/2023/171/t1/anniversaries-microformats-posse</a> This is post 15 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2024/151/t1/minimum-interesting-service-worker">https://tantek.com/2024/151/t1/minimum-interesting-service-worker</a> → 🔮 Post glossary: CMS <a class="auto-link" href="https://indieweb.org/CMS">https://indieweb.org/CMS</a> h-card <a class="auto-link" href="https://microformats.org/wiki/h-card">https://microformats.org/wiki/h-card</a> h-entry <a class="auto-link" href="https://microformats.org/wiki/h-entry">https://microformats.org/wiki/h-entry</a> h-feed <a class="auto-link" href="https://microformats.org/wiki/h-feed">https://microformats.org/wiki/h-feed</a> microformats2 syntax <a class="auto-link" href="https://microformats.org/wiki/microformats2-parsing">https://microformats.org/wiki/microformats2-parsing</a> rel-me <a class="auto-link" href="https://microformats.org/wiki/rel-me">https://microformats.org/wiki/rel-me</a> SSG <a class="auto-link" href="https://indieweb.org/SSG">https://indieweb.org/SSG</a> Webmention <a class="auto-link" href="https://indieweb.org/Webmention">https://indieweb.org/Webmention</a> Withknown <a class="auto-link" href="https://indieweb.org/Known">https://indieweb.org/Known</a> References: <a id="t5Xa1_note-1" href="#t5Xa1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me">https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me</a> <a id="t5Xa1_note-2" href="#t5Xa1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/rel-me#Letterboxd">https://indieweb.org/rel-me#Letterboxd</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-05-30T11:21:00-07:00</updated>
<published>2024-05-30T11:21:00-07:00</published>
<link href="https://tantek.com/2024/151/t1/minimum-interesting-service-worker" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/151/t1/minimum-interesting-service-worker</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Yesterday I proposed the idea of a “minimum interesting service worker” that could provide a link (or links) to archives or mirrors when your site was unavailable as one possible solution to the desire to make personal #indieweb sites more reliable by providing at least a user path to “soft repair” links to your site that may otherwise seem broken. Minimum because it only requires two files and one line of script in site footer template, and interesting because it provides both a novel user benefit and personal site publisher benefits. The idea occurred to me during an informal coffee chat over Zoom with a couple of other Indieweb community folks yesterday, and afterwards I braindumped a bit into the IndieWeb Developers Chat channel<a id="t5XD1_ref-1" href="#t5XD1_note-1">¹</a>. Figured it was worth writing up rather than waiting to implement it. Basic idea: You have a service worker (and “offline” HTML page) on your personal site, installed from any page on your site, that all it does is cache the offline page, and on future requests to your site checks to see if the requested page is available, and if so serves it, otherwise it displays your offline page with a “site appears to be unreachable” message that a lot of service workers provide, AND provides an algorithmically constructed link to the page on an archive (e.g. Internet Archive) or static mirror of your site (typically at another domain). This is minimal because it requires only two files: your service worker (a JS file) and your offline page (a minimal self-contained static HTML file with inline CSS). Doable in <1k bytes of code, with no additional local caching or storage requirements, thus a negligible impact on site visitors (likely less than the cookies that major sites store). User benefit: If someone has ever visited your personal site, then in the future whenever they click a link to your pages or posts, if your site/domain is unavailable for any reason, then the reader would see a notice (from your offline page) and a link to view an archive/mirror copy instead, thus providing a one-click ability for the reader to “soft-repair” any otherwise apparently broken links to your site. Personal site publisher benefits: Having such a service worker that automatically provides your readers links to where they can view your content on an archive or mirror means you can go on vacation or otherwise step away from your personal site, knowing that if it does go down, (at least prior) site visitors will still have a way to click-through and view your published content. Additional enhancements: Ideally any archive or mirror copies would use rel=canonical to link back to the page on your domain, so any crawlers or search engines could automatically prefer your original page, or browsers could offer the user a choice to “View original”. You can do that by including a rel=canonical link in all your original pages, so when they are archived or mirrored, those copies automatically include a rel=canonical link back to your original page or post. The simplest implementation would be to ping the Internet Archive to save<a id="t5XD1_ref-2" href="#t5XD1_note-2">²</a> your page or post upon publishing it. You could also add code to your site to explicitly generate a static mirror of your pages, perhaps with an SSG or crawler like Spiderpig, to a GitHub repo, which is then auto-served as GitHub static pages, perhaps on its own domain yet at the same paths as your original pages (to make it trivial to generate such mirror links automatically). If you’re using links to the Internet Archive, you can generate them automatically by prefixing your page URL with <a class="auto-link" href="https://web.archive.org/web/*/">https://web.archive.org/web/*/</a> e.g. this post: <a class="auto-link" href="https://web.archive.org/web/*/https://tantek.com/2024/151/t1/minimum-interesting-service-worker">https://web.archive.org/web/*/https://tantek.com/2024/151/t1/minimum-interesting-service-worker</a> Possible generic library: It may be possible to write this minimum interesting service worker (e.g. misv.js) as a generic (rather than site-specific) service worker that literally anyone with a personal site could “install” as is (a JS file, an HTML file, and a one-line script tag in their site-wide footer) and it would figure everything out from the context it is running in, unchanged (zero configuration necessary). This is post 14 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton">https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton</a> → <a class="auto-link" href="https://tantek.com/2024/173/t1/years-posse-microformats-adoption">https://tantek.com/2024/173/t1/years-posse-microformats-adoption</a> Post glossary: GitHub static pages <a class="auto-link" href="https://indieweb.org/GitHub_Pages">https://indieweb.org/GitHub_Pages</a> HTML <a class="auto-link" href="https://indieweb.org/HTML">https://indieweb.org/HTML</a> JS <a class="auto-link" href="https://indieweb.org/js">https://indieweb.org/js</a> rel-canonical <a class="auto-link" href="https://indieweb.org/rel-canonical">https://indieweb.org/rel-canonical</a> service worker <a class="auto-link" href="https://indieweb.org/service_worker">https://indieweb.org/service_worker</a> Spiderpig <a class="auto-link" href="https://indieweb.org/Spiderpig">https://indieweb.org/Spiderpig</a> SSG <a class="auto-link" href="https://indieweb.org/SSG">https://indieweb.org/SSG</a> References: <a id="t5XD1_note-1" href="#t5XD1_ref-1">¹</a> <a class="auto-link" href="https://chat.indieweb.org/dev/2024-05-29#t1717006352142600">https://chat.indieweb.org/dev/2024-05-29#t1717006352142600</a> <a id="t5XD1_note-2" href="#t5XD1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/Internet_Archive#Trigger_an_Archive">https://indieweb.org/Internet_Archive#Trigger_an_Archive</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-05-29T19:00:00-07:00</updated>
<published>2024-05-29T19:00:00-07:00</published>
<link href="https://tantek.com/2024/150/t1/ran-baytobreakers" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/150/t1/ran-baytobreakers</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Ran my 12th #BayToBreakers race in 1:59:54 on Sunday 2024-05-19. After a comedy of transit struggles to get to the start line, I jumped in with Corral C runners (my bib was for Corral B) and started with them. Great seeing the Midnight Runners crab rave cheer gang in Hayes Valley before Hayes Hill. Made it into Golden Gate Park, and eventually saw Vivek and David Lam making their way back from the finish. Just before the bison paddock, I saw Paddy & Eleanor walking back as well, and stopped to briefly chat with them. Soon after I saw Adrienne and a few other #NPSF pals running and as they stopped to say hi to Paddy, I took off to go finish. Adrienne and friends caught up to me on the last segment before Ocean Beach, and decided to run together. After turning the corner onto Great Highway, I could see the finish line. Glancing down at my watch there seemed to be enough time to finish under 2 hours if we picked it up. I asked Adrienne if we could try for a sub-2 hour time and she said to go for it. We picked up the pace and after crossing the finish line I stopped my Garmin — it read 1:59:54. Oddly the official Bay to Breakers results (which are not at a linkable URL) showed 2:00:07. The only explanation I have is after the first timing strip after the finish line where I stopped my watch, there was a big crowd of loitering people that made it hard to keep moving, and cross a second timing strip. It is possible the first timing strip did not register my bib chip, and only the second timing strip picked it up. I have emailed Bay to Breakers to see if they can correct it, and included a link to my Strava activity that shows I recorded the entire race on my watch. It was a harder race than usual, despite the good weather. There were a few things that contributed. First, I had run each of the prior two days: 5km+ at Friday night’s Midnight Runners 5th anniversary run and run/walk celebration afterwards totaling ~5 miles, and then 6.5 miles at SFRC on the trails on Saturday. I slept reasonably well the night before the race, and having checked the news announcements about the availability of transit options in the morning, planned accordingly. When I checked the actual train arrival times, none of the MUNI trains that were supposed to be running were running. I ran down to take the MUNI bus which was supposed to go downtown, except it stopped at Van Ness avenue, inexplicably, and the driver told everyone it was the last stop. Admittedly I was already annoyed that SF MUNI for some reason decided to stop the MUNI trains the morning of Bay to Breakers that could easily have taken thousands of runners to near the race start at Embarcadero via the Market Street subway. Having the bus stop sooner than expected was a second disappointment and discouragement. I (and many other runners) decided to run towards the start, which was still ~2 miles away at that point. Upon reaching the Civic Center station on Market street, we realized from the street level displays that BART trains appeared to be running normally like any other Sunday, so we went downstairs and paid for a second transit ticket to take the BART a few stops. The BART train was full of costumed Bay to Breakers runners. Disembarking at the Embarcadero station, I jogged/ran the rest of the way around the entrance corral maze to the right spot for Corral B entrants, and joined the group waiting at the start line. Lessons learned: I am not trusting MUNI rail or bus into downtown on Bay to Breakers race day again, despite any announcements from SFMTA. Too many years of bad experiences. However, BART seems reliable so I plan to find my way to taking BART in the future. Perhaps by taking a bus to the 16th street BART station, avoiding all street closures. Having missed my start corral due to the transit mishaps, I didn’t see anyone else I knew. The combination of being annoyed at MUNI’s unreliability (both in what was announced vs what was running and premature bus termination) and starting in a crowd not knowing anyone took my motivation down several notches. Still, the weather was pleasant yet cool, ideal for a race so I ran a pace that felt good for me, and kept an eye out for friends along the course. I stopped after mile 1 for a portapotty pitstop. Back in the chaos of Howard street and then Ninth to Hayes, I saw a few folks I knew from a distance. Seeing and high-fiving the Midnight Runners crab race cheer crew at Hayes Hill turned my mood around though, and I enjoyed the rest of the race, from Hayes Hill through Golden Gate Park. It was my slowest Bay to Breakers yet, however first in a while that I finished with friends! After we grabbed our medals and snacks in the finish area, I hiked/jogged back to the Panhandle, found the Midnight Runners crab rave crew keeping the party going and joined in. 2023: <a class="auto-link" href="https://tantek.com/2023/157/t1/ran-baytobreakers">https://tantek.com/2023/157/t1/ran-baytobreakers</a> #2024_140 #SanFrancisco #run #runner #race #roadrace #b2b #bay2breakers</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-05-18T17:07:00-07:00</updated>
<published>2024-05-18T17:07:00-07:00</published>
<link href="https://tantek.com/2024/139/t1/indiewebcamp-dusseldorf-btconf-inspiration" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/139/t1/indiewebcamp-dusseldorf-btconf-inspiration</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Still sitting with the awesomeness that was this past week and weekend’s 1-2 combination of: #IndieWebCamp Düsseldorf — <a class="auto-link" href="https://indieweb.org/2024/DUS">https://indieweb.org/2024/DUS</a> #btconf Düsseldorf — <a class="auto-link" href="https://beyondtellerrand.com/events/dusseldorf-2024">https://beyondtellerrand.com/events/dusseldorf-2024</a> Great seeing old friends and meeting new amazing people as well. So many thoughtful inspiring conversations germinating new ideas for creative projects. Took lots of photos and notes. We recorded all the IndieWebCamp day 1 #BarCamp style breakout sessions, and I believe all the Beyond Tellerand talks were recorded as well. I’m looking forward to rewatching the sessions and talks and reconnecting with all the ideas and open tabs in my browser. Aside: this past Tuesday, the second day of the 2024 Beyond Tellerand talks, was also the five year anniversary of my closing talk at btconf DUS 2019: _Take Back Your Web_ (<a class="auto-link" href="https://www.youtube.com/watch?v=qBLob0ObHMw">https://www.youtube.com/watch?v=qBLob0ObHMw</a> <iframe class="youtube-player auto-embed figure" width="480" height="385" style="border:0" src="https://www.youtube.com/embed/qBLob0ObHMw"/>)</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-05-10T04:51:00-07:00</updated>
<published>2024-05-10T04:51:00-07:00</published>
<link href="https://tantek.com/2024/131/t1/mozilla-origin-trials" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/131/t1/mozilla-origin-trials</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">For #webDevelopers who like to try out pre-release features in #browsers, in addition to the numerous #Firefox experimental features which everyone has access to in Nightly Builds (as documented by MDN<a id="t5Wt1_ref-1" href="#t5Wt1_note-1">¹</a>) did you know that #Mozilla also has Origin Trials? Instructions and how to participate on the Mozilla Wiki: <a class="auto-link" href="https://wiki.mozilla.org/Origin_Trials">https://wiki.mozilla.org/Origin_Trials</a> In addition, we’ve linked to the #originTrial documentation pages of #GoogleChrome and #MicrosoftEdge if you want to check those out. Linkbacks welcome of course. #webDev #originTrials #webBrowser #webBrowsers References: <a id="t5Wt1_note-1" href="#t5Wt1_ref-1">¹</a> <a class="auto-link" href="https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features">https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-04-29T18:53:00-07:00</updated>
<published>2024-04-29T18:53:00-07:00</published>
<link href="https://tantek.com/2024/120/t1/library-of-infinite-loan" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/120/t1/library-of-infinite-loan</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">The Library of Infinite Loan is a physical world practice I conceived of many many years ago<a id="t5Wh1_ref-1" href="#t5Wh1_note-1">¹</a>, implemented in minimal prototype form 5+ years ago<a id="t5Wh1_ref-2" href="#t5Wh1_note-2">²</a>, shared a summary with the #IndieWeb community at least four years ago at #IndieWebCamp Austin in 2020<a id="t5Wh1_ref-3" href="#t5Wh1_note-3">³</a> and last year in IndieWeb chat<a id="t5Wh1_ref-4" href="#t5Wh1_note-4">⁴</a>, so it’s about time<a id="t5Wh1_ref-5" href="#t5Wh1_note-5">⁵</a> I wrote it down. Summary: lend a #book from your personal library<a id="t5Wh1_ref-6" href="#t5Wh1_note-6">⁶</a> to a friend, on the conditions that they do not donate sell or dispose of it, and instead when they are done with it they return it or lend it to someone else who agrees to these conditions. My goal was to create a book lending system that: * preserves books — effectively in a giant #distributed communal #library * makes lending easier fiscally, psychologically, emotionally for both parties * encourages direct person-to-person lending without intermediaries * grows a culture of non-zero-sum sharing, preservation, and longterm thinking The basic steps to create a Library of Infinite Loan: 1. Create a separate space (like a particular bookshelf) for #books to infinite lend. A small shelf in a guest room or common space like a hallway works well. 2. Move books there that you are ok lending out and never seeing again 3. Label that space your “Library of Infinite Loan”, or invite guests to borrow from your “Library of Infinite Loan” 4. When visitors ask what that means, explain the Rules Rules for borrowing from a Library of Infinite Loan (“the Rules”) 1. Keep it as long as you like 2. Do not sell donate or otherwise dispose of it 3. You may give it a. back to the person you borrowed from b. or back to its original purchaser if they wrote their name and web address inside c. or (lend it) to someone else who agrees to the Rules There are several ways to extend / expand the Library of Infinite Loan: * custom book plate: design a custom book plate for yourself with room for your name (and web address) on it e.g. “From Tantek’s (<a class="auto-link" href="https://tantek.com">@tantek.com</a>) Library” (with space), print it on longterm adhesive paper, and place it inside new books you purchase. When you move a book to your Library of Infinite Loan, amend the book plate to say ”… Library of Infinite Loan” and attach a copy of the Rules. * add a “borrowers log” with blank lines for anyone you lend it to or they lend it to, transitively, to optionally add their name, web address, and a date of borrowing. Then amend the rules to allow returning a book to who you borrowed from or anyone in the borrower log or original purchaser. * more media: CDs, vinyl records, DVDs, LaserDiscs, VHS, cassette tapes, video game cartridges etc. * other things * large tools — which usually come in a box with instruction manual, so there’s a logical place to put an “owners plate”, “borrowers log”, and copy of the rules. * artwork — a great way to rotate art among a community This is what I remember off the top of my head and with a little web searching. I know I have a bunch more notes in various places of my thoughts (and conversations) over the years about a Library of Infinite Loan. As I find those notes, I’ll post them as well. #infiniteLoan #libraryOfInfiniteLoan References: <a id="t5Wh1_note-1" href="#t5Wh1_ref-1">¹</a> I’m looking through old personal logs for earliest mentions of “infinite loan” <a id="t5Wh1_note-2" href="#t5Wh1_ref-2">²</a> In my 2019 personal log I found a note that I “moved some books as library of infinite loan to guest room” where I had previously setup a small bookshelf for such books. <a id="t5Wh1_note-3" href="#t5Wh1_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/2020/Austin/reading">https://indieweb.org/2020/Austin/reading</a> <a id="t5Wh1_note-4" href="#t5Wh1_ref-4">⁴</a> <a class="auto-link" href="https://chat.indieweb.org/2023-10-01#t1696202307311300">https://chat.indieweb.org/2023-10-01#t1696202307311300</a> <a id="t5Wh1_note-5" href="#t5Wh1_ref-5">⁵</a> I was also inspired by sharing the idea again to a couple of friends in an espresso-making livestream this morning <a id="t5Wh1_note-6" href="#t5Wh1_ref-6">⁶</a> <a class="auto-link" href="https://indieweb.org/personal_library">https://indieweb.org/personal_library</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-04-18T20:20:00-07:00</updated>
<published>2024-04-18T20:20:00-07:00</published>
<link href="https://tantek.com/2024/109/t1/published-vision-for-w3c" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/109/t1/published-vision-for-w3c</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Recently <a class="auto-link" href="https://W3.org">@W3.org</a> (<a class="auto-link" href="https://w3c.social/@w3c">@w3c@w3c.social</a>) published the first Group Note of the Vision for W3C: <a class="auto-link" href="https://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/">https://www.w3.org/TR/2024/NOTE-w3c-vision-20240403/</a> I’m the current editor of the Vision for W3C and helped get it across the line this year to reach #w3cAB (W3C Advisory Board <a class="auto-link" href="https://w3c.social/@ab">@ab@w3c.social</a>) consensus to publish as an official Group Note, the first official Note that the AB (Advisory Board) has ever published. I’m very proud of this milestone, as I and a few others including many on the AB<a id="t5WX1_ref-1" href="#t5WX1_note-1">¹</a>, have been working on it for a few years in various forms, and with the broader W3C Vision TF<a id="t5WX1_ref-2" href="#t5WX1_note-2">²</a> (Task Force) for the past year. W3C also recently announced the Vision for W3C in their news feed: <a class="auto-link" href="https://www.w3.org/news/2024/group-note-vision-for-w3c/">https://www.w3.org/news/2024/group-note-vision-for-w3c/</a> One of the key goals of this document was to capture the spirit of why we are at #W3C and our shared values & principles we use to guide our work & decisions at W3C. If you work with any groups at W3C, anything from a Community Group (CG) to a Working Group (WG), I highly recommend you read this document from start to finish. See what resonates with you, if there is anything that doesn’t sound right to you, or if you see anything missing that you feel exemplifies the best of what W3C is, please file an issue or a suggestion: <a class="auto-link" href="https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22Project+Vision%22+-label%3ADefer">https://github.com/w3c/AB-public/issues?q=is%3Aissue+is%3Aopen+label%3A%22Project+Vision%22+-label%3ADefer</a> Check that list to see if your concerns or suggestions are already captured, and if so, add an upvote or comment accordingly. Our goal is to eventually publish this document as an official W3C Statement, with the consensus of the entire #w3cAC (W3C Advisory Committee). One key aspect which the Vision touches on but perhaps too briefly is what I see as the fundamental purpose of why we do the work we do at W3C, which in my opinion is: To create & facilitate user-first interoperable standards that improve the web for humanity The Vision does mention “#interoperable” explicitly as part of our Vision for the Web in <a class="auto-link" href="https://w3c.github.io/AB-public/Vision#vision-web">https://w3c.github.io/AB-public/Vision#vision-web</a>: ”There is one interoperable world-wide Web.” The Vision also mentions “#interoperability” explicitly in our Operational Principles <a class="auto-link" href="https://w3c.github.io/AB-public/Vision#op-principles">https://w3c.github.io/AB-public/Vision#op-principles</a>: “Interoperability: We verify the fitness of our specifications through open test suites and actual implementation experience, because we believe the purpose of standards is to enable independent interoperable implementations.” These are both excellent, and yet, I think we can do better, with adding some sort of explicit statement between those two about that “We will” create & facilitate user-first interoperable standards that improve the web for humanity. In the coming weeks I’ll be reflecting how we (the VisionTF) can incorporate that sort of imperative “We will” statement about interoperable standards into the Vision for W3C, as well as working with the AB and W3C Team on defining a succinct updated mission & purpose for W3C based on that sort of input and more. In a related effort, I have also been leading the AB’s “3Is Priority Project<a id="t5WX1_ref-3" href="#t5WX1_note-3">³</a>” (Interoperability and the Role of Independent Implementations), which is a pretty big project to define and clarify what each of those three Is mean, with respect to each other and Incubation, which is its own Priority Project<a id="t5WX1_ref-4" href="#t5WX1_note-4">⁴</a>. As part of the 3Is project, the first “I” I’ve been focusing on has unsurprisingly been “Interoperable”. As with other #OpenAB projects, our work on understanding interoperability, its aspects, and defining what do we mean by interoperable is published and iterated on the W3C’s public wiki: <a class="auto-link" href="https://www.w3.org/wiki/Interoperable">https://www.w3.org/wiki/Interoperable</a> This is still a work in progress, however it’s sufficiently structured to take a look if interoperability is something you care about or have opinions about. In particular, if you know of definitions of interoperable or interoperability that resonate and make sense to you, or articles or blog posts about interoperability that explore various aspects, I am gathering such references so we can make sure the W3C’s definition of interoperable is both well-stated, and clearly reflects a broader industry understanding of interoperability. References: <a id="t5WX1_note-1" href="#t5WX1_ref-1">¹</a> <a class="auto-link" href="https://www.w3.org/TR/w3c-vision/#acknowledgements">https://www.w3.org/TR/w3c-vision/#acknowledgements</a> <a id="t5WX1_note-2" href="#t5WX1_ref-2">²</a> <a class="auto-link" href="https://www.w3.org/wiki/AB/VisionTF">https://www.w3.org/wiki/AB/VisionTF</a> <a id="t5WX1_note-3" href="#t5WX1_ref-3">³</a> <a class="auto-link" href="https://www.w3.org/wiki/AB/2024_Priorities#Interoperability_and_the_Role_of_Independent_Implementations">https://www.w3.org/wiki/AB/2024_Priorities#Interoperability_and_the_Role_of_Independent_Implementations</a> <a id="t5WX1_note-4" href="#t5WX1_ref-4">⁴</a> <a class="auto-link" href="https://www.w3.org/wiki/AB/2024_Priorities#Incubation">https://www.w3.org/wiki/AB/2024_Priorities#Incubation</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-04-14T19:00:00-07:00</updated>
<published>2024-04-14T19:00:00-07:00</published>
<link href="https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/105/t1/w3c-advisory-committee-meetings</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Last week I participated <a class="auto-link" href="https://W3.org">@W3.org</a> (<a class="auto-link" href="https://w3c.social/@w3c">@w3c@w3c.social</a>) #w3cAC (W3C Advisory Committee<a id="t5WT1_ref-1" href="#t5WT1_note-1">¹</a>), #w3cAB (W3C Advisory Board<a id="t5WT1_ref-2" href="#t5WT1_note-2">²</a> <a class="auto-link" href="https://w3c.social/@ab">@ab@w3c.social</a>), and #w3cBoard (Board of the W3C Corporation<a id="t5WT1_ref-3" href="#t5WT1_note-3">³</a>) meetings in Hiroshima, Japan. 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 #w3cTAG), then separate meetings to focus on their own tasks & discussions. The W3C Process<a id="t5WT1_ref-4" href="#t5WT1_note-4">⁴</a> describes the twice a year AC (Advisory Committee) Meetings<a id="t5WT1_ref-5" href="#t5WT1_note-5">⁵</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 id="t5WT1_ref-6" href="#t5WT1_note-6">⁶</a> <a class="auto-link" href="https://w3c.social/@tag">@tag@w3c.social</a>), Working Group<a id="t5WT1_ref-7" href="#t5WT1_note-7">⁷</a> chairs, Chapter<a id="t5WT1_ref-8" href="#t5WT1_note-8">⁸</a> staff, and this time also a W3C Invited Expert designated observer<a id="t5WT1_ref-9" href="#t5WT1_note-9">⁹</a>. The AC currently meets in the Spring on its own and at a shorter meeting in the Fall as part of the annual #w3cTPAC (W3C Technical Plenary and Advisory Committee<a id="t5WT1_ref-10" href="#t5WT1_note-10">¹⁰</a> meetings). The existence, dates, and location of the event are public<a id="t5WT1_ref-11" href="#t5WT1_note-11">¹¹</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 & navigation (if you work for a W3C Member Organization<a id="t5WT1_ref-12" href="#t5WT1_note-12">¹²</a>): * <a class="auto-link" href="https://www.w3.org/wiki/AC/Meetings#2024_Spring">https://www.w3.org/wiki/AC/Meetings#2024_Spring</a> 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. Myself 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. Aside: 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: <a class="auto-link" href="https://www.w3.org/wiki/AB#Open_AB">https://www.w3.org/wiki/AB#Open_AB</a> Like most conferences, I got as much out of side conversations at breaks (AKA hallway track<a id="t5WT1_ref-13" href="#t5WT1_note-13">¹³</a>) and meals as I did from scheduled talks and panels. For now, here are the events, slides, and videos which are publicly viewable that provide an interesting glimpse into some of the topics discussed: * 📄 report: <a class="auto-link" href="https://www.w3.org/reports/ai-web-impact/">https://www.w3.org/reports/ai-web-impact/</a> * 🖼 slides: <a class="auto-link" href="https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/">https://www.w3.org/2024/Talks/ac-slides/engaging-the-members/</a> * 🖼 slides: <a class="auto-link" href="https://www.w3.org/2024/Talks/ac-slides/exploration/">https://www.w3.org/2024/Talks/ac-slides/exploration/</a> * 🖼 slides: <a class="auto-link" href="https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf">https://www.w3.org/2024/Talks/ac-slides/OHCHR.pdf</a> * ▶️ video 5m42s: <a class="auto-link" href="https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/9ad1e01b20d9b15d413f02c0ada3fe34/watch</a> * ▶️ video 4m16s: <a class="auto-link" href="https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch">https://customer-0kix77mxh2zzzae0.cloudflarestream.com/1bfde2bf614d7535b8a775217a949974/watch</a> * 🗓 event: <a class="auto-link" href="https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/">https://www.w3.org/events/meetings/13213a52-8159-4af8-b939-38c7880ba266/</a> * 🖼 slides: <a class="auto-link" href="https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/">https://www.w3.org/2024/Talks/ac-slides/lt-deepfake/</a> * 🖼 slides: <a class="auto-link" 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> * 🖼 slides: <a class="auto-link" 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 #IndieWeb mention) * 🖼 slides: <a class="auto-link" 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> * 🖼 slides: <a class="auto-link" 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 id="t5WT1_ref-14" href="#t5WT1_note-14">¹⁴</a>), more complex to author (requires sidefiles<a id="t5WT1_ref-15" href="#t5WT1_note-15">¹⁵</a>), harder to publish (requires site admin root access), likely to become inaccurate (Ruby’s postulate<a id="t5WT1_ref-16" href="#t5WT1_note-16">¹⁶</a>), and fragile (site admins frequently break .well-known for individual pages). A full critique likely requires its own blog post. * 🗓 event: <a class="auto-link" href="https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/">https://www.w3.org/events/meetings/df0b9dd8-2356-47ec-839d-eadc06da1ca1/</a> I’ll update this list with additional resources as they are made publicly viewable. If you work for a W3C Member Organization you can view the full list of resources linked from the Member-confidential agenda: <a class="auto-link" href="https://www.w3.org/2024/04/AC/ac-agenda.html#monday">https://www.w3.org/2024/04/AC/ac-agenda.html#monday</a> References: <a id="t5WT1_note-1" href="#t5WT1_ref-1">¹</a> <a class="auto-link" href="https://w3.org/wiki/AC">https://w3.org/wiki/AC</a> <a id="t5WT1_note-2" href="#t5WT1_ref-2">²</a> <a class="auto-link" href="https://w3.org/wiki/AB">https://w3.org/wiki/AB</a> <a id="t5WT1_note-3" href="#t5WT1_ref-3">³</a> <a class="auto-link" href="https://w3.org/wiki/Board">https://w3.org/wiki/Board</a> <a id="t5WT1_note-4" href="#t5WT1_ref-4">⁴</a> <a class="auto-link" href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a> <a id="t5WT1_note-5" href="#t5WT1_ref-5">⁵</a> <a class="auto-link" href="https://www.w3.org/2023/Process-20231103/#ACMeetings">https://www.w3.org/2023/Process-20231103/#ACMeetings</a> <a id="t5WT1_note-6" href="#t5WT1_ref-6">⁶</a> <a class="auto-link" href="https://w3.org/tag">https://w3.org/tag</a> <a id="t5WT1_note-7" href="#t5WT1_ref-7">⁷</a> <a class="auto-link" href="https://www.w3.org/groups/wg/">https://www.w3.org/groups/wg/</a> <a id="t5WT1_note-8" href="#t5WT1_ref-8">⁸</a> <a class="auto-link" href="https://chapters.w3.org/">https://chapters.w3.org/</a> <a id="t5WT1_note-9" href="#t5WT1_ref-9">⁹</a> <a class="auto-link" href="https://www.w3.org/invited-experts/#ac-observer">https://www.w3.org/invited-experts/#ac-observer</a> <a id="t5WT1_note-10" href="#t5WT1_ref-10">¹⁰</a> <a class="auto-link" href="https://www.w3.org/wiki/TPAC">https://www.w3.org/wiki/TPAC</a> <a id="t5WT1_note-11" href="#t5WT1_ref-11">¹¹</a> <a class="auto-link" href="https://www.w3.org/events/ac/2024/ac-2024/">https://www.w3.org/events/ac/2024/ac-2024/</a> <a id="t5WT1_note-12" href="#t5WT1_ref-12">¹²</a> <a class="auto-link" href="https://www.w3.org/membership/list/">https://www.w3.org/membership/list/</a> <a id="t5WT1_note-13" href="#t5WT1_ref-13">¹³</a> <a class="auto-link" href="https://en.wiktionary.org/wiki/hallway_track">https://en.wiktionary.org/wiki/hallway_track</a> <a id="t5WT1_note-14" href="#t5WT1_ref-14">¹⁴</a> <a class="auto-link" href="https://microformats.org/wiki/existing-rel-values">https://microformats.org/wiki/existing-rel-values</a> <a id="t5WT1_note-15" href="#t5WT1_ref-15">¹⁵</a> <a class="auto-link" href="https://indieweb.org/sidefile-antipattern">https://indieweb.org/sidefile-antipattern</a> <a id="t5WT1_note-16" href="#t5WT1_ref-16">¹⁶</a> <a class="auto-link" href="https://intertwingly.net/slides/2004/devcon/68.html">https://intertwingly.net/slides/2004/devcon/68.html</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-03-28T21:58:00-07:00</updated>
<published>2024-03-28T21:58:00-07:00</published>
<link href="https://tantek.com/2024/088/t1/world-piano-day-ordinal-date-iso-8601" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/088/t1/world-piano-day-ordinal-date-iso-8601</id>
<title type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml" class="if-your-feed-reader-displays-this-then-it-is-violating-the-Atom-spec-RFC-4287-section-4.2.14"/>
</title>
<content type="xhtml" xml:base="https://tantek.com/" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml" xml:space="preserve">Happy World Piano Day<a id="t5WA1_ref-1" href="#t5WA1_note-1">¹</a>! Because there are 88 keys on a standard piano, the 88th day of the year was established as a day to “celebrate the piano and everything around it: performers, composers, piano builders, tuners, movers and most important, the listener”. There are multiple websites about Piano Day: * <a class="auto-link" href="https://www.pianoday.org/">https://www.pianoday.org/</a> * <a class="auto-link" href="https://www.worldpianoday.com/">https://www.worldpianoday.com/</a> And related #socialMedia and other profiles: * <a class="auto-link" href="https://www.instagram.com/pianodayofficial/">https://www.instagram.com/pianodayofficial/</a> * <a class="auto-link" href="https://linktr.ee/PianoDay">https://linktr.ee/PianoDay</a> * Spotify playlist: <a class="auto-link" href="https://open.spotify.com/playlist/2v022joEJ1ZUPi99NHDVNm?si=mmT4rDchTzW60KC3lsTksQ&nd=1&dlsi=2a348a57822c4217">https://open.spotify.com/playlist/2v022joEJ1ZUPi99NHDVNm?si=mmT4rDchTzW60KC3lsTksQ&nd=1&dlsi=2a348a57822c4217</a> I appreciate that Piano Day is on an ordinal day of the year (88th) rather than a Gregorian date (e.g. 8/8 or August 8th) which is subject to leap year variances. The 88th day of the year is the 88th day regardless whether it is a leap year or not. From a standards perspective, we can express today’s Piano Day as 2024-088, an ISO ordinal date<a id="t5WA1_ref-2" href="#t5WA1_note-2">²</a>, however there is no standard date format for just "the 88th day of a year" without specifying a year (yearless). There is (was) a way to specify a yearless month and day, like you might see as a birthday displayed on a social media site, without disclosing the year, or an annual holiday like May Day<a id="t5WA1_ref-3" href="#t5WA1_note-3">³</a>, that is May 1st, without a specific year: --05-01 This yearless date format (--MM-DD or shorthand --MMDD) was supported in the ISO 8601:2000 standard, but then dropped in the 2004 revision. This omission or deliberate removal was an error, because there are both obvious human visible use-cases (communicating holidays, and yearless birthdays as noted above), and other standards already depended on this yearless date format syntax (e.g. vCard<a id="t5WA1_ref-4" href="#t5WA1_note-4">⁴</a> and specs that refer to it like hCard and h-card). Every version of ISO 8601 since 2000 has this flaw. Fixing (or patching) #ISO8601 is worth a separate post. Returning to yearless ordinal dates, since they lack an interchange syntax, we can define one resembling the yearless month day format, yet unambiguously parseable as a yearless ordinal date: ---DDD e.g. Piano Day would be represented as: ---088 We have to use three explicit digits because there's also pre-existing "day of the month" and "month of the year" syntaxes which are very similar, but with two digits: --MM ---DD This yearless #ordinalDate syntax (---DDD) is worth proposing as a delta "repair" spec to ISO 8601 (use-cases: Piano Day and others like Programmer’s Day<a id="t5WA1_ref-5" href="#t5WA1_note-5">⁵</a>), alongside at least a restoration of the --MM-DD yearless month day syntax (use-cases: publishing holidays and yearless birthdays), perhaps also the ---DD day of the month and --MM month of the year syntaxes (use-case: language independent numerical publishing of Gregorian months and days of months), and propose adding a NewCal bim of the year syntax --B (numerically superior replacement for Gregorian months and quarters). Glossary: hCard <a class="auto-link" href="https://microformats.org/wiki/hcard">https://microformats.org/wiki/hcard</a> h-card <a class="auto-link" href="https://microformats.org/wiki/h-card">https://microformats.org/wiki/h-card</a> NewCal <a class="auto-link" href="http://newcal.org/">http://newcal.org/</a> References: <a id="t5WA1_note-1" href="#t5WA1_ref-1">¹</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Piano_Day">https://en.wikipedia.org/wiki/Piano_Day</a> <a id="t5WA1_note-2" href="#t5WA1_ref-2">²</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Ordinal_date">https://en.wikipedia.org/wiki/Ordinal_date</a> <a id="t5WA1_note-3" href="#t5WA1_ref-3">³</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/May_Day">https://en.wikipedia.org/wiki/May_Day</a> <a id="t5WA1_note-4" href="#t5WA1_ref-4">⁴</a> <a class="auto-link" href="https://www.rfc-editor.org/rfc/rfc6350#section-6.2.5">https://www.rfc-editor.org/rfc/rfc6350#section-6.2.5</a> <a id="t5WA1_note-5" href="#t5WA1_ref-5">⁵</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Programmer%27s_Day">https://en.wikipedia.org/wiki/Programmer%27s_Day</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
</feed>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

Download the "valid Atom 1.0" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):

<a href="http://www.feedvalidator.org/check.cgi?url=http%3A//tantek.com/log/posts.atom"><img src="valid-atom.png" alt="[Valid Atom 1.0]" title="Validate my Atom 1.0 feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//tantek.com/log/posts.atom

Home · About · News · Docs · Terms