Tantek Çelik

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

💬 👏
  1. It was the longest day of the year, yet among the darkest days for the U.S.
    2300+ children still forcibly separated from their parents, “spread across states”:
    https://www.cnn.com/2018/06/21/politics/migrant-family-separation-what-next/index.html “by thousands of miles and a bureaucratic maze”: https://www.nytimes.com/2018/06/21/us/immigrant-children-separating-families.html

    All due to unacceptable inhumane directives from POTUS and the bible-distorting AG. Backing down to detaining whole families is still just cover for racist internment.

    More families being detained. More facilities being constructed. Because of an imagined (immigrant) threat.

    The parallels to WWII Japanese internment are blatant, yet here we are.

    It’s long past time to have the difficult conversations with friends and family that may have voted for POTUS, and the GOP that’s sacrificed all principles to support him. Keep the pressure up and see it through to making a difference in November.

    Previously: http://tantek.com/2016/314/t1/doublestandard-wtf

    on
  2. ↪ In reply to issue 93 of GitHub project “standards-positions” Mozilla has been participating in the design and development discussions of Houdini at the CSS Working Group since the beginning and continues to do so.

    For Houdini as a whole ("CSS Houdini family features" that have published drafts per this issue), I think the most accurate current summary position is "worth prototyping".

    As individual Houdini specifications technically mature (with web developer feedback & iteration) and assuming we see broader use-cases across the web, we can consider stating upgraded positions for each individual specification as appropriate, taking into account the importance of other web platform features.

    If anyone has concerns about particular Houdini drafts that should block an explicit "worth prototyping" position, please speak up and we can use "under consideration" while we file issues on those drafts and iterate accordingly.

    In addition, since https://github.com/surma ’s tracker was mentioned, this overall Houdini position should not be taken to apply to anything that is not yet at least a published working draft.

    If an explicit position is desired for proposals in https://ishoudinireadyyet.com without a working draft, please file separate issues for those.

    on
  3. CSS Basic User Interface Module Level 3 (#CSS3UI) is now a @W3C Recommendation!
    Congrats fellow co-editor @frivoal and thanks to the @CSSWG for all the hard work (and patience) for so many years. #openweb @CSS3UI
    https://www.w3.org/TR/2018/REC-css-ui-3-20180621/

    Previously: https://twitter.com/css3ui/status/941695566194597889
    and http://tantek.com/2015/189/b1/css-basic-user-interface-level-3

    on
  4. Happy 13th to @microformats.org!
    With more use of #microformats2^1, especially among the growing #indieweb^2 network of websites, we’ve iterated key^3 specs^4 for real-world needs and are seeing more active community members. More updates & posts coming up!

    ^1 http://microformats.org/wiki/microformats2
    ^2 https://indieweb.org/
    ^3 http://microformats.org/wiki/microformats2-parsing
    ^4 http://microformats.org/wiki/h-entry

    on
  5. 6 days til the 8th @IndieWebSummit gathers innovators, artists, designers, and journalists to share, make, and grow the independent web, publishing & interacting with each other using their personal websites instead of social media silos.

    Join us: https://2018.indieweb.org/

    on
  6. a jpg. Yesterday: finished my first #DoubleDipsea #race in 3:59:26! 📷 IG jasonthepatsfan
    Felt strong, especially on the downhill finish. When I saw the guy in front slow down with maybe 20 yards to go, I sprinted extra hard to beat him by mere feet: 620th of 691 finishers.

    #dserunners #optoutside #getoutside #raceeverything #run #runners #trailrun #trails #Dipsea #Stinsonbeach #Marin #yestergram #latergram #nofilter #2018_167

    Previously: http://tantek.com/2017/167/t2/went-double-dipsea-cheer-ran

    on
  7. ↪ In reply to @lightcoin’s tweet @lightcoin thanks for the post and photo!

    Would have loved to show more of @schnarfed’s great work on indiemap.org; definitely click through and try playing with the interactive network graph. Great visualization and data!

    on
  8. ↪ In reply to @csageland’s tweet @csageland thank you and looking forward to meeting you @IndieWebSummit!
    Got ideas for what you want to brainstorm and make?
    Join us in chat.indieweb.org (or via Freenode IRC, Slack, or Matrix indieweb.org/discuss#Join_Discussions)

    on
  9. likes @csageland’s tweet at , tweet at , and @lightcoin’s tweet at

    on
  10. RSVP yes to: www.eventbrite.com’s post going to Decentralized Web Meetup @InternetArchive tonight, looking forward to talking & sharing about #longevity #selfdogfooding #indieweb principles, demonstrating examples using my website, and inviting everyone to @IndieWebSummit!

    Links and thoughts for discussion:
    * Longevity https://twitter.com/internetarchive/status/741832908323708929
    * Use what you make https://indieweb.org/
    * Principles https://indieweb.org/principles supporting a plurality of projects
    * Owning my data, federating to participate: tantek.com
    * 2010+ every tweet, 2015+ photos & videos, 2017+ events
    * 2018-02+ GitHub issues, comments, reactions
    * indiemap.org
    * https://2018.indieweb.org/ - inviting everyone here to IndieWeb Summit in two weeks
     - back to selfdogfooding, it’s an indie event that accepts federated RSVPs, and also accepts sign-ups via webform.

    on
  11. ↪ In reply to a comment on issue 820 of GitHub project “beaker” Have been watching this thread, and want to also encourage vocabulary re-use wherever possible, as it greatly helps sharing content and bridging across various heterogenous systems.

    https://github.com/kevinmarks mentioned h-entry already, which builds on all the experience and expertise from RSS and Atom.

    Similarly, consider https://microformats.org/wiki/h-card (based on the IETF vCard standard, and adapted for the web and JSON-friendly) for references and descriptions of people.

    Most recently I saw the calendar-app event example in a previous comment, which could re-use https://microformats.org/wiki/h-event as well (similarly based on the IETF iCalendar standard). Happy to present an example using LZ syntax etc with h-calendar vocabulary if that would be helpful.

    All of these vocabularies have been both implemented and successfully interoperably deployed peer-to-peer across numerous websites, publishing and parsing / consuming. (stats and examples available at indiemap.org)

    Happy to help answer any questions about how these vocabularies are developed and how they’re community maintained, either here or chat.indieweb.org.

    on
  12. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. Remembering last Friday, running #hillsforbreakfast with #NPSF around a #waterfall on an #island in the middle of a lake in #GoldenGatePark, snapping wildlife, at sunrise. #takemeback #StrawberryHill #optoutside #getoutside #wakeupthesun #fromwhereirun #latergram #nofilter #2018_159

    on
  13. ↪ In reply to @xoxo’s tweet #XOXOFest, self-described “experimental festival celebrating independently produced art and technology”, opens for this year’s registration next week!

    http://blog.xoxofest.com/post/174829185270/registration-for-xoxo-2018

    Having been to @XOXO several times I highly recommend it to #independent #creatives of all backgrounds, even knowing the more people apply for it, the less chance I personaly have to go again (see blog post for details).

    on
  14. ↪ In reply to @Dries’s tweet Will miss you @Dries! Can you perhaps participate in the summit remotely? https://indieweb.org/2018#Remote_Participation
    Add yourself (no RSVP needed) https://indieweb.org/2018/Guest_Book#Remote_Participants
    And join the chat whenever you can and say hi! https://indieweb.org/discuss

    on
  15. The 8th annual @IndieWebSummit is in 2 weeks!

    Want to
    * Own your identity on the web
    * Reply to #Mastodon toots with your own website
    * Grow the practical user-centric #decentralizedweb #dweb
    * Build with @W3C + #IndieWeb standards & experts

    RSVP: https://2018.indieweb.org/

    Learn, get inspired, brainstorm, design, create, make, and help grow the present & future of the independent #openweb!

    on
  16. ↪ In reply to @ACLU’s tweet ICYMI: Yesterday #netneutrality protections expired. Via @ACLU (I‘m a member)
    https://www.aclu.org/blog/free-speech/internet-speech/how-net-neutrality-will-end

    This is a looming problem for everyone on the #internet, except maybe large telecomms shareholders.

    #openinternet #openweb #indieweb #sfallhands

    on
  17. #SFAllHands: @TheWebbyAwards lifetime achievement winner @MitchellBaker starts @Mozilla plenary with a reminder of the recent Manifesto addendum for a better open #internet. #openweb
    Previously: http://tantek.com/2018/133/t1/mozilla-manifesto-addendum

    on
  18. my #SFAllHands ⚡️intro
    * 8 yrs #openweb #standards @Mozilla[1]
    * may know me from: #CSS[2] #microformats[3] #indieweb[4]
    * recently: Standards Outreach w @david_bryant
    * editing: CSS2.2, CSS scrollbars
    * interesting: Vouch[5]
    * controversial opinion: technical contributors @Mozilla should be actively using their own website, even if just one blog post a year

    [1] https://wiki.mozilla.org/Standards
    [2] https://wiki.mozilla.org/CSS
    [3] microformats.org
    [4] https://indieweb.org/
    [5] https://indieweb.org/Vouch - vouching as a practical decentralized solution to commenting, with some trust without requiring a hard-identity, designed to reduce abuse etc. as we have seen in centralized social media, but distributed across the web peer-to-peer

    on
  19. Awesome #dweb/#openweb meetups & #IndieWeb Summit coming up!
    June
    13th: #DecentralizedWeb Meetup @InternetArchive
    18th: Re-Decentralising The Web, London @WebStandards
    26-27 @IndieWebSummit, Portland OR
    29th: @OSBridge, Portland OR

    Links & tickets: https://indieweb.org/Events#Upcoming

    on
  20. 👍 to issue 11 of GitHub project “gitpub”

    on
  21. ↪ In reply to a comment on issue 288 of GitHub project “confluence” I should have been more clear, it would be great if the Confluence Metrics graphs UI itself linked to the definition so it was more easily discoverable.

    I.e. by putting a span with an ID on the definition of "Grace Period" in the README, and then linking to that fragment from the web UI, by hyperlinking the first instances of "Grace Period" (with quotes) appearing in the div class="text-content" elements in https://github.com/GoogleChromeLabs/confluence/blob/301782981ff6eeee30f4d272dcce6635ed09c943/static/view/confluence.html

    I started a pull request at https://github.com/GoogleChromeLabs/confluence/pull/303 but figured you may have a more preferred method / markup for this.

    Thanks for your consideration!

    on
  22. ↪ In reply to aaronparecki.com’s post I think IndieAuth makes a lot of sense as the way to implement a federated login protocol to provide a "simpler UX for OAuth2" login for Gitea as this issue is named.

    It would also be possible to provide support for the "with GitHub" portion (as originally noted in the issue) without having to ask / wait for GitHub to implement IndieAuth, by adding https://indieweb.org/RelMeAuth support.

    https://indielogin.com/ is an example of an open source service that supports both of those, IndieAuth as github.com/aaronpk suggested and RelMeAuth, and is in daily use by folks signing-into the IndieWeb.org site.

    on
  23. RSVP yes to: a Facebook event went to Larkspur Community Run with Equator Coffees & Salomon @EquatorCoffees. Thanks @Amy_Leedham for the heads-up and Esther @SalomonSports for the Sense Ride shoe trial + Q&A! Despite many delays, made it, shoes were great, got a pair @SFRunCo!

    on
  24. Reminder @W3C Advisory Committee members:

    TODAY 23:59 EDT is the deadline to vote in the current @W3CAB election!

    Please take a few minutes to vote:
    https://www.w3.org/2002/09/wbs/101147/ab20180502/

    I and six others are running:
    https://www.w3.org/2018/05/02-ab-nominations

    Thanks for voting!

    on
  25. #NPSF Double PR Wednesday done!
    35:20 #earlygang ~5:30, no music
    34:40 #normalgang ~6:30, with music (19s slower than March)

    5hrs+ sleep. Some coffee. Again tough two sessions.

    Previously:
    2018-04: DNF. 1 lap, bathroom break, 2 more laps.
    2018-03: http://tantek.com/2018/087/t1/back-to-double-pr-wednesday

    on
  26. a jpg. a jpg. a jpg. a jpg. Grateful for so much this morning. Waking up with sunny skies, @Nov_Project_SF at Aquatic Park, sunbeams beaming and sparkling water.

    #NPSF #NovemberProject #SF #AquaticPark #beach #cove #sun #sunbeams #sparkling #water #nofilter

    on
  27. ↪ In reply to a comment on issue 2 of GitHub project “microformats2-parsing” I would disagree with applying this only to explicit u-photo, I think that would result in a surprise to web authors. The simpler model is to handle "alt" for u-photo regardless of whether it is implicit or explicit.

    In addition, why shouldn’t it apply to any use of u-* with an img?

    E.g. "u-featured" on an img should also pick up any alt attribute.

    In short, I’d rather NOT go through multiple proposal/consensus/prototype/changes to get "alt" to work properly. I’d rather we figure out how "alt" should work and change the parsing spec once to handle it.

    Note the issue name "image alt text is lost during parsing" is not specific to u-photo. Let’s fix this for any use of any image (img) tags in the parsing spec.

    on
  28. a jpg. a jpg. a jpg. a jpg. Overcast at #SFRC. Shorter run today (~11.1miles), still 2100+' of climbing.

    The cool weather was perfect for running, and the cloud cover provided nice diffuse lighting for the trail flowers. Made it to Muir Beach and touched the Pacific. Slowly getting faster at hills. Less than six months to ECSCA 50k.

    Previously: a few times in May (to be latergrammed) and tantek.com/2018/097/t1/last-saturday-sfrc-longest-trail-run

    #fromwhereirun #run #trail #trails #trailrun #optoutside #getoutside #Marin #Miwok #overcast #clouds #nofilter

    on
  29. RSVP yes to: 2018.indieweb.org going to IndieWeb Summit 2018! June 26-27th at the Elliot Center in Portland, Oregon!
    This will be the #indieweb #openweb #dweb event of the year. RSVPs limited to 100 total, sign-up before tickets sell-out: https://2018.indieweb.org/

    on
  30. Homebrew Website Club SF!

    When: Where: Mozilla San Francisco Host: Tantek Çelik

    17:30: Optional writing hour and quiet socializing
    18:30: IndieWeb demos and hack night!

    Homebrew Website Club retro 1980s-style logo

    Topics for this week:

    • Drupal and Mastodon add more IndieWeb support
    • IndieWeb Summit 2018 at 30+ sign-ups, including new keynotes!
    • No HWCSF in June! Come to the IndieWeb Summit instead!
    • What does the "decentralized web" or "distributed web" or just #dweb mean to you?

    Demos of personal website breakthroughs. Create or update your personal web site!

    Join a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web!

    Any questions? Ask in #indieweb Slack or IRC

    More information: IndieWeb Wiki Event Page

    RSVP: on the Facebook event or post an indie RSVP on your own site!

    on
  31. ↪ In reply to issue 3704 of GitHub project “html” Registration (on the microformats wiki) works fine. I just tried it and created a new account. If you are having trouble understanding the microformats wiki, whether with registration or anything, please state the problem as a question and check the FAQ accordingly: http://microformats.org/wiki/faq

    Recommend closure of issue #3704, works for me, no changes to HTML Standard needed.

    on
  32. ↪ In reply to a comment on issue 2696 of GitHub project “csswg-drafts” https://github.com/upsuper your suggested text makes sense to me, and I have also added an explicit note so implementers hopefully don’t accidentally propagate body to viewport.

    Please take a look at the prose after the property value table at https://drafts.csswg.org/css-scrollbars-1/#scrollbar-color-properties and if the updates are sufficient to resolve this issue, go ahead and close.

    on
  33. ↪ In reply to issue 2660 of GitHub project “csswg-drafts” Thanks https://github.com/upsuper, this suggestion makes sense per your reasoning. I have updated the spec accordingly. Please take a look https://drafts.csswg.org/css-scrollbars-1/#scrollbar-color-properties and if the updates are sufficient to resolve this issue, go ahead and close.

    on
  34. 🎉 to issue 824 of GitHub project “bridgy”

    on
  35. ↪ In reply to issue 2696 of GitHub project “csswg-drafts” Thanks https://github.com/upsuper and good call. Do you have any preferred wording for this, or shall I clone language from https://drafts.csswg.org/css-overflow/#overflow-propagation ?

    on
  36. 👍 to issue 2696 of GitHub project “csswg-drafts”

    on
  37. Ran #BayToBreakers 2018 Bonus 15k in 1:46:11! Slower pace than last year, but longer distance.

    ~3.5 min slower than the Hot Chocolate 15k: http://tantek.com/2018/007/t2/finished-hot-chocolate-15k

    Last year: http://tantek.com/2017/142/t1/beautiful-day-people-baytobreakers

    on
  38. The @W3CAB is now actively tracking @W3C Process issues in public @GitHub https://github.com/w3c/w3process/issues e.g. we recorded a consensus today: https://github.com/w3c/w3process/issues/190#issuecomment-389439047
    This is a new level of #OpenAB transparency, working in the open in real time (when we can)

    on
  39. 👍 to a comment on issue 190 of GitHub project “w3process”

    on
  40. 👍 to a comment on issue 190 of GitHub project “w3process”

    on