Tantek Çelik

Inventor, writer, teacher, runner, coder, more.

💬 👏
  1. ran the Spartan Turkey Trot #5k #race in 31:11 (MV CA, 8°C). my 2nd fastest on the @SpartanTurkey5k course, and first #turkeyTrot in 4 years! A pleasant surprise.
    niece(11) crushed it in 23+min, nephew2(14) in 29+min, dad in 38+min. #turkeyTrot2021

    Arrived early at Mountain View High School to do a warm-up, my first “proper” warm-up before a 5k. ~10min moderate steady running, a 1min intense push, then 4x 30s strides, and walked it off.

    Found my dad, niece, nephews and waited in wave 2 only a few minute before we got started.

    First mile felt a lot stronger than any flat road mile I’ve run in quite some time, at least a couple of years. Passing the 1 mile marker at under 10 minutes felt really good. Paced slowed a bit, but still passed the 2 mile marker at under 20 minutes. That’s when I knew I had a chance at a 31-something time. Tried to keep pushing in the last mile or so, and it went faster than I expected.

    When I reached the track for the last 300m, all my Kezar training kicked in.  Gradually picked up the pace until I kicked as hard as I could on the final 100m straight, passing several, not being passed by anyone.

    Stopped my watch after crossing both timing strips after the finish arch: 31:13. Official result: 31:11 (updated)
    Feels like with some training I could get a sub-30 next year.

    More: https://www.spartanturkeytrot.com/

    Previously:
    2017-11-23: 30:21 personal CR. No post, only a mention: https://tantek.com/2017/333/t1
    2016-11-24: 31:27. https://tantek.com/2016/329/t1
    2015-11-26: DNR. Recovering from injury. https://tantek.com/2015/330/t1
    2014-11-27: Time unknown. https://tantek.com/2014/331/t1
    2013-11-28: https://tantek.com/2013/332/t2
    2012-11-22: https://tantek.com/2012/327/t2

    on
  2. since the US & Europe switch DST on adjacent weekends, a well planned trip can skip weird DST-change ∆1hr effects* inside larger timezone shifts.

    there’s still winter “standard time” sunset before end of workdays and its problematic effects** (<17:00 here, and most of the U.S.).

    one possible solution, for those who have the option, is to set a 16:00 end to the workday. e.g. change your "Working hours" in Google Calendar to end at 16:00 to at least discourage meetings after that: https://calendar.google.com/calendar/u/0/r/settings


    *Undesired effects of DST-changes:
      - https://pubmed.ncbi.nlm.nih.gov/7398616/
      - https://www.healthline.com/health-news/daylight-saving-time-is-ending-how-to-adjust-to-the-change
      - https://www.forbes.com/sites/brucelee/2021/03/13/daylight-saving-time-starts-sunday-here-are-the-problems-and-what-to-do/

    **Problems of workdays ending in the dark
      - https://www.ccohs.ca/oshanswers/psychosocial/violence_working_late.html
      - https://labornotes.org/2021/10/letter-carriers-resist-after-dark-delivery

     
    Related reading/tips for wrapping up a work day, especially by a certain time:
    * https://blog.doist.com/end-work-day/
    * https://www.forbes.com/sites/jacquelynsmith/2012/08/28/14-things-you-should-do-at-the-end-of-every-work-day/
    * my favorite: schedule and go for a walk before sunset, during Golden Hour https://en.wikipedia.org/wiki/Golden_hour_(photography)

    on
  3. inspired by @csswizardry @btconf, tried ct.css on my homepage (had to disable HTTP CSP), & only 1 green box!

    No <script> in <head>, no problem.

    If you support Progressive Enhancement (all sites should), scripts can go at end of body, right before </body>

    on
  4. RSVP yes to: an IndieWeb event attending @IndieWebCamp #Düsseldorf!
    🗓 11/11
    📍 #Zentralbibliothek
    🎟 https://2021.indieweb.org/dusseldorf

    On holiday in Germany, popped over to see friends @btconf & help with the #IndieWebCamp side-event!

    More on the #IndieWeb wiki: https://indieweb.org/2021/D%C3%BCsseldorf

    on
  5. ↳ In reply to @HenriHelvetica’s tweet @HenriHelvetica @cwilso @carlfwalsh @Malcolm1001 @cyberspice @slightlycode @LEGOEngineering can confirm, me @sfalken @jimmyg and a handful of others. At the time I collected links here: https://tantek.com/ie/macielinks.html
    See also this thread: https://twitter.com/jimmyg/status/1213810286077054977

    on
  6. registered to run #BayToBreakers 2022-05-15!
    Join me in corral A! https://baytobreakers.com/

    @baytobreakers said $39.99, and again registration added $5.95 for “Handling”, for what? Why separate? Why not charge $46?

    Previously: https://tantek.com/2019/304/t1/registered-run-baytobreakers-2020

    on
  7. likes @jyasskin’s tweet

    on
  8. ↳ In reply to issue 154 of GitHub project “standards-positions” Locking this conversation. We asked folks a week ago (https://github.com/mozilla/standards-positions/issues/154#issuecomment-948985820) to keep it on topic and subsequent comments for the most part have not, nor have they added any new technical information (advocacy, "implications", "consequences", SDO processes, and market dynamics are not; there are other venues for those things, and if you’re not sure where, start with your own blog).

    on
  9. 💉 J&J boosted.

    Previously, previously, previously:
    https://tantek.com/2021/105/t1/fully-vaccinated
    https://tantek.com/2021/093/t1/days-til-fully-vaccinated
    https://tantek.com/2021/092/t1/jnj-vaccinated

    #JNJ #COVID19 #vaccinated

    #GetVaccinated to protect those who can’t (<12yo, or yet like 5-11yo), and continue to #WearAMask

    on
  10. Led two #w3cTPAC breakout sessions this week:
    * Environmental Concerns and #Sustainability (#s12y) of Web Technologies[1]
    * What is the value of and are the values of @W3C[2]
    and helped @seaotta with
    * What is the WebWeWant.fyi[3]
    Notes:
    [1] https://www.w3.org/2021/10/19-sustainability-minutes.html
    [2] https://www.w3.org/2021/10/22-what-values-minutes.html
    [3] https://www.w3.org/2021/10/19-webwewant-minutes.html

    Also participated in Accessibility & CSS (https://www.w3.org/2021/10/20-cssa11y-minutes.html).

    Preparing for, speaking, facilitating, and participating in virtual TPAC sessions a second year in a row was very draining. Despite that, I thought the sessions went fairly well overall.

    Most passionate and contentious was the session on sustainability, especially regarding what we should (or should not) do @W3C. There was a lot more alignment on the seriousness and urgency to act than I expected, and I was pleased to see that.

    There was a lot of support for figuring out how to establish Sustainability as an aspect of Horizontal Review of all technical specifications, as important as Accessibility (a11y), Internationaliation (i18n), Security, and Privacy. This would likely require an explicit Interest Group, with a charter, discussed and voted on by the W3C’s Advisory Committe (AC).

    Our shared sense of urgency made it clear we needed to start something sooner rather than later. A Community Group (CG) makes the most sense in the short term, chartered to work on both immediate horizontal review and the establishement of a more official Interest Group.

    I created a #sustainability channel on the W3C’s Community Slack instance for informal discussions to get a Community Group started.

    Join us: https://www.w3.org/wiki/Slack

    on
  11. ↳ In reply to issue 154 of GitHub project “standards-positions” Reminder on comments on standards-position issues:

    Please keep it on topic, and respectful, per https://github.com/mozilla/standards-positions/blob/main/CONTRIBUTING.md#discussing-mozillas-position-on-a-web-specification

    Thanks,

    Tantek

    on
  12. ↳ In reply to issue 1077 of GitHub project “bridgy” Most important here is Bridgy backfeed support for existing discussion posts on GitHub, similar to the backfeed support for responses to GitHub issues.

    Bridgy Publish of a "discussion" post would be great too, should that be a separate issue / feature request?

    on
  13. 👍 to issue 1077 of GitHub project “bridgy”

    on
  14. New issue on GitHub project “bridgy”

    Feature request: Bridgy backfeed reacjis on POSSEd comments

    In Bridgy backfeed documentation it says "Bridgy detects and sends webmentions for … GitHub comments and emoji reactions on your issues and pull requests" which would seem to imply that Bridgy does not yet send webmentions for emoji reactions (reacjis) on POSSEd comments on GitHub issues and pull requests, e.g. the reacjis on this comment POSSEd by Bridgy.

    According to GitHub API docs: List reactions for an issue comment it looks like this information is available in the GitHub API. It would be great if Bridgy could add support for backfeeding reacjis on POSSEd comments! Thanks for your consideration.

    on
  15. likes @solarpunk_girl’s tweet

    on
  16. RSVP yes to: an IndieWeb event attending @IndieWebCamp Create Day (today!) and working on my personal #openweb site. This week’s @W3C #Instagram & #Facebook #outages were a good reminder to cook what we want, and eat what we cook.

    #IndieWeb RSVP & Zoom: https://events.indieweb.org/2021/10/indieweb-create-day-ZKw5v2nFDu6f

    on
  17. ↳ In reply to issue 282 of GitHub project “strategy” Mozilla also prefers the W3C Software and Document license for working group charters, and we have been consistently requesting this license whenever charters are updated.

    on
  18. likes @edent’s tweet at , @samuelgoto’s tweet at , and @dweekly’s tweet at

    on
  19. 👍 to a comment on issue 25 of GitHub project “ethical-web-principles”

    on
  20. 👍 to a comment on issue 25 of GitHub project “ethical-web-principles”

    on
  21. 👍 to a comment on issue 41 of GitHub project “WebID”

    on
  22. ↳ In reply to a comment on issue 25 of GitHub project “ethical-web-principles” tl;dr: prefer using phrase “manipulative design” instead of “harmful patterns” as a replacement for “dark patterns”.

    Also adding thanks to https://GitHub.com/LeaVerou, and agreed with the reasoning in https://www.ccianet.org/wp-content/uploads/2021/06/2021-05-28-CCIA-Comments-on-FTC-Dark-Patterns-Workshop.pdf (since this issue was filed!) particularly from an inclusiveness perspective, “[avoiding] connection of “dark-light dualism” to judgments about morality”.

    And as https://GitHub.com/harrybr is quoted: “during the Workshop by Professor Harry Brignull, while the term “dark pattern” (originated and popularized in part by Brignull) has been useful for marketing and raising awareness, it would be both “vague and sloppy” if used as a legal term or standard.”

    That being said, “harmful patterns” is vague and dilutes the intent of this issue.

    It’s also not strictly accurate from the perspective of a company implementing such patterns, from their (typically attention/growth/profit-maximizing) perspective, such patterns are helpful to them personally, their shareholders/investors if any, and not harmful.

    Such patterns are also too easy for such companies to hide behind a vague "intent" of supposedly "helping" people connect (quiet importing of contacts, suggesting joining radicalizing groups), or "helping" people get products they want/"need" (deceptive marketing, creating fear/insecurity in people’s minds then selling them a product to cope), etc.

    More precise (and preserving of intent, meaning, and literal effect) would be the phrase “manipulative design”, also used & recommended by that ccianet workshop (same link): “Rather than employ the terminology of “dark patterns,” these comments will refer to “manipulative design” practices or interfaces”.

    on
  23. After @Facebook & @Instagram outages and today's @W3C #outage https://status.w3.org/incidents/lfwjx05yvldr, I’m wondering if there is a secret movement to get people to stop depending on any corp/org sites to get things done. #W3Cdown #redecentralize

    🤔

    (#indieweb is open, not secret)

    on
  24. likes @nuzz’s tweet

    on
  25. ↳ In reply to @stop’s tweet @stop same friend, same. Maybe we could even do an easy run/walk/chat sometime (saw "Wanna-be runner" in your bio, and tbh often still feel that myself)

    on
  26. likes @stop’s tweet at , @bbedit’s tweet at , aaronpk’s note at , and note at

    on