I woke up to the colors of impressionist sunrise lit clouds. #NPSF #earlygang #run #wakeupthesun #hillsforbreakfast #getitdone #fromwhereirun #heysweatdaily #sunrise #sf #skyline #nofilter
#NPSF #PRWednesday this morning: 31:00! 2:40 faster than last month. 1:17 faster than 11 months ago. fastest in 2016, 2nd fastest overall, just 52 seconds slower than my all time PR nine months ago.
Todayâs start: * ~05:30 got up * vitamins * 800mg ibuprofen (to prevent knee swelling :/) * 1 orange Clif shot blok * espresso en route at Starbucks * #nopasoparungang 2+ mile warmup to Alta Plaza park
Today was a pleasant surprise after the past couple of months of struggles. Even Bay To Breakers just a month-ish ago, my annual "how am I doing" race, was a disappointing 1:20:46 (forgot to post it), slower than 1:17:53 last year, which itself was slower than my 1:14:57 PR the year before that.
After ~7 months of recovery from knee injury it feels like I am finally within reach of my pre-injury performance levels. I did let go of my "new" fore-foot striking running form (except for uphills), and returned to my mid-foot/heel-striking comfort zone. I think that new form needs more short distance practice before I can use it effectively for anything more than a track lap.
Despite still struggling with remnants of knee injury recovery (hence the need for preventative ibuprofen to avoid knee swelling), I'm now comfortably faster than I was a year ago, which has renewed my confidence that I will at least do "ok" at the San Francisco Marathon First Half in 32 days. Until then I'm going to NP, and doing a few long training runs on trails (to keep it easier on the knees).
Iâve (pretty much) let go of any hope/chance of setting a half marathon PR, nevermind the goal I set last year of under 2 hours. However, I may have a chance of beating my course time of 2:23:45 from the first time I ran the San Francisco Marathon First Half two years ago.
The next 32 days I just need to train smart not hard, and keep focusing on recovery, stable/balanced form, and incremental improvement.
Running a half marathon feels doable again, for which Iâm grateful.
I caught a few new Invaders on this trip but the killer robot from Berserk seemed appropriate for the times. There are so many Invaders in Paris now that collectively they are like a landmark of their own. #Paris #latergram #nofilter
Tour Eiffel, the Seine, and boats. A week ago after arriving in Paris (and enjoying the previously posted pain au chocolat and espresso tantek.com/2016/177/t3/pain-au-chocolat-espresso-paris), I went for a walk with a colleague and crossed a #bridge over the #Seine, catching this view of the #TourEiffel and a #boat or two. #Eiffeltower #Paris #river #latergram #notilter
Watching a train zoom under a walking bridge. #motionblur #paris #latergram #nofilter
One snap, as fast as I could get the camera app to open and take, the train was almost gone by the time the software woke up and responded. #train #time #latency #bridge #walkingbridge
Pain au Chocolat and an espresso upon arriving in Paris this past Tuesday. #latergram #nofilter.
I've been in #Paris since Tuesday taking photos of nice things. Going to post more than usual here because it's one of those times where it's better to err on the side of posting more nice things rather than just one or so per day.
Both recently deliberately stoked fears across US/EuropeÂč, and the agingÂČ (but more likely to voteÂł) less educated⎠sadly self-defeatingâ” are not to be underestimated â even financial marketsⶠand prediction markets were mistaken about Brexit outcome. Nevermind the polls.â·
We (in the US) must not underestimate these forces, or else we may suffer an even worse fate. The Republican Party already has (barring an improbable insurrection at their party convention next month).
Think like a time-traveler.
You wake up 2016-11-09 and Trump has won the presidency due to unexpectedly high turnout among the aging less educated, predominantly white, isolated/isolationist.
Did you do everything in your power to prevent that outcome, or better, to promote an alternative outcome (Hillary being elected)?
If not, what would you go back in time to change?
You can travel back to 2016-06-25 to change what you did.
How would you refocus your time and effort between then and now?
These are the questions that Brexit has me asking myself.
These are the questions I think we need to all ask ourselves.
@robinberjon@marcosc glad to hear JSONLD helped inspire incubation model. Will look for repo.
Google because, well one small group in Google to be fair, because:
(1) they (that small group) bullied Microsoft and their search engine licensee Yahoo into the original "co-launching" (in name only) of schema_org. Oligopoly/collusion etc.
(2) they (same small group) did introduce (AFAIK) the "embed JSONLD in a script tag in HTML" (AKA JSONLD data islands) thing which is the latest DRY-violating thing SEOs are shoving into other peopleâs pages, which means it wonât get maintained, will get out of sync with the actual visible content of the page, turn into noise/junk like meta keywords, and Google will stop indexing the noise (long before 15 years from now) and switch to some other thing. They do this every 2-3 years. See also GoogleBase/GBase. data-vocabulary. etc.
@robinberjon@marcosc implemented by whom? when? what real live website(s)? + Google made-up JSONLD data islands in HTML right? Where was that incubated? Or was it just declared by fiat by Google?
@robinberjon@marcosc incubated like recent doings in @W3C@microformats@indiewebcamp. Implement before WD etc. Make the proposer(s) actually build their brainstorm and show it (preferably on their own site) before accepting anything like a spec.
Treat all architecture astronomy/astronaut* proposals as experiments for ideas and nothing more.
@robinberjon@marcosc ignore if not incubated Not incubated: RDFa microdata JSONLD Incubated: #microformats2 and most of #hcard #hcalendar #hatom (some old microformats and some properties were also not incubated and were dropped and not carried forward to microformats2 vocabularies.)
Also ignore stuff that the inventors do not selfdogfoodÂč on their own websites, e.g.: * microdata: @Hixie never used it on hixie.ch * schema_org: Guha never used it on his site. etc.
New modern microformats2 parsers continue to be developed in various languages, and this past year, four new parsing libraries (in three different languages) were added, almost doubling our previous set of six (in five different languages) that brought our year 11 total to 10 microformats2 parsing libraries available in 8 different programming languages.
microformats2 parsing spec updates
The microformats2 parsing specification has made significant progress in the past year, all of it incremental iteration based on real world publishing and parsing experience, each improvement discussed openly, and tested with real world implementations. The microformats2 parsing spec is the core of what has enabled even simpler publishing and processing of microformats.
The specification has reached a level of stability and interoperability where fewer issues are being filed, and those that are being filed are in general more and more minor, although once in a while we find some more interesting opportunities for improvement.
We reached a milestone two weeks ago of resolving all outstanding microformats2 parsing issues thanks to Will Norris leading the charge with a developer spec hacking session at the recent IndieWeb Summit where he gathered parser implementers and myself (as editor) and walked us through issue by issue discussions and consensus resolutions. Some of those still require minor edits to the specification, which we expect to complete in the next few days.
The number of microformats2 parsers in different languages continues to grow, most of them with deployed live-input textareas so you can try them on the web without touching a line of parsing code or a command line! All of these are open source (repos linked from their sections), unless otherwise noted. These are the new ones:
The Java parsers are a particularly interesting development as one is part of the upgrade to Apache Any23 to support microformats2 (thanks to Lewis John McGibbney). Any23 is a library used for analysis of various web crawl samples to measure representative use of various forms of semantic markup.
The Elixir, Haskell, and Java parsers add to our existing in-development parser libraries in Go and Ruby. The Go parser in particular has recently seen a resurgence in interest and improvement thanks to Will Norris.
These in-development parsers add to existing production parsers, that is, those being used live on websites to parse and consume microformats for various purposes:
As with any open source projects, tests, feedback, and contributions are very much welcome! Try building the production parsers into your projects and sites and see how they work for you.
Still simpler, easier, and smaller after all these years
Usually technologies (especially standards) get increasingly complex and more difficult to use over time. With microformats we have been able to maintain (and in some cases improve) their simplicity and ease of use, and continue to this day to get testimonials saying as much, especially in comparison to other efforts:
This last testimonial really gets at the heart of one of the deliberate improvements we have made to iterating on microformats vocabularies in particular.
evolving h-entry
We have had an implementation-driven and implementation-tested practice for the microformats2 parsing specification for quite some time.
More and more we are adopting a similar approach to growing and evolving microformats vocabularies like h-entry.
We have learned to start vocabularies as minimal as possible, rather than start with everything you might want to do. That âstart with everything you might wantâ is a common theory-first approach taken by a-priori vocabularies or entire "predefined ontologies" like schema.org's 150+ objects at launch, very few of which (single digits?) Google or anyone bothers to do anything with, a classic example of premature overdesign, of YAGNI).
With h-entry in particular, we started with an implementation filtered subset of hAtom, and since then have started documenting new properties through a few deliberate phases (which helps communicate to implementers which are more experimental or more stable)
Proposed Additions â when someone proposes a property, gets some sort of consensus among their community peers, and perhaps one more person to implementing it in the wild beyond themselves (e.g. as the IndieWebCamp community does), it's worth capturing it as a proposed property to communicate that this work is happening between multiple people, and that feedback, experimentation, and iteration is desired.
Draft Properties - when implementations begin to consume proposed properties and doing something explicit with them, then a postive reinforcement feedback loop has started and it makes sense to indicate that such a phase change has occured by moving those properties to "draft". There is growing activity around those properties, and thus this should be considered a last call of sorts for any non-trivial changes, which get harder to make with each new implementation.
Core Properties - these properties have gained so much publishing and consuming support that they are for all intents and purposes stable. Another phase change has occured: it would be much harder to change them (too many implementations to coordinate) than keep them the same, and thus their stability has been determined by real world market adoption.
The three levels here, proposed, draft, and core, are merely "working" names, that is, if you have a better idea what to call these three phases by all means propose it.
In h-entry in particular, it's likely that some of the draft properties are now mature (implemented) enough to move them to core, and some of the proposed properties have gained enough support to move to draft. The key to making this happen is finding and citing documentation of such implementation and support. Anyone can speak up in the IRC channel etc. and point out such properties that they think are ready for advancement.
How we improve moving forward
We have made a lot of progress and have much better processes than we did even a year ago, however I think thereâs still room for improvement in how we evolve both microformats technical specifications like the microformats2 parsing spec, and in how we create and improve vocabularies.
Itâs pretty clear that to enable innovation we have to ways of encouraging constructive experimentation, and yet we also need a way of indicating what is stable vs in-progress. For both of those we have found that real world implementations provide both a good focusing mechanism and a good way to test experiments.
In the coming year I expect we will find even better ways to explain these methods, in the hopes that others can use them in their efforts, whether related to microformats or in completely different standards efforts. For now, letâs appreciate the progress weâve made in the past year from publishing sites, to parsing implementations, from process improvements, to continuously improving living specifications. Here's to year 12.
@cyberdees thanks for e-intro! @davidwalshblog just read+enjoyed bunch of your posts. Letâs chat at #MozLondon! P.S. This reply is posted from my site, and automatically syndicated to Twitter.
Note: problem of nonsense replies still exists, public or private.
Twitter has no mechanism for deleting (or at least disconnecting/hiding) nonsense (or abusive) replies to your tweets, on your tweet permalink pages, e.g. the replies after @iwontsignuphere@jkphl to this thread:
The key parts here are the "p-rsvp" property with a value of "yes" I am going to this event and the "in-reply-to" property on a link to the event.
Then he needs to notify me. He uses key IndieWeb building block called Webmention (webmention.net) which uses a POST with parameters: "source" is the RSVP URL, "target" is the event URL.
My site receives that, goes and gets the source, verifies the RSVP.
So he RSVPd to the event, between two websites peer-to-peer, no intermediary.
There's also a copy of the event on Facebook. We feel strongly about meeting people where they already are, and right now largely that's in the silos.
On the event on my site, you can see people have retweeted it, and commented on Google+.
[Shows grid of building blocks]
We use a set of simple building blocks for all this. [Paraphrased from memory.]
Some stats: * ~100 million sites live with @microformats * ~100,000+ webmentions sent / received * ~10,000s IndieWeb sites [from memory]
If you have a personal website you likely already have microformats and don't know it.
Everyone here, keep tackling the huge problems, we're right there with you.
At the same time, try thinking small, try thinking incremental, and meet people where they are.
Q&A:
Q: Are microformats are something you guys designed and invented? or found? What are your thoughts on JSON vs HTML?
A: microformats existed before IndieWebCamp. We chose HTML because it is there. There are milliions billions of websites, and with microformats. We want to meet people where they are.
Q: Could you explain relationship between IndieWebCamp technologies and the @W3C Social Web Working Group?
A: We are fortunate that key @IndieWebCamp players are in the @SocialWebWG. These core building blocks are open standards. Webmention, Micropub are working their way through these standards bodies. [and are W3C Recommendation track documents!]
Last Friday: #IndieWeb Leaders gathered (đ· @iwontsignuphere) and discussed improving our community, our outreach, and even our website, which updated that night, right before the IndieWeb Summit: indiewebcamp.com
Leaders are those who have stepped up and organized an IndieWebCamp in the past 2 years, or have hosted at least two Homebrew Website Club meetups (and documented them, with at least one photo).
It was really great to have a chance to talk about community issues and improvement that we are all passionate about, without having to take time to do so during the IndieWeb Summit itself.
We concluded with the key steps to flip the switch on our site & logo updates (Aaron distributed new stickers), and discussed what steps to take to potentially switch from indiewebcamp.com to indieweb.org. The way we as a community openly discussed and agreed on the logo change made sense for this too.
Afterwards we celebrated our first successful IndieWeb Leaders Summit with snacks, drinks, and video games at Ground Kontrol.
The top photo is from @iwontsignuphere but the rest in this post are mine, uploaded to the IndieWebCamp wiki.
(Written while sitting next to rhiaro.co.uk who asked if I automatically send webmentions to my person-tags and I realized I did not! So I just added support for it. Starting with this post, any person-tags on my photos get homepage webmentions at publishing time!)
Did you see the @IndieWebCamp site update? * nicely refined new logo * modern Vector theme And one more thing: * one fewer HTML table for presentation.
I started with State of the IndieWebCat 2016 which people seemed to appreciate. đž
Today we also launched a new IndieWebCamp logo, and an updated indiewebcamp.com website.
Reviewing what the @IndieWebCamp community accomplished this past year in preparation really made me realize how much everyone has gotten done in just a year, and how much we has a community have grown and are reaching more and more different, diverse, and interesting people.
Aside: for my âpresentationâ I used tabs not slides. That is, I switched between open browser tabs to show content live and online. However I totally forgot my âbut also, spaces not tabsâ joke. Next time.
going to Decentralized Web Summit 2016-06-08âŠ09 in SF.
This is my decentralized RSVP, federated via Webmention to Bridgy Publish to Facebook, which then marked me as âGoingâ, without me having to directly interact with Facebook.
In that time the page has grown, had sections moved around, but in general is being edited by nearly every member of the AB. In three years we have achieved a new level of acceptance of opennness in the AB. I would say the AB is now both as individuals, and as a whole, "open friendly", that is, friendly and supportive of being open.
That being said Iâm still doing much more editing than others, which is not by design but by habit and necessity.
On any given discussion it still takes some careful thinking on the part of the AB about if we can make the discussion public, how should we make it public, what is a good summary, etc. Thereâs rarely any obvious answers here, so the only way to get better at it is by practicing, so we practice in meetings, discuss / decide how to openly communicate, repeat.
My role is still very much one of taking the initiative and encouraging such open documentation (sometimes doing it too).
My goal for the next period is to effect cultural transfer so that Iâm no longer doing more/most of the edits on our open wiki page, and instead have us all collectively reminding each other to publicly document decisions, priorities, summaries.
My goal is to eliminate my specific role in this regard. So that it just becomes accepted as the way the AB works, as a habit, both as individuals, and as a whole.
I donât know if such a cultural change is possible in two years time, but I think we have to try.
Open Priorities
Any group of people with as broad a mission as the AB can potentially spend their time on any number of things. To both operate more affectively as a board (not just a set of elected individuals), and to help the broader W3C community provide us feedback, we publish our priorities openly, as we re-evaluate them annually (potentially semi-annually with new members joining in June / July)
I think this is pretty important as it communicates what is it that we, the AB as a whole think is most important to work on, and with our initials, what we as individuals feel we can most effectively contribute to.
I am going to touch on the few that I see as both important for the AB, and areas that I am bringing my personal skills and experience to help solve:
Maintenance
Maintenance is about how specifications are maintained, making sure they are, and frankly, obsoleting dead specs. It is perhaps the most important longterm priority for W3C.
This gets at the heart of one of the biggest philosophical disagreements in modern specification development.
Whether to have "living" specifications that you can depend on to always be updated, but youâre not sure what parts are stable, or to have "stable" specifications that you can depend on to not change from underneath you, but not be sure if are seeing the latest errata, the latest fixes incorporated.
Or worse, a stable specification which "those in the know" know to ignore because itâs been abandoned, but which a new developer (market entrant) does not know, wastes time trying to implement, and then eventually gets frustrated with W3C or standards as a whole because of the time they wasted.
Right now there are unmaintained specifications on the W3Câs Technical Reports (TR) page. And there are also obsolete specifications as well. Can you tell quickly which are which? I doubt anyone can. This is a problem. We have to fix this.
Best practices for new specifications
Best practices for rec track. Yes we have a maintenance problem we need to fix, but thatâs only half the equation, the other half is getting better at producing maintainable specifications, that hopefully we wonât have to obsolete!
The biggest change happening here at W3C, instigated and promoted by many of us on the AB, is a focus on incubating ideas and proposals before actually working on them in a working group.
This incubation approach is fairly new to W3C, and frankly, to standards organizations as a whole.
It completely changes the political dynamic from, trusting a bunch of authoritative individuals to come up with the right ideas, design etc. a priori and via discussion, compromise, consensus, to instead forcing some amount of early implementation testing, filtering, feedback, iteration.
The reality is that this is a huge philosophical change, and frankly a huge shift in the balance of power & influence of the participants, from academics to engineers, from architects to hackers. So if you were an idealist academic that had a perfect design that you thought everyone should just implement, youâre going to find yourself facing more challenges, which may be frustrating. Similarly if you were a high level enterprise architect, used to commanding whole teams of people to implement your top-down designs.
Incubation shifts power to builders, to implementers, and this is seen as a good thing, because if you cannot convince someone (including yourself and your time) to implement something, even partially, to start with, you should probably reconsider whether it is worth implementing, its use-cases, etc.
By prototyping ideas early, we can debunk bad (e.g. excessively complex) ideas more quickly. By applying the time costs of implementation, we quickly confront the reality that no feature is free, nothing should be included for completeness sake. Everything has a cost, and thus must provide obvious user-value.
Incubation works not only to double-check ideas, but to also provide secondary, tertiary perspectives that help chisel away inessential aspects of a feature, an idea. Aspects that might otherwise be far too easy to include, for politeness sake by those seeking consensus at the cost of avoiding essential conflict and debate.
I bring a particularly strong perspective to the incubation discussions, and that is from my experience with IndieWebCamp where not only do we strongly encourage such incubation of any idea, we require it by the person proposing the idea! And not just in a library, but deployed on their personal website as part of their identity online. We call this practice selfdogfooding, and it has helped reduce and minimize many a feature, or whole specifications.
Security
Lastly but perhaps most user-visible, security (and privacy), in particular fear of losing either, is perhaps the number one user-visible challenge to the open web. Articles like this one are being written fairly frequently:
Some of this is perception, some of it as a result of nearly monthly "data breaches" of major web site / data silos, and others from fears of mass involuntary surveillance, from both governements, and private corporations seeking to use any information to better target their advertisements.
The key aspects we can work on and improve at W3C are related to the very specifications we design. We can, at a minimum work to minimize possible security threats from new features or specifications. On the up side, we can promote specifications that provide better security than previous works. Thereâs lots to do here, and lots of groups are working on various aspects of security at W3C, including the W3C Technical Architecture Group (TAG).
The ABâs role in security is to help these groups both coordinate, share approaches, and to provide encouragements in W3C processes to promote awareness and consdieration of security across the entire web platform.
Looking Forward
That is a lot to work on, and those are only three of the W3C ABâs priorities for 2016. I hope to continue working on them, and help make a difference in each over the next two years.
Thanks for your all your feedback and support. Letâs keep making the open web the best platform the world has ever seen.
Update: 2016-06-01
Update: Iâve been re-elected to the AB for another two years, starting 2016-07-01. Congrats to my fellow elected AB members!
One Saturday morning last August I got a ride with some friends from San Francisco to Mill Valley for the weekly San Francisco Running Company (SFRC) trail run. My favorite route is the ~7 mile round trip to Tennessee Valley Beach and back.
The SFRC crowd tends to be pretty quick, both those from November Project SF and other regulars. I kept up with the beach group most of the way but slowly fell behind as we got closer to the shore. I reached the beach just as everyone else was turning around from the sand. I still wanted to go touch the Pacific.
Running down to the surf by myself brought a lot of things to mind. I was inspired by the waves & rocks to try a handstand on the rocky black sand.
I didnât think anyone was watching but not everyone had run back right away, and my friend Ali caught me handstanding at a distance with her iPhone 6.
I held it for a split second, long enough to feel the physical shift of perspective, and also gain a greater sense of the possible, of possibilities. Being upside down, feeling gravity the opposite of normal, makes you question the normal, question dominant views, dominant forces. The entire run back felt different. Different thoughts, different views of the trail. I stopped and took different photos.
They say never look back.
I say reflection is a source of insight, wisdom, and inspiration.
After returning to the SFRC store, we promptly drove back to SF and grabbed a quick bite at the Blue Front Cafe.
I went home to shower, change, pack, and take a car to the airport. Made it to the gate just as my flight started boarding and found a couple of my colleagues also waiting for the same direct flight to Paris.
After boarding and settling into my seat, the next moments were a bit fuzzy. I donât remember if they fed us right after take-off or not, or if I took a nap immediately, or if I started to look through the entertainment options.
Whether I napped first or not, I do distinctly remember scrolling through new movie releases and coming upon Tomorrowland. When I saw the thumbnail of the movie poster I got a very different impression from when I saw the Metreon marquee three months earlier.
In one week the independent webâs innovators will gather at the IndieWeb Summit in Portland. Join us! A few tickets are still available: 2016.indieweb.org
#NPSF #PRWednesday this morning: 33:40, 0:17 slower than last month. Form felt better, but low energy. Perhaps recovering from a weekend of ~45-50 bicycle miles, and 10km+ trail/beach run. And @Nov_Project_SF Monday.
I have a distinct memory, it must have been late last May, of seeing the digital movie marquees on the outside of San Franciscoâs Metreon complex. I donât remember exactly what day it was, and the experience at the time was too unremarkable for me to bother capturing in my personal log.
I remember seeing âTomorrowland, George Clooneyâ crawling on the marquee and reflexively thinking: another film based on a theme park (ride), likely to be silly and shallow. And in particular, disappointing.
As a child growing up in Southern California, Tomorrowland was my favorite part of Disneyland. So many rides that inspired imagination, and hope for the potential of technology to explore, educate, empower. From Space Mountain to Adventure Thru Inner Space. I also remember slowly becoming disillusioned with Tomorrowland. Rides changed from science hope & curiousity, to science fantasy & entertainment (Star Wars based Star Tours, Captain EO). Exploration fell out of fashion, the Submarine Voyage and Mission to Mars rides were both closed.
I had not even seen a trailer for the Tomorrowland film.
I expected disappointment from something I had no direct experience with, based on what I associated it with, and assumed it would be. I was also extrapolating from other theme-park-ride movies like Pirates of the Carribean.
The difference between a themed âlandâ and a specific ride didnât seem important. Little did I know, that difference apparently allowed for sufficient writer(s)/director creativity for the film to be something much more than anything defined by a particular ride.
It would be almost three months before I returned to Tomorrowland.
Critics disliked it and the general public ignored it.
I, on the other hand, both enjoyed it, and found that the film connected various disparate thoughts that I had considered.
It took me almost three months after its release for me to see the film, and then, I saw it on a flight from San Francisco to Paris, and rewatched it several times.
Seeing Tomorrowland was one of the two most impactful things for me last year. Now that a year has passed since its release, Iâm going to write about the film, bit by bit, explaning what I got out of it, and why it could be considered the best film of 2015.
10km+ run/walk from Crissy field, along the coast, to Baker Beach, back up to Lands End, around to the Sutro Baths, then Ocean Beach for a brief bonfire stop before getting açai bowls in the sunset. Had no idea I was going to do this when I woke up today. Grateful for running friends with simple plans, encouragement, and being open to a detour and tasty destination.
How I spent most of my Saturday: @teamhandstand's #TheSFHunt with âTeam New Englandâ (Got 9th/~270!). Special Thanks to Wayne Grout for the early morning just-in-time bicycle repair help (and tube replacement lesson).
Counting the bike ride from home to Sports Basement in the Marina, and the ride after our last riddle to the after party, and then home, I bicycled ~45-50 miles. More than Iâve ever done in a day. Grateful for muscles that didnât complain.
Sun, smiles, teammate bonding, adventures on the beach, in parks, finishing up on the bay at sunset.
Thank you teammates, @teamhandstand, and all the volunteers for an amazing day.
Sometimes you have to take a midday beach break, soak your feet in the cold Pacific on an especially warm day, and absorb a couple of hours of solar energy (with sunscreen of course). Grateful to live a mere 15 minute drive from this, and fellow beach friends that also "get it". #latergram #nofilter
Ready for my 6th Bay To Breakers #race, first race of #2016. #NPSF #teamrainbow #rainbowteam #yellow #b2b105 #fluorescent #hiliter #novemberproject #rainbowtheme #b2b #running
Recent personal site updates and projects: * werd.io: <meta http-equiv="Status" content="..."/> on all pages * @Falcon: deleted posts with dt-deleted; also supports expiring posts * @benwerd: a single page generator for "aboutme" like sites * @npdoty: ephemeral short-URLs for temporary sharing * @kylewmahan: quiettime.xyz for temporary Twitter muting * @brittb: a tool to help you manage politicians newgov.net/demomap
Hacking on the edge with @benwerd. Open air, floating above the street, talking tombstones, <meta http-equiv="Status" content="410 GONE"/>, auto-expiring posts, Confirm Delete POSSE copies, gone, this post is gone. #indieweb #nofilter
t
Thanks to Julie Anne Noying for the meme birthday card.
