Tantek Çelik

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

💬 👏
  1. Dense past 2.5 weeks

    #HomebrewWebsiteClub @MozSF
    @W3C #CredWeb f2f @Meedan

    @theSFMarathon half
    @IndieWebCamp #SF / #DWeb #HackersDay
    #DWebSummit browsers panel
    & #indieweb talk
    #DataTransferProject f2f

    16.5mi run
    @W3CAB f2f @MIT
    Joshua Tree yoga retreat

    on
  2. ↪ In reply to tantek.com’s post One "simple" way to do this would be to create a public repo like: https://github.com/w3c/ABpub which would thus have public issues by default.

    on
  3. New issue on GitHub project “AB”

    @W3CAB issues ought to be public by default absent a specific reason to be kept private

    The W3C Advisory Board keeps track of some issues in a private repository in the W3C GitHub org: https://github.com/w3c/AB/issues and in my opinion the AB should move to tracking issues publicly by default instead.

    This requires two things: 1. creating new AB issues in a public forum/repo by default, and 2. analyzing current open issues to see if they can be moved to being public issues.

    I have created the public label in the existing repo to help with the latter, and am attempting to label this issue accordingly as well.

    As background, I created the public W3C AB wiki page five years ago which has served the group and W3C community quite well in practice. I think the AB can similarly benefit from public issues discussion by default.

    Labels: public, enhancement

    on
  4. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. Saturday’s #longrun: 16.5 miles & 2300'+ started with ~12 miles from home to the Tennessee Valley Trailhead, joined friends for a bit more, nearly 14 to the #beach. Climbed up for a view, ran back to the parking lot.

    #optoutside #getoutside #run #trailrun #runner #runners #sf #city #marin #trails #2018_216 #latergram #nofilter

    1. View of the city from SCA trail
    2. Sunrise on the Panhandle park
    3. Crissy Field Marsh
    4. Golden Gate and Bridge
    5. Flowers on the run up to GGB
    6. Rolling hills and the Pacific
    7. Alta trail and forest
    8. Tennessee Beach
    9. 📷 @thats_a_moret #selfie with Kelsey
    10. View from Coastal Fire Road

    on
  5. Gave my lightning talk at the #DWebSummit:

     #IndieWeb. Taking back your content with practical #decentralization steps

    Outline & links: https://indieweb.org/dweb2018

    Great questions everyone! Thanks @benwerd for posts and photo!
    https://twitter.com/benwerd/status/1025134936016076800

    on
  6. Started #IndieWebCamp SF with a brief intro then handed it off to our excellent keynotes:
    * Miriam Avery (evermoreperfecteyes.com, @myravery)
    * Dietrich Ayala (metafluff.com, @dietrich)
    * Ryan Barrett (snarfed.org, @schnarfed)

    on
  7. #IndieWebCamp SF / DWeb Hackers day is TODAY @MozSF!

    https://indieweb.org/2018/SF

    If you’ve RSVP’d already great! We’re expecting you at 10am.

    If you’re just hearing about this, reply or drop by https://chat.indieweb.org/ and say hello!

    on
  8. ↪ In reply to a comment on issue 36 of GitHub project “microformats2-parsing” https://github.com/sknebel yes that is the interpretation I intended, and thanks for the review and suggestion. I have added "explicit" explicitly :)

    http://microformats.org/wiki/index.php?title=microformats2-parsing&diff=66898&oldid=66890

    If with that change we have sufficiently resolved this issue 36, go ahead and close it. Thanks!

    on
  9. a jpg. a jpg. a jpg. Finished @theSFMarathon first half in 2:33:00.

    #TSFM2018 #SF #halfmarathon #runner #runners #overcast #baybridge #nofilter

    It was a muggy and overcast morning (photo 2).

    And I started at the end of the last corral for the #SFM first half marathon (photo 3), due to a series of transport mishaps! Race day bus route changes, cabs ignoring all attempts to hail (losing all sympathy for ride-hail ires).

    After a longer than expected warm-up (2.4 miles!), I finally caught a bus on Market street to the Embarcadero. The last corral for the SFM First half marathon was lining up to start. Took a quick pitstop and walked to the back of the corral.

    Got a good start and set a decent pace up to Aquatic Park and around to the Marina. I walked a bit every couple of miles. Ignoring my pace, I ran with my breath.

    After running by the bridge (under the roadway), down Lincoln to Seacliff, the race directed us on to 26th avenue into the park. Everything felt familiar from my practice run last Sunday, but a bit faster, despite the humidity.

    This new course (without the bridge) felt harder (more vertical climb I’m pretty sure).

    I didn’t see a single November Project person in the course or race. In fact I didn’t see anyone I knew at all. Quite a contrast from last year’s full marathon.

    I finished, just grateful to do so, feeling strong, without injury. That’s 13 half marathons. After walk-jogging home, I stretched, cleaned up, and met November Project friends for brunch in Potrero flats, where they had cheered and handed out water at mile 23 of the full marathon.

    Previously SF first #halfmarathon runs (including GGB)
    * 2016-07-31 2:27:37 tantek.com/2016/221/t2/moments-before-crossing-starting-line
    * 2014-07-27 2:23:45 tantek.com/2014/208/t1/finished-sf-half-marathon

    Previous half marathons-ish:
    * 2018-06-16 3:59:26 tantek.com/2018/168/t1/finished-first-doubledipsea
    * 2018-04-08 2:23:31 tantek.com/2018/098/t1/rock-n-roll-half-marathon-finished
    * 2017-11-11 3:32:20 tantek.com/2017/321/t2/last-saturday-racing-tam-half-marathon
    * 2017-02-05 2:24:58 tantek.com/2017/038/t1/race-time-faster-than-first-reported

    on
  10. ↪ In reply to @csageland’s tweet @csageland open to all curious about anything and everything #dweb #indieweb.
    Please join us!

    on
  11. RSVP yes to: tantek.com’s post co-organizing IndieWebCamp SF / Decentralized Web Hackers Day next Tuesday 2018-07-31 @MozSF, complementary to #DWebSummit 2018!
    <20 spots left!
    Details & RSVP: http://tantek.com/2018/212/e1/indiewebcamp-sf-dweb-hackers-day
    #mozilla #openweb #indieweb #dweb

    on
  12. One year ago today:
    Finished my first #marathon @theSFMarathon #TSFM2017
    http://tantek.com/2017/253/b1/my-first-marathon #2017_204

    on
  13. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. Twin Peaks #hillsforbreakfast in #clouds (1), #sunshine in Glen Canyon (2-3), succulents en route back to Twin Peaks (4), #extravert up Tank Hill (5), Mount Olympus (6), Corona Heights (7-8), Buena Vista (9-10) for 8.9 miles & 2533'

    #optoutside #getoutside #run #trailrun #runner #runners #sf #city #nofilter

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

    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
  15. IndieWebCamp SF / #DWeb Hackers Day

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

    In town for the Decentralized Web Summit August 1-2 and not otherwise busy on July 31st?

    Mozilla invites you to a complementary (and complimentary) all day Decentralized Web Hackers Day and IndieWebCamp SF at our Mozilla San Francisco offices.

    Spend a day creating the web you want collaborating with others doing the same, using the latest in decentralized and indieweb technologies.

    Schedule

    • 10:00 Opening keynotes and lightning intros/demos
    • 11:15 BarCamp breakout session scheduling
    • 12:00 Open hack day and discussion sessions
    • 16:00 Lightning Demos!
    • 17:00 Wrap-up and transit to DWeb pre-party

    We will open the day with a few brief introductory keynotes to set the stage and get your creativity flowing, followed by a round of lightning intros/demos by participants who want to (yes that means you!)

    In our usual BarCamp style, we’ll spend a few minutes having participants propose different discussion/hacking sessions for the day and pick rooms & time slots. Sessions will start promptly after scheduling. Don’t worry if this is your first time participating in a BarCamp, we will explain the process for everyone and especially make sure newcomers get a chance to propose their session ideas.

    Final sessions and hacking will wrap at 16:00 and we will all reconvene in the main room for a round of lightning demos of hacks, insights, whatever you made or thought up.

    Afterwards we’ll direct you to local transit that will take you to the Internet Archive for the Decentralized Web Summit Science Faire and Pre-party (requires separate registration)

    Any questions? Ask in #indieweb Slack or IRC

    More information: IndieWeb Wiki Event Page

    RSVP: post an indie RSVP on your own site or add yourself to the wiki (or both!)

    Optional: Facebook POSSE event for your calendaring convenience

    on
  16. ↪ In reply to adactio.com’s post @adactio not “yet prove to be” but rather Santa Cruz has been for almost 7 years already (nearly 6 years at the time of your @adactioJournal post).

    Posted about it at the time: http://tantek.com/2011/228/t4/minority-report-programs-not-precogs-santa-cruz

    #minorityreport #precog #precogs #precrime #ai

    on
  17. ↪ In reply to issue 803 of GitHub project “bridgy” Here is another more recent example:

    http://tantek.com/2018/190/b1/scrollbar-gutter-move-to-css-scrollbars

    New issue, with two labels: css-overflow-4, css-scrollbars-1

    Only the first label was added to the Bridgy Publish POSSE copy:

    https://github.com/w3c/csswg-drafts/issues/2899

    Is this the same problem? I thought perhaps with the switch from GraphQL to the GitHub v3 API a few weeks (months?) ago, this might have been fixed at the same time.

    Whatever the cause is, some labels are still not getting through via publish.

    on
  18. 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:

    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
  19. a jpg. a jpg. #TBT to the Rodeo Valley 30k and how good the first half felt, running uphill (1) and downhill (2). Then learning in the second half that I had what it took to endure hours of 90-95°F temperatures to run, jog, and hike to finish a five hour trail race. Race photos 📷 Chris Cleary @insidetrail

    #optoutside #getoutside #run #trailrun #insidetrail #runner #rodeovalley #race #trailtuesdaythrowback #latergram #nofilter #2018_174

    Previously: tantek.com/2018/175/t1/finished-rodeovalley-my-first-30k

    on
  20. ↪ In reply to issue 419 of GitHub project “csswg-drafts” The new CSS Scrollbars 'scrollbar-width' property with a value of 0 (or 'none' if we go that route), has the requested effect for this issue.

    https://drafts.csswg.org/css-scrollbars-1/#scrollbar-width

    That is, hidden scrollbars, but content remaining scrollable.

    label: #css-scrollbars-1

    on
  21. New issue on GitHub project “csswg-drafts”

    scrollbar-gutter should move to CSS Scrollbars 2nd draft

    Once CSS Scrollbars has been resolved and published as a FPWD, the scrollbar-gutter property should be moved from CSS Overflow 4 to CSS Scrollbars.

    This was discussed briefly at the recent f2f in Sydney with general agreement among those discussing that scrollbar-* properties ought to be in the same spec, and @astearns pointed out to me the detail that it would be better to move it after FPWD, since 'scrollbar-gutter' has already been published in a FPWD, and I agree.

    Labels: css-overflow-4, css-scrollbars-1

    on
  22. 👍 to pull request 98 to GitHub project “webmention”

    on
  23. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. Beautiful Saturday for a #trailrun in the #Marin #hills at #SFRC! Steady 12 miles, ~2150', 2 beaches, and bones of a beached whale.

    #optoutside #getoustide #run #trails #beach #whalebone #whalebones #latergram #nofilter

    1 panoramic from Horizonal Control Mark Coyote Ridge 2
    2 look back down Miwok
    3 view of Pirates Cove from Coastal Trail
    4 Pirates Cove beach
    5 Pirates Cove looking North
    6 Stepping into the coarse sandy surf at Tennessee Beach
    7 Tennessee Beach looking North
    8 vertical panoramic of sun and mottled clouds over the beach
    9 large whale bone
    10 remaining whale bones and beach looking South

    First long run since my 30k. Quite a sluggish start, took me a few miles to warm-up and get into a good groove. Subsequent hills felt easier than when I ran them two weeks ago. Another bright sunny day with temperatures mostly in the 80s F, much better than the 90s during the 30k!

    Previously: http://tantek.com/2018/175/t1/finished-rodeovalley-my-first-30k

    on
  24. ↪ In reply to a comment on issue 1958 of GitHub project “csswg-drafts” 'scrollbar-width' added to the draft accordingly with a few details defined, and a few details in notes. Please review:

    https://drafts.csswg.org/css-scrollbars-1/#scrollbar-width

    Comment if you find aspects we can improve.

    Thumbs-up this comment if everything looks good enough for a public working draft.

    on
  25. ↪ In reply to issue 1988 of GitHub project “csswg-drafts” Section added: https://drafts.csswg.org/css-scrollbars-1/#security-privacy-considerations

    Closing issue.

    on
  26. ↪ In reply to issue 2879 of GitHub project “csswg-drafts” This seems reasonable to me. Now that we also have 'scrollbar-width', do we also want a 'scrollbar' shorthand to do both colors and the width?

    Can we rename this issue to something like:
    Shorthands for scrollbar colors, and colors + width?

    Let’s use this issue to discuss scrollbar shorthands in general.

    on
  27. ❤️ to a comment on issue 863 of GitHub project “csswg-drafts”

    on
  28. ↪ In reply to issue 1958 of GitHub project “csswg-drafts” There appears to be consensus at least in the current comments on this issue for adding a property to modify scrollbar size, with some additional preference for that to be treated as a maximum size, allowing implementations to show smaller scrollbars if it’s more appropriate.

    I have captured the use-cases mentioned here and to me in person on the wiki accordingly:

    https://www.w3.org/wiki/Css-scrollbars#Web_App_small_scrolling_areas

    Regarding the concern about terminology raised by https://github.com/silverwind about using "width" for horizontal scrollbars, vs the suggested alternative "thickness", note that CSS already has a notion of modifying the width of horizontal and vertical "bars" in the 'border-width' and 'outline-width' properties.

    In particular note the pre-existing 'border-top-width' and 'border-bottom-width' properties (https://drafts.csswg.org/css-backgrounds-3/#border-width) which specifically apply to horizontal borders. Thus I think it is both ok and desirable to use "width" to refer to the scrollbar size as well, since it is consistent with those existing properties, and matches what web developers will likely already be familiar with in CSS.

    I’m going to specify a 'scrollbar-width' property that takes length units that sets the maximum width of any scrollbars on an element when they are shown. 'auto' will be used as the initial value that means just use the platform default scrollbar size.

    on
  29. 👍 to issue 2472 of GitHub project “csswg-drafts”

    on
  30. 👍 to a comment on issue 1960 of GitHub project “csswg-drafts”

    on
  31. 👍 to a comment on issue 1960 of GitHub project “csswg-drafts”

    on
  32. 👍 to a comment on issue 1960 of GitHub project “csswg-drafts”

    on
  33. 👍 to issue 2851 of GitHub project “csswg-drafts”

    on
  34. ↪ In reply to issue 2846 of GitHub project “csswg-drafts” The examples given are definitely challenging to consider.

    I would be in favor of documenting some “simpler” interesting and desirable examples in spec itself with sample browser renderings.

    For example an inline flow element that is wrapped across multiple lines, both where the boxes are disjoint, and where the boxes are touching, or perhaps wrapped across 3+ lines, to illustrate an “outline that encloses all the element’s boxes” as a more ideal rendering than say separate boxes for each piece.

    Perhaps related, the spec mentions non-rectangular (effectively) three times in the outline section, “Outlines may be non-rectangular” (twice) and “The parts of the outline are not required to be rectangular”. While clarifying/documenting some preferred outline renderings, perhaps we can simplify the definition and remove the apparent duplicate descriptions.

    on
  35. 👍 to issue 2820 of GitHub project “csswg-drafts”

    on
  36. ↪ In reply to @csageland’s tweet @csageland sorry to miss you!
    Best #IndieWebSummit yet!
    Wide variety of sessions, hacks, demos. Check out session notes & videos: https://indieweb.org/2018/Schedule#Tuesday
    And join us in chat! https://indieweb.org/discuss

    on
  37. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. a jpg. A few from #Portland this week:
    1 #IndieWebSummit group photo, 📷 @aaronpk’s camera on timer
    2 #IndieWeb Leaders Summit the day before @MozPDX, 6 in room + 6 remote
    3 Bowl of the gods #acaibowl with peanut butter on top at Kure that morning
    4 Chipotle chili bowl with quinoa at Prasad the night before that
    5 Berlin IWS Remote Viewing hosted @EmbassyNetwork by 📷 @anikasai
    6 Participant proposed & led @IndieWebSummit sessions
    7 Running @Nov_ProjectPDX with @DesignNatalie (not pictured)
    8 Fresh #NP_PDX tag thanks to co-leaders Lara & Shelby
    9 Black Currant Cider limited-edition #donut @BlueStarDonuts

    #2018_176 #2018_177 #2018_178

    More photos soon. Got photos from @IndieWebSummit to share?
    Add them to https://indieweb.org/2018#Photos

    on
  38. Finished my @IndieWebSummit coding project!

    Completed plain text readable reply-contexts^1 (instead of just URLs) for all responses; in particular got these working:
    * in-stream^2 for new GitHub issues
    * on permalinks for all replies & reacji^3
     
    Sometimes it’s the small details.

    ^1:https://indieweb.org/reply-context#Minimal_text_reply_contexts
    ^2 https://indieweb.org/reply-context#Why_in-stream
    ^3 https://indieweb.org/reacji

    on
  39. Grateful for the 10th (likely final?) @OSBridge.

    @OSBridge culture & values continue to be an inspiration that can benefit every tech/OSS conference (including those I help with).

    If you have been to @OSBridge, pass on what you have learned*

    *http://www.yodaquotes.net/always-pass-on-what-you-have-learned/

    on
  40. This is your last @xoxo reminder!

    ~25min to do #xoxofest registration survey!

    https://my.xoxofest.com/attend

    You can do it in <10 min!

    1 line answers to (abbr’d)

    What do you do?
    What are you working on?
    What’ve you made that you’re proud of?

    on
  41. Sharing brief @IndieWebSummit notes as they come to mind.

    This was the first year people pre-wrote proposals before the #BarCamp organizing session. As facilitator I decided to have people who never proposed before go first.
     
    Coincidentally, @Christi3k just announced the same thing @OSBridge unconference organizing session.

    This may be worth codifing as a normal practice. Let first-timers propose sessions first before anyone who has done this before, especially at an @IndieWebCamp before.

    The other thing I did was, after the the first-timers finished explaining and scheduling their BarCamp session proposals, I had people *other than* the remaining session proposers choose from the remaining session proposals posted on the side of the grid, and advocate for them. I think that worked quite well for selecting for the sessions that were more compelling for more people. #2018_177

    on
  42. The 8th annual @IndieWebSummit wrapped up yesterday and simply put, I was blown away by the sessions everyone organized and especially by the incredible things everyone made & demonstrated.

    Notes & videos: https://indieweb.org/2018/Schedule#Tuesday

    Photos coming #indieweb #openweb

    on