1. registered to run #baytobreakers 2023-05-21!
    Join me in corral A: https://baytobreakers.com/

    @baytobreakers said $39.99, added $3.60 for “Booking Fee”, less than last year’s $5.95 for “Handling”, yet still a required extra charge.

    Previously: https://tantek.com/2021/304/t1/registered-run-baytobreakers-2022

  2. #TwitterMigration, first time?

    Have posted notes to https://tantek.com/ since 2010, POSSEd tweets & #AtomFeed.

    Added one .htaccess line today, and thanks to #BridgyFed, #Mastodon users can follow my #IndieWeb site


    No Mastodon install or account needed. Just one line in .htaccess:

      RewriteRule ^.well-known/(host-meta|webfinger).* https://fed.brid.gy/$0  [redirect=302,last]

    is enough for Mastodon users to search for and follow that @tantek.com username. Took a little more work to setup Bridgy Fed to push new posts to followers.

    Note by the way both the redundancy & awkwardness (it’s not a clickable URL) of such @-@ (AT-AT) usernames when you’re already using your own domain.

    Why can’t Mastodon follow a username of “@tantek.com”? Or just tantek.com”?
    And either way expanding it internally if need be to the AT-AT syntax.

    Why this regression from what we had with classic feed readers where a domain was enough to discover & follow a feed?

    Also, why does following show a blank result?

    Contrast that with classic feed readers which immediately show you the most recent items in a feed you subscribed to.

    Lastly (for now), I asked around and no one knew of a simple public way to “preview” or “validate” that @tantek.com actually “worked”. You have to be *logged-in* to a Mastodon instance and search for a username to check to see if it works.

    Contrast that with https://validator.w3.org/feed/ which you can use without any log-in to validate your classic feed file.

    Why these regressions from the days of feed readers?

  3. Tantek running with a focused look in a 2020 MUC50 cap, black singlet & shorts, on a dirt trail with grass, bushes, & trees on both sides, and two runners out of focus ~20 meters behind him.Trail running shoes, socks, shorts, singlet, water bottle, Suunto watch, Spring Energy gel packets, Picky bars, November Project buffs, ziplock with drop bag supplies, and waist belt arranged orderly on hardwood floor.About ten trail runners starting a race on a lawn, just in front of a temporary metal arch with logo text for Scena Performance & Skyline 50k, and a large FINISH white text on black background banner across the top, park buildings in the background, and trees behind them.Tantek crossing the finish line sensor under the FINISH arch in the bright sunshine, smiling & stopping his watch, a volunteer in the foreground holding out a finisher medal, David Tran photographing from the sidePlain white index card with “GO T GO, SKYLINE 50K 2022, WOO HOO !!!” written on it in black marker.Tantek standing at an angle on a wide trail in bright sunshine with pine trees behind him, holding his water bottle, leaning forward on his right foot, head turned slightly to face the camera and smile.Tantek running on a wide smooth dirt trail with plowed rough dirt edges, bits of grass and a tree in the background nearby with many more trees in the distance, a single runner out of focus about 50 meters behind hime.Tantek fast-walking downhill on an asphalt path in the shade next to some dry grass and trees, a lake peaking thru between their branches.Tantek running mid-stride, arms swinging, on a lawn between orange cones with a park building and trees behind him.Trail runners Amanda, David Tran, Tantek, Kristina, Ramona standing side-by-side with arms around each other smiling, in front of the race finish area, the latter three still wearing their bibs and finish medals.10w ago: 9:29:05 50k PR, hot #trailRace @ScenaPerform #Skyline50k

    Thanks @bryanting @aeables @dtran320 @vivekgowri pics&support, @corrinemalcolm training me back to an ultra start+finish 3y after #ECSCA.

    #run #trailRun #trailRunning #ultraRunning #trailRunner #ultraRunner #50k #50kTrailRace #50kFinish #50kFinisher #ultraMarathon #2022_219 #20220807 #WorkHardDreamBigDoCoolShit #latergram #nofilter

    This was my second ultra race finish, and sixth ultra-distance run. Since last year’s Rodeo Valley 30k (https://tantek.com/t5E81), I signed-up for seven races, started six, and finished five (including this one). I’m behind on a year of race posting so for now here’s a mini-report and story of a 50k in 10 photos.

    Mini race-report: decent fueling, very good hydration, hottest race I’ve ever run, first time using ice in a neck buff & under my cap, left knee-pain (IT band) struggle in the last 7-8mi, had to fast-walk the last 4mi. Thankful for Vivek Gowri crewing me at the Skyline Gate aid station (17.2mi) making sure I had/got what I needed (no sunburns!), Amanda’s so thoughtful mini cheer sign (📷5) she snuck into my dropbag, and the two of them plus David Tran for running me in the last mile-ish which helped push me to a sub-9h30m time. Thanks also to Bryan Ting for both recommending this race to me and being at so many spots on the course to take race photos. Seeing friends along the way turned a hot & hard race into a fun time.

    Photos in time order:

    📷2: There’s a certain calm in the ritual of arranging all your race gear & fuel the night before. This was my second race where I packed a drop bag, with extra water & gels I might need if temperatures rose higher, or I took longer than expected. Having trained with nearly everything in that pile at some point, and run the course trails over a couple of days a few weeks beforehand, I went to bed knowing I was prepared.

    📷3 by Bryan: Knowing I’d be close to the course limit, I opted for the early start option, an hour before the normal start, just ineligible for any competitive medals. It was dark when we arrived, but you can see how much it lightened up (even with cloud cover) for the 6am early start.

    📷1 by Bryan: I kept a steady pace up to the second aid station, stopping only briefly at mile 4 to use the bathroom at the golf course next to the first aid station which wasn’t set up yet. Right before the second aid station, Bryan Ting was camped out taking race photos, and captured me focused on my run.

    📷5: From there on it was steady work making it up and down various trails as it warmed up in the first half of the race. Made it up to the Skyline Gate station where Vivek was waiting with my drop bag, and handed me a surprise race sign card that Amanda had made for me.

    📷6 by Vivek: It was 85F+ at Skyline Gate, so I sat for a few minutes and took time to calmly hydrate some more. I grabbed a couple of spare gels from my drop bag, and after Vivek helped me re-apply sunscreen, I stood for a moment before jumping back on the trails.

    📷7 by Bryan: The push up to the last aid station was a tough hike in the open sun. I saw Bryan again taking photos and focused on a steady run-shuffle up the trail.

    📷8 by Vivek: Vivek, David Tran, and Amanda found me on the paved path around Lake Chabot with ~1.5mi to go and captured my determined struggle. Plenty of energy left, I was more annoyed by the pace-limiting knee-pain that started in mile 25 and became too painful to run at mile 28. They chatted with me to keep me distrated, and told me I looked good (amazing how much that helps). I kept a steady fast-walk, gently run-shuffling on the rolling downhills as pictured.

    📷9 by David Tran: Running ahead, David took photos & video of me. With the finish area in sight, I swung my arms and pushed past the knee-pain into a run, first on the remaining asphalt then across the lawn through the orange cones toward the finish.

    📷4 by Bryan: Stopping my watch as I lept over the finish line, eyes on the finisher’s medal offered by a volunteer. Happiness and relief as I completed my first ultramarathon race since 2019.

    📷10 by Bryan: @ScenaPerform’s Skyline 50k brought friends & community together like no other race since @TheNorthFaceECS races. A bunch of us 50k finishers recalled our adventures during the race while rehydrating & snacking on Impossible burgers at the finish area picnic. Bryan saw us gathered and we lined up for a group photo which perfectly captured the moment.

    I’ll be back to run this race again.

  4. W3C TPAC 2022 Sustainability Community Group Meeting


    This year’s W3C TPAC Plenary Day was a combination of the first ever AC open session in the early morning, and breakout sessions in the late morning and afternoon. Nick Doty proposed a breakout session for Sustainability for the Web and W3C which he & I volunteered to co-chair, as co-chairs of the Sustainability (s12y) CG which we created on Earth Day earlier this year. Nick & I met during a break on Wednesday afternoon and made plans for how we would run the session as a Sustainability CG meeting, which topics to introduce, how to deal with unproductive participation if any, and how to focus the latter part of the session into follow-up actions.

    We agreed that our primary role as chairs should be facilitation. We determined a few key meeting goals, in particular to help participants:

    • Avoid/minimize any trolling or fallacy arguments (based on experience from 2021)
    • Learn who is interested in which sustainability topics & work areas
    • Determine clusters of similar, related, and overlapping sustainability topics
    • Focus on prioritizing actual sustainability work rather than process mechanics
    • Encourage active collaboration in work areas (like a do-ocracy)

    The session went better than I expected. The small meeting room was packed with ~20 participants, with a few more joining us on Zoom (which thankfully worked without any issues, thanks to the W3C staff for setting that up so all we had to do as chairs was push a button to start the meeting!).

    I am grateful for everyone’s participation and more importantly the shared sense of collaboration, teamwork, and frank urgency. It was great to meet & connect in-person, and see everyone on video who took time out of their days across timezones to join us. There was a lot of eagerness in participation, and Nick & I did our best to give everyone who wanted to speak time to contribute (the IRC bot Zakim's two minute speaker timer feature helped).

    It was one of the more hopeful meetings I participated in all week. Thanks to Yoav Weiss for scribing the minutes. Here are a few of the highlights.

    Session Introduction

    Nick introduced himself and proposed topics of discussion for our breakout session.

    • How we can apply sustainbility to web standards
    • Goals we could work on as a community
    • Consider metrics to enable other measures to take effect
    • Measure the impact of the W3C meetings themselves
    • Working mode and how we talk about sustainability in W3C
    • Horizontal reviews

    I introduced myself and my role at Mozilla as one our Environmental Champions, and noted that it’s been three years since we had the chance to meet in person at TPAC. Since then many of us who participate at W3C have recognized the urgency of sustainability, especially as underscored by recent IPCC reports. From the past few years of publications & discussions:

    For our TPAC 2022 session, I asked that we proceed with the assumption of sustainability as a principle, and that if folks came to argue with that, that they should raise an issue with the TAG, not this meeting.

    In the Call for Participation in the Sustainability Community Group, we highlighted both developing a W3C practice of Sustainability (s12y) Horizontal Review (similar to a11y, i18n, privacy, security) as proposed at TPAC 2021, and an overall venue for participants to discuss all aspects of sustainability with respect to web technologies present & future. For our limited meeting time, I asked participants to share how they want to have the biggest impact on sustainability at W3C, with the web in general, and actively prioritize our work accordingly.

    Work Areas, Groups, Resources

    Everyone took turns introducing themselves and expressing which aspects of sustainability were important to them, noting any particular background or applicable expertise, as well as which other W3C groups they are participating in, as opportunities for liaison and collaboration. Several clusters of interest emerged:

    • Technologies to reduce energy usage
    • W3C meetings and operations
    • Measurement
    • System Effects
    • Horizontal Review
    • Principles

    The following W3C Groups were noted which are either already working on sustainability related efforts or would be good for collaboration, and except for the TAG, had a group co-chair in the meeting!

    I proposed adding a liaisons section to our public Sustainability wiki page accordingly explicitly listing these groups and specific items for collaboration. Participants also shared the following links to additional efforts & resources:

    Sustainability Work In Public By Default

    Noting that since all our work on sustainability is built on a lot of public work by others, the best chance of our work having an impact is to also do it publicly, I proposed that Sustainability CG work in public by default, as well as sustainability work at W3C in general, and that we send that request to the AB to advise W3C accordingly. The proposal was strongly supported with no opposition.

    Active Interest From Organizations

    There were a number of organizations whose representatives indicated that they are committed to making a positive impact on the environment, and would like to work on efforts accordingly in the Sustainability CG, or would at least see if they could contact experts at their organizations to see if any of them were interested in contributing.

    • Igalia
    • mesur.io
    • Mozilla
    • Lawrence Berkeley National Laboratory
    • Washington Post

    Meeting Wrap-up And Next Steps

    We finished up the meeting with participants signing up to work on each of the work areas (clusters of interest noted above) that they were personally interested in working on. This has been captured on our wiki: W3C Wiki: Sustainability Work Areas.

    The weekend after the meeting I wrote up an email summary of the meeting & next steps and sent it directly to those who were present at the meeting, encouraging them to Join the Sustainability Community Group (requires a W3C account) for future emails and updates. Nick & I are also on the W3C Community Slack #sustainability channel which I recommended joining. Signup link: https://www.w3.org/slack-w3ccommunity-invite

    Next Steps: we encouraged everyone who signed up for a Work Area to reach out to each other directly and determine their preferred work mode, including in which venue they’d like to do the work, whether in the Sustainability CG, another CG, or somewhere else. We noted that work on sustainable development & design of web sites in particular should be done directly with the Sustainable Web Design CG (sustyweb), “a community group dedicated to creating sustainable websites”.

    Some possibilities for work modes that Work Area participants can use:

    • W3C Community Slack #sustainability channel
    • public-sustainability email list of the Sustainability CG
    • Our Sustainability wiki page, creating "/" subpages as needed

    There is lots of work to do across many different areas for sustainability & the web, and for technology as a whole, which lends itself to small groups working in parallel. Nick & I want to help facilitate those that have the interest, energy, and initiative to do so. We are available to help Work Area participants pick a work mode & venue that will best meet their needs and help them get started on their projects.