Tantek Çelik

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

💬 👏
  1. ↳ In reply to issue 6 of GitHub project “AB-public” This is another “to-do list” issue that is open-ended and requires someone to go through a bunch of somewhat lengthy existing discussions elsewhere to try to extract specific proposals for improvement, similar in that regards to https://github.com/w3c/AB-public/issues/2 except that was primarily about extracting from a curated pre-existing crafted text, and this issue is more of an amalgam of a bunch of lists of things from several authors, some of which are already handled in the Vision.

    Similar to https://github.com/w3c/AB-public/issues/2:

    Proposed resolution:
    * defer this issue and leave it open to specific proposals (in new issues) for inclusion of any relevant specific points & content from the those old discussions. If there are no specific proposals by end of year 2022, close this issue without changes, noting that new issues for specific points may still be raised, yet due to lack of interest, no one is being assigned to attempt to extract specific points from other people’s lists made in GitHub comments. I.e. if folks feel strongly about specific points in their lists, it is their responsibility to file new specific issues for each point they feel strongly about.

  2. ↳ In reply to issue 5 of GitHub project “AB-public” Original issue both has some points and may be requesting more detail than is appropriate for a Vision document.

    Per the one response on the original issue, I’m not sure how to adequately address this issue either, except to perhaps consider linking to more detailed documents regarding “good of its users” and “safe for its users”, though I’m not certain enough about that approach to propose resolving in that manner. That is, this issue may merit some additional time and thoughtful consideration to come up with ways to address the points the original issue creator brought up.

    Proposed resolution:
    * keep this issue open to asynchronous discussion til the end of the year 2022. If it hasn’t made progress by then, consider linking the phrases “good of its users” and “safe for its users” to other related documents at W3C such as the TAG Ethical Web Principles https://www.w3.org/2001/tag/doc/ethical-web-principles/

    Alternatively, if the AB deems that consideration (just linking those phrases to the TAG Ethical Web Principles) sufficient now, I would be ok with making edits to the Vision accordingly and closing the issue.

  3. ↳ In reply to issue 4 of GitHub project “AB-public” Original issue had one response pushing back on how this was attempted in crafting the Vision but essentially did not work in practice.

    Having worked on the Vision myself and seeing firsthand that combining principles related to the web and W3C in one document provides important context, and improves understanding & collective sense-making, I agree with the pushback.

    As there was no follow-up response (for nearly 3 months), and I don’t think this is worth pursuing:

    Proposed resolution:
    * close this issue without changes, as addressed by the response in the original issue and this follow-up comment.

  4. 👎 to issue 4 of GitHub project “AB-public”

  5. ↳ In reply to issue 3 of GitHub project “AB-public” This is an astute insight. The Vision’s Purpose section https://github.com/w3c/AB-public/tree/main/Vision#our-purpose-focusing-on-the-integrity-of-the-web can be improved in many ways to more explicitly document W3C’s existing practices which serve the public at large.

    Proposed resolutions:
    * Add “and public feedback” to the end of the first point “Provide an open forum…”
    * Change “Ensure that standards are developed” to “Ensure that standards are openly developed”, perhaps defining “openly developed” in the Glossary per https://github.com/w3c/AB-public/issues/1 which could note that “openly developed” means publicly viewable discussion notes, proposals, issues, drafts, test suites, implementation reports, decisions, and conflict resolutions.
    * Add “for the public at large” after “… address evolving use cases”

  6. 👍 to issue 3 of GitHub project “AB-public”

  7. ↳ In reply to issue 2 of GitHub project “AB-public” Archived link to said “7 points” document for context:
    * https://web.archive.org/web/20210507094551/http://www.w3.org/Consortium/Points/

    There was a side comment in prior discussion of this issue to also consider updating other pages about mission, principles, and vision, such as:
    * https://www.w3.org/Consortium/mission
    However, “updating [other] existing pages” is off-topic for this specific issue, which is about updating the Vision document in particular.

    Proposed resolutions:
    * defer this issue and leave it open to specific proposals (in new issues) for inclusion of any relevant content from the old “7 points” document. If there are no specific proposals from the suggested old “7 points” document by end of year 2022, close this issue without changes.
    * create a separate new issue for “Update w3.org/Consortium/mission to align with updated Vision”

  8. ↳ In reply to issue 1 of GitHub project “AB-public” Proposed resolution: accept & resolve this issue: there was no objection in prior discussion, and it will help make the Vision more understandable to a broader audience, while helping it stay succinct which helps keep the Vision more accessible to a broader audience.

    Proposed next steps to close this issue:
    * create a Glossary file as a peer to the Vision document
    * stub it (explicitly) with scope (the Vision document) and one or a few obvious jargon terms from the Vision (e.g. “phishing”) with anchors
    * link to Glossary from the footer of the Vision document
    * link from the first occurence of a jargon term in the Vision to the specific term in the Glossary
    * add a “How to contribute” footer to Glossary encouraging proposed additions to grow the Glossary as necessary to define additional jargon terms in the Vision with broadly accepted uses & definitions within the W3C community, perhaps encouraging singular pull requests for terms that may require in depth discussion such as “centralization” or are otherwise contentious in actual practical use in W3C discussions.

    Aside: in the interest of re-use, resources at https://www.w3.org/Glossary.html may be helpful, but let’s please avoid the trap of creating yet another “system” (to be unmaintained & abandoned) like https://www.w3.org/Terms

  9. 👍 to issue 1 of GitHub project “AB-public”

  10. 👍 to a comment on issue 56 of GitHub project “microformats2-parsing”

  11. Since ~2021* I’ve redirected /github to my GitHub profile to own my links to GH repos like https://tantek.com/github/cassis

    Apache htaccess code to #OwnYourLinks:

    RedirectTemp /github https://github.com/tantek

    change /tantek to your GitHub /username

    More on this technique: https://indieweb.org/ownyourlinks

    * https://tantek.com/2021/084/t1/ownyourlinks-indieweb-github-redirect

  12. Ran my 10th #BayToBreakers in 1:38:32 on Sunday, apparently 3 seconds faster than the most recent in 2019, again the day after an @SFRunCo Saturday trail #run, and a double-day Friday.

    #2022_135 #SanFrancisco #runner

    2019: https://tantek.com/2019/139/t1/ran-baytobreakers

  13. May the 4th be with you!

    (except for Alioto and other #SCOTUS justices with plans to overturn #RoeVsWade)


    #MayThe4th #MayThe4thBeWithYou #StarWars #StarWarsDay

  14. @IndieWebCamp Düsseldorf is a wrap!

    For Create Day, I added code to my publishing system to only syndicate (POSSE) a reply post to Twitter if it actually has an @-name, otherwise if it’s a peer-to-peer reply, just directly send them a Webmention.

  15. ↳ In reply to calumryan.com’s post IndieWebCamp Create Day participants looking eager to create!

    Inspirational quote on https://indieweb.org/creator to get us started:

     “When you don’t create things, you become defined by your tastes rather than your ability. Your tastes only narrow & exclude people. So create.” — Why The Lucky Stiff

  16. ↳ In reply to calumryan.com’s post Nice photo of day 1 IndieWebCamp participants!

  17. likes Calum's photo at and Calum's photo at

  18. RSVP yes to: an IndieWeb event co-organizing @IndieWebCamp Düsseldorf this weekend with @marcthiele @calum_ryan @jkphl!
    🗓 2022-04-30…05-01
    📍 @cgi_global
    🎟 https://btco.nf/iwcdus22
    ℹ️ https://indieweb.org/2022/DUS

    Also excited for the @btconf main event! https://twitter.com/btconf/status/1519910629561319424

  19. Happy Earth Day!

    Thanks to the W3C #sustainability Community, we’ve created a W3C Sustainability Community Group (CG)!


    Last fall at my #TPAC2021 Sustainability session I proposed that W3C needed to consider sustainability for horizontal review. We now have a community group for discussing exactly that.

    Copied from the W3C Community Slack:

    Note past/existing CGs which this proposed group is not intending to replace (thanks Nick Doty for digging through CGs)


    I’m proposing starting the CG with myself (with background as leading the Sustainability session at TPAC 2021) and Nick Doty (experienced co-chair of Privacy Interest Group) as co-chairs to start with, and certainly open to adding additional co-chairs (especially those with both topical experience/expertise and experience de-escalating conflicts and promptly resolving Code of Conduct (CEPC) violations)

  20. On this 4/04 day, pour one out for sites & permalinks lost this past year like:
    * Google App Maker (site not found)
    * Yahoo Groups (posts & permalinks gone, subdomain redirects)

    More 404 Not Found: https://indieweb.org/site-deaths#2021
    #404NotFound, day of the #deadweb

  21. Introducing #metaformats (https://microformats.org/wiki/metaformats), an extension to #microformats2 for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations.

  22. Dear #SanFrancisco friends who went to #SXSW or #Austin #Texas recently, please stay home, isolate for a week, and test on days 5-7. The #SXSWSARS was particularly bad this year.

    #COVID19 #superSpreader #wearAMask


    h/t @KevinMarks

  23. Published today, years of working with co-workers @Mozilla and something I'm proud of: https://webvision.mozilla.org/

    #OpenWeb #IndieWeb fans & #WebDevs see https://webvision.mozilla.org/full/ with #HTML #CSS #JS, nods to nascent #OpenUI & #sustainability #s12y efforts, and a lot more.

  24. ↳ In reply to @tomcoates’s tweet @tomcoates I’ve been vicariously enjoying the @SwarmApp checkins, though there’s nothing like Austin in-person. Even for a (relatively new) plant-eating person. Missing Torchy’s tacos 🔥 and Iron Cactus’s made-at-the-table guacamole 🥑

  25. likes @tomcoates’s tweet at and @shiflett’s tweet at

  26. ↳ In reply to @shiflett’s tweet @shiflett thank you Chris! Hope you’re doing well friend.

    Also I relate so strongly to this: https://twitter.com/shiflett/status/968899276129488897

  27. likes @shiflett’s tweet

  28. Sometimes with months of nearly weekly meetings with co-workers & colleagues at other companies debating things, and building upon lots of prior hard work, you can help ship a pretty cool #openweb collaboration

    #Interop2022 blog posts:
    * https://hacks.mozilla.org/2022/03/interop-2022/
    * https://webkit.org/blog/12288/working-together-on-interop-2022/
    * https://bocoup.com/blog/interop-2022
    * https://web.dev/interop-2022
    * https://www.igalia.com/news/interop2022.html
    * https://aka.ms/microsoft-interop2022

    Really appreciated the time and thoughtfulness that everyone across companies put into this. It was great working together with so many folks that also care deeply about the open web and collectively making the web better for authors & developers.

  29. likes @mozhacks’s tweet