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)
According to @Strava:
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!
Feels good to be back.
Previous Bay to Breakers:
* 2016 1:20:46 tantek.com/2016/181/t1
* 2015 1:17:53 tantek.com/2015/137/t1
* 2014 1:14:57 tantek.com/2014/138/t1
* 2013 1:31:39 tantek.com/2013/139/t2
* 2012 1:36:33 tantek.com/2012/141/t1
* 2011 1:39:47 tantek.com/2011/135/t5
Previous 5km at Stow Lake Stampede:
* 2017-04-23 31:15 tantek.com/2017/114/t1
Previous 9.8km at the Hot Chocolate "15k":
* 2017-01-08 tantek.com/2017/008/t3
Aside: Unexpected competitive results:
* top 20% overall
* top 25% in division
One weekend of #YTT remaining. Have learned so much, yet so much more to learn.
Tomorrow: my 7th #baytobreakers
hosting Homebrew Website Club 17:30 @MozSF 2017-05-17!
FB event: https://www.facebook.com/events/1785514098429850/
went to A Jivamukti Master Class with Ruth Lauer Manenti today @YogaFlowSF on Ocean ave. #YTT make-up work done!
Inspired by #IndieWebCamp Düsseldorf demos, a bit on pinned posts: https://indieweb.org/pinned#Brainstorming
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:
in the hopes that others implementing similar features for their sites may benefit or can contribute suggestions as well.
Just two weekends of YTT left. And some homework.
@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.
Added timeline to my unlocked post: tantek.com/2017/131/t1/twitter-account-unlocked
@sil hence I waited ~24hrs before pinging. Hoped "normal support path" would work like before: tantek.com/2016/301/t4/your-account-now-unlocked-twitter
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”
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.
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.
My twitter account @t has been locked, no specific reason.
Support request filed. Previously previously: http://tantek.com/2016/301/t3/why-twitter-growth-stalled-broken-locked http://tantek.com/2016/301/t4/your-account-now-unlocked-twitter
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.
Longtime friend & fellow #indieweb leader @veganstraightedge is fighting cancer. Please consider helping:
Sometimes being so focused results in missing really important things.
Long form: https://veganstraightedge.com/articles/2017/04/17/i-have-cancer
@Johannes_Ernst (cc #iiw),
come to 17:30 #IndieWeb Homebrew Website Club @MozSF, dinner after! https://indieweb.org/events/2017-05-03-homebrew-website-club
Google phish update:
Tweetstorm tips: https://indieweb.org/tweetstorm