↪ In reply to @meyerweb’s tweet@meyerweb even better — perhaps the (subconscious) genius of it! Knowing (feeling?) that undohtml did not meaningfully convey its actual usefulness, then naturally (re)naming even the idea to something shorter, more memorable & easily (re)teachable, thus actually helping more people.
Finished Hot Chocolate 15k #HC15k in 2:05:25. 2 mile warm-up to the start with running pal Michele. We started with a slow run, switched to a run-walk after ~5k, then walked to the finish. Neither of us really trained for the #HotChocolate15k, so we took it easy, kept a conversational pace. Grateful for a beautiful day in the sun, running through the park and along the beach.
↪ In reply to @SmugMug’s tweet@SmugMug Also looking forward! Minor nit, seems @Flickr went down last night as payment processed, didn’t complete. Retried FLICKRPRO15, got "Invalid coupon code". Email on 7th said: "Use offer code FLICKRPRO15 at checkout. Offer expires January 15, 2019."
Flickr already has the best API of any photo site, and thus has the best Brid.gy support for IndieWeb sites wanting to syndicate to Flickr, and backfeed responses.
I have more positive thoughts about @Flickr’s future potential with its new owners, especially with respect to even better IndieWeb integration. More on that later. For now, see the additional research and links being collected and documented by the IndieWeb Community:
where one (or more) of the reply-to URLs is to a Flickr permalink post (likely others's photos, but could be my own that I'm adding tags to after I published it), Bridgy Publish (of my tag reply) should propagate that tag reply to that Flickr permalink.
This is the publish equivalent of the following backfeed features, and may be easier to start with (consider implementing publish before implementing backfeed for equivalent interaction)
December 1st (5 weeks ago today), I baked my first pie (1) and got 2nd best sweet pie in a friendly bake-off!
Using an apple pie recipe from the web, I peeled & chopped apples(3), squeezed a lemon & added flour, sugar, cinnamon(4), and mixed it(5). Buttered & pressed dough into a pie plate(6), filled and dotted it with butter(7). Covered & cut slits(8), glazed(9), and baked it(10).
I placed the still hot pie on a cork trivet, slid it carefully into a sideways brown paper bag, and let it cool en route to the bake-off. Cut slices, still warm, and shared.
🌴🌇🌘 dark clear & cold (42F) #predawn skies after #NPSF. Always impressed with the 05:30 crew (was a few min late) and especially grateful to Ali for leading all three workouts. 2nd 📷 in-between early/abs and 06:30 workouts. #wakeupthesun #fromwhereIrun #run #runner #runners #NovemberProject #earlygang #doublegang #dawn #sunrise #SanFrancisco #SF #palmtree #skyline #nofilter
🌳🌧🌊 December 1st, 24hrs later. It’s not always sunshine & rainbows, sometimes it’s rain & puddles. A week after 55k, stretched my legs at #SFRC to Tennessee beach & back. Grateful for a wet yet smooth 7.6 miles and a few segment PRs.
🌇 November 30th, six days after I ran 55k*, waking up with #NPSF Friday hills at the 22nd Street Jungle Stairs to cotton candy skies on fire. That evening, a seagull friend on the ledge at dusk, disappearing sunset beams glistening off East Bay windows and distant tops of Bay Bridge towers. Lastly, the N Judah MUNI rush hour commute home, passengers losing it, running into an assertive woman asking everyone to squeeze in to make more room, who turned out to be my friend Stephanie.
Goodnight 2018. Many ups and many unexpected downs. New highs despite unexpected battles and losses. Still, finishing the year stronger, fitter, more understanding, more at peace. Appropriate to wake up this 365th day before dawn, work out til sunrise with #NPSF friends, pack in a full day, then drive off into the sunset.
No objections in above discussion, and positive opinions (👍) from a few implementors on the proposal. Proposal text incorporated into spec and reviewed.
Proposal implementation in mf2py parser, test cases provided, and Brid.gy verification that mf2py implementation satisfies use-case for the issue is sufficient to demonstrate implementability and utility, all as noted/linked in issue thread.
Edited specification accordingly. Thanks everyone for all the hard work on this one! Took a while but I think it was worth it to get it just right.
December was too busy to post. A few days: 1 7.6mi rainy trail run(tantek.com/t4yH3); baked my first (apple) pie(tantek.com/t4yM1) 3 returned to Orlando 3 yrs later, differently optimistic, packed lighter 9 first Sunday SFRC trail run 10 reframed W3C "agenda bashing" to "agenda gardening" 11 completed 2nd 8-week yoga philosophy study course 15 XFN 15th anniversary, rel=me keeps growing (Mastodon etc.) 16 baked my first triple chocolate chip cookies 18 back to Tuesday track 21 misty Dipsea trail run to Cardiac and back 25 baked my first gluten free pie (also apple) 26 did double-NPSF workout
Individual posts (most with photos) when time permits.
Donate/renew NOW for 2018+2019 for 2-3x match and keep funding science ! Why:
Why you must act TODAY (everyone)
Several of the above charitable organizations have matching donations that will increase your donation 2-3x IF you donate by end of day TODAY 2018-12-31 US Timezones.
See the 2x/3x next to the @-names for which organizations and how much.
Why you must act TODAY (US friends)
It’s the last day of 2018. By donating today, you may be able to itemize your donations and deduct them from your 2018 Federal taxes (IANAA, talk to your accountant regarding itemizing vs using the standard deduction).
You can donate to all of these organizations online and get an email receipt in minutes (I confirmed this by donating/renewing all the above personally).
See each Twitter profile above for their site/donation URLs.
When posting positive things promptly*, I think it first makes sense to post positive things from that day (for reason 6**), and then from previous days (that week, or month), in pure date-time order (oldest to newest), regardless of subject (topic) or type of post (e.g. text note vs. photo).
Subject-focused or clustered may make it easier to think/write about all posts for one topic at once (less context switching). However sometimes you don’t know the subject(s) of a post until you’ve actually written it, which means you have to finish at least drafts for posts before you can actually successfully categorize and cluster them, which seems like a lot more work (finishing all drafts before posting one) than just finishing/publishing one post at a time.
Using the date-time (of when that positive thing happened that you’re posting about), has the following advantages over clustering by subject:
* easier to get started: because "date" has an objective (don’t need to think about it) absolute answer that makes it easy to sort your drafts and just start posting them in date order (oldest first within some reasonable timeframe like, in the past week, or in the past month).
* easier to post incrementally, and pause / resume posting: since your "index" is linear (time), you can choose a date / point in time to pause, and later pick-up at whatever date you left-off, no need to think about what subjects did you already posted and what subjects are remaining.
Another consideration for publishing older posts is whether to post different types of posts before others, like text notes vs. photos vs. longer blog posts, or just interleave different post types all by date.
If one type of content had a particular workflow, like editing photos, it could make sense to cluster publishing those. However even photos have captions to write which are similar enough to text notes. Blog posts often open with a featured photo. It almost seems like more work to try to distinguish different types (as an author), than just post in date order, and add aspects to the content, text, photo(s), as they make sense for the post. Publishing them all in date-time order seems the simplest approach.
No objections in above discussion, and positive opinions (👍) from a few implementors on the proposal.
Proposal implementations in mf2py and phpmf2 parsers, and https://github.com/dshanske verification that phpmf2 implementation satisfies use-case for the issue is sufficient to demonstrate implementability and utility, all as noted/linked in issue thread.
In this case, “author - including compat root vcard in the absence of h-card” means to look for an “author” class name, *including* looking for a “vcard” class name on the same element, only if there is no “h-card” class name on the same element.
Thus yes, according to the spec, the code snippet:
<span class="author">Tom Morris</span>
Inside an hentry as noted above must be treated like:
<span class="p-author">Tom Morris</span>
And thus in the parsed JSON it becomes a simple "author": ["Tom Morris"] as noted as a “preferable result”.
If you can suggest wording that would help clarify this in the spec, I would be happy to make an editorial change to make this more explicitly clear (as well as similar for h-event location).
1. Stronger reinforcement of positive behaviors. The sooner you post about having finished something positive, the stronger such a positive self-affirmation will reinforce that positive action or habit.
2. Use recency bias for good. Part of recency bias is treating things that happened more recently as more important than things that happened less recently. Thus by promptly (rather than later) posting about a positive thing, it’s seen as more important than if you wait to post about it.
3. Make positive waves sooner. The sooner you post something positive, especially about something positive, the sooner others may see and be inspired by your example to say and do positive things, inspire others, in a likely compounding domino effect of positivity.
4. Beat future negativity. By publishing sooner and getting your positive post out there, you may be doing so before something bad happens in the future that you may have to deal with instead.
5. Details are better sooner. The sooner you can post about positive things that you personally observed or especially participated in (actions, events, accomplishments), the more details you will remember, and the more you reinforce your own short-term (then longterm) memory of the thing! Since that value decreases as the time since the thing happened increases, post the about the most recent thing first to get the details down, the the next most recent thing etc.
(more promptly posted as a note, perhaps worth expanding into an article with citations)
Last year I completed 100 Days of Positive Posts #100DoPP.^1 This year I started 100 Days of Positive Doing Posting Days #100PDPD and stopped after 8 days.^2 Missing from both of those was why. Why post positive things? Why may be insufficient to motivate, which implies a drive to action. More motivating: why post positive things promptly?