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:
1776-07-04 Declaration of Ind. "life, liberty" [for white men only]¹. Via @aclu² 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.
@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.
@solarpunk_girl good questions; been pondering these and others since last Friday’s @moral_imagining. Urban planning & home architecture implications, autonomy vs community, evolution vs resilience. Some history/analyses: https://www.theatlantic.com/magazine/archive/2020/03/the-nuclear-family-was-a-mistake/605536/ One thought: upgrading homes to support multi-generational configurations may be a good distributed return, actionable without requiring coordination, yet mutually beneficial among incrementally participating families.
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.
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.