Tantek Çelik

inventor, connector, writer, runner, scientist, more.

💬 👏
  1. I recently wrote a high level summary blog post:

    W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023


    of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.

    Posting this note to explicitly #hashtag that article with topics mentioned therein:

    #Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub

    because I forgot to put explicit categories (p-category markup) in the article post.

    Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.

    Post glossary:

    article post
    note post

  2. W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023

    This year’s W3C TPAC (Technical Plenary and Advisory Committee) meetings felt denser in many ways, packed tighter with more topics, and more active participants. There were so many specific things in specific meetings, new connections, victories, new challenges, that in addition to capturing summary notes, I'm considering writing blog posts about each meeting or session.

    Nearly all of them have public minutes that document both participants, and a good portion of what was discussed. I have my own notes, and combined with recollected details of what was minuted, I have my own observations to share. I encourage everyone who participated at TPAC (whether in-person or remote) to consider either writing a summary blog post about the experience, perhaps highlighting a few things that stood out, or if there were specific technical discussions that advanced something in a positive direction, or challenges blocking progress, those are worth their own blog posts as well.

    TPAC week 2023 took place from Monday through Friday , in Sevilla, Spain.

    Here is a summary outline of meetings, sessions, and discussions I participated in. Not listed: conversations at breakfasts, morning & afternoon breaks, lunches, dinners, and of course hallways. Unlinked for now, each of these has a calendar event with description, minutes, almost all of which are public.

    • Monday
      • WICG (Web Incubator Community Group)
    • Tuesday
      • Social Web Incubator CG (community group), AKA SocialCG or SWICG
      • DID WG rechartering discussion
      • AC meeting
      • Vision TF
      • Fediverse meetup
    • Wednesday — Breakouts day!
      • Chartering at W3C
      • Technical Roadmap at W3C
      • SocialWeb Test Suite Discussion
      • SocialWeb Data Portability Discussion
      • Introducing the Web Sustainability Guidelines (WSGs)
      • Report to Members, Hearing from Members
      • Technical Plenary reception
    • Thursday
      • CSS WG, briefly
      • Afternoon break: Solid charter discussions, use-cases, IndieWeb Micropub, ActivityPub
    • Friday
      • Social CG planning
      • Departing conversations & reflections

    Those are the sessions & discussions that I found in my notes. I also met a lot of new people during meetings, meals, and discussions at breaks. As I write up my notes on specific sessions and their minutes (and hyperlink the above list items), I expect to recall more context and details. If you were at TPAC in Seville, I encourage you to write-up your experiences as well, while the thoughts, feelings, and insights are fresh in your mind. By documenting & publishing our collective experiences (using the #w3cTPAC hashtag) we can build upon them together.

  3. 👍 to a comment on issue 113 of GitHub project “AB-public”

  4. 👍 to a comment on issue 8693 of GitHub project “html”

  5. 👍 to issue 387 of GitHub project “activitypub”

  6. 👍 to a comment on issue 96 of GitHub project “AB-public”

  7. 👍 to issue 112 of GitHub project “AB-public”

  8. RSVP yes to: www.w3.org’s post going to the #SocialWeb CG meeting @W3C #w3cTPAC tomorrow (2023-09-12) at 09:30 CEST.

    Looking forward to seeing @evanp.me (@evan@cosocial.ca @evanpro) and many others!

    So many advances in #ActivityPub, #Webmention, Micropub, #IndieAuth etc. that it may be time to restart the #SocialWebWG to officially update all our active specifications.

    We can & should also reach out to #Bluesky & #Nostr communities to work together on shared semantics and bridging protocols to continue growing a heterogenous #fediverse built on the #OpenWeb.

    We know it is possible. We worked hard in the Social Web working group to align a lot of semantics across #ActivityStreams and #microformats2. The fruitful results of that are services like http://fed.brid.gy/ which I myself use to send a Webmention when I make a new post (like this one) and have #BridgyFed automatically federate it via ActivityPub using my personal site identity to #Mastodon followers and others.

    @snarfed.org wrote up a recent comparison of top #decentralized #socialProtocols that can help inform a lot of this discussion: https://snarfed.org/2023-09-04_50856

  9. 👍 to a comment on issue 43 of GitHub project “tpac2023-breakouts”

  10. ↳ In reply to Tantek’s note Shared times with Molly mostly captured on Flickr, our community sharing site of that era.


    Conferences like #SXSW #WWW2005 #OpenWebCamp and a @CSSWG meeting @W3C #w3cTPAC 2006.

    But this one hurts the most:
    Molly Holzschlag and Cindy Li at Web Directions North 2007.

  11. ↳ In reply to @zeldman’s tweet @Zeldman day by day my friend. If you would have asked a month ago I would have said no, for unrelated reasons which are thankfully mostly resolved.

    At #w3cTPAC this week, with many who also knew Molly. I expect there’ll be a lot of sharing.

    Day by day.

  12. I was traveling when I heard the news about Molly Holzschlag (@mholzschlag).


    Her #CSS #accessibility #OpenWeb contributions are well documented. May she be at peace. Appreciated @Zeldman.com’s (@Zeldman) note: https://twitter.com/zeldman/status/1699395939792822335

  13. Threads.net now supports the #indieWeb #microformats #openStandard rel-me for distributed ✅ verification!¹ (supported since 2023-08-09)

    My Threads profile already had my domain since it was created from my Instagram profile.

    View source on https://www.threads.net/@tantek and you can see the #relMe on a link tag:
     <link rel="me" href="https://tantek.com/" />

    Instructions to add yours:
    * Add your domain to your Threads profile "Link" field. That’s it.
    Longer explicit steps: https://indieweb.org/rel-me#Threads

    Thanks especially to @timothychambers.net (@tchambers@indieweb.social,  @timothyjchambers@threads.net) for requesting rel-me support² which one Threads engineer “decided to hack it together” one night!³

    You can view Tim’s profile @tchambers@indieweb.social for a real world example of a Mastodon profile showing a green text ✅ verified link to a Threads profile.

    Tim made several good points in his request:

    “… a small, but disproportionately helpful addition would be to support this "rel=me" feature in your profiles. That could launch well before full ActivityPub, & show the first real integration to open social web standards”

    Microformats (and IndieWeb) standards in general are deliberately designed as small, incremental building blocks which are disproportionately helpful as Tim says.

    These small building blocks which directly enable user features are usually something a web developer can code at least some (often complete!) support for in one day/night which makes them particularly appealing as a way to rapidly support open #socialWeb standards used by the #fediverse and beyond.

    Incrementally implementing microformats & IndieWeb standards also demonstrates good will and good intentions for supporting the #openWeb.

    This is day 44 of #100DaysOfIndieWeb. #100Days

    ← Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse
    → 🔮

    * 2023-02-01 Wikipedia.org supports multiple rel=me links: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me

    ¹ https://www.threads.net/@mosseri/post/Cvu2eXurRbB
    ² https://www.threads.net/@timothyjchambers/post/CupCvChAxI8
    ³ https://www.threads.net/@0xjessel/post/Cvu7-A4viZu

  14. ↳ In reply to a comment on issue 852 of GitHub project “standards-positions” Thanks https://github.com/bgrins for this summary write-up. Per this analysis I’m going to label our position on this proposal as negative.

    Since this is a proposal in a personal GitHub repo, and not standards track work nor in any open incubation group, there is no need for a dashboard entry. Closing accordingly.

  15. ↳ In reply to issue 8930 of GitHub project “csswg-drafts” Regarding History:
    > The earliest such proposal I could find was this one from 2009. (https://lists.w3.org/Archives/Public/www-style/2009Apr/0225.html)

    This sounded familiar (as in I thought I had proposed something similar a while ago), and it turns out I had proposed exactly a "tooltip pseudo-element" nine years earlier 🙈😭


    Note that the year 2000 was before the WG switched to the "::" prefix for pseudo-element selectors, so all pseudo-elements and pseudo-classes used the single ":" prefix.

  16. June #trailRunner #ultraRunner weekends
    3 finished #MUC50k @InsideTrail #RodeoBeach 9:38:28, my 3rd #50k #ultraMarathon #trailRace
    11 volunteered @TheDipsea #DipseaRace at #MuirWoods
    18 finished @BrokenArrowCA #BA23k 5:22:54 #RingDasBell, my 1st #skyRace
    24-25 crewed pal @davidtlam @wser.org 100mi to a successful #WS100 finish!

    #runner #running #trailRunning

    Heart & mind full, body pushed to its limits, capturing my experiences in a few write-ups.

  17. Two anniversaries today: microformats (18y) and POSSE (11y).

    Happy 18 years of https://microformats.org/ #microformats!

    Most prominent this past year (again) has been the littlest #microformat that could:

    rel=me — AKA #relMe, now effectively the standard for #distributed #verification on the web:
    * https://microformats.org/wiki/rel-me (originally introduced in 2004¹)

    with support added in the past year for:
    * #GitHub multiple rel-me links²
    * #Wikipedia User page rel-me link³

    Figure out how you want to fit into the network.
    #POSSE, short for “Publish (on your) Own Site, Syndicate Elsewhere”, as a term of use is now 11 years old³, which is surprising since when it was conceived, the #IndieWeb community was in a period of very rapid innovation & iteration.

    POSSE itself replaced a previous term, "POSE", short for “Publish Once Syndicate Everywhere”, which had only been around a year or two at most (I’m still looking for the first use of the "POSE" abbreviation for that meaning).

    Since “publish once” was vague enough to include practices of publishing once on a social media silo, or in someone else’s garage, we needed to clearly express the requirement to use your own site instead, first, as the source of your truth. Cross-posting to other sites & channels, is a second, optional step, ideally with a permalink linking back to your original post so viewers can easily discover and use your site.

    That distinction was enough for POSSE to express a strong creator-owned-first publishing model that resonated and grew. Every time a silo shutdown at the end of its incredible journey, removing posts & permalinks from the web, POSSE was there for people who were tired of losing their data, permalinks, & profiles, and wanted an alternative.

    This is day 43 of #100DaysOfIndieWeb. #100Days

    ← Day 42: https://tantek.com/2023/160/t1/mastodon-activitypub-follow-form-bridgy-fed
    → Day 44: https://tantek.com/2023/234/t1/threads-supports-indieweb-rel-me




    ¹ https://gmpg.org/xfn/11#me
    ² https://tantek.com/2023/032/t1/years-relmeauth-replace-openid
    ³ https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me

  18. ↳ In reply to hachyderm.io user renegadejade’s post @renegadejade@hachyderm.io in short, yes, it is a thing!

    Lots of great replies to your post already about directly using #WithKnown or #WordPress with the #ActivityPub plugin, or cross-posting from/via GitHub.

    Another #IndieWeb compatible option is Bridgy Fed (https://fed.brid.gy/) which can proxy posts, replies, likes etc. directly from a blog to #fediverse / ActivityPub (no #Mastodon account needed). Details: https://fed.brid.gy/docs

    This very reply to your toot is from my own domain, and its #hashtags are also discoverable via fediverse hashtags.

    I set up #BridgyFed last October¹ along with the broader #TwitterMigration I saw happening in my circles, and am quite happy with it. Posted more about my experience after a few months², and using BridgyFed to add a fediverse follow form to my homepage³.

    Whether WordPress, Known, or with another blog setup & Bridgy Fed, pick what works best for you and your setup. There’s #IndieWeb folks using each, feel free to drop by https://chat.indieweb.org/dev to chat more about any IndieWeb/fediverse option!

    ¹ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
    ² https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
    ³ https://tantek.com/2023/020/t2/bridgy-fed-follow-form

  19. If you added a #Mastodon / #ActivityPub follow form to your #IndieWeb site based on Bridgy Fed (e.g. using code/instructions I previously posted¹), you need to update it to add another invisible input element for the "protocol", e.g.:

    <input name="protocol" type="hidden" value="web" />

    Otherwise people trying to use your form to follow you may see an error from #BridgyFed like:
    > Bad Request
    > Missing required parameter protocol

    Here is the complete example that I posted previously with the new invisible input:

    <form method="post" action="https://fed.brid.gy/remote-follow">
     <label for="follow-address">🐘 Follow
      <kbd>@tantek.com@tantek.com</kbd>:<br />
      enter your @-@ fediverse address:</label>
     <input id="follow-address" name="address" type="text" required="required"
            placeholder="@you@instance.social" alt="fediverse address" value="" />
     <input name="domain" type="hidden" value="tantek.com" />
     <input name="protocol" type="hidden" value="web" />
     <button type="submit">Follow</button>

    I also updated that previous post¹ with the new input in case people find that instead.

    This is day 42 of #100DaysOfIndieWeb. #100Days

    ← Day 41: https://tantek.com/2023/139/t1/wikipedia-supports-indieweb-rel-me
    → Day 43: https://tantek.com/2023/171/t1/anniversaries-microformats-posse

    ¹ https://tantek.com/2023/020/t2/bridgy-fed-follow-form

  20. ↳ In reply to an IndieWeb page @tchambers@indieweb.social thanks Tim! And now two more years of work on AB Priority projects¹ (and whatever else we come up with @AB@W3C.social).

    ¹ https://www.w3.org/wiki/AB/Priorities

  21. Congrats to fellow re-elected W3C Advisory Board (@AB@W3C.social @W3CAB) members:
    * @cwilso.com (@cdub@mastodon.social @cwilso)
    * @fantasai.inkedblade.net (@fantasai@w3c.social @fantasai)
    * Avneesh Singh
    and newcomers:
    * @reidmore@mastodon.social (@wendy_a_reid)
    * Song XU

    Thanks to Heejin Chung and Charles Nevile for your service on the #W3CAB.

    via #W3C (@w3.org @w3c@w3c.social @w3c): https://w3c.social/@w3c/110491804762139049

    Previously: https://tantek.com/2023/128/t1/w3c-advisory-board-election-support

  22. Ran my 11th #BayToBreakers in 1:47:11 on Sunday 2023-05-21, again the day after an @sfrunco.com (@SFRunCo) Saturday trail #run, but this time in the middle of a very long training run, my last before the rescheduled #MUC50k trail race. Ran over 4 miles to the start, hopped in the next race corral, ran Bay to Breakers with the colorfully costumed crowd, picked up my medal, ate a banana, ran back through Golden Gate Park, and then a bit more up city hills to round out 18 miles and 1000'.

    #2023_141 #SanFrancisco #runner

    2022: https://tantek.com/2022/138/t1/ran-baytobreakers

  23. 👍 to issue 493 of GitHub project “bridgy-fed”

  24. ↳ In reply to alpaca.gold user Jeremiah’s post @jeremiahlee.com (@Jeremiah@alpaca.gold) you’re right that the #IndieWeb is more of a movement. It’s a community based on shared values & principles¹, one of which is plurality², explicitly prioritizing interoperability over any “particular piece of technology”.

    As to “subdomains as usernames using #ActivityPub?”, myself and others are using our (sub)domains as usernames, e.g. via the #BridgyFed service³. Mine should be self-evident in the header of this post wherever you’re reading #fediverse posts.

    Completely agree that “a link that also works as a mention name is obvious / intuitable”, have been practicing that for a while, and wrote up some notes about how & why:

    * https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
    * https://tantek.com/2023/014/t4/domain-first-federated-atmention
    * https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
    * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo

    which I should organize into a longer blog post at some point.

    ¹ https://indieweb.org/principles
    ² https://indieweb.org/plurality
    ³ https://indieweb.org/Bridgy_Fed#IndieWeb_Examples

  25. ↳ In reply to a comment on issue 764 of GitHub project “w3process” Thanks for the FO Council experiments reports citations https://github.com/frivoal.

    > https://www.w3.org/2023/03/council-ttwg-report.html
    > https://www.w3.org/2022/11/council-das-report.html

    These two make it clear that Tim Berners-Lee was a member of at least two FO Council experiments, despite not participating in their final decisions.

    From these examples, we retract the premise of the second paragraph of this issue that "We believe the opposite was intended", and thus also the specific fix in that paragraph.

    We still think it would be better for the W3C Process for any "life member" of any group to be a non-voting member at most, however we will raise a separate new issue for that for consideration in the normal workflow of triaging & handling Process CG issues.

    Given the resolution of the semantics of the first two paragraphs for this issue, no Pull Request (PR) is necessary for those.

    For the remaining "consistency and to reduce the chance of confusion" point, as noted, that can go in a separate purely editorial issue/PR and is thus unnecessary to resolve this specific issue.

    Ok to close this issue without waiting for those separate issues/PRs to be filed.

  26. ↳ In reply to a comment on issue 764 of GitHub project “w3process” Thanks https://github.com/fantasai, despite multiple reviews, somehow missed that https://www.w3.org/Consortium/Process/Drafts/snapshots/2023-04#groups line:
    > … and a participant is a member of such a group.

    This resolves the semantics of the first paragraph of this issue as invalid, leaving only potential editorial confusion from the use of multiple terms for the same thing, which is not a MUSTFIX (issue title adjusted accordingly).

  27. 👍 to a comment on issue 764 of GitHub project “w3process”

  28. 👍 to a comment on issue 764 of GitHub project “w3process”

  29. New issue on GitHub project “w3process”

    Normative prose for role of Chair / Team Contact cites informative reference for description

    There are two sentences of normative prose that cite the informative Art of Consensus as [GUIDE] in the Informative References.

    The two sentences are in the Requirements for All Chartered Groups, specifically these two:

    The role of the Chair [CHAIR] is described in the Art of Consensus [GUIDE].


    The role of the Team Contact [TEAM-CONTACT] is described in the Art of Consensus [GUIDE].

    It is inconsistent and misleading for a normative sentence to claim that a description (implied to be normative from that context) is written in an informative reference.

    It also seems like a bad practice to import via prose "is described in " and essentially upgrade-by-reference external informative content into normative context.

    The relatively quick short-term fix would be to mark those quoted sentences of prose non-normative. E.g. move the above quoted sentences to their own class="note" role="note" paragraphs as:

    Note: The role of the Chair [CHAIR] is described in the Art of Consensus [GUIDE].
    Note: The role of the Team Contact [TEAM-CONTACT] is described in the Art of Consensus [GUIDE].

    respectively. That way the inline prose is clearly non-normative, consistent with the informative imports from and citations of the Art of Consensus [GUIDE]. We will work on a Pull Request to address this.

    Label: Needs Proposed PR

  30. New issue on GitHub project “w3process”

    New W3C Council and updated TAG Composition section errantly only includes Tim Berners-Lee from the TAG, in W3C Council Composition

    Update: per comments https://tantek.com/2023/144/t3/ and https://tantek.com/2023/144/t4/, the semantic points in this issue have been addressed, and remaining editorial issues or desired changes can be filed as separate issues/PRs, and this issue can be closed without waiting for those.

    While this is clearly not what the Experimental Formal Objection Council has been doing in practice, nor what was intended in Process 2023, the current language in the definition of the W3C Council Composition only includes "members of the Technical Architecture Group" (emphasis added), and the only literal member in the definition of the Composition of the Technical Architecture Group is Tim Berners-Lee, while the elected & appointed are labeled participants. By using different terms "member" and "participant" for disjoint sets of people, a literal reading must treat these as separate sets, and thus references elsewhere in the Process to "members" cannot be assumed to include "participants". This is not just ambiguity, a literal reading of the current Process 2023 draft forces an undesired composition of W3C Councils that only includes Tim Berners-Lee from the TAG in particular.

    We believe the opposite was intended, and this can be fixed by using the term "member" in the Composition of the Technical Architecture Group section to refer to the elected & appointed, and separately listing Tim as a "life-time invited participant, but not a member of the TAG for purposes of this document."

    This requires a Pull Request (PR) and we will work on submitting one that we believe addresses this issue which we believe must be a blocker for Process 2023.

    Similarly, for consistency and to reduce the chance of confusion, only the term "member" should be used to refer to those elected to the Advisory Board, rather than "participant". This can go in a separate PR, and we will work on providing this as well.

    Label: Needs Proposed PR

    Label: Director-free: FO/Council

  31. ↳ In reply to @stolinski’s tweet @stolinski
    43 CSS V&U length units¹
    em rem
    ex rex
    cap rcap
    ch rch
    ic ric
    lh rlh
    vw lvw svw dvw
    vh lvh svh dvh
    vi lvi svi dvi
    vb lvb svb dvb
    vmin lvmin svmin dvmin
    vmax lvmax svmax dvmax
    cm mm Q
    in pc pt
    +6 cont. q²
    cqw cqh cqi cqb cqmin cqmax
    +% = 50?

    ¹ CSS Values & Units Level 4: https://drafts.csswg.org/css-values/#lengths
    ² https://developer.mozilla.org/en-US/docs/Web/CSS/length#container_query_length_units