#trailtuesdaythrowback to 13.2+ miles and ~2500' last #Saturday at #SFRC. Clear blue skies, a stark contrast from the previous week’s cold rain!
1 Gravel steps up Miwok 2 Hills and the Pacific from Miwok 3 Miwok looking back towards Tennessee Valley 4 Dias Ridge looking west to the Pacific 5 Muir Beach 6 Up Coastal Trail looking south to Pirates Cove 7 Looking down Fox Trail towards the #SF #skyline 8 Coastal Fire Road winding downhill
🌳 Easy 10km #run in #GoldenGatePark on re-opened #trails for #Sunday #runday #funday! #fromwhereIrun #trailrun #California #SF #SanFrancisco #optoutside #nofilter
1 freshly re-opened #GGP trails 2 #running around Stow lake 3 up Strawberry Hill 4 Huntington Falls 5 blooming #flowers by the boathouse 6 Phil Arnold #Trail / Oak Woodlands trailhead on the Bay Area Ridge Trail, just off the Eastern JFK entrance to Golden Gate Park.
↪ In reply to a comment on issue 27 of GitHub project “arewedistributedyet”https://github.com/lgrahl, by “which umbrella organisation”, which organizations do you think are setup / intended to handle incubation efforts that are not yet ready for standardization? Or do you think there is already something that has been incubated that is ready for standardization? If so, could you link to what in particular and where it was incubated?
You also referenced W3C’s paid membership model. Note that W3C Community Groups (which this is a proposal for) are open to all (anyone may participate) and without fee (no membership is required) per https://www.w3.org/community/about/
The existing W3C CG WICG https://www.w3.org/community/wicg/ has a fairly good track record for incubating proposals in their GitHub repos which then either graduate to a working group (some have gone to W3C, others to WHATWG), or incubation stalls/fails as a result of discovering an area or proposal is unworkable or lacks market interest etc.
Are there other incubation-friendly/centric organizations that you think would be a better home for a dweb/p2p incubation group than a W3C CG?
↪ In reply to @schofeld’s tweet@h2vx@schofeld thanks for your patience. https://h2vx.com/ updated (from dev.h2vx version) with support for #HTML5 elements: article aside figure footer header hgroup mark meter nav progress section time #h2vx to-do: time datetime attribute
The webmention.io /api endpoints accept a 'target' query parameter which currently must be an absolute URL. This proposal extends the 'target' query parameter to also accept a protocol relative URL (i.e. starting with "//") and return all mentions of that target with any protocol (e.g. both 'http:' and 'https:').
Use-case: this will allow sites which have migrated from http to https, or which still serve both http and https and accept webmentions for both, to easily query webmention.io for all mentions to either http/https versions of their permalinks, to show webmentions regardless of which protocol was used in their webmention target URLs.
Test-case: http://tantek.com/2019/065/e1/homebrew-website-club-sf is live with an iframe that embeds a display of RSVP webmentions via a service using a protocol relative URL in the target param to a webmention.io api call. Check both of these:
And you should see at least one RSVP displayed in the bottom from v2.jacky.wtf, likely with a green checkmark ✅. Here’s a direct link to just the RSVP display for that post but hardcoded to 'http:' mentions only: v2.jacky.wtf RSVP.
Super #green, #muddy, somewhat #rainy #SFRC this morning. Stress tested the Altra Superior size 11 trail shoes through #mud #up & #downhill, on turns, in deep #puddles. They gripped well, and in squishier sections slid smoothly & predictably. Good enough to set a handful of segment PRs/2nds.
1. Near the top of Miwok Cutoff toward Coyote Ridge 2. Curvy uphill Miwok North of Tennessee Valley 3. Steep & rocky Miwok North of Tennessee Valley 4. Gentle Miwok Cutoff flat curve cut into the hillside 5. Fogged in Coyote Creek descent — normally you can see the Pacific Ocean here (e.g. #7 in tantek.com/t4yz1) 6. Fogged in Fox trail descent
Browsers currently paint a window with a default background before/while loading web pages, CSS, and other resources. This happens both upon opening a new window with a URL (initial paint), and when navigating from one page to another (transitional paint), and is currently unspecified by the CSS rendering model.
This hole in the CSS rendering model results in proposals to use meta tags instead, such as viewport, and potentially for a dark mode.
Rather than awkwardly punting this area of rendering behavior(s) to an HTML meta tag or other non-CSS solution, CSS should define how browsers should (or at least may) render initial and transitional paints, preferably with a feature that permits author control, especially (at least) between pages of the same origin.
↪ In reply to @briankardell’s tweet@briankardell How easy as in how much time and/or emotional labor is (even perceived to be) necessary to cause a (comparably useful) change in either that you can then use in subsequent work?
↪ In reply to @briankardell’s tweet@briankardell contribute as in, How easy is it for a #webdev to contribute to the evolution of #CSS features & standards, compared to how easy is it to contribute similarly to #framework (#JS #template #toolkit #preprocessor …) features, #API etc.
Twitter is like the Matrix. Every few months/years someone trapped in Twitter reboots an idea to decentralize social media as The One (idea), gets attention & excited responses, not realizing they're just the latest cycle, soon to be forgotten by the next.