Tantek Çelik

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

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

  2. 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

  3. 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

  4. May the 4th be with you!

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


    #MayThe4th #MayThe4thBeWithYou #StarWars #StarWarsDay

  5. @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.

  6. ↳ 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

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

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

  9. 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

  10. 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)

  11. 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

  12. 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.

  13. 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

  14. 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.

  15. ↳ 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 🥑

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

  17. ↳ 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

  18. likes @shiflett’s tweet

  19. 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.

  20. likes @mozhacks’s tweet

  21. ↳ In reply to @seaotta’s tweet blog posts = top level posts on your own site. I like that.

    @seaotta re: discoverability, sharing posts, algorithm isn't serving

    give the algorithm no choice:
    * write all posts on your site (even replies & likes)
    * share (POSSE) them wherever people read

  22. likes @seaotta’s tweet at and tweet at

  23. ↳ In reply to @seaotta’s tweet @seaotta is it a length of post thing (longer than a tweet) or only posts with titles?

    or does neither matter as long as they’re on your own website (like this reply)?

    or do you mean top level posts (not replies) on your own site?

    #indieweb thoughts

  24. 🚀 to issue 82 of GitHub project “webappswg”

  25. 👍 to issue 82 of GitHub project “webappswg”

  26. ↳ In reply to @tomcoates’s tweet @tomcoates yes Google Search lost temporal depth, prioritizes days-old froth.

    Ironically, Twitter date-scoped search finds historical news links: https://twitter.com/search?q=Trump%20Ukraine%20until%3A2020-01-01%20since%3A2008-01-01&src=typed_query&f=live

    Wikipedia has a bunch: https://en.wikipedia.org/wiki/Trump%E2%80%93Ukraine_scandal

    Could use former to improve latter.

  27. Last month was the anniversary of two #IndieWeb #distributedWeb building block specifications becoming @W3C Recommendations:
    * 5y Webmention: https://www.w3.org/TR/2017/REC-webmention-20170112/
    * 4y WebSub: https://www.w3.org/TR/2018/REC-websub-20180123/
    Both specs are peer-to-peer mechanisms, Webmention for a site to notify another of a new or updated link to it, and WebSub for a site to broadcast (or subscribe to) notifications for when that site has published new content.

    Bridgy is a good source of metrics for Webmention. The Bridgy stats from last June https://snarfed.org/2021-06-05_bridgy-stats-update-6 show steady growth in both total Webmentions sent and perhaps more importantly, unique domains sending and receiving Webmentions. In addition the number of implementations & support libraries continues to grow, interoperable across multiple languages: https://indieweb.org/Webmention-developer#Implementations

    Webmentions still have interesting social and UX challenges. While spam has not (yet) been a major challenge, there is the larger challenge of how to semi-automatically moderate and/or prioritize handling webmentions received from others, especially people you have not met before. The nascent Vouch extension https://indieweb.org/Vouch has been prototyped and implemented on some sites yet needs some work to address the more sublte social challenges. There are challenges with even trusting and displaying the icons of authors who have sent webmentions. Pixelated icons https://indieweb.org/pixelated are one possible approach.

    WebSub has shown slower growth. While the number of sites that provide WebSub notifications for new content continues to grow: https://indieweb.org/WebSub#IndieWeb_Examples the number of hubs and hub implementations have been fairly stable for the past year https://indieweb.org/WebSub#Hubs as well as implementations that consume WebSub notifications: https://indieweb.org/WebSub#Consuming_Implementations

    The key next step for WebSub is more Reader implementations, e.g. in modern Social Readers https://indieweb.org/social_reader to provide realtime updates immediately when publishing sites post new content. Once there is broader incentive for more sites to provide WebSub notifications, consuming sites such as readers will have more incentive to implement receiving WebSub notifications, reinforcing a positive implementation feedback loop.

    With the combination of Social Readers showing new posts in real time via WebSub and personal sites showing new comments & other responses in real time via Webmention, the peer-to-peer web will provide a responsive experience comparable to centralized social media silos.

    Want to support Webmention and/or WebSub on your own site?

    Drop by the IndieWeb Developer chat and say hi!


  28. ↳ In reply to a comment on issue 27 of GitHub project “standards-positions” https://github.com/gobengo please use the Bugzilla bug for Web Share API to check for info about Firefox support in particular. In this case it looks like it was implemented in Firefox 71: https://bugzilla.mozilla.org/show_bug.cgi?id=1312422 (also linked from the standards-position dashboard entry via the wrench).

    You can also check the corresponding MDN page (also linked from the dashboard entry) if you only wanted to check whether or not Firefox (or another browser) supports it: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/share#browser_compatibility

    For Web Share Target API, I checked https://mozilla.github.io/standards-positions/#web-share-target and it also has a wrench icon link to its corresponding Bugzilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1476515