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'
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.
10:00 Opening keynotes and lightning intros/demos
11:00 BarCamp breakout session scheduling
11:30 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)
#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
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.
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!
↪ 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:
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.
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.
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
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
It looks like you can intercept document.oncopy and change the selection (using selection.selectAllChildren) to then cause the copy command itself to copy whatever text you want, rather than having to use execCommand("copy").
Instead of "Link to Text", I want "Copy link to text" that copies the fragmention to the clipboard rather than navigates to it. Copying the link is a better default desired action than navigation. Why would you want to navigate to the thing you just selected? It's more likely you want to copy a link to what you just selected so you can post a highlight of, or comment on the selected text.
Finished #RodeoValley 30k in 05:10:17 yesterday! 📷 @kellyfuson #2018_174 My first 30k and the hardest #race I’ve run. First 2 hours felt great, powered up the Miwok ridge, then the heat slowed everything down to a struggle. Race write-up continues after photo summaries: 2 🌄 Marin Headlands sunrise 3 Dressed to race! 4 Ready 30k 50k start 5 SCA photo stop 6 Hill 88 view to Rodeo Beach 7 Race temperature over time
Always better participating in a race with friends. Kelly and I carpooled, and picked up our Inside Trail race bibs (different races), got ready, and had someone take our photo with Rodeo Beach in the background (photo 3).
The air was cool at the 30k & 50k start (photo 4), and the crowd started at a nice easy pace (in contrast to everyone bursting out of the gate at Double Dipsea).
The 30k course started with a gradual uphill. Everyone pacing themselves provided a good sense of momentum, enough to run up the first set of hills, all the way up to the SCA trail where I saw a few taking photos so I did too (photo 5).
Smooth run up and down SCA and Alta trails to Marincello, took off downhill without missing a beat, and somehow passed a lot of people who had passed me on the uphills.
Made it down to the Tennessee Valley parking lot in (personal) record time. Refilled my water bottle at the aid station and headed up Miwok, where the temperature got noticeably warmer the higher I went. It was a tough slog by myself. When another runner passed me who was also struggling, I found the energy to barely keep up, several paces behind.
We reached the turn onto Coyote Ridge and it had definitely heated up.
Weather forecasts had predicted mid 70s in Mill Valley, and 80 at Rodeo Valley. Clear, not a cloud in the sky.
I didn’t realize until after I synced the temperature data from my watch (photo 7) that since that 2 hour mark, temperatures on the course went from 80 up to 95°F (except for a brief drop to 75°F after hour 4 in Tennessee Valley).
When I felt the heat hiking up Coyote Ridge, I figured it was the predicted mid 70s, accentuated by the direct sunglight. With a full water bottle I pressed on, hitting the halfway mark at about 2h15m in, with over 2200' (much more than half) of vertical climb completed. I had started feeling the effects of the heat, my stomach would no longer accept any food, and I had to slowly sip from my bottle up the hill.
Ran most of the way downhill to Coastal, it was hot enough to slow down and walk a few times. Made my way down to Pirates Cove, without much difficulty. Then the real challenge started.
The climb up out of Pirates Cove was brutal and long. It was feeling hotter still, and I figured it had crept up to ~80°F (when it was actually closer to 95). I knew I had enough water to make it back to the aid station. I focused on my breathing, and watched my heartrate, pushing uphill only hard enough to keep it between 140-150bpm.
The hill seemed to go on forever. I kept pushing until a couple of times I literally had to stop, take a few deep breaths, and then keep pressing on. By the time I got to the top, I was exhausted, too tired go downhill as fast I normally would. It was still a morale boost to see the valley below. I knew I could make it back to the Tennessee Valley parking lot aid station.
Taking it slow back to the aid station, I was able to snack when I got there. Refilled my water bottle, and took off back down Tennessee Valley trail for the remaining 4 miles.
The final steep Coastal Trail south ascent was brutal. Just kept pushing uphill like I did out of Pirates Cove, hands on my knees when necessary. Every so often the plants alongside the trail were tall enough to cast a shadow, and I paused to restabilize my legs, focus on breathing regularly. Again it felt like 80 degrees when it was more like 95.
For over a year now I’ve been doing warm Vinyasa yoga (90-95 degrees) about twice a week. As I practiced more I was better able to reach a conscious flow, better able to think clearly despite the 95 degree temperatures. Only after my run (and seeing the temperature chart) did it click — all that warm Vinyasa had trained me to push sustainably even in that much heat, and still focus & think with a strong enough will to keep going.
Reached the Hill 88 crest (photo 6) where I could see Rodeo Beach (the finish) in the distance! As I started an easy run down the hill, I heard someone call out my name. I was so focused on finishing that I didn’t recognize his voice or face until he was much closer. Clayton and Kissie were running up the hill on their on Saturday trail run! They wished me luck and I kept trudging down the hill.
Eventually I picked up speed and passed one person who had passed me on the Coastal uphill. Knowing I’d finish in minutes, I focused on a swift but steady pace, on sure footing more than speed.
Finished (photo 1), saw Kelly cheering me in (she’d finished her half marathon about two hours before).
30k (18.6mi) done! (my Suunto watch only recorded 29.97km, clearly I should have ran it out another 30 meters after crossing the finish 😂) The farthest I have ever ran on trails.
3,780 feet elevation gain (secondmost during a run, only to Double Dipsea last Saturday) according to my Suunto watch / Strava.
And a 1 mile PR of 7:20, during my sprint down Marincello, finally beating my nearly three year old timed track mile PR of 7:23 (tantek.com/2015/188/t1) under totally different conditions (downhill vs flat, trail vs track, after ~7mi vs 1mi warm-up).
Thirsty & hungry, I refilled my water bottle, drank deeply, ate snacks, and picked up my finisher’s medal and t-shirt. We retrieved our bags from bag-check and headed to the beach.
Stripped down to my running shorts, walked into the surf, and dove in, fully submerged.
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.
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.
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!
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.