1. using BBEdit

    https://igcdn-photos-c-a.akamaihd.net/hphotos-ak-xtp1/t51.2885-15/11208222_287966931327250_1393997391_n.jpg https://instagram.com/p/2JSbLeg9aR/ Saw a Corona Heights sunrise this morning after running #NPSF #hillsforbreakfast #earlygang with this great crew. https://igcdn-photos-a-a.akamaihd.net/hphotos-ak-xfa1/t51.2885-15/11189998_1700532250174120_2109592547_n.jpg https://instagram.com/p/2JPwhIBzMR/ Keeping it all in mind to get through the next week.

  2. using BBEdit in reply to: Reclaim Your Domain (With Known)

    “Reclaim Your Domain” http://audreywatters.com/2015/04/29/reclaim-known/ Nice post on how @WithKnown helps you reclaim your online self & stuff.

  3. using BBEdit also posted on Facebook

    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. http://november-project.com/wp-content/uploads/2015/04/DSC_01331-768x515.jpg 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.

  4. using BBEdit in reply to Ben Werdmüller's note and tweet:

    Congratulations @benwerd @erinjo! You should both be very proud with what you’ve done @Withknown in just one year.

  5. using BBEdit Ben Werdmüller's note “Our little company is a year old”
  6. using BBEdit

    Hard enough find someone to get along with in #love, why would anyone object to that? Thoughts with #marriageequality.

  7. using BBEdit in reply to @scatteredbrainV’s tweet:

    @scatteredbrainV sure! See also http://microformats.org/wiki/how-to-start-new-translation which has some tips. Feedback welcome!

  8. using BBEdit
  9. using BBEdit in reply to @scatteredbrainV’s tweet:

    @scatteredbrainV yes very much so! Perhaps start with syncing up http://microformats.org/wiki/Main_Page-it with http://microformats.org/wiki/ ?

  10. using BBEdit
  11. using BBEdit
  12. using BBEdit in reply to @scatteredbrainV’s tweet:

    @scatteredbrainV #microformats2 http://microformats.org/wiki/microformats2 incorporates lessons learned from microformats, RDFa, microdata

  13. using BBEdit

    https://igcdn-photos-a-a.akamaihd.net/hphotos-ak-xaf1/t51.2885-15/11203407_1588133714789784_1034620108_n.jpg https://instagram.com/p/2B9kohg9WU #NPSF #trackattack done: warmup, 400 800 1200 1600 1200 800 400 https://scontent-sjc.xx.fbcdn.net/hphotos-xpa1/v/t1.0-9/11182220_10203820312768607_4522554706895697871_n.jpg?oh=c5a7066102677dd9a47a0ce34792780e&oe=559EC92F&ext=.jpg Prev: tantek.com/2015/104/t1/npsf-trackattack-woke-up-late

  14. using BBEdit

    “HTML is my API” @aaronpk on @HackerNews’s HTML vs JSON, reliability, and using #microformats2 https://aaronparecki.com/articles/2015/04/26/1/html-is-my-api

  15. using BBEdit
  16. using BBEdit
  17. using BBEdit
  18. using BBEdit
  19. using BBEdit
  20. using BBEdit
  21. using BBEdit
  22. using BBEdit

    Everyone at Homebrew Website Club SF/PDX/NYC this week was ok with @IndieWebCamp July 11-12. Mark your calendars!

  23. using BBEdit
  24. using BBEdit in reply to https://twitter.com/wilkieii/status/591805843915538432

    @wilkieii no fuss here. @LynnMagic you’re active on your own site and building @CQT_Quirell. Just a quiet fan here.

  25. using BBEdit Ryan Barrett’s “Introducing Color Genomics”
  26. using BBEdit

    Every morning: 1. What’s the most I can do with what I have? 2. Remember everyone is struggling with something.

  27. using BBEdit

    New York City friends TONIGHT 1st NYC 2015 #IndieWeb meetup 7p EDT @WeWork Charging Bull 25 Bwy fb.com/events/1596554663924436

  28. using BBEdit

    Likely dates for @IndieWebCamp 2015: 2015-07-11..12. Can you make it? Other suggestions? Edit: https://indiewebcamp.com/2015#Candidate_Dates

  29. using BBEdit in reply to: https://twitter.com/nialljthompson/status/590594767282642944

    @nialljthompson no problem. Here's a good start: http://microformats.org/wiki/microformats2 http://microformats.org/2014/03/05/getting-started-with-microformats2

  30. using BBEdit
  31. using BBEdit
  32. using BBEdit
  33. using BBEdit
  34. using BBEdit
  35. using BBEdit
  36. using BBEdit
  37. using BBEdit in reply to: https://twitter.com/nialljthompson/status/590593036737982464

    @nialljthompson @Malarkey @westleyknight @KevinMarks schema-org is overly complex, more effort. #microformats2 simpler

  38. using BBEdit in reply to: https://twitter.com/kevinmarks/status/590554432938635264 https://twitter.com/Malarkey/status/590446922026082304 https://twitter.com/westleyknight/status/590444882373828608

    @Malarkey @westleyknight @KevinMarks Markup for markup sake not worth it. For usecases it is: * #indieweb * accessibility * search etc. See also and start using microformats2: http://microformats.org/2014/03/05/getting-started-with-microformats2

  39. using BBEdit

    One more thing on #extwebsummit thoughts: In addition to trimming specs, editors should selfdogfood spec features.

  40. using BBEdit
  41. using BBEdit
  42. using BBEdit
  43. using BBEdit in reply to: https://twitter.com/SwiftOnSecurity/status/590280995426988032

    @SwiftOnSecurity #HTTPS/#SSL #UX critiques on point for #extwebsummit today: https://twitter.com/SwiftOnSecurity/status/590280995426988032 https://twitter.com/SwiftOnSecurity/status/590280560435671040 and deleted: https://twitter.com/SwiftOnSecurity/status/590281233189449728 "The user experience for SSL is the height of nerd-centric design incompetence." 2015-04-20 15:29 PDT

  44. using BBEdit
  45. using BBEdit
  46. using BBEdit

    New rule: reject claims by "Linked Data" advocate(s) until they provide *links* (URLs) to actual *data*. #extwebsummit

  47. using BBEdit also on Facebook post 10101608295524673.

    good luck Boston Marathon runners @Amy_Leedham @hilzhayz @sheilabhardwaj @eflandro @runalivesd @denizofboston @orrinwhalen and #NovemberProject friends not on Twitter too: Jorge Kristyn Bill Micah and all the rest! Have a great race!

  48. using BBEdit.

    great talk by @barryf on “Why We Need The IndieWeb” https://vimeo.com/125167234 with why, how to, markup, code etc.

  49. using BBEdit.

    #NPSF #trackattack plan: 400 800 2x1600 800 400 abs I did: 800 2x1600 800 400 abs 400 Woke up late at 5:40 without my alarm because its sound was fully muted, so I warmed up on the jog to the track, and missed the first 400 for a pit stop. Made up for it afterwards. Also it was a much colder than expected morning. Like hurt your lungs cold when you inhale too deep. They didn’t feel warmed up until after the second 1600. Still, made good times according to Nike+ Running so I’ll take it. Another solid track workout in the books. I’m counting this as having done the whole thing even though I swapped the first 400 to after abs. Previously: tantek.com/2015/097/t1/weatherproof-trackattack-morning

  50. using BBEdit.

    Wake up after falling asleep, lights on, laptop open. Finish post, fix a bug, reply thanks, lights off, back to sleep.

  51. using BBEdit in reply to: https://twitter.com/tigt_/status/582341803447287808

    @tigt_ great catch! And a good example of when you actually want to double-HTML-encode some text. Fixed. Thank you.

  52. using BBEdit.

    https://scontent-sjc.cdninstagram.com/hphotos-xaf1/t51.2885-15/11098491_909195885797240_1967885540_n.jpg https://instagram.com/p/1ZRAX4g9ZG 2nd trail race done! Woodside/Purisima Creek Crossover 10km 1100' 81:47 77/114; 14/17 age/gender group.

  53. using BBEdit.

    Yesterday FriendFeed shutdown indiewebcamp.com/site-deaths#FriendFeed invented "Like" in 2007 indiewebcamp.com/like#FriendFeed before FB in 2009.

  54. using BBEdit.

    https://igcdn-photos-f-a.akamaihd.net/hphotos-ak-xaf1/t51.2885-15/11143072_1429392700705805_1251090571_n.jpg https://instagram.com/p/1TcyWFg9Re my Friday "peak" experience 1. run to Twin Peaks 2. 30min #NPSF #hillsforbreakfast 3. #sunrise #mayurasana https://igcdn-photos-f-a.akamaihd.net/hphotos-ak-xfa1/t51.2885-15/10881956_876720719032853_1403997861_n.jpg https://instagram.com/p/1TIEynA9Zp photo by @Lucemagoose16 Balancing and breathing in that moment, I felt incredibly grateful for * Being able to actually run non-stop from home up to Twin Peaks (even if @thegreenk pulled over and shuttled me up the last little bit) and still breathe * The incredible @Nov_Project_SF community that #justshowup — the energy and inspiration everyone brings makes us all go farther faster longer stronger * Watching the sunrise on a beautiful San Francisco morning * Running/hiking for another 30 minutes (including all of what I skipped the first time up) - three repeats * Being able to hold myself up with just my hands — strong enough to balance a plank (improved mayurasana (yoga peacock pose) form, with more to improve) after all that. https://scontent-sjc.xx.fbcdn.net/hphotos-xpf1/t31.0-8/1797002_622434381226392_7236544914449407498_o.jpg https://www.facebook.com/NovemberProjectSF/photos/a.622433624559801.1073742032.276430682493432/622434381226392/ photo by Laura McCloskey

  55. using BBEdit. in reply to: https://kylewm.com/2015/04/homebrew-website-club-1 https://www.facebook.com/events/807045706055031

    going to Homebrew Website Club 17:30 @MozSF 2015-04-22. Indie event kylewm.com/2015/04/homebrew-website-club-1 silo fb.com/events/807045706055031

  56. using BBEdit

    New @CSS3UI TR WD published w3.org/TR/2015/WD-css3-ui-20150409 with minor fixes. 2 issues remain, to be resolved in next draft.

  57. using BBEdit. also on Facebook

    You think you’re ok, at peace, and then a memory hits you. Last time you drove through Vegas, stopping in artificially glowing darkness only for fuel, Starbucks, and to switch drivers to finish the last leg of a half-cross-country-road-trip before midnight. You honestly thought, and felt, that despite twists and turns, like driving those roads, you were working together towards something, when actually you were just part of a transition, even if neither of you knew it at the time. Or you want to believe that at least, in good, honest intentions. Things didn’t work out, and there's no one to blame because everyone was honest, with themselves, with their feelings, with each other. And respectful. No wrong was done so there is nothing to forgive, nothing to ask forgiveness for. And yet the feelings linger. The feelings not of loss, no those were months ago, but the feelings of what could have been. Not expectations, but hopes. Not imagined, but actively worked. Then you exhale, inhale, and keep going with your yoga class, figuring no one will notice a tear or two streaming down your face mixing with your sweat.

  58. using BBEdit.

    https://scontent-sjc.cdninstagram.com/hphotos-xfa1/t51.2885-15/11116970_331576557051475_2102234676_n.jpg https://instagram.com/p/1L13E4g9Qm #weatherproof #wet #trackattack morning: warmup 3x1200 3x600 300 cooldown Previously: http://tantek.com/2015/090/t1/timed-mile-track-get-better

  59. using BBEdit. in reply to: https://kylewm.com/2015/04/homebrew-website-club https://www.facebook.com/events/647998125333311

    going to Homebrew Website Club @TheCreamerySF 2015-04-08. Indie event kylewm.com/2015/04/homebrew-website-club FB fb.com/events/647998125333311

  60. using BBEdit
  61. using BBEdit
  62. using BBEdit
  63. using BBEdit Kyle Mahan’s “bapp”
  64. using BBEdit Kevin Marks’s “Puzzled by Medium”
  65. using BBEdit
  66. using BBEdit
  67. using BBEdit
  68. using BBEdit
  69. using BBEdit
  70. using BBEdit Aaron Parecki's run
  71. using BBEdit also on Facebook post 10101576268187713

    ~7:30 plank PR this morning @Nov_Project_SF #plankoff! New goal: plank longer than timed mile time. Related: http://november-project.com/npsf-newsflash-whole-tribe-late-for-work-after-lengthy-plankoff/ No pigeon pose today (yet), just legit (if shakey at the end) planking that made it to the top 7-8 of #NPSF plankers! (see that blog post)

  72. using BBEdit

    Reflecting on the close of a quarter. A tragic loss & unexpected gains. Much accomplished, much to do. Still grateful.

  73. using BBEdit in reply to: https://twitter.com/Wikisteff/status/582918924267851776

    @Wikisteff the 10 year old was me.

  74. using BBEdit

    8:20 timed track mile! Wish I could tell the 10 year old that couldn’t run 1 lap without wheezing that someday it would get better.

  75. using BBEdit

    bicycled 30+ miles solo (incl. two ~10mi stints) today, more than ever. focusing on one thing (cheering), accomplished something else much harder that I would have otherwise not attempted directly. https://instagram.com/p/0zLPdNA9Rb/ https://igcdn-photos-f-a.akamaihd.net/hphotos-ak-xaf1/t51.2885-15/11084626_1417259171921733_1825550009_n.jpg

  76. using BBEdit

    wonderful time biking around Livermore, cheering on @KatLucky09 and the other #RunLiv Half Marathon runners. #fuckyeah http://instagram.com/p/01blz4nsow/ https://igcdn-photos-f-a.akamaihd.net/hphotos-ak-xfa1/t51.2885-15/11116967_1569431696675757_1917036865_n.jpg

  77. using BBEdit also on Twitter and Swarm

    👕 athletic tshirts on sale $11! (@ Adidas in San Francisco, CA)

  78. using BBEdit also on Twitter and Swarm

    Post bike riding yum (at @YoppiYogurt in San Francisco, CA)

  79. using BBEdit in reply to: https://twitter.com/PetraGregorova/status/575645717529632768

    <div class="h-entry"> Thanks <a class="u-in-reply-to" href="https://twitter.com/PetraGregorova/status/575645717529632768"> @PetraGregorova </a>! </div>

  80. using BBEdit in reply to: https://twitter.com/marcosc/status/575634985622892544 https://twitter.com/kylewmahan/status/575696803137392641 https://twitter.com/jmsmcfrlnd/status/575775276245843968

    @marcosc thanks and yes to June. @kylewmahan thank you, the feeling is mutual. @jmsmcfrlnd thanks as well!

  81. using BBEdit in reply to: https://twitter.com/leyink/status/575574886439124992 https://twitter.com/Wordridden/status/575575534299668480 https://twitter.com/Cennydd/status/575580758955401217 https://twitter.com/obiwankimberly/status/575603931868491776 https://twitter.com/f/status/575614299445575680 https://twitter.com/jeremyzilar/status/575614480471584768 https://twitter.com/brucel/status/575615003887271936 https://twitter.com/scatteredbrainV/status/575626249533521920

    @leyink @Wordridden @Cennydd @obiwankimberly @f @jeremyzilar @brucel @scatteredbrainV thank you for birthday wishes!

  82. using BBEdit
  83. using BBEdit.

    Did #NPSF Double-PR Wednesday today: 38:32 & 37:04 Last month: 36:02 & 36:15 Next: driving to a multi-hour MV meeting.

  84. using BBEdit.

    #indieweb: “As writers, we don’t need companies like Medium to tell us how to use the web. Or define openness and democracy. Or tell us what’s a ‘waste of [our] time’ and what’s not. Or determine how and where readers experience our work. We need to decide those things for ourselves.” http://practicaltypography.com/billionaires-typewriter.html

  85. using BBEdit
  86. using BBEdit.

    #trackattack is back! did a 400 warmup 800 800 800 800 4x200, abs workout: warmup 800 1600 800 1600 4x200, abs Reopening of Kezar Stadium has definitely brought a bigger crowd. We had 29 people today. Though I need to build back up to doing the full track workout, I did have a couple of minor personal achievements this morning. During part of the second 1600, when I was starting my 800, I managed to draft Jeff drafting Andy Cochrane for 200m (half a lap). Though Andy is still in recovery mode he's still ridiculously fast from my perspective. Being able to "keep up" with Andy, even for just a half a lap, even when he was "taking it easy", and in the middle of a 1600, felt like doing the impossible, and emboldened me to push harder on average in my other runs, including... On the second 200 I made sure to take-off exactly when Kate said go. As I exited the turn onto the back straight, I started kicking farther back & up, and managed to pass & finish that 200 ahead of a couple of people who are usually much faster than me. I could barely breathe afterwards. Also my 1 year trackiversary was 2015-063 (20 days ago) tantek.com/2014/064/t2/yesterday-npsf-track-kezar-trackattack Hard to believe I've been running track workouts (on & off, mostly on) for over a year. Previously: * 2015-069 did Trackish Tuesday 2x600 4x400 2x300 4x200 * tantek.com/2015/062/t1/ran-trackish-tuesday-before-dawn-sunrise * tantek.com/2015/055/t6/morning-legs-tired-did-deck-instead * tantek.com/2015/048/t1/excellent-trackish-tuesday * 2015-034 did Trackish Tuesday warmup of 2x600, 600, 2x200 * 2015-027 did Trackish Tuesday 5x600 3x300 * 2014-350 did Trackish Tuesday 6x600 * 2014-315 post-Berkeley Half recovery fast walk/jog at Tempo Tuesday * 2014-294 did Tempo Tuesday ~16km 94:30 (10 mi at < 9:30min/mile) * 2014-287 did Tempo Tuesday ~7km * 2014-273 did Tempo Tuesday ~15.2km * 2014-266 did Track Tuesday workout all but one 1600 * tantek.com/2014/245/t1/just-short-today-trackattack-workout

  87. using BBEdit. in reply to: https://kylewm.com/2015/03/homebrew-website-club-2015-march-25 https://www.facebook.com/events/1565113317092307

    going to Homebrew Website Club 17:30 @MozSF 2015-03-25. Indie event kylewm.com/2015/03/homebrew-website-club-2015-march-25 silo fb.com/events/1565113317092307

  88. using BBEdit in reply to: http://tantek.com/2015/080/t1/boarded-flight-sf https://twitter.com/t/status/579218866150121472

    late BOS departure, SFO arrival, too late to make it to yoga. Who’s up for a quick run in Golden Gate park?

  89. using BBEdit

    Finally catching up with tweets from a week and more ago. Grateful for so many. Will keep working to improve the web.

  90. using BBEdit

    Boarded flight back to SF. Hope to make it back in time for 11:00 intermediate vinyasa yoga @MissionCliffs.

  91. using BBEdit
  92. using BBEdit
  93. using BBEdit
  94. using BBEdit
  95. using BBEdit
  96. using BBEdit
  97. using BBEdit
  98. using BBEdit
  99. using BBEdit
  100. using BBEdit
  101. using BBEdit
  102. using BBEdit
  103. using BBEdit
  104. using BBEdit
  105. using BBEdit
  106. using BBEdit
  107. using BBEdit
  108. using BBEdit
  109. using BBEdit
  110. using BBEdit
  111. using BBEdit
  112. using BBEdit
  113. using BBEdit
  114. using BBEdit
  115. using BBEdit
  116. using BBEdit
  117. using BBEdit
  118. using BBEdit
  119. using BBEdit
  120. using BBEdit
  121. using BBEdit
  122. using BBEdit
  123. using BBEdit
  124. using BBEdit
  125. using BBEdit
  126. using BBEdit
  127. using BBEdit
  128. using BBEdit
  129. using BBEdit in reply to: https://twitter.com/sandhawke/status/579131512408403968

    @sandhawke sorry to hear that! After this week you’ve definitely earned some weekend rest. Get well soon.

  130. using BBEdit

    Thanks @SandHawke for hosting @IndieWebCamp, @dshanske for remote participation setup, and @dissolve333 especially for organizing the whole thing overall including getting sponsors for food, setting it all up, and keeping things running smoothly in general! https://instagram.com/p/0bCGxnA9Vp https://igcdn-photos-c-a.akamaihd.net/hphotos-ak-xfa1/t51.2885-15/10979618_749621595137186_414240620_n.jpg http://timowens.io/2015/indiewebcamp-dinner-at-cambridge-2015 http://timowens.io/file/a3f213bdebdfd022ecb9d74fc29dc2e5/image.jpg Photos from Tim Owens (timowens.io)

  131. using BBEdit

    Dublin Core Application Profiles — A Brief Dialogue

    IndieWebCamp Cambridge 2015 is over. Having finished their ice cream and sorbet while sitting on a couch at Toscanini’s watching it snow, the topics of sameAs, reuse, and general semantics leads to a mention of Dublin Core Application Profiles.

    1. A:
      Dublin Core Application Profiles could be useful for a conceptual basis for metadata interoperation.
    2. T:
      (Yahoos for dublin core application profiles, clicks first result)
    3. T:
      Dublin Core Application Profile Guidelines (SUPERSEDED, SEE Guidelines for Dublin Core Application Profiles)
    4. T:
      Kind of like how The Judean People’s Front was superseded by The People’s Front of Judea?
    5. A:
      (nervous laugh)
    6. T:
      Guidelines for Dublin Core Application Profiles
    7. T:
      Replaces: http://dublincore.org/documents/2008/11/03/profile-guidelines/
    8. T:
      Hmm. (clicks back)
    9. T:
      Dublin Core Application Profile Guidelines
    10. T:
      Is Replaced By: Not applicable, wait, isn’t that supposed to be an inverse relationship?
    11. A:
      I’m used to this shit.
    12. T:
      (nods, clicks forward, starts scrolling, reading)
    13. T:
      We decide that the Library of Congress Subject Headings (LCSH) meet our needs. - I’m not sure the rest of the world would agree.
    14. A:
      No surprises there.
    15. T:
      The person has a name, but we want to record the forename and family name separately rather than as a single string. DCMI Metadata Terms has no such properties, so we will take the properties foaf:firstName and foaf:family_name
    16. T:
      Wait what? Not "given-name" and "family-name"? Nor "first-name" and "last-name" but "firstName" and "family_name"?!?
    17. A:
      Clearly it wasn’t proofread.
    18. T:
      But it’s in the following table too. foaf:firstName / foaf:family_name
    19. A:
      At least it’s internally consistent.
    20. A:
      Oh, this is really depressing.
    21. A:
      Did they even read the FOAF spec or did they just hear a rumour?
    22. T:
      (opens text editor, starts typing up a blog post)
  132. using BBEdit

    First day of Spring 2015 #IndieWebCamp @MIT wrapped. Snow in Cambridge. Free wifi & power @Tosci. And ice cream. But that’s not free. Except for the samples.

  133. using BBEdit

    Lots of personal site hacking @indiewebcamp today! https://indiewebcamp.com/images/5/59/IWCCambridge_hack_grid.jpg More photos: https://indiewebcamp.com/2015/Cambridge#Photos

  134. using BBEdit in reply to: https://twitter.com/slightlylate/status/578801995160502272

    @slightlylate fortunately your action (post on a site with HTML content) speaks louder than your words ;) @smashingmag

  135. using BBEdit in reply to: http://tantek.com/2015/078/t1/google-mission-information-neglect-delete https://twitter.com/t/status/578764218209452032

    Remember when you could find 1980s Usenet posts on DejaNews? Next: Google Groups is neglected: https://en.wikipedia.org/wiki/Deja_News#Criticism

  136. using BBEdit

    Google’s new mission: organize the world’s information, universally neglect it, & delete it. #googlecode #youhadonejob

  137. using BBEdit Twitter post 578402322210009088

    switched my site from Google’s PubSubHubbub hub to @superfeedr for: * better PuSH 0.4 * HTML new content notifications

  138. using BBEdit Twitter post 578389037288914944

    Finished W3C Social Web Working Group meeting with more demos, co-evolution + bridges over competition, photo: https://aaronparecki.com/notes/2015/03/18/5/w3c http://aaronparecki.com/notes/2015/03/18/5/files/photo.jpg

  139. using BBEdit in reply to: https://twitter.com/Nov_Project/status/578203895278612480

    2014-06-11: 26 Harvard Stadium sections @Nov_Project 2015-03-18: 32 sections, PR. #weatherproof Goal: 37, a full tour. https://instagram.com/p/0YpSK_g9Yz https://scontent-lga.cdninstagram.com/hphotos-xaf1/t51.2885-15/10990624_277768962415189_378194688_n.jpg

  140. using BBEdit Ben Robert’s photo
  141. using BBEdit Aaron Parecki’s note “Just launched PuSH 0.4 support for Monocle!”
  142. using BBEdit Aaron Parecki's photo
  143. using BBEdit

    chairing the afternoon session of @W3C Social Web Working Group, and @timberners_lee stops by to join the discussion!

  144. using BBEdit

    Kezar is open! That means… Return of the Track https://youtu.be/DjzskFSU9Pc #justshowup Tue 6am; @t me, rub in the #FOMO.

  145. using BBEdit
  146. using BBEdit in reply to: http://tantek.com/2015/075/t4/superb-follow-up-javascript-did-not-read https://twitter.com/t/status/577651884434944001

    Note: @edsu’s post reads *beautifully* without ANY Javascript being loaded. Fast too. #WordPress #indieweb #nojsneeded

  147. using BBEdit in reply to: https://kylewm.com/2015/03/this-by-edsu-http-inkdroid-org-journal-2015-03-12 https://twitter.com/kylewm2/status/577559327688429569

    Superb follow-up by @edsu to my "js;dr" JavaScript required did not read post: inkdroid.org/journal/2015/03/12/javascript-and-archives/ via @kylewm2

  148. using BBEdit

    Hello Cambridge MA! I am in you. And you’re a lot less cold than I expected. Haven’t had to use my gloves or hat yet!

  149. using BBEdit

    to MIT for @W3C Social Web WG, @IndieWebCamp! Let’s focus on live user-centric demos only, no architecture astronomy plumbing demos, no video playback. Live demos with real websites with real content (no Lorem Ipsum) and real URLs / permalinks that anyone can load, browse, verify for themselves. See Also: http://tantek.com/2015/069/t1/js-dr-javascript-required-dead

  150. using BBEdit

    wrote draft of attribution practices for @W3C specs, using the wiki. @W3CAB said good to share https://www.w3.org/wiki/Attribution

  151. using BBEdit

    A week ago I woke up at ~6:15 in Big Basin to @LaurBreu shouting “Time to get up for morning run!”. It was significantly colder than any recent morning in San Francisco. I put on three layers and joined about a half dozen other fellow #NPSF campers; I think we finally got going about 6:45. When I returned to camp I had completed my longest trail run to date, most of it solo. https://instagram.com/p/0Nm00jA9XW/ https://igcdn-photos-d-a.akamaihd.net/hphotos-ak-xaf1/t51.2885-15/10860163_439238959576483_1093254551_n.jpg We ran down to the park headquarters, checked out the trail options, and quickly decided on Berry Creek Falls, whick seemed about another 4.5 miles away. There was a brief debate about whether to do a full 9 mile loop or run back after a halfway point. Everyone started down the trail at a fast clip. In less than half a mile I had lost sight of them. After about a mile, I saw one friend come back, she'd noted beforehand that she had to cut short for another engagement. Not long after I saw another friend walking back, apparently having twisted her ankle running. After that I didn’t see anyone else on the trail. I kept running, stopping a few times to take photos. After making it about 3/4 of the way to Berry Creek Falls, I kept expecting to see the rest of the group running back. With just 1 mile to go I decided to keep going all the way to the falls. Made it to a bench with a beautiful view of the falls, yet it looked like I could get closer. The trail meandered downhill closer to the creek eventually to a large fallen tree. To my right was a large boulder embedded in the ground that looked too slippery to descend down to the flowing water. I crossed the creek with the fallen tree as bridge. On the other side I had to jump down to another fallen tree, then down to the creekbank where the path continued back towards the falls. Hiking up I finally got close enough for a better view. At this point I had no idea where everyone else had gone. Last I had heard the plan was to run to the falls and run back. Since I was on my own, and after all the wandering about 5 miles away from the park headquarters, I decided the best option was to run back the way I came. I ran back to the fallen tree. But this time I crossed the rocks in the stream to the large boulder on the other side. At about a 60 degree incline, with plenty of ridges to grab, and chips to dig my feet into, I climbed up the boulder without difficulty. On the run back the layers came off until I was running in a tshirt and sweatpants, the rest tied around my waist. I’d never run this far by myself, in a new place, miles away from help or other resources. No headphones, no network contact. A lot of time to just think, run, and focus. Focus on running, on keeping a good pace, and regular breathing. It was good to see landmarks that I had passed on the way in. I’d counted three trail markers, and as I passed each one on the way back I sipped just that much from the remaining water bottle strapped to my waist. About halfway back I finally started to see people coming the other way. Hikers. With jackets, backpacks, and hats. As we exchanged good mornings and they stopped to stand back as I ran by, I couldn't help but think, I used to be you, now I'm this. I reached the trail head at park headquarters, checked a map for the road back to the camp, and ran uphill the rest of the way. The trail was estimated to take ~6 hours. I ran ~11 miles from camp to the waterfall and back in under 2.5 hours. At some point in the last few months apparently I changed from a hiker to a trail runner. It felt more comfortable, and was more fun, to run the trail than walk it.

  152. using BBEdit

    “amplifications of lesser heard voices are vital to a free society.” — @acegiak #indiewebcamp. Continued: “Solidarity with minorities you're not a part of prevents authorities from dividing people and conquering” http://indiewebcamp.com/irc/2015-03-11/line/1426064607414

  153. using BBEdit

    Made it once more around the sun.

  154. using BBEdit

    New @CSS3UI WD published w3.org/TR/2015/WD-css3-ui-20150310 All but 1 issue resolved. Fewer features too, consistent with: http://tantek.com/2015/068/b1/security-towards-minimum-viable-web-platform

  155. using BBEdit

    js;dr = JavaScript required; Didn’t Read. Pages that are empty without JS: dead to history (archive-org), unreliable for search results (despite any search engine claims of JS support, check it yourself), and thus ignorable. No need to waste time reading or responding. Also known as, if it’s not curlable, it’s not on the web. https://indiewebcamp.com/curlable Because in 10 years nothing you built today that depends on JS for the content will be available, visible, or archived anywhere on the web. All your fancy front-end-JS-required frameworks are dead to history, a mere evolutionary blip in web app development practices. Perhaps they provided interesting ephemeral prototypes, nothing more. Previously: * pdf;dr: https://tantek.com/2013/305/t2/pdf-dr-avoid-clicking-link-pdf Related: * tos;dr: https://tosdr.org See Also: * https://htmlcssjavascript.com/web/youre-so-smart-you-turned-javascript-into-xhtml/ * https://sourcegraph.com/blog/switching-from-angularjs-to-server-side-html * https://adactio.com/journal/7706 * https://www.reddit.com/r/learnprogramming/comments/3cfvst/the_number_of_javascript_frameworks_available_is/cswpr3d Responses and follow-ups: * 2015-03-11 JavaScript and Archives: https://inkdroid.org/journal/2015/03/12/javascript-and-archives/ * 2015-03-12 https://reddit.com/r/programming/comments/2ys5nk/jsdr_javascript_required_didnt_read/ * 2015-03-16 https://tantek.com/2015/075/t5/reads-beautifully-without-javascript-loaded-fast * 2015-03-19 https://irreal.org/blog/?p=3798 * 2015-03-19 https://www.facebook.com/smashmag/posts/10153198367332490 (2019 Internet Archive snapshot: https://web.archive.org/web/20191123225253/https://www.facebook.com/smashmag/posts/10153198367332490 missing the content (js;dr), subsequent snapshots redirect to a login wall) * 2015-05-12 https://news.ycombinator.com/item?id=9531411 More examples, screenshots, and ongoing research: * https://indiewebcamp.com/js;dr

  156. using BBEdit

    Simplifying Standards & Reducing Their Security Surface: Towards A Minimum Viable Web Platform

    At the start of this month, I posted a simple note and question:

    Thoughts yesterday lunch w @bcrypt: @W3C specs too big/complex. How do we simplify WebAPIs to reduce security surface?

    With follow-up:

    And @W3C needs a Security (#s6y) group that reviews all specs, like #i18n & #a11y (WAI) groups do. cc: @bcrypt @W3CAB

    Which kicked off quite a conversation on Twitter (18 replies shown on load, 53 more dynamically upon scrolling if various scripts are able to load & execute).

    Security & Privacy Reviews

    Buried among those replies was one particularly constructive, if understated, reply from Mike West:

    […] mikewest.github.io/spec-questionnaire/security-privacy/ is an initial strawman for security/privacy self-review.

    A good set of questions (even if incomplete) to answer in a self-review of a specification is an excellent start towards building a culture of reviewing security & privacy features of web standards.

    While self-reviews are a good start, and will hopefully catch (or indicate the unsureness about) some security and/or privacy issues, I do still think we need a security group, made up of those more experienced in web security and privacy concerns, to review all specifications before they advance to being standards.

    Such expert reviews could also be done continuously for "living" specifications, where a security review of a specification could be published as of a certain revision (snapshot) of a living specification, which then hopefully could be incrementally updated along with updates to the spec itself.

    Specification Section for Security & Privacy Considerations

    In follow-up email Mike asked for feedback on specifics regarding the questionnaire which I provided as a braindump email reply, and offered to also submit as a pull request as well. After checking with Yan, who was also on the email, I decided to go ahead and do so. After non-trivially expanding a section, very likely beyond its original intent and scope (meta-ironically so), it seemed more appropriate to at least blog it in addition to a pull request.

    The last question of the questionnaire asks:

    Does this specification have a "Security Considerations" and "Privacy Considerations" section?

    Rather than the brief two sentence paragraph starting with Not every feature has security or privacy impacts, which I think deserves a better reframing, I've submitted the below replacement text (after the heading) as a pull request.

    Reducing Security Surface Towards Minimum Viability

    Unless proven otherwise, every feature has potential security and/or privacy impacts.

    Documenting the various concerns that have cropped up in one form or another is a good way to help implementers and authors understand the risks that a feature presents, and ensure that adequate mitigations are in place.

    If it seems like a feature does not have security or privacy impacts, then say so inline in the spec section for that feature:

    There are no known security or privacy impacts of this feature.

    Saying so explicitly in the specification serves several purposes:

    1. Shows that a spec author/editor has possibly considered (hopefully not just copy/pasted) whether there are such impacts.
    2. Provides some sense of confidence that there are no such impacts.
    3. Challenges security and privacy minded individuals to think of and find even the potential for such impacts.
    4. Demonstrates the spec author/editor's receptivity to feedback about such impacts.

    The easiest way to mitigate potential negative security or privacy impacts of a feature, and even discussing the possibility, is to drop the feature.

    Every feature in a spec should be considered guilty (of harming security and/or privacy) until proven otherwise. Every specification should seek to be as small as possible, even if only for the reasons of reducing and minimizing security/privacy attack surface(s).

    By doing so we can reduce the overall security (and privacy) attack surface of not only a particular feature, but of a module (related set of features), a specification, and the overall web platform. Ideally this is one of many motivations to reduce each of those to the minimum viable:

    1. Minimum viable feature: cut/drop values, options, or optional aspects.
    2. Minimum viable web format/protocol/API: cut/drop a module, or even just one feature.
    3. Minimum viable web platform: Cut/drop/obsolete entire specification(s).

    Questions and Challenges

    The above text expresses a specific opinion and perspective about not only web security, web standards, but goals and ideals for the web platform as whole. In some ways it raises more questions than answers.

    How do you determine minimum viability?

    How do you incentivize (beyond security & privacy) the simplification and minimizing of web platform features?

    How do we confront the various counter-incentives?

    Or rather:

    How do we document and cope with the numerous incentives for complexity and obfuscation that come from so many sources (some mentioned in that Twitter thread) that seem in total insurmountable?

    No easy answers here. Perhaps material for more posts on the subject.

    Thanks to Yan for reviewing drafts of this post.

    Update 2015-03-31

    Thanks to Mike West accepting my pull request, my above suggested edit and additional text is now inline in the Security & Privacy Questionnaire!

  157. using BBEdit

    Camped this weekend. 48 hrs 100% off grid. Only device usage: * took a few photos & notes * tracked ~11 mile trail run

  158. using BBEdit in reply to: http://stream.withknown.com/2015/introducing-known-pro-the-best-way-to-reach-your-audience https://twitter.com/withknown/status/573571404173471745

    Known Pro is here! https://withknown.com/pro/ Congrats @benwerd @erinjo! #indieweb @Withknown’s superior interoperability, mobile web support, user experience, and integration with existing silos, is far beyond any other content publishing system, independent or otherwise in existence. And it’s open source as well. http://stream.withknown.com/2015/introducing-known-pro-the-best-way-to-reach-your-audience

  159. using BBEdit. in reply to: http://aaronparecki.com/events/2015/03/19/1/indiewebcamp https://www.facebook.com/events/437461433068146/

    going to @IndieWebCamp Cambridge @MIT 2015-03-19..20! indie event: aaronparecki.com/events/2015/03/19/1/indiewebcamp silo: fb.com/events/437461433068146/

  160. using BBEdit. in reply to: http://aaronparecki.com/events/2015/03/17/1/socialwg-2015 https://www.facebook.com/events/444025702419735/

    going to @W3C Social Web WG meeting @MIT 2015-03-17..18 indie event aaronparecki.com/events/2015/03/17/1/socialwg-2015 silo fb.com/events/444025702419735/

  161. using BBEdit in reply to: https://twitter.com/todrobbins/status/572891051905572864

    @todrobbins @andyet big fan of talky.io, using it @indiewebcamp @W3C Social Web mtgs. Telecons still need POTS-compat.

  162. using BBEdit in reply to: http://tantek.com/2015/062/t2/broke-today-hangouts-touch-tones-refrigerator https://twitter.com/tylergillies/status/572887094764285953

    @tylergillies @Google Hangouts iOS app touch-tones started working again today = participated in @W3C @CSSWG telecon.

  163. using BBEdit

    Finished @CSS3UI edits for all (but one) open resolved and minor issues, and have requested that WG / @W3C publish it as a TR Working Draft: http://dev.w3.org/csswg/css-ui-3/

  164. using BBEdit

    Things that broke so far today * @Google Hangouts iOS app touch-tones = no joining W3C telcon * refrigerator (at home)

  165. using BBEdit

    ran Trackish Tuesday before dawn: 3x600 2x200 600 400 200 600 2x200 Then saw the sunrise. Going to need that today.