When:
Where: Presidio Lawn, North Side, near the Disney Museum
I’m teaching a Vinyasa flow at 14:00 today on the Presidio lawn near the Disney Museum. Bring your own mat, and wear comfortable layers for wind & warmth. All levels welcome!
The Presidio Picnic itself is from 11:00-16:00 with a variety of tasty food truck options.
#NPSF PR Wednesday 32:53 (1:18 slower than May) after a rough #earlygang half-PR-routine.
Stayed up late working / making travel arrangements last night. Got less than 5 hours of sleep (again, not recommended). Barely made it to the early workout ~10min late, and had to run to a pit-stop mid-first-lap. After two laps and 20 burpees, called it quits since everyone else from earlygang was done and doing abs already. Joined in.
On the plus side, got to practice running tired and groggy. For 2-3ish workouts. 25 days left til @TheSFMarathon. And nice briefly catching-up with a missed friend. Ran at my breathing limits, no joint or muscle pain or soreness.
After only ~5 hours of sleep (note: I recommend getting more), getting up the morning after flying across three time zones, making a last minute decision to Lyft line rather than run 2.6 miles before the workout, I managed to "run" (more like hike) 37 sections of steps at Harvard Stadium, beating my previous record of 32 by 5 sections.
I barely had the self-awareness this morning to realize that I was moving just too slowly to run to the 05:30 Harvard Stadium workout and be on time. I called a Lyft line, and shortly after picking me up, another rider was added. Not surprisingly, she turned out to be a fellow NovemberProject member.
We arrived in plenty of time (~05:25) and even among the large crowd, I managed to find my friend Kat who used to be @Nov_Project_SF and moved to Boston a while ago.
After the bounce we found out we would be running the "Frogman1" workout — 50 sections (or as many as you can) in 45 minutes (or less), starting from the bottom of section 37, up and down every section down through section 13 (thus 25 total), then up section 13 again, and down and up every section back up through section 37 (another 25) for a total of 50 sections.
I had no illusions of completing 50 sections. I started with the third wave of people at the bottom of section 37. I focused on conscious breathing, and pushing myself as much I could while keeping an explicit breathing rhythm (thank you yoga training), and also glanced occasionally at my watch for time elapsed and heartrate (keeping it under 150).
Made it to section 13, redid it, and kept steadily going until I was back to section 22 and heard co-leader Chris shout "3 minutes!" at which point I decided to give it a final stronger (not as sustainable) push to make it to section 24. Made it up 22, up 23, up to the top of 24, and not hearing a time warning, ran down the steps to the bottom of 25. A few steps from the bottom I heard the 10 second countdown.
37 sections would do for today.
A full tour's section count if not an actual full tour of the stadium, which will have to wait til next time.
Grateful for every high-five, every encouragement, every shout, every hug. Made my morning and definitely helped me finish 37 sections for the first time.
Afterwards: went to breakfast at swissbakers with Kat and friends instead of doing doublegang at 06:30, got a ride back to Backbay from Kat, and ran the ~1.3miles back to my hotel to shower, change, and Lyft to make it in reasonable time to the @W3CAB meeting @MIT.
This is me. Two weeks ago, after #NPSF #earlygang, before the 6:30 workout. I had a lot on my mind.
Sometimes I take things too seriously. It was two days before I was to co-teach my first public Vinyasa yoga class as part of my last weekend of YTT, graduating that Sunday after co-teaching a second class. Yoga sequences and philosophical challenges occupied my thoughts nearly every waking minute. Still do.
I am imperfect. Grateful for the humility reminder, and optimism that I can do better in the future.
I am old(er). Old enough to be grateful for every day. Old enough to feel holes in my heart every day from the losses of too many younger friends. Old enough to fill those holes with memories of our shared times, and intentions to live and pass on their joy, happiness, energy, care, and positivity towards others.
I am strong(er). Strong enough to know the barriers inside are often bigger than the barriers outside.
I am grateful. For too much to list. Enough to remind myself in moments of craving or emptiness.
I am hopeful, for the potential of every moment, for the positive changes we can make inside, and by our actions, outside, while being present in every moment, appreciating what is.
49d to #TSFM2017. #NationalTrailsDay yesterday: 10.4mi & 2129' of mist cooled trails at SFRC, day after #NPSF hills. Rest day today.
Saw deer, rabbits, and a partridge. Ran the last mile on pavement to make it back in time for the Good Earth breakfast bar. Everything felt fine, if just a bit slower, the day after tantek.com/2017/153/t1/sunrise-fog-summits-npsf.
Happy National Trails Day!
Photos: 1. Old Springs trail start and deer! 2. Old Springs trail view to a fog covered Pacific 3. Wolf Ridge Trail into the mist 4. Coastal Trail single track descent: “Steep grade / Stay on trail” 5. Coastal Fire Road ascent, @micheleperras in sight! 6. Tennessee Valley view to Tennessee Valley Beach 7. Peak: Coyote Ridge 2 Reference Mark (Previously: tantek.com/t4jj3) 8. Fork left to Marin Drive, into a twisty maze of roads 9. @Strava run path satellite hybrid view 10. Golden Gate Bridge southbound back to foggy SF
🌇 #sunrise vs #fog on 4 summits before 6:40, then #NPSF #hillsforbreakfast. 1552' in 4.7mi. 51d til #TSFM2017, my longest race so far @THESFMARATHON.
Photos from / by / of: 1. Twin Peaks Summit 2. Twin Peaks Summit (North/Eureka Peak) 3. Twin Peaks Summit (South/Noe Peak) 4. Mount Davidson (view from vista point) 5. 📷 by https://instagram.com/lauramcgreen 6. My attempt to honor @ryanscura of dooster.tv with a dramatic backlit shot of him running counter-balanced by rainbow tinted sunbeams 7. Similar shot of friends @jerseyblauvs & instagram.com/therealboops 8. @Strava run elevation graph for the morning 9. Mount Davidson view after running @Nov_Project_SF Hills
Running uphill is still the hardest for me to run, though with sustained effort and practice I am slowly getting better at it. I climbed over 2000' just two days ago, the combined total from double-PR Wednesday¹@Nov_Project_SF and evening run/hikes to finish out the Strava Mt. Everest Running Climbing Challenge for the month of May². Thanks to a restday yesterday and enough sleep last night, my legs felt fine (not sore) on the hills this morning.
I know that “proper” training for a marathon requires increasing distance, both in long runs, and total weekly miles. Since uphill is my weakpoint, I’m focusing my training on that, and especially on trails since they are more forgiving (thus more body sustainable) than running on the road. Rather than total miles, I’m focusing on time spent at high-effort running. That feels more right for my body, and if my PR Wednesday improvement over the past two months is any indication, the right thing for me to do too.
Now that I have Saturdays again, I will be running SFRC every Saturday morning that I’m in SF, doing my long runs on trails as well. I’ll eventually do at least one longish run (maybe 16-18 miles?) on road just to get used to doing so in the shoes I plan to wear for the race. Also planning to do at least a few track workouts to mix-in some speedwork.
For now I’m happy with the progress I’ve made, both in the past few months and the past few years running with @Nov_Project_SF., and for the increased body awareness from yoga teacher training³ that has really helped me consciously keep track of how my body feels while running, and adjust breathing, posture, pace, stride, etc. accordingly.
As always, grateful to running/fitness/yoga friends, teachers, and communities (@Nov_Project@missioncliffs@YogaFlowSF) whose support has been essential to reinforcing regular sustainable physical practices.
#NPSF PR Wednesday 31:35! 4:32 faster than March. May #doublegang done.
Considering how much less running I’ve done over the past three months (spending far more hours per week doing (and practice teaching) heated Vinyasa yoga) I was pretty surprised by over 4.5 minutes of improvement in two months! That 31:35 #earlygang time is also my fastest PR Wednesday in 2017 by 3:01, as well as my 3rd all time fastest.
When I re-ran the PR Wednesday course at the 06:30 workout, I was only 10s slower: 31:45, now my 4th overall fastest PR Wednesday time.
This was the fifth Wednesday in a row that I have done both the 05:30 (sometimes a few min late) @Nov_Project_SF Wednesday workout, and the 06:25 workout, thus completing an entire month of double-ganging it.
My plan is to keep up with double-gang as part of my endurance training for the San Francisco Marathon in July.
co-taught first public yoga class last night @YogaFlowSF. So grateful for @Nov_Project_SF friends, #YTT colleagues & teachers, all my yoga teachers over the past 19 years, Paola for getting me to start doing yoga post-injury recovery, and my mom for perhaps planting the idea decades ago doing ~5am yoga from broadcast TV while I patiently waited for Speed Racer to come on ~6am.
< 32 hours to Yoga Teacher Training graduation. * wrapping up homework * class all day today * final exam and co-teaching another public class tomorrow.
Beautiful day, beautiful people. Ran #baytobreakers in 1:15:03, 5.5min faster than 2016! 6s slower than my 2014 PR of 1:14:57.
I hit my main two goals: * Finish without injury * Run strong, finish strong
These I had considered beforehand, but I had let go of, until about halfway through the race when they seemed not only possible, but reasonable: * Sub-10 min/mile average pace (9:49, 20s/mi faster than the Hot Chocolate "15K" actually 9.8km) * Make it to the NovemberProject group photo (see above)
I also set a 5km PR of 28:30 during the last 5km of Bay to Breakers’s 12km. Nearly 3 minutes faster than 31:15 at the Stow Lake Stampede 5km race four weeks ago!
My current #indieweb itches need more design thinking before building and deploying. By iterating, minimizing, simplifying, eventually something clicks and it’s easier to switch into coding thinking, then build, test, ship, use, demo.
Capturing and sharing my design thinking in progress on various site features here: * https://indieweb.org/Falcon#Working_On in the hopes that others implementing similar features for their sites may benefit or can contribute suggestions as well.
@sil pinged ~22h after support request, before @t unlocked. By the time he checked, support had unlocked it.
Finding it unlocked the next morning my time, I presumed it was due to that and only saw the message this morning that he had not had to escalate it after all.
Today: account @t unlocked after asking Twitter friend 24hr after support request. He escalated, vouched.
2017-05-12 CORRECTION: Timing was coincidence, normal support had unlocked @t by the time my friend went to escalate it internally. Timeline:
+00h 2017-05-09 13:15 email notification: “Your Twitter account has been locked” +07h 2017-05-09 20:17 filed support request, email confirmation: “Case# ___: Appealing a locked account - @t” +29h 2017-05-10 18:25 pinged a friend at Twitter (but he didn’t get around to escalating until after the following) +37h 2017-05-11 02:49 follow-up email: “Case# ___: Appealing a locked account - @t”
" Hello,
We have restored your account, and we apologize for any inconvenience this may have caused.
Twitter takes reports of violations of the Twitter Rules very seriously. After reviewing your account, it looks like we made an error.
Thanks,
Twitter Support "
This is a well written support email, however reveals something disturbing. Having been attacked in the past with numerous reset attempts, phishing attempts, nevermind outright email demands to hand over my single letter Twitter account, I suspected that trolls may have taken the next step and group-reported (perhaps with bots?) my account as an attack.
I’m guessing that Twitter has an automated system that locks an account after some number of different accounts have reported it for abuse. Eventually a human reviews the account in question and makes a determination but who knows how long that might take. (2017-05-12 UPDATE: Apparently in this case ~30 hours after a support request)
This leaves open the possibility for a targeted denial of service attack of sorts, on any account you use on any service. I would expect that accounts on "free" services are particularly vulnerable, as without a paying relationship, the services are driven more by incentives to please advertisers (thus the "mass appeal" of free content in aggregate), rather than the users.
In theory, this should mean that such "mass report abuse" denial of service attempts should be less effective on accounts you pay for, like your own domain name, your web host, and your internet service provider, who have more incentive to keep you as a paying customer.
In addition if your account on a paid service is locked or otherwise has a problem, I would also expect a quicker response from support.
In actual examples of problems with my accounts, I have had support requests to my web host and internet service provider handled within hours if not minutes.
Another trade-off to consider when deciding what to use for your primary online identity and content: an account on a free service potentially more vulnerable to such attacks and longer support delays, or an account on a paid service, likely less vulnerable, with faster support response times.
Note: I have not done anything with my @t twitter account since posting two days ago besides just reading tweet permalinks and occassionally checking the home tweet stream.