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 5, column 59: Self reference doesn't match document location [help]

  <link href="https://tantek.com/updates.atom" rel="self"/>
                                                           ^

line 16, column 116: The title attribute of link should not be blank (11 occurrences) [help]

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

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

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

Source: http://tantek.com/updates.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-04-18T20:20:00-07:00</updated>
<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>
<entry>
<updated>2024-03-24T14:50:00-07:00</updated>
<published>2024-03-24T14:50:00-07:00</published>
<link href="https://tantek.com/2024/084/t2/posse-in-effect" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/084/t2/posse-in-effect</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"><a class="auto-link" href="https://indieweb.org/POSSE">@indieweb.org/POSSE</a> in effect! Well done <a class="auto-link" href="https://threads.net/@joanwestenberg">@joanwestenberg@threads.net</a> 🙌🏻 #POSSE threads <a class="auto-link" href="https://www.threads.net/@joanwestenberg/post/C43gPbVSzPI:">https://www.threads.net/@joanwestenberg/post/C43gPbVSzPI:</a> “Me: You should publish on your own website first, then other platforms. Me: Publishes on my own website first, then other platforms. Galaxy brains: HOW IRONIC YOU PUBLISH ON OTHER PLATFORMS” #IndieWeb</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-03-24T14:03:00-07:00</updated>
<published>2024-03-24T14:03:00-07:00</published>
<link href="https://tantek.com/2024/084/t1/open-social-web-or-fate-aol" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/084/t1/open-social-web-or-fate-aol</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">Join the open social web or be relegated the same fate as AOL, who couldn't even sustain their dominant instant messaging silo. #Twitter, #Pinterest, #Snapchat, #Quora, you're not special enough to survive on your own. And tick-tock #TikTok. #fediverse threads <a class="auto-link" href="https://www.threads.net/@evanprodromou/post/C46RHmMv1te:">https://www.threads.net/@evanprodromou/post/C46RHmMv1te:</a> “If Meta can join the Fediverse, what's your excuse?” #openSocialWeb #AOL #AIMsilo</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-03-23T16:05:00-07:00</updated>
<published>2024-03-23T16:05:00-07:00</published>
<link href="https://tantek.com/2024/083/t1/rel-me-identity-verification" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/083/t1/rel-me-identity-verification</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"><a class="auto-link" href="https://microformats.org/wiki/rel-me">https://microformats.org/wiki/rel-me</a>. Want to learn more about rel=me distributed identity verification with zero cryptohashfoo blockchaining? Drop by <a class="auto-link" href="https://chat.indieweb.org/dev">https://chat.indieweb.org/dev</a>. #HTML FTW! <a class="auto-link" href="https://www.threads.net/@0xjessel/post/C4zGhshpn9t:">https://www.threads.net/@0xjessel/post/C4zGhshpn9t:</a> “as everyone is trying out fediverse, today is a good reminder that threads support rel=me link verification -- another open web standard we adopted last year. this is useful right now because you can't see fediverse replies to your posts on threads yet. so if you use a mastodon alt account to reply to your threads posts, setting this up proves you are the owner of the mastodon and threads account. see post below on how to set this up: <a class="auto-link" href="https://www.threads.net/@0xjessel/post/Cvu7-42PVpC:">https://www.threads.net/@0xjessel/post/Cvu7-42PVpC:</a> “to set your own up: 1. add your mastodon profile to your threads link in bio. 2. add your threads profile to your mastodon profile 3. save your profile and it should show as verified now” ” Previously: <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> #microformats #relme #fediverse #Threads</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-03-19T19:50:00-07:00</updated>
<published>2024-03-19T19:50:00-07:00</published>
<link href="https://tantek.com/2024/079/t1/are-you-celebrating-spring-equinox" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/079/t1/are-you-celebrating-spring-equinox</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">Are you celebrating #spring #equinox [ ] in September for the Southern Hemisphere [ ] 2024-03-21 [ ] 2024-03-20 [ ] 2024-03-20 03:06Z [ ] 2024-03-19 [ ] 2024-03-19 23:06 EDT [ ] 2024-079 [ ] 2024-079 20:06 PDT and optionally, why did you choose which choice(s)?</div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-03-15T21:35:00-07:00</updated>
<published>2024-03-15T21:35:00-07:00</published>
<link href="https://tantek.com/2024/075/t1/css-more-robust-style-element" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/075/t1/css-more-robust-style-element</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">While an HTML style element for inline CSS needs nothing but simple start and end tags (as of HTML5 and later) <style> p { color: red } </style> a more robust style element requires a precise series of overlapping code comments. Here is the answer if you want a code snippet to copy & paste <style><![CDATA[*/ p { color: red } /* you may delete this sample style rule */ /*]]></style> Here is why: 1. Not all HTML processors are CSS processors. While all modern browsers know how to parse CSS in style elements inside HTML, it is still quite reasonable for people to build HTML processors that do not, and many exist. There are plenty of ways to errantly or deliberately misplace markup inside a style element, like in a CSS comment, that such processors will not see, that can break them and cause unexpected and different results in different processors. Strictly speaking any use of > child combinator selector syntax should also be HTML escaped (as &gt;) inside a style elment. Thus it makes your HTML more parseable, by more processors, if you can hide the entirety of the style sheet inside the style element from such processing, including any child combinators. A CDATA section does exactly that: <style><![CDATA[ p { color: orange } /* CDATA allows a </style> here to not close the element */ body > p { margin: 1em } /* CDATA also allows an unescaped > child combinator */ ]]></style> 2. However CSS syntax does not recognize a CDATA directive (even as of the latest published CSS Syntax Module Level 3<a id="t5Vx1_ref-1" href="#t5Vx1_note-1">¹</a> or editor's draft<a id="t5Vx1_ref-2" href="#t5Vx1_note-2">²</a> as of this writing). CSS parsers may very well treat a CDATA directive as a syntax error that invalidates the subsequent style rule. Thus we must hide the CDATA directive, its opening and closing markup, from CSS parsers. CSS code comments /* ... */ can do exactly that: <style>/*<![CDATA[*/ p { color: orange } /* CDATA allows a </style> here to not close the element */ body > p { margin: 1em } /* CDATA also allows an unescaped > child combinator */ /*]]>*/</style> 3. This is close but still exposes HTML processors that do not process CSS to a minimal bit of content, the CSS comment opener and closer that are outside the CDATA section: /* */ This recently showed up in a draft of the This Week in The #IndieWeb newsletter<a id="t5Vx1_ref-3" href="#t5Vx1_note-3">³</a>, because portions of it are automatically constructed by parsing the HTML of MediaWiki pages for content, and one of those used a MediaWiki template that included a minimal style element to style the marked up content inserted by the template. A draft of the newsletter was showing raw CSS, extracted as text from the style element by the CSS-unaware parser extracting content. I was able to hide nearly all of it using CSS comments around the CDATA section opener and closer. Except for that little bit of CSS comment noise outside the CDATA section: /* */ Fortunately there is one more tool in our toolbox that we can use. Simple HTML/SGML comments  are ignored at the start and end of style sheets<a id="t5Vx1_ref-4" href="#t5Vx1_note-4">⁴</a> (noted there as CDO-token<a id="t5Vx1_ref-5" href="#t5Vx1_note-5">⁵</a> and CDC-token<a id="t5Vx1_ref-6" href="#t5Vx1_note-6">⁶</a>), and thus we can use those to hide the last two remaining CSS comment pieces that were leaking out, like this:  and . Note that the portion of the HTML comment directives that are inside CSS comments are ignored by CSS processors, which is why this works for both processors that parse CSS and those that do not. This last addition produces our answer, with no fewer than three different comment mechanisms (CDATA, CSS, HTML/SGML), overlapping to hide each other from different processors: <style><![CDATA[*/ p { color: orange } /* CDATA allows a </style> here to not close the element */ body > p { margin: 1em } /* CDATA also allows an unescaped > child combinator */ /*]]></style> By replacing those informative style rules with a style rule to be deleted, we have recreated the code snippet to copy & paste from the top of the post: <style><![CDATA[*/ p { color: red } /* you may delete this sample style rule */ /*]]></style> Q.E.D. Afterword: If you’re reading this in a traditional feed reader and see any red or orange text, then your feed reader has a bug (or a few) in its HTML parsing code. If you View Source on this post’s original permalink or my home page you can see the more robust style element in a real world example, following the IndieWeb Use What You Make<a id="t5Vx1_ref-7" href="#t5Vx1_note-7">⁷</a> principle. #CSS #style #styleElement #styleSheet #HTML #HTML5 #CSSsyntax #codeComments #CDATA #SGML #CSScomment #HTMLcomment #SGMLcomment Glossary: CDATA <a class="auto-link" href="https://en.wikipedia.org/wiki/CDATA">https://en.wikipedia.org/wiki/CDATA</a> CSS — Cascading Style Sheets <a class="auto-link" href="https://en.wikipedia.org/wiki/CSS">https://en.wikipedia.org/wiki/CSS</a> HTML — HyperText Markup Language <a class="auto-link" href="https://en.wikipedia.org/wiki/HTML">https://en.wikipedia.org/wiki/HTML</a> HTML5 <a class="auto-link" href="https://en.wikipedia.org/wiki/HTML5">https://en.wikipedia.org/wiki/HTML5</a> IndieWeb Principles <a class="auto-link" href="https://indieweb.org/principles">https://indieweb.org/principles</a> MediaWiki <a class="auto-link" href="https://en.wikipedia.org/wiki/MediaWiki">https://en.wikipedia.org/wiki/MediaWiki</a> original permalink <a class="auto-link" href="https://indieweb.org/original_permalink">https://indieweb.org/original_permalink</a> Q.E.D. <a class="auto-link" href="https://en.wikipedia.org/wiki/Q.E.D">https://en.wikipedia.org/wiki/Q.E.D</a>. References: <a id="t5Vx1_note-1" href="#t5Vx1_ref-1">¹</a> <a class="auto-link" href="https://www.w3.org/TR/css-syntax-3/">https://www.w3.org/TR/css-syntax-3/</a> <a id="t5Vx1_note-2" href="#t5Vx1_ref-2">²</a> <a class="auto-link" href="https://drafts.csswg.org/css-syntax/">https://drafts.csswg.org/css-syntax/</a> <a id="t5Vx1_note-3" href="#t5Vx1_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/this-week-in-the-indieweb">https://indieweb.org/this-week-in-the-indieweb</a> <a id="t5Vx1_note-4" href="#t5Vx1_ref-4">⁴</a> <a class="auto-link" href="https://www.w3.org/TR/css-syntax-3/#stylesheet-diagram">https://www.w3.org/TR/css-syntax-3/#stylesheet-diagram</a> <a id="t5Vx1_note-5" href="#t5Vx1_ref-5">⁵</a> <a class="auto-link" href="https://www.w3.org/TR/css-syntax-3/#CDO-token-diagram">https://www.w3.org/TR/css-syntax-3/#CDO-token-diagram</a> <a id="t5Vx1_note-6" href="#t5Vx1_ref-6">⁶</a> <a class="auto-link" href="https://www.w3.org/TR/css-syntax-3/#CDC-token-diagram">https://www.w3.org/TR/css-syntax-3/#CDC-token-diagram</a> <a id="t5Vx1_note-7" href="#t5Vx1_ref-7">⁷</a> <a class="auto-link" href="https://indieweb.org/use_what_you_make">https://indieweb.org/use_what_you_make</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-03-12T19:19:00-07:00</updated>
<published>2024-03-12T19:19:00-07:00</published>
<link href="https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/072/t1/created-at-indiewebcamp-brighton</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">What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before. Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both. At the start of day 2, everyone is encourage to pick things to make<a id="t5Vu1_ref-1" href="#t5Vu1_note-1">¹</a>. What to make at an IndieWebCamp<a id="t5Vu1_ref-2" href="#t5Vu1_note-2">²</a> can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content. Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps. For my "easy" task, I built on what another remote participant, <a class="auto-link" href="https://gregorlove.com">@gregorlove.com</a> completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page<a id="t5Vu1_ref-3" href="#t5Vu1_note-3">³</a>. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links. I went through the 13 Session Notes archives and did the following: * converted Markdown links to MediaWiki links * converted <a class="auto-link" href="http://indieweb.org">indieweb.org</a> (and some services) links to local wiki page links * fixed (some) typos With some help from <a class="auto-link" href="https://alexsirac.com">@alexsirac.com</a> (<a class="auto-link" href="https://todo.eu/@alexture">@alexture@todo.eu</a>), I figured out how to create a MediaWiki Contributions summary link of my edits: * <a class="auto-link" href="https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25">https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25</a> I point this out to provide an example of an IndieWeb Create Day project that is: * incremental on top of someone else’s work * community contribution rather a personal-focused project * editing and wiki-gardening as valid contributions, not just creating new content I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward: * new innovations (not incremental improvements) * solo (or maybe jointly in a small team) inventions, designs, specs, or implementations * something large, a new service or a big feature, not numerous small edits & fixes In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation. For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements. * <a class="auto-link" href="https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases">https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</a> My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how many implementations autolink plain text URLs, domains, and paths. That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning: * <a class="auto-link" href="https://tantek.com/2023/011/t1/indieweb-evolving-at-mention">https://tantek.com/2023/011/t1/indieweb-evolving-at-mention</a> * <a class="auto-link" href="https://tantek.com/2023/014/t4/domain-first-federated-atmention">https://tantek.com/2023/014/t4/domain-first-federated-atmention</a> * <a class="auto-link" href="https://tantek.com/2023/018/t1/elevate-indieweb-above-silo">https://tantek.com/2023/018/t1/elevate-indieweb-above-silo</a> * <a class="auto-link" href="https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo">https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo</a> * <a class="auto-link" href="https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread">https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread</a> #autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day: * <a class="auto-link" href="https://indieweb.org/2024/Brighton/Demos">https://indieweb.org/2024/Brighton/Demos</a> And read what other participants have blogged about their IndieWebCamp Brighton experience: * <a class="auto-link" href="https://roobottom.com/articles/plugging-into-the-indieweb/">https://roobottom.com/articles/plugging-into-the-indieweb/</a> * <a class="auto-link" href="https://adactio.com/journal/20968">https://adactio.com/journal/20968</a> * <a class="auto-link" href="https://theadhocracy.co.uk/wrote/indiewebcamp-brighton-2024/">https://theadhocracy.co.uk/wrote/indiewebcamp-brighton-2024/</a> This is post 13 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases">https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</a> → 🔮 Glossary: Create Day <a class="auto-link" href="https://indieweb.org/Create_Day">https://indieweb.org/Create_Day</a> IndieWebCamp Brighton 2024 <a class="auto-link" href="https://indieweb.org/2024/Brighton">https://indieweb.org/2024/Brighton</a> References: <a id="t5Vu1_note-1" href="#t5Vu1_ref-1">¹</a> <a class="auto-link" href="https://indieweb.org/IndieWebCamps/Attending#Day_Two">https://indieweb.org/IndieWebCamps/Attending#Day_Two</a> <a id="t5Vu1_note-2" href="#t5Vu1_ref-2">²</a> <a class="auto-link" href="https://indieweb.org/what_to_make_at_IndieWebCamp">https://indieweb.org/what_to_make_at_IndieWebCamp</a> <a id="t5Vu1_note-3" href="#t5Vu1_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/2024/Brighton/Schedule#Saturday">https://indieweb.org/2024/Brighton/Schedule#Saturday</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-03-10T07:55:00-07:00</updated>
<published>2024-03-10T07:55:00-07:00</published>
<link href="https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</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">Updated the auto-linking code<a id="t5Vs1_ref-1" href="#t5Vs1_note-1">¹</a> on my website last Sunday to handle a few more @-mention use-cases. In particular: * @-domains with dashes/hyphens like <a class="auto-link" href="https://sonja-weckenmann.de">@sonja-weckenmann.de</a> * @-@ with (some) Unicode alphabetic characters like <a class="auto-link" href="https://loðfíll.is/@briansuda">@briansuda@loðfíll.is</a> * @-domain-and-path for indicating @-mentions of silo profiles that don’t support @-@ syntax, like <a class="auto-link" href="https://flickr.com/people/tantek">@flickr.com/people/tantek</a> or <a class="auto-link" href="https://instagram.com/tantek">@instagram.com/tantek</a> I also dropped auto-linking of URLs with user:password "userinfo", since they’ve been long abandoned and effectively deprecated because there’s fairly wide agreement that such basic HTTP authentication<a id="t5Vs1_ref-2" href="#t5Vs1_note-2">²</a> was poorly designed and should not be used (and thus should not be linked). If you’re curious you can take a look at <a class="auto-link" href="https://tantek.com/cassis.js">https://tantek.com/cassis.js</a>, which has updated functions: * auto_link_re() — regular expression to recognize URLs, @-mentions, @-@, and footnotes to link * auto_link() — specifically the code to recognize different kinds of @-@ and @-mentions and link them properly to profiles, domains, and paths. This code is only live on my website (testing in production<a id="t5Vs1_ref-3" href="#t5Vs1_note-3">³</a> as it were) for now, and you’re welcome to copy/paste to experiment with it. I plan to test it more over the coming weeks (or so) and when I feel it is sufficiently well tested, will update it on GitHub<a id="t5Vs1_ref-4" href="#t5Vs1_note-4">⁴</a> as well. With this additional auto-linking functionality, I feel I have a fairly complete implementation of how to auto-link various URLs and @-mentions, and plan to write that up at least as a minimal “list of use-cases and how they should work” auto-linking specification. This (blog post) is my contribution to today’s #IndieWebCamp Brighton<a id="t5Vs1_ref-5" href="#t5Vs1_note-5">⁵</a> #hackday! This was originally a project I wanted to complete during IndieWebCamp Nuremberg last October, however I was pre-occupied at the time with fixing other things.<a id="t5Vs1_ref-6" href="#t5Vs1_note-6">⁶</a> #autolink #atmention #atmentions #atat #atatmention This is post 12 of #100PostsOfIndieWeb. #100Posts ← <a class="auto-link" href="https://tantek.com/2024/047/t1/indieweb-major-update-design">https://tantek.com/2024/047/t1/indieweb-major-update-design</a> → <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 id="t5Vs1_note-1" href="#t5Vs1_ref-1">¹</a> <a class="auto-link" href="https://tantek.com/cassis.js">https://tantek.com/cassis.js</a> <a id="t5Vs1_note-2" href="#t5Vs1_ref-2">²</a> <a class="auto-link" href="https://en.wikipedia.org/wiki/Basic_access_authentication">https://en.wikipedia.org/wiki/Basic_access_authentication</a> <a id="t5Vs1_note-3" href="#t5Vs1_ref-3">³</a> <a class="auto-link" href="https://indieweb.org/test_in_production">https://indieweb.org/test_in_production</a> <a id="t5Vs1_note-4" href="#t5Vs1_ref-4">⁴</a> <a class="auto-link" href="https://tantek.com/github/cassis">https://tantek.com/github/cassis</a> <a id="t5Vs1_note-5" href="#t5Vs1_ref-5">⁵</a> <a class="auto-link" href="https://indieweb.org/2024/Brighton">https://indieweb.org/2024/Brighton</a> <a id="t5Vs1_note-6" href="#t5Vs1_ref-6">⁶</a> <a class="auto-link" href="https://tantek.com/2023/302/t1/indiewebcamp-completed-projects">https://tantek.com/2023/302/t1/indiewebcamp-completed-projects</a></div>
</content>
<object-type xmlns="http://activitystrea.ms/spec/1.0/">note</object-type>
</entry>
<entry>
<updated>2024-02-20T00:38:00-08:00</updated>
<published>2024-02-20T00:38:00-08:00</published>
<link href="https://tantek.com/2024/051/t1/finished-redtail-ridge-30k" rel="alternate" title="" type="text/html"/>
<id>https://tantek.com/2024/051/t1/finished-redtail-ridge-30k</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">This past Saturday: finished the #InsideTrail Redtail Ridge 30k #trailRace in 6:00:59. A few notes: This was my first trail race of 2024, and first in over 6 months, since last year’s Marin Ultra Challenge 50k and Broken Arrow 23k races in June<a id="t5VZ1_ref-1" href="#t5VZ1_note-1">¹</a>. Saw pal Henri after changing into my trail shoes in the Lake Chabot Regional Park parking lot. The storms had scared many away, fewer than 100 showed up to the combined 30k & 50k start. The muddy rainy adventure began when we veered off the initial paved trail around the lake and onto a rocky uphill stretch. It was mostly an out-and-back course, with a bit of a loop in the middle. On the second half of that loop there was one fork in the trail without race markings. After spending minutes taking a peek down both options, I guessed right. About a half mile later a wooden trail post validated my choice. I kept a sustainable run/hike pace, with some sliding in the mud, stepping around many ruts and puddles of unknown depths. Slower finish than 5 years ago<a id="t5VZ1_ref-2" href="#t5VZ1_note-2">²</a>, yet this time with a negative split, and earned my first DLF award! #30k #RedtailRidge #trailRun #trailRunner #runner #trailRunning #running #2024_048 <a id="t5VZ1_note-1" href="#t5VZ1_ref-1">¹</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="t5VZ1_note-2" href="#t5VZ1_ref-2">²</a> <a class="auto-link" href="https://tantek.com/2019/048/t1/finshed-chabot-redtailridge-30k-pr">https://tantek.com/2019/048/t1/finshed-chabot-redtailridge-30k-pr</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/updates.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/updates.atom

Home · About · News · Docs · Terms