Tantek Çelik

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

💬 👏
  1. signed up for @insidetrail Marin Ultra Challenge 50 Mile #MUC50 on 2022-03-12! https://insidetrail.com/calendar/marin-ultra-challenge/

    I ran this in 2020, unofficially after it was canceled 2 days beforehand https://tantek.com/2020/073/t3/racekit-muc50 https://tantek.com/2020/075/t1/50-miles-running-muc50-trails https://tantek.com/2020/081/t2/dark-stormy-morning

    My goal is to finish, healthy, within the time limit of 14.5h

    Pacers are allowed the last ~20miles. @-me if you want to help out!

    on
  2. ↳ In reply to @schnarfed’s tweet 🎂 Happy birthday Bridgy! Congrats Ryan (@schnarfed), contributors, users!

    10 years of bridging #indieweb & #socialmedia. #POSSE posts, #backfeed responses. #Federate systems, like the web was invented to.

    Stats & charts & more: https://snarfed.org/2022-01-08_happy-10th-birthday-bridgy

    on
  3. If I post notes to my site instead of Twitter, who will see them?

    It’s not either or, it’s yes and.

    Post to your Own Site, and Syndicate Elsewhere (to Twitter etc.) https://indieweb.org/POSSE

    POSSE directly or use a service like https://brid.gy

    on
  4. I, for one, welcome all the independents speaking truth to power, criticizing organizations when they do or encourage harmful actions, especially in a systemic or global scope.

    Even better when folks post said critiques to their personal sites. #indieweb

    on
  5. Posting notes on your site is the “Hello World” of the independent web.

    If you speak to the ideals of the #openWeb #decentralizedWeb #distributedWeb #federatedWeb #indieWeb or even #smallWeb, walk your talk: post your notes somewhere you control. Whether static HTML, server-generated from storage, or a service supporting your domain, choose a method that works sustainably for you, and stick to it.

    Questions about options and when or why to choose one or another?

    Ask: https://chat.indieweb.org/

    on
  6. Happy 2022 friends!

    12 years ago I began posting notes on my site before Twitter: https://tantek.com/2010/001/t1/declaring-independence-building-it

    Have a site? Own your notes in 2022.

    Be the #P2P #decentralization you want to see, instead of tweeting to the wind.

    Questions? Ask the #indieweb community:

    https://chat.indieweb.org/

    2 years ago: https://tantek.com/2020/001/t1/10-years-notes-my-site

    on
  7. #UnintendedTrilogy (#MoviesThatShouldBeATrilogy) that I’ve told friends about for a few years:

    1974 The Conversation
    1998 Enemy of the State
    2004 I, Robot

    Gene Hackman plays the same character in the first two, Will Smith in the latter two. Many have posted about EOTS being a sequel to TC, e.g.:
    * https://screenrant.com/enemy-state-conversation-sequel-fan-theory-explained/
    * https://web.archive.org/web/20211223220730/https://www.avclub.com/to-be-continued-sort-of-11-unofficial-sequels-1798273052/slides/2 (Internet Archive version because too many 3rd party scripts on avclub)
    * https://twitter.com/treatshair/status/1468952964261896195
    and it was quite obvious to anyone who saw Enemy of the State after seeing The Conversation.

    The key to extending this to a trilogy is what happens to Will Smith’s character. In EOTS, his character evolves from having mild techno-optimism/naïveté towards a more critical outlook by the end. In I, Robot, his outlook has continued evolving into full-on techno-skepticism, and he has several encounters where others treat him as crazy or paranoid after he is attacked by robots. Plus there’s his line:

    “Does believing you're the last sane man on the planet make you crazy? 'Cause if that's the case, maybe I am.”

    Along the way he has also held onto non-networked, non-smart technologies like his old motorcycle, further underscoring his established techno-skepticism.

    I’ll leave it at that for now, and may add more later to fill in the narrative & connections between Enemy of the State and I, Robot.

    on
  8. ↳ In reply to @toddbarnard’s tweet @toddbarnard that’s a well-written article, with many good critiques.

    However, I’m not the author, @tante is.

    on
  9. #CSS Scrollbars Styling Module Level 1 is a @W3C Candidate Recommendation (CR)
    https://www.w3.org/TR/2021/CR-css-scrollbars-1-20211209/ which is a call for implementations, cc: @googlechrome @webkit

    Thanks @CSSWG and congrats co-editors @cssrossen @frivoal!
    https://twitter.com/w3cdevs/status/1468958585904193554

    'scrollbar-width' & 'scrollbar-color' are much easier to use than prior -webkit- prefixed mechanisms. Firefox has an implementation of both properties, see MDN for details:
    * https://developer.mozilla.org/en-US/docs/Web/CSS/scrollbar-color
    * https://developer.mozilla.org/en-US/docs/Web/CSS/scrollbar-width

    on
  10. 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
  11. 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
  12. 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
  13. 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
  14. ↳ 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
  15. 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
  16. likes @jyasskin’s tweet

    on
  17. ↳ 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
  18. 💉 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
  19. 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
  20. ↳ 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
  21. ↳ 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
  22. 👍 to issue 1077 of GitHub project “bridgy”

    on
  23. 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
  24. likes @solarpunk_girl’s tweet

    on
  25. 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
  26. ↳ 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
  27. likes @edent’s tweet at , @samuelgoto’s tweet at , and @dweekly’s tweet at

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

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

    on