Tantek Çelik

Inventor, writer, teacher, runner, coder, more.

💬 👏
  1. As announced over a week ago, @Mozilla had a “significant reduction in our workforce by approximately 250 people” https://blog.mozilla.org/blog/2020/08/11/changing-world-changing-mozilla/

    See https://talentdirectory.mozilla.org/ and #MozillaLifeBoat for amazing people.

    I worked directly with many of these individuals and am sad to see them go.

    I’ve ignored my LinkedIn for many years; will be logging in to connect with Mozillians, and helping to make introductions.

    Previously: https://tantek.com/2020/015/t1/mozilla-roles-mozillalifeboat

  2. ↳ In reply to issue 336 of GitHub project “standards-positions” In response to (most of) the continued commentary here.

    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.

  3. I’m sorry this happened Yan :(

    I know @bcrypt and trust her. Read the images.

  4. ↳ 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 🐦🎶

  5. #TechIsNotNeutral. Laws SHOULD NOT mandate specific technologies (certainly #notBlockchain) nor unproven standards.

    @Mozilla blog:
     By embracing #blockchain, a California bill takes the wrong step forward: https://blog.mozilla.org/netpolicy/2020/08/06/by-embracing-blockchain-a-california-bill-takes-the-wrong-step-forward/


  6. RSVP yes to: an IndieWeb event going to part of the IndieAuth Pop-up Session
    🗓 9:30-11:30am PDT, Sat 8/8
    🎟 RSVP: https://events.indieweb.org/2020/08/indieauth-1-1-identity-protocol-standards-session-6xlxgeCEMgv8

    #IndieAuth is the most implemented decentralized #identity #protocol, built on #OAuth 2.

    #IndieWeb #OpenWeb #WebIdentity
    #noBlockchain needed

  7. New issue on GitHub project “bridgy”

    backfeed GitHub labels on your issues

    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

    Bridgy Publish already supports POSSEing tag-of posts in reply to GitHub issues, as labels on those issues, and this is the backfeed counterpart. Brainstormed here: https://indieweb.org/tag-reply#How_to_post_a_tag-reply.

    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.

    Label: backfeed.

  8. New issue on GitHub project “microformats2-parsing”

    Should we specify a MIME type / Content-Type for canonical JSON from parsed mf2?

    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?

    Labels: enhancement, question, needs proposed resolution.

  9. New issue on GitHub project “standards-positions”

    CSS Overflow 3: overflow:clip

    Request for Mozilla Position on an Emerging Web Specification

    • Specification Title: CSS Overflow Module Level 3: overflow:clip
    • Specification or proposal URL: https://drafts.csswg.org/css-overflow-3/#valdef-overflow-clip
    • Caniuse.com URL (optional):
    • MDN (optional): https://developer.mozilla.org/en-US/docs/Web/CSS/overflow
    • Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1531609
    • Mozillians who can provide input (optional): @emilio, @heycam
    • W3C Tag Design Review issue: none

    Other information

    This value has recently been implemented in Nightly: overflow:clip (as announced yesterday).

    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".

    Label: w3c.

  10. New issue on GitHub project “standards-positions”

    CSS Images 4: cross-fade()

    Request for Mozilla Position on an Emerging Web Specification

    • Specification Title: CSS Image Values and Replaced Content Module Level 4: cross-fade()
    • Specification or proposal URL: https://drafts.csswg.org/css-images-4/#cross-fade-function
    • Caniuse.com URL (optional):
    • MDN (optional): https://developer.mozilla.org/en-US/docs/Web/CSS/cross-fade
    • Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=546052
    • Mozillians who can provide input (optional): @dholbert, @heycam
    • W3C Tag Design Review issue: none

    Other information

    This function has recently been implemented in Nightly: cross-fade() (as announced yesterday).

    This is a useful declarative presentational feature for web developers, and thus we should consider giving it an explicit status of "important".

    Label: w3c.

  11. Looking forward to 2021, when 2020 will finally be hindsight.

  12. * 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

    Welcome to August.

    Berlin anti-mask/anti-vax protests:
    * https://in.reuters.com/article/germany-protests-idINKBN24X3SC
    * https://www.bbc.com/news/world-europe-53622797

    "Day X" thread and article:
    * https://twitter.com/kbennhold/status/1289568828691746816
    * https://www.nytimes.com/2020/08/01/world/europe/germany-nazi-infiltration.html

    Ware State Prison riot:
    * https://www.ajc.com/news/breaking-violent-riot-reported-at-south-georgia-prison/3EISC6BDTZBRHI7YATPM3HPPNU/

    Murder Hornet trapped:
    * https://www.npr.org/2020/08/01/898173003/researchers-in-washington-state-have-trapped-their-first-murder-hornet

  13. 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:

    Content warning: domestic violence, images


  14. 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.

  15. Thoughts with Portland friends, and implications.
    Watching indicators:
    * # cities DHS Operation Legend
    * # kidnapped from protests, streets
    * dystopia phrases like “proactively arrest”
    * USPS delays, defunding
    * swing state outbreaks
    * novel voter disenfranchisements
    * “resignations” of or “retiring” US generals
    * border closures
    * airport closures

    Some links:

    “Operation Legend”:
    * https://www.politico.com/news/2020/07/21/trump-federal-force-cities-377273
    * https://en.wikipedia.org/wiki/Operation_Legend

    People kidnapped from protests, streets:
    * https://www.portlandmercury.com/blogtown/2020/07/20/28659148/what-to-do-if-youre-kidnapped-by-federal-officers-while-protesting
    * https://twitter.com/matcha_chai/status/1283328232033411072
    * https://www.wweek.com/news/2020/07/17/federal-officers-appear-to-be-using-rental-cars-from-enterprise-to-snatch-portland-protesters/

    Dystopia phrases, especially from police/military dystopias:
    * https://www.newsweek.com/portland-federal-agents-minority-report-1519574

    * https://www.npr.org/2020/07/23/894794250/critics-say-changes-to-usps-may-completely-transform-the-post-office
    * https://fortune.com/2020/07/24/usps-mail-delivery-postmaster-general-louis-dejoy-us-postal-service/
    * https://www.commondreams.org/news/2020/07/22/maine-letter-carriers-allege-usps-leadership-willfully-delaying-mail-sabotage-postal
    * https://www.vox.com/21328220/senate-democrats-usps-vote-by-mail

    Novel voter disenfranchisements:
    * https://americanindependent.com/texas-gop-electoral-college-rig-elections-popular-vote-senate/

  16. 👍 to a comment on issue 334 of GitHub project “w3process”

  17. ↳ In reply to @b_cavello’s tweet @b_cavello, been reflecting. "immunity" not the goal. "#decentralisation" has been colonized by #blockchain snakeoil

    * agency+community instead of corp dominance
    * humble interop, choices, direct practices
    Like end of tweet #IndieWeb post links
    which allow us to write and post more on our own sites,
    and link to more resources like:
    * https://indieweb.org/principles
    * https://indieweb.org/why
    * https://indieweb.org/start

    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).

  18. Good #IndieWeb reminder from @brentsimmons: https://inessential.com/2020/07/15/zillion_times_easier (https://twitter.com/brentsimmons/status/1283534944493502470)

    And #BlueChecks appear to be frozen, unable to tweet, only retweet.

    So of course this exists: @EveryWord

  19. #TwitterHacked. What she said https://twitter.com/AOC/status/1283513914597298178 via @b_cavello

    Y’all know:
    #Bitcoin is a coal-burning CO2 producing currency for organized crime
    #blockchain is mostly #dweb snakeoil (singleton, OSS monoculture)

    Go #IndieWeb or SSB for the real: https://indieweb.org/

  20. @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.

  21. New issue on GitHub project “standards-positions”

    Media Queries Level 5: prefers-reduced-motion, prefers-contrast, prefers-color-scheme

    Request for Mozilla Position on an Emerging Web Specification

    • Specification Title: Media Queries Level 5: User Preference Media Features
    • Specification or proposal URL: https://drafts.csswg.org/mediaqueries-5/#prefers-reduced-motion
    • Specification or proposal URL: https://drafts.csswg.org/mediaqueries-5/#prefers-contrast
    • Specification or proposal URL: https://drafts.csswg.org/mediaqueries-5/#prefers-color-scheme
    • Caniuse.com URL (optional):
    • Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1365045
    • Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1506364
    • Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1494034
    • Mozillians who can provide input (optional): @heycam, @dbaron
    • W3C Tag Design Review issue: none

    Other information

    This issue is scoped to three of the new features in Media Queries Level 5, which we have implemented, as part of evaluating Media Queries Level 5 as a whole: prefers-reduced-motion, prefers-color-scheme, and most recently, prefers-contrast (as announced last week).

    These features enhance accessibility features of the platform and thus we should consider a status of "important" for these three as a whole.

    Label: w3c.

  22. New issue on GitHub project “standards-positions”

    CSS Media Queries Level 5

    Request for Mozilla Position on an Emerging Web Specification

    • Specification Title: Media Queries Level 5
    • Specification or proposal URL: https://drafts.csswg.org/mediaqueries-5/
    • Caniuse.com URL (optional):
    • Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1434491
    • Mozillians who can provide input (optional): @heycam, @dbaron
    • W3C Tag Design Review issue: none

    Other information

    We have implemented several of the features in Media Queries Level 5: prefers-reduced-motion, prefers-color-scheme, and most recently, prefers-contrast (as announced Monday).

    In general Media Queries Level 5 has several accessibility enhancing features and thus we should consider an overall status of "important".

    Label: w3c.

  23. New issue on GitHub project “standards-positions”

    HTML: dialog element

    Request for Mozilla Position on an Emerging Web Specification

    • Specification Title: HTML: The dialog element
    • Specification or proposal URL: https://html.spec.whatwg.org/multipage/interactive-elements.html#the-dialog-element
    • Caniuse.com URL (optional): https://caniuse.com/dialog
    • Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=840640
    • Mozillians who can provide input (optional): @annevk, @dbaron
    • W3C Tag Design Review issue: none

    Other information

    We have implemented the HTML dialog element in Nightly (announced Monday), with a few caveats as described in Bugzilla 1645046.

    Along with inert (#174), this seems worthy of recording as "worth prototyping".

    Label: whatwg.

  24. RSVP yes to: an IndieWeb event hosted Homebrew Website Club West Coast tonight:
    Discussed many topics: proposed h-entry p-content-warning property https://github.com/microformats/h-entry/issues/19, IndieAuth test suite, UX personas roles as a way to update https://indieweb.org/generations, and more

  25. RSVP yes to: an IndieWeb event went to Homebrew Website Club London:
    Great chatting with folks about rethinking person-tagging public photos (now considered harmful), and discussed #IndieWeb Organizers & Organizing blog post: https://tantek.com/2020/187/b1/changes-indieweb-organizing-indiewebcamp-west

  26. 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.

    * * *

  27. New issue on GitHub project “dap-charter”

    DASWG: Drop Network Information API because it is harmful to the web

    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.

    cc: @dwsinger @pes10k @marcoscaceres

  28. New issue on GitHub project “dap-charter”

    DASWG: Drop Orientation Sensor in favor of existing APIs

    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.

    cc: @dwsinger @pes10k @marcoscaceres

  29. New issue on GitHub project “dap-charter”

    DASWG: Drop Geolocation Sensor in favor of existing APIs

    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.

    cc: @dwsinger @pes10k @marcoscaceres

  30. New issue on GitHub project “dap-charter”

    DASWG: Leave Fold Angle in WICG for now and collaborate with CSS

    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).

    cc: @dwsinger @pes10k @marcoscaceres @torgo @dbaron

  31. New issue on GitHub project “dap-charter”

    DASWG: Leave System WakeLock API in WICG until there is a second implementer

    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).

    cc: @dwsinger @pes10k @marcoscaceres

  32. New issue on GitHub project “dap-charter”

    DASWG: Drop Ambient light sensor API for privacy and lack of implementer support

    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.

    cc: @dwsinger @pes10k @marcoscaceres

  33. New issue on GitHub project “dap-charter”

    DASWG: Drop Proximity sensor API for privacy and lack of implementer support

    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.

    cc: @dwsinger @pes10k @marcoscaceres

  34. New issue on GitHub project “dap-charter”

    DASWG: Drop Battery API for privacy and lack of implementer support

    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.

    cc: @dwsinger @pes10k @marcoscaceres

  35. Changes To IndieWeb Organizing, Brief Words At IndieWebCamp West

    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

    Chris mentioned that one of his favorite parts of our code of conduct is that we prioritize marginalized people’s safety above privileged folks’s comfort.

    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.

    Thanks. — Tantek

  36. New issue on GitHub project “Meetable”

    Meetable should redirect /tag to /tags

    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.

  37. RSVP yes to: an IndieWeb event hosting Homebrew Website Club West Coast NOW!
    🗓 started at 18:00, seven of us here, hop on Zoom and say hi!
    @brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @indirect @generativist @BenWerd @pvh @aaronpk

  38. 👍 to a comment on pull request 143 to GitHub project “PWETF”

  39. 👍 to a comment on pull request 143 to GitHub project “PWETF”

  40. 👍 to a review on pull request 143 to GitHub project “PWETF”

  41. New issue on GitHub project “bridgy”

    Bridgy Publish: Support reacji to pull request reviews

    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:


    And returned this error:

    2020-06-30 20:05:17.817455 Please remove the fragment #pullrequestreview-440206392 from your in-reply-to URL.

    Expected result: apply the reacji to the pull request review.

    Label: publish.

  42. 👍 to a comment on pull request 143 to GitHub project “PWETF”

  43. RSVP yes to: an IndieWeb event going to IndieWebCamp West this weekend!
    🗓 9am-6pm both Sat & Sun
    🎟 RSVP & more https://2020.indieweb.org/west
    ✉️ Join us for keynotes, and pop-in for sessions thru the weekend!
    @brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @BenWerd @indirect @generativist @pvh @chrisaldrich

  44. RSVP yes to: an IndieWeb event going to IndieWebCamp West - Eat Your Own Cooking Pre-Party!
    🗓 8-10pm Friday!
    🎟 Details: https://events.indieweb.org/2020/06/indiewebcamp-west-eat-your-own-cooking-pre-party-DH5F8SRjSHff
    ✉️ Join us from your dining table, coffee table etc!
    @brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @BenWerd @indirect @generativist @pvh @chrisaldrich

  45. ↳ In reply to @brb_irl’s tweet @brb_irl looking forward to it!

    Also join us @IndieWebCamp West this weekend! https://2020.indieweb.org/west

    and Friday pre-party: https://events.indieweb.org/2020/06/indiewebcamp-west-eat-your-own-cooking-pre-party-DH5F8SRjSHff
    @generativist HWC West is weekly! Add a repeating event, or subscribe: https://events.indieweb.org/tag/sanfrancisco

  46. RSVP yes to: an IndieWeb event hosting Homebrew Website Club West Coast NOW!
    🗓 18:00 today
    🎟 RSVP & more: https://events.indieweb.org/2020/06/homebrew-website-club-west-coast-nR8FpEvMNsh5
    ✉️ Join us on Zoom! @brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @indirect @generativist @BenWerd @pvh @chrisaldrich

  47. ↳ In reply to Tantek’s note 1776-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?

    ^1 https://en.wikipedia.org/wiki/United_States_Declaration_of_Independence#Slavery_and_the_Declaration
    ^2 https://twitter.com/ACLU/status/1273944617600184320

  48. Yesterday was #Juneteenth, a holiday I hadn’t heard of before this June. Read a bit https://en.wikipedia.org/wiki/Juneteenth
    Grateful @Mozilla closed that day.

    Thanks @GavinNewsom https://twitter.com/CAgovernor/status/1274043072045813760
    Please make it an official paid state holiday like TX VA NY PA (per Wikipedia).


  49. ↳ In reply to @w3cdevs’s tweet @w3cdevs @mozilla Thanks @frivoal @TzviyaSiegman! Honored to rejoin you @W3CAB with Tatsuya Igarashi, @daithesong, @fantasai, Avneesh Singh, Eric Siow, @LeonieWatson, @cwilso, & Judy Zhu.
    Auspicious times. Protests worldwide declare Black Lives Matter; as elected leaders we must ask uncomfortable questions about privilege & institutional biases @W3C.

    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:


    We must provide more details and do better.

    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.

  50. Stencil street art of George Floyd on a red wall with the word JUSTICE above his head, and FOR GEORGE below.Stencil street art of George Floyd on a gray wall with the word JUSTICE above his head, and FOR GEORGE below. Two of the dried drippings of gray paint appear as if they are tears coming from his right eye.Justice For George.

    Yesterday on Haight street, artist unknown.

    #GeorgeFloyd #SayHisName #JusticeForGeorge #BlackLivesMatter #laterGram #20200531 #2020_152 #noFilter

  51. ↳ 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.

    Another idea, playing on stone:

    “Feeding two birds with one stonefruit”

    Summer is coming. #moralimaginations

  52. Ten years ago today I started working with Mozilla on #webStandards.


    Still @Mozilla (now @W3C AC Rep), still working for a more #OpenWeb, and for an #IndieWeb that puts users in control instead of #BigTech.

  53. There are systems of division, dominance, extraction, & growth, and systems of solidarity, community, stewardship, & sustainability.

    Each has metaphors & narratives, in everyday language & framing.

    Which systems shape your thoughts, words, and actions?

  54. ↳ 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

  55. Intersection of Frederick and Ashbury streets at night, looking westward, everything is dark except for streetlamps, lights outside a boarded up Ashbury Market, and a second floor corner apartment on the other side, above a lit bus stop for the number 6 outbound bus.Intersection of Frederick and Downey streets at night, looking eastward, everything is dark except the aforemention things at Frederick and Ashbury, the trees of Buena Vista Park are very dark, outlined by the gray sky above them.🌃🌳 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).

    #run #runner #AshburyHeights #FrederickStreet #night #nightrun #midnight #darkness #empty #ShelterInPlace #COVID19 #CoronaVirus #SFdistancing #SF #SanFrancisco #optOutside #fromWhereIRun #NeverStopExploring #InstaRunner #2020_088 #20200328 #laterGram #noFilter

  56. Yesterday @moral_imagining, @solarpunk_girl asked us to tell a story of this time, from the future. I wrote this (edited)

    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

  57. ↳ In reply to @BarackObama’s tweet ▶ watched President @BarackObama’s Message to the #ClassOf2020

     1. Don’t be afraid
     2. Do what you think is right
     3. Build the communty

     Leave behind old ways of thinking that divide us.


  58. 🎂 This Week in the IndieWeb celebrates six years of weekly newsletters! 🎉

    This week (no pun intended), the IndieWeb community’s “This Week in the IndieWeb” turned 6!

    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.

    You can subscribe to the newsletter via email, RSS, or h-feed in your favorite Reader.

    This week we also celebrated:

    See the Timeline page for more significant events in IndieWeb community history.

  59. New issue on GitHub project “Meetable”

    Meetable should set a license for image uploads

    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.

  60. ↳ In reply to @solarpunk_girl’s tweet @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.

  61. Strava map showing a roundtrip running route in red from Haight Ashbury to near a hairpin turn on Twin Peaks and back.Hazy sky over a view of downtown San Francisco, Buena Vista park with dark green trees, and a row of bushes in the foreground.View of Mount Tam in the distance, Marin Headlands in front of it, the Golden Gate Bridge, the Presidio hills, trees close by, and the roofs of houses near by, some with solar panels on top.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.

    More: https://en.wikipedia.org/wiki/Shooting_of_Ahmaud_Arbery

  62. ↳ 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".

  63. RSVP yes to: an IndieWeb event going to ONLINE Homebrew Website Club West Coast
    🗓 18:00 today, now weekly!
    🎟 RSVP & more: https://events.indieweb.org/2020/05/online-homebrew-website-club-west-coast-GX4yAV3eoPwh
    ✉️ Join us! @brb_irl @Kongaloosh @AllAboutGeorge @JackyAlcine @AndiGalpern @indirect @generativist @BenWerd @pvh @JohnMattDavis @html5cat

  64. I’m running for @W3CAB (The @W3C Advisory Board), one of eight candidates for five seats: https://twitter.com/w3cdevs/status/1257294597530755072
    Official statement: https://www.w3.org/2020/05/04-ab-nominations.html#tc
    Blog post to follow!

  65. Ten years ago the death of Blogger FTP two days before inspired introducing “the indie web” as a definite noun phrase:
    > Blogger turned off FTP May 1st [2010] Who/what will step up for the indie web?
    http://tantek.com/2010/123/t2/blogger-turned-off-ftp-what-indie-web-diso (https://twitter.com/t/status/13329370781)

    “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.

  66. Support essential workers:
    * Reduce or stop purchases from Amazon, Fedex, Instacart, Shipt, Target, Walmart, Whole Foods
    * Don’t cross the picket line
    Until workers get:
    * PPE
    * hazard pay
    * paid sick leave
    * healthcare for all
    More about #MayDay2020:

  67. Midday view from the top of Corona Heights Park of downtown San Francisco on a sunny day, scattered white clouds on a blue sky, clear views of East Bay hills, downtown Oakland, the bay, and trees & dirt paths of Corona Heights Park below.Sign in front of a store entrance with text TO HELP CURBE THE SPREAD OF COVID-19, WE ARE LIMITING THE NUMBER OF SHOPPERS IN THE STORE TO 15 AT A TIME. THANK YOU, THE COLE VALLEY HARDWARE STAFF.Shelves with Clorox bleach, Scott rags, under a sign stating limit 2 per customer, gloves limit 1 per customer, other cleaning supplies below.🏙🌳 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).

    #run #runner #CoronaHeights #CoronaHeightsPark #ColeHardware #bleach #limit2perCustomer #limit1perCustomer #sign #ShelterInPlace #COVID19 #CoronaVirus #SFdistancing #SF #SanFrancisco #optOutside #fromWhereIRun #NeverStopExploring #InstaRunner #2020_087 #20200327 #laterGram #noFilter

  68. Line of people on the sidewalk on Haight street, about six feet apart, waiting to get into Haight Street Market.San Francisco Chronicle newspaper front page above the fold on March 26th, 2020, with large print headline: Economic help on the way.New York Times newspaper front page above the fold on March 26th, 2020 with main headline: $2 TRILLION BOOST FOR U.S. MAY BE JUST A START.👥📰 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.

    #line #queue #HaightStreet #HaightAshbury #HaightStreetMarket #GussMarket #HSMCafe #newspaper #newspapers #SanFranciscoChronicle #NewYorkTimes #NYTimes #ShelterInPlace #COVID19 #CoronaVirus #SFdistancing #SF #SanFrancisco #2020_086 #20200326 #laterGram #noFilter

  69. Scattered dark clouds above cumulus clouds over the ocean, waves breaking upon a wet shore, reflecting the clouds and post-sunset sky, bits of orange in the gaps between the clouds on the horizon.Sunset sky backlighting cumulus clouds, small orange light in the middle behind clouds where the sun is setting above the ocean, smooth empty sand in front.Hundreds of small birds backlit walking on the sand just at the edge of the beach where it meets the waves, cumulus clouds above the ocean, reflected in the wet sand below.Hundreds of small birds flocking and flying up from the shore as a wave breaks at their feet, backlit by the post-sunset light.Orange post-sunset glow on the horizon above clouds and waves, a radially divergent pattern of streaks across the