[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

tantek.com

t

  1. [charter] SustyWeb IG charter should coordinate with IETF environmental efforts

    on

    The SustyWeb IG charter Coordination section says: “We will also monitor the work of and where appropriate collaborate with standards bodies (external to the W3C) such as those listed below…” and then lists two organizations.

    The IETF should be added to this list of standards bodies, perhaps even their Environmental Impacts of Internet Technology (eimpact) group in particular.

    The aspects of coordination could include each group’s email lists, meetings, and perhaps even collaborating on documents.

    If it would help, I could start a Pull Request with a basic one-sentence group and coordination description, and invite the editor(s) to make further changes as necessary.

    on

  2. I concur with https://github.com/TzviyaSiegman’s comment, and support making “WSG a living document rather than 1.0”.

    Sustainability best practices are constantly evolving, related conditions change year over year (such as how power is generated, how devices consume electricity, etc.), and the CG has strong productive momentum which is worth maintaining and focusing on continuously improving the WSG.

    The proposed IG charter could be updated accordingly, listing publishing the WSG as an intended living document rather than focusing on a “1.0” deliverable.

    on

  3. 👍

    on

  4. [charter] SustyWeb IG charter should state intended audience of guidance

    on

    The SustyWeb IG charter Motivation and Background says: “The Sustainable Web Interest Group will provide evidence-led guidance alongside methods to observe, measure, and improve the sustainability of digital products and services” and then states who will create that guidance.

    Before stating who will create the guidance, the charter Background should state who the guidance is intended for. I believe the Web Sustainability Guidelines (WSG) can answer some of this implicitly, however I think it would be helpful for the charter to explicitly state the intended audience. For example (not intended as a specific suggestion), the charter could state something like “This guidance is intended for …” and then perhaps a list of various roles like executives and other decision-makers, managers, designers, developers etc.

    I suggest asking the editor(s) of the WSG for a summary of the intended audience, and incorporating that summary into the charter’s Background section. If it would help, I could start a Pull Request with a basic one-sentence suggestion, and invite the editor(s) to make further changes as necessary.

    on

  5. ⚠️ .io domain¹ likely being phased-out² — seven suggested steps

    Good article in The Verge summarizing recent .io related events, see that for more context if this is news to you:
    * https://www.theverge.com/2024/10/8/24265441/uk-treaty-end-io-domain-chagos-islands

    It looks likely .io (and .io domains) will go away in the next few years (as .cs and .yu did³), so here are my suggested steps to take depending on your usage of .io domains:

    1. Avoid buying new .io domains (or making plans with existing ones; sell if you can)
    2. If you currently run a .io service⁴ (for a company or community), make and publicize a transition plan (like a new domain, redirection, orderly shutdown plan for redirects)
    3. If you have a personal site on a .io domain⁵ or subdomain, make your own transition plan, and perhaps post about how others should link to your posts
    4. If you are using someone else’s .io domain to publish (like #GitHubPages⁶), make a transition plan to publish elsewhere and leave a forwarding note and link behind
    5. If you use a .io domain as your Web sign-in login on any sites, switch them to another non-io personal domain
    6. Similarly if your site accepts #WebSignIn logins (via #IndieAuth, #RelMeAuth, or even #OpenID), consider discouraging any new sign-ups from .io domains, and warning any existing users with .io domains to switch per # 5
    7. If you have posts (or a whole #indieweb site) with links to .io sites or pages (like those in 2-4 above), make a plan for editing those links to point to an alternative or an archival copy (like on the Internet Archive)

    And of course, post about your #dotIO plans.

    Glossary

    Domain
     https://indieweb.org/domain
    IndieAuth
     https://indieweb.org/IndieAuth
    Internet Archive
     https://web.archive.org/
    OpenID
     https://indieweb.org/OpenID
    Redirect
     https://indieweb.org/redirect
    RelMeAuth
     https://indieweb.org/RelMeAuth
    Web sign-in
     https://indieweb.org/Web_sign-in


    References:

    ¹ https://indieweb.org/.io
    ² https://en.wikipedia.org/wiki/.io#Phasing_Out
    ³ https://en.wikipedia.org/wiki/.cs
    ⁴ E.g. https://indieweb.org/webmention.io or https://indieweb.org/granary.io
    ⁵ E.g. https://indieweb.org/werd.io
    ⁶ https://indieweb.org/github.io

    This is post 25 of #100PostsOfIndieWeb. #100Posts

    ← https://tantek.com/2024/283/t1/metaphors-constructive-cooperative-joyful
    → https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug

    on