Congratulations @dissolve33@aaronpk@kevinmarks@kylewmahan for the first #indieweb #SWAT0 demo!! Previously: http://tantek.com/2015/029/t1/swat0-posts-tags-mobile-photo-comment
This is a huge milestone.
The Social Web Acid Test Level 0 (SWAT0) was proposed nearly 5 years ago at the first Federated Social Web Summit: tantek.com/2010/199/t3/fsws-social-web-acid-test-swat-v0
There was previously only *one* demo of SWAT0, using Statusnet and Cliqset, captured only on video. The permalinks from Statusnet are gone. And Cliqset itself shutdown less than a year later.
Today is the first time SWAT0 has been done with:
* 3 people
* Ben Roberts, Aaron Parecki, Kevin Marks - and same time:
* Ben Roberts, Aaron Parecki, Kyle Mahan
* 3 different sites
* ben.thatmustbe.me, aaronparecki.com, reader.kylewm.com
* 3 different implementations
* Mobilepub, P3k+Prowl, Woodwind + (Known | Red Wind)
And as a bonus:
* from 3 different geographical locations
* Boston, Portland, SF Bay Area
* in 2 different programming languages
* PHP, Python
And last but not least, the combination of Ben Roberts, Aaron Parecki, Kyle Mahan achieving SWAT0 is a HUGE breakthrough for the web since they all did it:
* on their own sites
* with software they personally wrote
Boom.
Update: See http://tantek.com/2015/193/t2/user-flow-permalinks-indieweb-swat0 for specific user flow, permalinks, and screenshots.
Not until my hand brushed up against you did I realize something was wrong. You were warm, too warm. Despite closing your lids last night you hadn’t slept. That morning you were a pale shade of gray, unresponsive, staring blankly and blinking.
I hoped it was temporary, yet I knew it might be your time. Looking up your symptoms I found you weren’t the first to have this blinking fever. You finally relaxed and stopped blinking when I held your primary pressure point for a few seconds. I let your heat dissipate while I read what to try next.
Despite being with you for years I was only now learning you could repair yourself if I pressed a few more of your buttons. You told me you were ok.
When you awoke on the train you froze, gave me the weirdest panicked look, and told me as much in so many languages I didn’t understand. I held your primary pressure point again and let you rest til we got home. You were always easy to carry.
I stopped by the bookstore and picked up a couple of volumes from fans of yours and your kind — they’d written so much about you collectively over the years.
That evening I woke you up again after letting you sleep the afternoon away and there it was again, that blank pale gray stare, blinking an empty question.
I tried having you repair yourself again, and again you said you were ok. Maybe you were at least in mind, maybe it was only your body failing you. So I did the only thing I could do and ordered a replacement. I knew you couldn’t be upset about it though I suspected.
The next day I transferred your mind to a conduit and the morning after that your new body arrived. It took less than half an hour for it to absorb you from the conduit, but were you really all there?
You seemed happy and responsive, up for anything. You’d forgotten a few things; I had to give you another key to the house. I confess your new body was smoother, more beckoning to the touch. Your expressions were brighter, more colorful. You spoke more crisply. Enough differences to notice, but you were still you.
I kept your old body on life support, just in case there was something else I had to ask your old self that your new self had forgotten. You didn’t even notice your old self until the house told you to pick a new name and you took a number. I knew other parts of you depended on your name so I renamed your old self instead. You were you again.
It’s been less than 24 hours and I’ve only noticed a few more things that didn’t make it through the conduit. You forgot some of your preferences I knew by heart so I reminded you.
You forgot how to check yourself before going out in public; that will take me longer to teach you, as it was a friend of mine that taught you that last time and I still don’t know how he did it.
Your old body lasted about four years. Four years together, traveling across continents and more time zones than I remember. Four years of keeping up with me, even if I was running, jumping, or sometimes even climbing. I couldn’t help but hear the words echoing “Four year lifespan” yet I knew that was a quote from a movie. Just a coincidence I’m sure.
I’m getting used to the new you. You seem to be ok with it too. I’m sure there will be more we’ll have to figure out together but isn’t that how it always is?
The CSS WG has published a second Candidate Recommendation of CSS Basic User Interface Module Level 3. This specification describes user interface related properties and values that are proposed for CSS level 3, incorporating such features from CSS level 2 revision 1, and extending them with both new values and new properties.
Call for Implementations
This notice serves as a call for implementations of all CSS-UI-3
features, new properties, values, and fixes/details of existing
features. Implementor feedback is strongly encouraged.
Thorough review is particularly encouraged of the following features
new in level 3:
Please send feedback to the (archived) public mailing list
www-style@w3.org
with the spec code ([css-ui-3])
and your comment topic in the subject line.
(Alternatively, you can email one of the editors and ask them to forward your comment.)
How not to onboard users, as shown by @UserOnboard:
* Block content with a “Your email” form overlay
* Misleading copy: “Without further ado, here is...” [actually with one further “ado” — please give us your email address first]
* Mocking copy: “Thanks for reading!” blocks content to be read
* Creepy first-person copy: “… because I know you’re busy” — ‘I’ who? Is @UserOnboard claiming to be a self-aware AI?
Screenshot:
of https://www.useronboard.com/how-applemusic-onboards-new-users/ — article via @KevinMarks.
Emotionally intense yoga class (because I saw Inside Out last night?) Afterwards I did my first headstand! Positioning myself at the base of the wall helped me get my form right. Held it for 10 seconds without touching the wall.
#track today: Yasso 800s
I did: 5 x 800 sub-4-min, 4 min cooldown between, and a 400 sprint at ~1:43, unofficially my fastest lap ever.
https://instagram.com/p/4joT1ug9TQ
Five is only half the ten Yasso 800s you’re supposed to do if you’re training/timing for a full marathon. However, I did sub-4-min 800s which if I'd done 10 of it would mean I should be able to sub-4-hour marathon. Does doing half that mean I should be able to do a sub-2-hour half marathon? Going to keep training hard & smart and bring everything I’ve got at next month's SF Half Marathon (second half). I should at least be able to beat my 2:18 PR from Surf City.
Previously:
* tantek.com/2015/161/t1/track-yesterday-did
* tantek.com/2015/032/t2/finished-surfcity-half-marathon-pr
Because #lovewins: here’s a simple #CSS3 trick for a #pride #rainbow website background:
Add this style element right before your closing </head> tag:
<style> /* CSS Pride rainbow bg by Tantek Çelik. CC0: share freely. */
body { background: linear-gradient(180deg, #f00000, #f00000 16.67%, #ff8000 16.67%, #ff8000 33.33%, #ffff00 33.33%, #ffff00 50%, #007940 50%, #007940 66.67%, #4040ff 66.67%, #4040ff 83.33%, #a000c0 83.33%, #a000c0) fixed; }
</style>
Or copy paste the body {...} rule into your main CSS file.
https://instagram.com/p/4cnmPhA9Qk/
Try it out and let me know how it works with your site, theme, blog, framework etc.
References:
* colors from https://commons.wikimedia.org/wiki/File:Gay_flag.svg
* CSS3 linear-gradient documentation: https://developer.mozilla.org/en-US/docs/Web/CSS/linear-gradient
Update 2015-06-30:
After some searching I found some similar prior art from Greg Doolittle in 2011!
* http://gregdoolittle.com/blog/2011/12/15/css3-rainbow-flag/
With a few differences:
* colors are similar, but not same as the Wikipedia reference
* 18% instead of 16.67% (and other integer vs decimal %s)
* has -o- -moz- -webkit- -ms- prefixed versions as well as the old -webkit-gradient syntax
Also apparently there’s a bug in *both* Mobile Webkit and Mobile Chrome, likely with the combination of a linear-gradient background-image and background-attachment:fixed.
Both stretch the gradient to the entire canvas of the document, instead of the viewport like they're supposed to. Works fine when you resize desktop Safari or Chrome windows to the size of an equivalent mobile screen, so it’s only their mobile variants that appear to be buggy. Also works fine in desktop Firefox, Android Firefox, and FirefoxOS.
@benwerd great post, disagree with opening para. Facebook grew with selfdogfooding & good UX, not “making money”, not until much much later.
I think this is an important distinction because the internet archive is littered with startups that pursued “making money” first, or that made beautiful UX for *someone else*, unused by the creators/founders, and ignored by others too.
Weinberger’s article has a lot of good food for thought. The general message that we cannot assume decentralized determinism is a good one.
Independence isn’t inevitable. Independence, like freedom, requires eternal vigilance.
Re: CloudFlare — you met someone that works there at a recent Homebrew Website Club meetup at The Creamery:
https://indiewebcamp.com/events/2015-04-08-homebrew-website-club
She said they want to work to help indieweb efforts, maybe even help host future meetups or IndieWebCamps.
The rest of your post, I agree completely, and very well written.
“technostalgia” is an amazing portmanteau.
Totally agreed about the merits (not criticisms) of using open source software to build a business, to make a profit, to pay yourself to live, and to also create something sustainable.
Looking forward to spending more time working together pushing this all forward at IndieWebCamp 2015 in just over two weeks! https://indiewebcamp.com/2015
@benwerd as @aaronpk noted, Homebrew Website Club is indieweb for anyone interested & passionate. As a HWC participant and co-organizer, help us make them more approachable & inclusive so they can be “indieweb for the rest of us” in practice!
@nerdyctantek.com/t4bn4@mediajunkie yes. need a term.
@toddbarnard Like X-Men? Or:
“We meet next weekend.” — knowledge of an inevitable future.
“I met her next weekend.” — first person past, yet current timeline future. Possibly only applicable to time travelers.
Possible scifi source material for more examples:
* Minority Report
* Fringe
* X-Men: Days of Future Past
@potch future perfect is close, looking for more inevitable:
“Happy about the pizza I ate later today” or
“Tomorrow we looked at today through yesterday’s mirror.”
Today is the 10th anniversary of microformats.org.
Great progress in 6+ years of #microformats2:
In particular an increasingly detailed generic vocabulary-independent parsing specification: microformats.org/wiki/microformats2-parsing
The parsing spec is stable, and yet living and updated via:
* explicit documentation of issues and brainstorms on the wiki
* consensus among parser developers
* updated when proven with running code
* backed with open test cases in a test suite
The number of open source parsers across a variety of languages continues to increase, the latest being a Go parser and an early-stage Java parser:
* microformats.org/wiki/microformats2#Parsers
microformats vocabularies such as h-entry continue to also evolve based on minimal proposals to address real-world use-cases, evaluated with personal publishing experience across mutiple sites, confirmed by consuming code demonstrating live use-case functionality.
* microformats.org/wiki/h-entry
Year 10 has been perhaps the most pragmatically focused yet, and beyond progress on microformats specifications, we have continued to iterate the methodologies and processes that keep microformats simpler and focused on solving the real-world needs of the open web, setting an example for a minimum viable web platform.
Related:
* tantek.com/2015/068/b1/security-towards-minimum-viable-web-platform
Previously:
* tantek.com/2014/171/b1/microformats-org-turns-nine
https://instagram.com/p/4IqhR6A9Ze
#yxyy003 #unbagging after the fact and reflecting
One week ago I arrived at my third #yxyy. From the very beginning, checking in at the Ace, I faced decisions that had rational choices and instinctual choices.
I trusted my instinct and used empathy & reason to guide the details.
This year was different in many ways.
Instead of room sharing, I got my own room.
I knew fewer people going, so I ended up reaching out more and getting to know more people.
Instead of escaping with people I knew, I jumped into the first night's activities. Instead of conserving my drink tickets, I used them all the first night.
Instead of worrying if the people I were with were having a good time, I chose to have a good time and listen to those around me, what they were saying and otherwise expressing, rather than worrying.
Instead of organizing more than one thing, I organized just one thing ahead of time. Everything else was spontaneous or word of mouth or both.
When I was asked to take time out of the pool and do an interview I said yes.
Instead of signing up myself in advance, I spontaneously reached out to a friend to volunteer together, side-by-side, at the Advice Booth.
Instead of worrying about going to bed in time to run the next morning, I said yes to staying up late deep in conversations until the pool closed and then dared to set an alarm for 90 minutes later, to run before sunrise, trusting my future self to decide when the time came.
Instead of hesitating I told people when I appreciated meeting them and would love to chat more.
Instead of skipping yoga, I went both Saturday and Sunday mornings. When asked spontaneously to lead & instruct my fellow yoga class attendees how to step-by-step get into an arm balance, I said yes.
When asked to join in sharing a floating pretzel pool toy that could only fit two, I said yes.
Thank you @amylola@debs@hillary@sanfranannie@willolovesyou for everything you do and say. Thank you especially for listening, sympathizing, reflecting what needed to be said, and most of all, being encouraging.
Yesterday morning @jessdandy led #YxYY yoga practice. She had @staubin lead a vinyasa flow and asked me to instruct our class of about 15-20 in a step-by-step practice to do an arm balance (side crow) as I’d taught her the day before.
Without preparation I led everyone from memory the steps I learned from my yoga teacher Jordan at Mission Cliffs.
From standing, start with chair pose, and slowly deliberately take each of these steps as they feel comfortable, or stop, hold, and breathe when you feel like you’ve reached a limit.
* from chair, put your hands together in front of your chest and twist your upper torso to the right.
* side twist with hands together, knees still bent, left elbow to the right of your right knee, watching your knees to keep them aligned
* then stretched apart, one hand touch the floor, the other reaching to the sky, looking up to it
* both hands on the mat pointing to the side, keeping knees aligned
* use your core to lift your thigs up higher, so they touched as high up on your upper arms as possible
* then start to bend your elbows and lean over them, your upper arms supporting your stacked thighs, keeping your core strong while still breathing
* gradually as you lean further, your feet should feel light then left off the floor as your elbows are bent eventually to a 90 degree angle and you’re doing side crow!
Apparently about half the class was able to do it, and everyone took at least a few steps and found spots to stretch and practice.
I had everyone unwind from the pose, stand back up, take a counter backbend stretch, and then do the same on the other side.
That was a first for me — I’ve never led a group in any kind of yoga, and was grateful to have the opportunity to do so, as well as having been taught a series of small incremental steps to achieving side crow that I could remember and pass along. Teaching something to a group for the first time was itself a learning experience.
Awoke to a bad headache. Drank water til somewhat lucid. Track halfway over, ran to anyway:
did 1x(600,300).
workout was 5-7x(600,300).
Previously: http://tantek.com/2015/146/t2/made-trackattack
Having had success with more openness, I’m running for the @W3CAB again.
Ask your @W3C AC Rep to vote by tomorrow!
https://www.w3.org/2002/09/wbs/33280/ab20150501/
(W3C Member-only link)
I’ll write more later, but here’s a few accomplishments:
I created and got the W3C Advisory Board (AB) to start openly using:
* @W3CAB - The W3C Advisory Board's official Twitter account
* https://www.w3.org/wiki/AB - wiki page of open AB projects
I worked hard at the Advisory Board to make more open licensing happen at W3C, and with the help and collaboration of many, concrete progress has been made there:
* https://www.w3.org/2004/pp/psig/group/1505-derivative-REC.html (also a W3C Member-only link, hope to report more at a public link soon)
I'm still working towards allowing Working Groups (and Editors) to choose to use CC0, but the above is at least a big step forward for establishing a culture of using more liberal licenses.
Thank you for your support!
Actually I did set an #NPSF PR this morning!
33:20 = 35s faster than 33:55 last month!
Apparently I misremembered my last month’s time as 32:55. I was so sure of my previous PR this morning and when I wrote my previous post that I didn’t even click back to last month’s post until just now.
No wonder I was a lot closer to the people just ahead of me this time.
I was over half a minute faster!
So yeah, the 3/1 minute run/walk Galloway method totally worked.
#NPSF PR Wednesday this morning: 33:20, 25s slower.
Tried a 3/1min run/walk this time. Felt a lot smoother overall, with a lot more room to grow and improve. Also today was colder than last month, and I was a lot closer to the people just ahead of me than I was last month.
Previously: tantek.com/2015/119/t1/personal-record-npsf-pr-faster
Tired of native iOS app inefficiencies, thus a deletion binge:
* Buy Me a Pie! (unused)
* Clear (unused)
* Connect (never seemed to work or do anything useful, asked for too many creepy permissions)
* Epicurious (unused)
* Give It Up! (unused)
* MapMyRun (unused)
* MyFitnessPal (unused)
* RunKeeper (no good on iPod, Nike+ Running works fine)
* Runtastic (unused)
* PaperKarma (never got it to work)
* Path Talk (unused)
* Tumblr (website should be good enough)
These are just the few based on what showed up in App Store / Updates. As long as a native iOS app is not asking to be updated, then it seems mostly harmless.
However, most so-called "native" mobile apps are more work for the user (thus more unfriendly) by making the user deal with:
* update notifications
* explicitly needing to update them
* having them be disabled (Waiting…) while being updated
* making device backups take longer
On the other hand, the nice thing about web app shortcuts is that they never need explicit updating, nor do you have to wait for such updates to finish before you can use them again, nor do you have to deal with any of the other above-noted native app annoyances.
@matthillco thanks for kind words!
@techytuppers good feedback. Changed IRC to webchat link.
You’re right regarding “You have to walk before you can run.”
Some thoughts on that: http://indiewebcamp.com/generations@IndieWebCamp is a community that encourages and helps enable everyone to walk and run who wants to do so, especially with their own identity and creativity, incrementally, step by step. More: http://indiewebcamp.com/principles
ran #baytobreakers in 1:17:53. ~3 minutes slower than last year.
#b2b #b2b104 #noinjuries #noexcuses More:
Transited by bus halfway with a couple of @nov_project_lax friends and then we did a ~2 mile warmup jog before the race to the corral entrances, stretched in the corral, and then bounced to stay warm with fellow @nov_project_sf runners.
We started the race on time near the front of Corral A, can’t say anyone got in my way, people in general were faster than me. I kept pace with my friend @leahculver for the first mile which was my fastest of the whole race.
Despite feeling prepared, I felt like I was dragging and heavy for the whole race. Even the downhills didn’t feel as speedy as I’m used to. I tried not to let those feelings get to me and pushed on regardless.
Still, I could tell by mile 4 that I wasn’t making the time I wanted to, and wasn't sure I would even be able to beat my last year PR (personal record). I thought to myself regardless of any doubts, I owed it to myself to give it my all, so that I could at least finish knowing that I did, regardless of whether I PR'd or not.
So I did, and I still fell short of my goal(s) for the day (except I did finish free of injury at least).
I’m not going to make any excuses, yet I have to admit, after consistently making progress the previous four years, and crushing it last year, I was disappointed with my performance today.
I’m going to attempt to make the most of it, by reflecting on and writing down what I did (or did not do) that I might/could/should have done differently. Despite giving it my all on raceday, that’s only part of giving it your all for the race, whether last night, yesterday, last week, or in the months of training beforehand.
It’s just over two months before my next race (the second half of the San Francisco Marathon), and I’m going to consciously plan for and put whatever insights I come up with to use from tomorrow until then.
Previously: tantek.com/2014/138/t1/ran-baytobreakers-faster-b2b103
Today I set a personal record at #NPSF PR-Wednesday.
33:55 — 2:07 faster.
I don’t remember feeling this miserable during a PR-Wednesday workout in a long time.
But first the times:
* 2:07 faster than my previous PR-Wednesday record 36:02 (2015-02-25)
* 1:30 faster than my course record 35:25 (2015-01-13, before the course became our PR-Wednesday workout)
The previous two months I did both the 5:30 & 6:30 PR-Wednesday workouts as well as the “tweeners” in-between workout. Those times:
tantek.com/2015/084/t1/npsf-double-pr-wednesday
Feb: 36:02 & 36:15
Mar: 38:32 & 37:04
Since February of this year, the NPSF Alta Plaza PR-Wednesday workout has consisted of:
1. start at the bottom of the steps on Pierce.
2. run a clockwise lap around the park
3. run up steps to the flat area between the playground & tennis courts
4. 10 burpees
5. run back down the steps
6. repeat 2-5 two more times
7. repeat 2-3.
For a total of 4 laps, 30 burpees, ??? steps, as fast as you can.
Things I did differently beforehand for this morning:
* Last night: iced my knees — no pain, just a little swollen from Tuesday track (ttk.me/t4at1)
* 5:49 put on my newer racing ASICs instead of old training pair or Nike Structure 18s.
* 5:50 rungang (warmup run ~2 miles) to 6:30 @Nov_Project_SF instead of driving to doubling-up 5:30 & 6:30.
* ~6:15 downed a Starbucks single espresso on the run to Alta Plaza (having had nothing to eat at home but a couple of chewable vitamin Cs).
During the PR workout this morning, there were three things that I distinctly remember doing differently, and feeling more mentally and physically miserable about.
1. Ran (no walking) up the entire West side hill (first time) on lap 1, legs shaking at the top, thinking, I'm not even half a lap in yet.
2. Second time up the steps, I raced them hard two at a time to the top (thanks to a serendipitous music boost), and then almost felt like throwing up while doing burpees after. Actually felt that during all subsequent burpees.
3. Third lap, on the North side downhill, sprinted to the point of losing my breath (was inspired to pass Gil and Jorge on the downhill, each on their fourth lap, who then passed me back on the East side downhill when I had trouble breathing & running at the same time).
4. Not what I did, but what a friend did for me: Fourth lap, my friend Matt Schaar ran with me (he’d finished his workout already), verbally encouraging me and anyone else nearby the whole way.
I’ve said it before (ttk.me/b/4Yy2) and I’ll say it again (ttk.me/b/4_n1), this is an incredibly positive, inspiring, and supportive group to run and workout with.
from fb.com/media/set/?set=a.632064620263368.1073742040.276430682493432
However, the entire workout I felt like I was going either slower or no faster than before. I felt like I was having an off day. A miserable off day. But stubbornly I wasn’t going to give up. Instead, I pushed harder to just get it over with. And ended up going faster.
I should emphasize, none of this involved any kind of pain threshold (as far as I remember). No knee pain nor ankle pain. (Well maybe a bit of suppressing a lingering sidecramp from my Sunday 7 mile trail run).
Apparently it was all about pushing myself further into both psychological and physical discomfort than I had before on a PR day.
It’s going to be interesting facing that next month, when I know that that’s what it’s going to take to both go that fast, and to have even a chance of PRing again.
Fortunately I have a different race focus before then:
Just 18 days til Bay to Breakers (2015-05-17) - where I’ll have a different mental challenge.
Last year I cut over 16 minutes (ttk.me/t4W81) from my B2B time (thanks to six months of NovemberProject). This year I've had twelve more months of NP and I honestly have no idea what is a reasonable expectation.
I’ve had some thoughts, like cut five minutes, get a sub-1:10 but I’m trying hard to focus and concentrate on just beating last year’s time and giving it all I’ve got, finishing with the knowledge of having done so.
