tantek.com

t

  1. Many companies publish their environmental impacts, often annual metrics and specific practices, on their websites.

    Are any individuals doing this on their #IndieWeb sites?

    https://indieweb.org/environmental_impact

    E.g. @rhiaro has https://rhiaro.co.uk/2019/09/reflections-climate

    Beyond the environmental impact of our websites themselves (see https://indieweb.org/green_computing), we can do better than corporations, e.g. with "/environment" pages on our own sites, and help inspire & teach each other.

    Previously: https://tantek.com/2020/021/t1/first-flights-changes-make

    on

  2. Buildings with only a few lights across the photo, reflections of the lights drawn out in the dark canal below, viewed from a bridge.Walking over a stone bridge, building lights reflecting twinkling on a dark river, gentle gusts of crisp cold air, sudden flashbacks to charming nights mere months ago.

    on

  3. Fragmention must define what “space collapsing” means

    on

    The Fragmention processing model says to “contiguous text that matches the fragment with white space collapsing”. “space collapsing” is ambiguous here and must be better defined for interoperable implementation. Examples of questions that need to be answered explicitly by normative text in the spec:

    Is space collapsed in the fragment?

    Is space collapsed in the document text?

    Is space collapsed "inter-word" (in either or both fragment and document text)?

    Is space collapsed at the beginning and end (of either or both)?

    Is space at the beginning and end collapsed or stripped (of either or both)?

    Which definition of “white space” is used? Which characters are considered space to be collapsed, or can the spec link to a canonical definition of that elsewhere?

    The specification should at least answer these questions, preferably with examples demonstrating why the specific answers were chosen, and add tests for them accordingly.

    on

  4. Fragmention must define what “plain text content” means

    on

    The Fragmention processing model says to “Search through the plain text content” and hyperlinks the phrase “plain text content” to the HTML definition of a text node. That link is insufficient for precise (interoperable) implementation. Examples of questions that need to be answered explicitly by normative text in the spec:

    Does it just mean to concatenate all the text nodes, including CDATA?

    Does that include the text of inline script elements?

    Does it instead include the text of noscript elements?

    Does that include the text of inline style elements?

    As already proposed in issue #4, does that include alt text from images?

    The specification should at least answer these questions, preferably with examples demonstrating why the specific answers were chosen, and add tests for them accordingly.

    on

  5. Fragmention should also explicitly forbid (with "MUST NOT" language) use of fragmentions that start with a "/" character, thus allowing for hashslash (#/) routing URLs like Matrix/Riot URLs: https://riot.im/develop/#/room/#freenode_#indieweb:matrix.org

    on

  6. How does Secure EcmaScript (SES) relate to other subsets of 262?

    on

    The Draft Proposal for SES (Secure EcmaScript) appears to be a description of a subset of EcmaScript (262). How does it relate to other subsets of 262, and could this be explicitly documented?

    The Subsetting EcmaScript diagram appears to describe some of the ways that SES relates to 262 and other subsets. Is this diagram still accurate? Would an updated diagram like this make sense to include even non-normatively in the SES proposal?

    Label: question

    on