tantek.com

t

  1. Pretty shocked to hear of Emil Eklund (@eae) passing šŸ˜”

    @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 šŸ’”

    on
  2. I believe in the #webPlatform (#EngineDiversityAbsolutist)
    And the web as *your platform* (#IndieWeb over #BigTech #socialMedia corporate web)

    #webDeveloper @ohhelloana @smashingmag:
    ā€œAutonomy Online: A Case For The IndieWebā€ https://www.smashingmagazine.com/2020/08/autonomy-online-indieweb/

    on
  3. 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

    on
  4. 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:

    https://github.com/WICG/serial/blob/gh-pages/EXPLAINER.md

    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.

    on
  5. I’m sorry this happened Yan :(

    I know @bcrypt and trust her. Read the images.
    https://twitter.com/bcrypt/status/1292550669044297728/

    on
  6. @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
  7. #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/

    https://twitter.com/mozilla/status/1291504303870562305

    on
  8. 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

    on
  9. backfeed GitHub labels on your issues

    on

    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.

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

    on

    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.

    on
  11. CSS Overflow 3: overflow:clip

    on

    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.

    on
  12. CSS Images 4: cross-fade()

    on

    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.

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

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

    on
  15. 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

    https://twitter.com/EmilyKager/status/1288864659584450560

    on
  16. 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.

    on
  17. 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

    USPS:
    * 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/

    on
  18. šŸ‘

    on
  19. @b_cavello, been reflecting. "immunity" not the goal. "#decentralisation" has been colonized by #blockchain snakeoil

    Goals:
    * 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).

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

    on
  21. #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/

    on
  22. @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.

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

    on

    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.

    on
  24. CSS Media Queries Level 5

    on

    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.

    on
  25. HTML: dialog element

    on

    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.

    on
  26. hosted Homebrew Website Club West Coast tonight:
    https://events.indieweb.org/2020/07/homebrew-website-club-west-coast-ZObv0hlGOdR5
    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

    on
  27. went to Homebrew Website Club London:
    https://events.indieweb.org/2020/07/online-homebrew-website-club-europe-london-eIf6VfMWuhLY
    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

    on
  28. 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.

    * * *

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

    on

    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

    on
  30. DASWG: Drop Orientation Sensor in favor of existing APIs

    on

    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

    on
  31. DASWG: Drop Geolocation Sensor in favor of existing APIs

    on

    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

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

    on

    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

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

    on

    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

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

    on

    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

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

    on

    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

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

    on

    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

    on
  37. Changes To IndieWeb Organizing, Brief Words At IndieWebCamp West

    on

    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

    on
  38. Meetable should redirect /tag to /tags

    on

    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.

    on