The current
h-entry change control process
does not specify how to update the definition of a proposed feature, which means it falls back to being as strict as updating a stable feature which is more strict that desired for proposals. This issue is for considering a proposal for updating the definition of a proposed feature, as discussed during the
recent Microformats Issue Resolution pop-up.
Proposal: the definition of a proposed feature may be updated to be more consistent with one or more real world public web sites publishing and or consuming the feature, by citing URLs for those examples in an edit summary. New proposed property or value definitions may also be added for consideration per the existing requirements for adding a proposed feature. If you’re not sure whether to update an existing definition or add a new definition, try to work with the proposer(s) of an existing definition to come to a consensus to update it. Lacking consensus, add a new definition for consideration, retaining any previous definition(s).
This proposal also adds a convergence requirement for moving a feature from proposed to draft. If there are multiple definitions for a proposed feature, an issue must be opened to discuss how to converge the definitions by consensus agreement among those with real world public web sites publishing and or implementations consuming the feature.
This is a rough first draft, feel free to propose alternatives, simplifications, editorial suggestions.
Runair is awesome! Would be great to give an explicit open source license like CC0 (preferred), or BSD, MIT, Apache etc. of your preference and mention it in README.md.
For example, the IndieWeb newBase60py library uses CC0: https://github.com/indieweb/newBase60py and you could copy this LICENSE file in its entirety https://github.com/indieweb/newBase60py/blob/master/LICENSE
@slightlylate sorry for your and all of our collective loss. Saw him at #W3CTPAC 2019. He was kind & welcoming to new folks @W3C (@CSSWG etc.); appreciated his contributions & conversations 💔
This issue is not the place to make pitches for use-cases.
While we (Mozilla) are definitely sympathetic to use-cases that help users, a better place to capture those is either on your own blog with blog posts, or perhaps as pull-requests to add them to the respective Explainer, e.g. in this case:
Better yet both, so you can fully express the use-cases yourself and then cite them with a brief summary in the Explainer.
On the specific medical use-cases provided, if anything these are great examples both in terms of greater potential harm to users, and more vulnerable infrastructure due to systemic IT process issues. Those are both good reasons to expose fewer potentially risky features, not more.
↳ In reply to @slbedard’s tweet@slbedard or a Shazam for #birdsong, showing both which bird(s) and map of where heard, with optional contribution of location, naturally with @SwarmApp checkin integration for the obvious birds & bees mashup, and Twitter to tweet your #twitching 🐦🎶
On GitHub, project team members are able to add labels to your issues on a project. If your issue is a POSSE copy of an original post on your site, Bridgy should backfeed these as "tag-of" responses to the original post. cc: @dshanske
This is similar to
issue #776
which is the same backfeed feature request but for Flickr.
This is also the “labeled” specific subfeature of
issue #833
which documents many more backfeed for GitHub requests.
And similar to
this comment on #811
(original post)
requesting Bridgy Publish untag-of support,
it’s worth considering Bridgy Backfeed untag-of support
(the “unlabeled” specific subfeature of #833),
so when someone removes a label from your issue, your original issue post is notified. However, the
brainstorming of how to markup untagging
is still ongoing, and thus may need to wait for more discussion before implementing.
There has been some past brainstorming about possible MIME types for the JSON resulting from a compliant microformats2 parsing implementation:
microformats2-mime-type.
It seems one in particular, application/mf2+json, has seen some adoption in the wild: https://indieweb.org/application/mf2+json.
Should we specify an explicit MIME type for the parsed JSON result of an mf2 parser? And if so, should we adopt application/mf2+json or some other alternative?
This feature is both a useful declarative presentational feature for web developers and one that formerly had a non-standard -moz prefixed value (-moz-hidden-unscrollable). Thus we should consider giving it an explicit status of "important".
* 17k+ #Berlin anti-mask/anti-vax protesters gathered without masks (#COVID19 surge coming) * "Day X" preppers infiltrate German state institutions (@kbennhold), like a real-life MCU Hydra * Ware State Prison riot * Murder Hornet trapped, <2 mo. to find their nest
Hey guys (yes, literally), and anyone in a position of power (management, leads) at Google, or any tech company, or any company, please read this thread by @EmilyKager:
2wks "virtual" @W3C F2Fs: Prev: MTW 06:00-09:30 @W3CAB, first as a returning AB member This: MT1-5p ThF7-11a @CSSWG Long Zoom/gMeet hrs, missed in-person time & break chats. Though I could reference 30yo typography books for ::first-letter issues, like The Elements of Typographic Style, and How to Spec Type.
We reject traditional "fast growth" capitalist narratives, and instead humbly encourage slow sustainable growth across numerous projects that interoperate with each other.
Longevity & dependability directly benefit the people participating, instead of shortterm excitement which typically only benefits investors (sometimes "serial" entrepreneurs).
Would love to chat more about these topics: https://chat.indieweb.org/ (There’s a Slack link there too to use Slack to join).
@solarpunk_girl still reflecting on https://twitter.com/solarpunk_girl/status/1261196542519672834, how to design modern multi-generational housing? E.g. with care-sharing & support as primary goals, and COVID persisting: create quarantine split levels/sections with separate BRs/BA. Healthy half could provide food etc. for those in quarantine. Would work both for traveler / suspected exposure quarantine (like many countries requiring 14 days), and confirmed cases recuperating. If there were both (suspected and confirmed cases), they would need to be split apart as well, both sections accessible for care-providing without intersecting the other. We need new architectures of local sustainable support for a post-pandemic world.
A month ago @moral_imagining, @solarpunk_girl asked us to write a #MoralImaginations continuation to The Impossible Train story.
* * *
Since the train stopped, we’ve seen so many odd, shocking, and inspiring things.
People outside their train cars protesting to be let back on to enjoy their window views and demanding their familiar entitlements served by others.
Tensions outside the train bringing rise to new & familiar tragedies, now more visible to all.
A pair of humans board a shiny new train to the sky, launch, and arrive at the sky station to much applause.
People from different train cars, witnessing tragedy on tragedy, declaring enough, band together in solidarity, confronting and witnessing more tragedies.
Reports arrive that despite the apparent stoppage, the train is still moving, slowly, and the upcoming cliff, still crumbling away.
Per DAS charter feedback:
Mozilla has significant concerns about the inclusion of the
Network Information API in the charter (as a specification to potentially
adopt from the WICG) — Mozilla's public position is that this API is
"harmful" to the Web as the information that it provides is unreliable and,
at the same time, open to privacy abuses. As we have
stated publicly,
we believe it is "better that sites use methods that dynamically adapt to
available bandwidth, as that is more accurate and likely to be applicable
in the moment". Or, alternatively, use newer declarative solutions, such as
"lazy loading" images and alike.
Per DAS charter feedback:
Where we already have an existing Web APIs, e.g., Orientation Sensor,
we would prefer the working group cease work on
those items and instead focus on evolving the existing specifications.
Per DAS charter feedback:
Where we already have an existing Web APIs, e.g., Geolocation Sensor,
we would prefer the working group cease work on
those items and instead focus on evolving the existing specifications.
As is
evident with the Geolocation API,
implementers have continued to
make significant privacy and security enhancements to existing APIs, and
those enhancements have made their way back to the W3C. As such, we feel
it's unnecessary to have duplicate specifications.
Per DAS charter feedback:
The Fold Angle specification should be
incubated in the WICG before it becomes a working group deliverable. For
Fold Angle, we'd also like to see closer collaboration and input from the
CSS WG on the design.
Having said that, we would be comfortable with having WICG incubated specs
being explicitly listed as charter work items that the working group could
adopt at a future date. However, we'd like to see them listed in a manner
similar to the
Web Apps WG Charter's section on WICG Specs (i.e.,
separated out of the main deliverables list for the working group).
Per DAS charter feedback:
We believe it would be prudent for the System WakeLock API to go through
the WICG process until it gets implementation commitment from at least a
second browser vendor.
Having said that, we would be comfortable with having WICG incubated specs
being explicitly listed as charter as work items the working group could
adopt at a future date. However, we'd like to see them listed in a manner
similar to the
Web Apps WG Charter's section on WICG Specs (i.e.,
separated out of the main deliverables list for the working group).
Per DAS charter feedback:
On the the grounds of privacy, and given a lack of implementer support, we
would like the Devices and Sensors Working Group to cease work on the Ambient light sensor API and see it published as a Working Group Note instead.
Per DAS charter feedback:
On the the grounds of privacy, and given a lack of implementer support, we
would like the Devices and Sensors Working Group to cease work on the Proximity sensor API and see it published as a Working Group Note instead.
Per DAS charter feedback:
On the the grounds of privacy, and given a lack of implementer support, we
would like the Devices and Sensors Working Group to cease work on the Battery API and see it published as a Working Group Note instead.
A week ago Saturday morning co-organizer
Chris Aldrich opened
IndieWebCamp West
and introduced the keynote speakers. After their inspiring talks he asked me to say a few words about changes we’re making in the IndieWeb community around organizing. This is an edited version of those words, rewritten for clarity and context. — Tantek
That was a change we deliberately made last year, announced at last year’s summit. It was well received, but it’s only one minor change.
Those of us that have organized and have been organizing our all-volunteer IndieWebCamps and other IndieWeb events have been thinking a lot about the events of the past few months, especially in the United States. We met the day before IndieWebCamp West and discussed our roles in the IndieWeb community and what can we do to to examine the structural barriers and systemic racism and or sexism that exists even in our own community. We have been asking, what can we do to explicitly dismantle those?
We have done a bunch of things. Rather, we as a community have improved things organically, in a distributed way, sharing with each other, rather than any explicit top-down directives. Some improvements are smaller, such as renaming things like whitelist & blacklist to allowlist & blocklist (though we had documented
blocklist since 2016, allowlist since this past January, and only added whitelist/blacklist as redirects afterwards).
Many of these changes have been part of larger quieter waves already happening in the technology and specifically open source and standards communities for quite some time. Waves of changes that are now much more glaringly obviously important to many more people than before. Choosing and changing terms to reinforce our intentions, not legacy systemic white supremacy.
Part of our role & responsibility as organizers (as anyone who has any power or authority, implied or explicit, in any organization or community), is to work to dismantle any aspect or institution or anything that contributes to white supremacy or to patriarchy, even in our own volunteer-based community.
We’re not going to get everything right. We’re going to make mistakes. An important part of the process is acknowledging when that happens, making corrections, and moving forward; keep listening and keep learning.
The most recent change we’ve made has to do with Organizers Meetups that we have been doing for several years, usually a half day logistics & community issues meeting the day before an IndieWebCamp. Or Organizers Summits a half day before our annual IndieWeb Summits; in 2019 that’s when we made that aforementioned update to our Code of Conduct to prioritize marginalized people’s safety.
Typically we have asked people to have some experience with organizing in order to participate in organizers meetups. Since the community actively helps anyone who wants to put in the work to become an organizer, and provides instructions, guidelines, and tips for successfully doing so, this seemed like a reasonable requirement. It also kept organizers meetups very focused on both pragmatic logistics, and dedicated time for continuous community improvement, learning from other events and our own IndieWebCamps, and improving future IndieWebCamps accordingly.
However, we must acknowledge that our community, like a lot of online, open communities, volunteer communities, unfortunately reflects a very privileged demographic. If you look at the photos from Homebrew Website Clubs, they’re mostly white individuals, mostly male, mostly apparently cis. Mostly white cis males. This does not represent the users of the Web. For that matter, it does not represent the demographics of the society we're in.
One of our ideals, I believe, is to better reflect in the IndieWeb community, both the demographic of everyone that uses the Web, and ideally, everyone in society.
While we don't expect to solve all the problems of the Web (or society) by ourselves, we believe we can take steps towards dismantling white supremacy and patriarchy where we encounter them.
One step we are taking, effective immediately, is making all of our organizers meetups forward-looking for those who want to organize a Homebrew Website Club or IndieWebCamp. We still suggest people have experience organizing. We also explicitly recognize that any kind of requirement of experience may serve to reinforce existing systemic biases that we have no interest in reinforcing.
We have
updated our Organizers page with a new statement of who should participate, our recognition of broader systemic inequalities, and an explicit:
… welcome to Organizers Meetups all individuals who identify as BIPOC, non-male, non-cis, or any marginalized identity, independent of any organizing experience.
This is one step. As organizers, we’re all open to listening, learning, and doing more work. That's something that we encourage everyone to adopt. We think this is an important aspect of maintaining a healthy community and frankly, just being the positive force that that we want the IndieWeb to be on the Web and hopefully for society as a whole.
If folks have questions, I or any other organizers are happy to answer them, either
in chat or privately, however anyone feels comfortable discussing these changes.
Currently meetable supports tag browsing pages like: https://events.indieweb.org/tag/hwc
However if you trim the last segment, you get a 404: https://events.indieweb.org/tag/ or https://events.indieweb.org/tag
Meetable should instead redirect those to: https://events.indieweb.org/tags
Additionally, Meetable should consider redirecting https://events.indieweb.org/tags/ with the trailing slash to https://events.indieweb.org/tags without the trailing slash instead of serving duplicate content at those two URLs.
GitHub pull requests accept reacji just like comments, issues, etc. But currently Bridgy seems to not recognize reacji in reply to a pull request review permalink like:
↳ In reply to Tantek’s note1776-07-04 Declaration of Ind. "life, liberty" [for white men only]^1. Via @aclu^2 1863-01-01 Emancipation Proclamation 1865-06-19 EP & Civil War end announced to TX enslaved 1865-12-06 13th amend
Why celebrate July 4 more than #Juneteenth when rights were declared for all, not only white men?
When I was last on the Advisory Board (AB), I asked W3C Management (W3M) to provide a report on diversity of W3C, and in 2018 gender & geographic barcharts over time were provided for the AB, TAG, and W3M:
For example, what percentage of the AB, TAG, and W3M are white?
As far as I know, these W3C leadership groups lack even a single Black individual.
How many (if any) are in the Advisory Committee as a whole?
If W3C truly represents the interests of world-wide web standards, it’s long past time to ask these and other uncomfortable questions about who holds positions of authority & power @W3C. We must have the courage to ask them, and keep asking them, and actively work to dismantle systemic biases.
↳ In reply to @solarpunk_girl’s tweet@solarpunk_girl really like this! Need to replace & move beyond violent metaphors for common activities. Working on a longer post on this.
↳ In reply to @solarpunk_girl’s tweet@solarpunk_girl yes! Gardening & farming are ripe with metaphors for #NewNarratives. Also considering sourcing from cooking, baking, and toolmaking. New story arcs for the #NewPossible. #DontGoBackToNormal
🌃🌳 March 28th, SF distancing day twelve. Spent the day inside (except to move my car) until leaving 10 minutes to midnight for a night run.
Started tracking at Frederick & Ashbury, an empty intersection, lights out except the corner 2nd floor apartment(1). Empty to the East as well, up to the dark trees of Buena Vista Park, outlined by a gray sky above(2). Continued onward to spell NO FEAR on the streets (https://tantek.com/t55q1).
There was so much fear As we started sheltering we felt safer and yet more lonely Venturing outside, it was so quiet Fewer cars, fewer machines making noises Even in the city, we heard nature’s sounds from the crows to the parrots We closed streets to cars, welcoming runners, hikers, bicyclists Without cars, without their noise & pollution, more animals wandered near us. Coyotes, birds, rabbits, squirrels Even red tailed hawks swooped near the ground, showing off the bright tops of their tailfeathers Strangers started to greet strangers, as they passed each other at a distance, Maybe a smile, a nod, a wave, a hello, perhaps a brief exchange of greetings, well wishes, introductions to pets Slowly, our sense of fear transformed into a sense of solidarity
First
published on 2014-05-12,
the newsletter started as a fully-automatically generated weekly summary of activity on the IndieWeb’s community wiki: a list of edited and new pages, followed by the full content of the new pages, and then the recent edit histories of pages changed that week.
Since then the Newsletter has grown to include photos from recent events, the list of upcoming events, recent posts about the IndieWeb syndicated to the IndieNews aggregator, new community members (and their User pages), and a greatly simplified design of new & changed pages.
Meetable events allow uploading images, both a banner for the event itself,
and photos of the event afterwards. There should be a setup feature to explicitly pick and set one or more required licenses for image uploads.
At a minimum, Meetable should allow choosing a Creative Commons license like Flickr does
(radio buttons), perhaps defaulting to a CC-BY-NC license like the Wikimedia upload default, to encourage compatibility with the broader Wikimedia commons,
so images uploaded to default Meetable installations can also be published to Wikimedia,
and to allow Wikimedia images to be used for Meetable event banners.
Maybe allow multi-licensing as well, e.g. picking more than one license (checkboxes),
so uploads are required to be multi-licensed.
Additionally, consider allowing a user to enter one or more license URLs,
so those setting up their own Meetable can choose other licenses beyond
a predefined set of Creative Commons licenses.
Yesterday I ran 2.23mi(1) in memory of #AhmaudArbery, who would have turned 26. He was shot on 2/23 for jogging while black. The video is horrifying. #BlackLivesMatter because how is this still happening in 2020. #IRunWithMaud
This weekend #RunWithMaud in solidarity. If you’re in SF, you can start at Haight & Ashbury, run up Ashbury until it merges with Clayton, turn up Twin Peaks Boulevard, and turn around a bit after the first major turn, before the hairpin turn(2,3), running back down to Haight & Ashbury to complete 2.23 miles.
↳ In reply to issue 6103 of GitHub project “browser-compat-data”From a strict interpretation, in the W3C at least, a specification must be at least a publicly published Working Draft (WD) by an active Working Group (WG) to be on an official "standards track", and thus that should be our condition for explicitly labeling a technology in a W3C document as "standards track".
At a minimum a specification must be accepted into a WG’s charter, and not just as a NOTE, in order to qualify to be standards track. However it’s not actually on that track (and citable as such) per se until the WG has agreed to publish it publicly as a WD.
By at least a WD, I’m explicitly saying yes it can also obviously be a Candidate Recommendation (CR), Proposed Recommendation (PR), or Recommendation (REC, or edited, or amended). If it’s an Obsolete Recommendation we should use the "Obsolete" label.
If it’s only in an Editor’s Draft or a WD (before a CR), that would be reasonable to label as "Experimental", as anything that’s not yet in a CR can "Expect behavior to change in the future."
If a document is for example only developed in a Community Group (CG) such as WICG, it is not standards track (CGs cannot make standards), and thus we should explicitly label any technologies there as "Non-standard", until such document makes its way into a WG and the WG publishes it as a WD, therefore publicly signaling that the WG has agreed to advance it onto the standards track.
For IETF and other orgs, I’ll let others chime in about what state a document must be in to transition between "non-standard" and "experimental" and "standards track", or "obsolete".
“The indie web” was a name given to the collective us that used and still uses our domains for our actively independent web presence, a practice Blogger FTP helped enable for many years, for many people. Our sites worked (were at least viewable) without requiring (truly independent of) another web site or service being actively up & running.
Blogger FTP was a nice-to-have, even if/when it was down, your site and permalinks were still browsable, and you could still manually FTP and edit your site, your blog, on whatever generic web hosting service you were using. You could migrate your blog by FTPing your static storage files from one web host to another. Without any database export/import/(re)configuration.
Subsequently of course https://indiewebcamp.com/ was founded, eventually (and currently) https://indieweb.org/, recognizing a pre-existing practice by naming it and giving it a community focus. A community to discover & find each other, to actively collaborate, building on each other’s ideas & building blocks, evolving our sites, innovating the practical peer-to-peer web with a plurality of approaches, designs, interoperable implementations, and sustainable solutions.
🏙🌳 March 27th, SF distancing day eleven. Midday run/walk up to Corona Heights for another clear view of downtowns, San Francisco and Oakland(1). Later that afternoon a trip to Cole Hardware, limited to 15 store customers at a time(2). Inside, purchase limits on bleach, soap, paper towels, and gloves(3).
👥📰 March 26th, SF distancing day ten. Longer line to get into Haight Street Market(1). The newspapers reported on the $2 trillion stimulus(2,3). The New York Times in particular noted that states have begun discouraging visitors from other states, or requiring them to stay in quarantine, e.g. for 14 days.
☁️🌊 March 25th, SF distancing day nine. Spent nearly the whole day inside, drove to the beach (when we were still allowed to) as the sun set. Made it just as the sun sank into the horizon, just an orange dot filtered by the clouds(2). Ocean Beach was nearly empty.
As I approached the shore, I saw numerous small dark shapes in motion where the waves lapped the sand. When I got closer I realized they were birds, hundreds of them(3). I’ve never seen so many birds flocking together at the beach. Something in the waves made them briefly take flight(4).
The wind had really picked up. Orange glow on the horizon where the sun had been, the wind strong enough to blow ripples in the millimeters deep water on the sand(5). Walking back, the wind paused for a moment, long enough for the wet sand to sit still and reflect the sky(1).
For a #NewPossible future, cc: @LondonBreed can SF do more of this?
* Immediately pass a coronavirus relief package now that provides emergency funding assistance to cover expenses to massively test the population in the millions and provide emergency food and shelter to all homeless and poor. * Provide a protection and testing plan for incarcerated people while in custody and upon release. * Expand SNAP and unemployment for the duration of the pandemic. * Immediately legislate fully paid sick leave for all workers. * Implement an immediate moratorium on evictions and utility shut-offs. * Emergency funding for family and community-based childcare for families who cannot work from home.
👥📰 March 24th, SF distancing day eight. New requirements announced by the city have been implemented, like limiting the number of people allowed into grocery stores, one in one out. Line down the block to get into Haight Street Market, people in line stayed about six feet apart even without explicit markings(1).
The day’s newspapers showed progress in some areas like testing(2), critiques (New York’s density enabled the virus, yet why haven’t denser cities worldwide had the same problems?), and premature considerations of lifting restrictions by the president and wall street executives(3,4).
🌸 March 23rd, SF distancing day seven. Had a nice afternoon run to the Conservatory of Flowers and back. The flowers in the gardens out front were in full bloom. One week of sheltering in place.
🌳🌇 March 22nd, SF distancing day six. Later run than usual, made it to Kezar Stadium just after sunset on a mostly clear day(1). That morning I picked up brunch to go from Zazie, including a complimentary bag of their buttermilk pancake mix(2). It had been a week since I’d celebrated my birthday there, so much had changed already.
“This virus has worked liked an MRI or like an X-Ray on societies & countries and exposed their barebones and exposed ... almost in the same way that it seems to prey on people with other illnessess, people with co-morbidities, it is doing the same with societies, it is expanding & amplifying all the weaknesses, all the injustices, all the racisms, all the castisms.”
“Right now what's happening is that national authoritarianism is colluding with international disaster capitalism and data gatherers and they are preparing another world for us.”
“For me writing is thinking. I write to think. It is almost like talking to myself. Sometimes the only reason I write is in order to not lose my sanity.”
“A lot of people think that democracy equals elections. And this is the stupidest thing that has happened to us. Elections are just one part of it. Sometimes I just look at it as vote for the enemy that you want to have.”
↳ In reply to @solarpunk_girl’s tweet@solarpunk_girl #moralimaginations are refreshing like our cleaner air, encouraging us to look farther, to distant views suddenly visible, and listen to new sounds, voices, ideas we can hear as the noises of broken systems subside. Thank you
🌁⛰🏙📰 March 21st, SF distancing day five. Ran up to Twin Peaks, North Peak, and South Peak for a clear view of Sutro tower, Mount Tam, the Golden Gate Bridge, downtown San Francisco, East Bay hills, and tiny container ships & the Grand Princess still idling on the bay(1).
There’s a third mini peak south of the two official Twin Peaks, with a beautiful field of poppies(2). At the time I’d stopped to admire the poppies on the inside of the hairpin turn up to Twin Peaks(tantek.com/t55h1). Afterwards a post-run stop at Haight Street Market for a coffee.
The day’s weekend Wall Street Journal had a photo of a nearly empty Times Square, a scene previously only imagined in disaster movies (and Vanilla Sky). The headline article described how 1 in 5 Americans were now under orders to limit their outside activity(3).
⛰🌁 March 20th, SF distancing day four. Ran up to Tank Hill for the clearest views. Distant sights like Mount Tam and the Marin Headlands had sharper outlines, and crisper more colorful features. Even the Golden Gate Bridge seemed to shine a brighter reddish orange(1).
To the Southeast, a clear view of the bay itself, including tiny tankers, cargo ships, and the white outline of the idling Grand Princess cruise ship parked in the bay, behind bright views of city neighborhoods(2). Only a couple of others were up at Tank Hill park that day, observing distancing requirements in addition to the views(3).
Stopped by Haight Street Market for more supplies, noticed that they had suspended all self-serve food options(4), including their delicious soups(5). The cafe’s tip jar choices reflected reactions to only a few days of sheltering at home(6).
The day before (Thursday) the Governor of California had essentially replicated Monday’s San Francisco shelter-in-place order for the entire state, the first state to do so, which the Chronicle reported in large type(7).
The New York Times exclaimed in all caps: DOCTORS SOUND ALARM AS A NATION STRUGGLES above a map of the United States, with numbers of cases and proportionate red circles(8). Later that day, Connecticut, Illinois, and New York states issued their own shelter-in-place orders.
It would take two more weeks for most other states to follow suit.
March 19th, SF distancing day three. First run since my 50-miler. I had rested my legs, only brief walks for a few days, then longer walks, up & down hills. When that felt completely fine, I decided to try an easy run. First up to Buena Vista Park where the poppies were in full bloom(1), then over to Corona Heights Park, where the clean air provided very clear views of downtown San Francisco, and across the bay to Oakland too(2)!
Finished my run with a coffee from Haight Street Market, where they had just changed store hours to close earlier for sanitizing, and limited the first hour of opening to those 60+ years old and Instacart workers(3).
Scanning the newspapers while waiting for my coffee, the day’s headlines captured only a few concerns & fears(4,5,6).
As a visual palate cleanser after those headlines, here’s my almond latte in a paper cup(7), since they stopped serving in reusable cups two days ago (tantek.com/t5661).
