mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-27 14:12:09 +00:00
Fix canonical link for miniclub ring
This commit is contained in:
parent
6fe97c2c5e
commit
49d597a17e
6 changed files with 11 additions and 11 deletions
|
@ -16,7 +16,7 @@ About me
|
||||||
<meta itemprop="url" content="https://seirdy.one" />
|
<meta itemprop="url" content="https://seirdy.one" />
|
||||||
<div itemprop="author" itemscope="" itemtype="https://schema.org/Person" itemid="https://seirdy.one/#seirdy" class="p-author author h-card vcard" id="seirdy">
|
<div itemprop="author" itemscope="" itemtype="https://schema.org/Person" itemid="https://seirdy.one/#seirdy" class="p-author author h-card vcard" id="seirdy">
|
||||||
|
|
||||||
I'm <a itemprop="url" href="https://seirdy.one" rel="author me home canonical" class="u-url u-uid url">{{% indieweb-icon %}} <span itemprop="name" class="p-name fn n"> <span itemprop="givenName" class="p-given-name given-name">Rohan</span> <span itemprop="familyName" class="p-family-name family-name">Kumar</span></span></a> (<span class="p-pronouns"><a href="https://pronoun.is/he/him" class="u-pronouns"><span class="p-pronoun">he</span>/<span class="p-pronoun">him</span></a></span>). I'm also known by my more casual online handle <span itemprop="alternateName" class="p-nickname nickname">Seirdy</span> (<span class="p-pronouns"><a href="https://pronoun.is/they/them" class="u-pronouns"><span class="p-pronoun">they</span>/<span class="p-pronoun">them</span></a></span>). Mixing them up is fine.
|
I'm <a itemprop="url" href="https://seirdy.one" rel="author me home canonical" class="u-url u-uid url">{{% indieweb-icon %}} <span itemprop="name" class="p-name fn n"> <span itemprop="givenName" class="p-given-name given-name">Rohan</span> <span itemprop="familyName" class="p-family-name family-name">Kumar</span></span></a> (<span class="p-pronouns"><span class="p-pronoun">he</span>/<span class="p-pronoun">him</span></span>). I'm also known by my more casual online handle <span itemprop="alternateName" class="p-nickname nickname">Seirdy</span> (<span class="p-pronouns"><span class="p-pronoun">they</span>/<span class="p-pronoun">them</span></span>). Mixing them up is fine.
|
||||||
|
|
||||||
The Director's Cut of my bio is at my [About page](./about/ "{itemprop='subjectOf'}").
|
The Director's Cut of my bio is at my [About page](./about/ "{itemprop='subjectOf'}").
|
||||||
|
|
||||||
|
|
|
@ -27,7 +27,7 @@ I go by <span itemprop="name" class="p-name fn n"><span itemprop="givenName" cla
|
||||||
<dd class="p-gender-identity" itemprop="gender">Male</dd>
|
<dd class="p-gender-identity" itemprop="gender">Male</dd>
|
||||||
|
|
||||||
<dt>Pronouns</dt>
|
<dt>Pronouns</dt>
|
||||||
<dd class="p-pronouns"><a href="https://pronoun.is/he/him" class="u-pronouns"><span class="p-pronoun">he</span>/<span class="p-pronoun">him</span></a></dd>
|
<dd class="p-pronouns"><span class="p-pronoun">he</span>/<span class="p-pronoun">him</span></dd>
|
||||||
|
|
||||||
<dt>Time zone</dt>
|
<dt>Time zone</dt>
|
||||||
<dd>Pacific (UTC-08:00, or UTC-07:00 during daylight savings)</dd>
|
<dd>Pacific (UTC-08:00, or UTC-07:00 during daylight savings)</dd>
|
||||||
|
@ -61,7 +61,7 @@ I go by <span class="p-nickname nickname" itemprop="alternateName">Seirdy</span>
|
||||||
<dd class="p-gender-identity" itemprop="gender">Agender</dd>
|
<dd class="p-gender-identity" itemprop="gender">Agender</dd>
|
||||||
|
|
||||||
<dt>Pronouns</dt>
|
<dt>Pronouns</dt>
|
||||||
<dd class="p-pronouns"><a href="https://pronoun.is/they/them" class="u-pronouns"><span class="p-pronoun">they</span>/<span class="p-pronoun">them</span></a></dd>
|
<dd class="p-pronouns"><span class="p-pronoun">they</span>/<span class="p-pronoun">them</span></dd>
|
||||||
|
|
||||||
<dt>Social (Fediverse)</dt>
|
<dt>Social (Fediverse)</dt>
|
||||||
<dd><a href="https://pleroma.envs.net/seirdy" rel="me">@Seirdy<wbr />@pleroma<wbr />.envs.net</a> (primary)</dd>
|
<dd><a href="https://pleroma.envs.net/seirdy" rel="me">@Seirdy<wbr />@pleroma<wbr />.envs.net</a> (primary)</dd>
|
||||||
|
|
|
@ -254,7 +254,7 @@ HTTP/3 uses QUIC instead of TCP, which makes things a bit different; the importa
|
||||||
|
|
||||||
### The golden kilobyte
|
### The golden kilobyte
|
||||||
|
|
||||||
One of the benefits of HTTP/2 and HTTP/3 is multiplexing: multiple resources can download over a single connection. Try to initiate downloads for blocking resources as soon as possible.
|
One of the benefits of HTTP/2 and HTTP/3 is multiplexing: multiple resources can download over a single connection. Try to initiate downloads for blocking resources as soon as possible.
|
||||||
|
|
||||||
A TCP packet is 1460 bytes. Your first TCP packet will be partly taken up by a stapled TLS certificate, leaving you with under one kilobyte to work with. Make good use of this golden kilobyte; most or all of it will likely be taken up by HTTP headers.⁹ Ideally, the first kilobyte transferred should inform the client of all blocking resources required, possibly using preload directives; all of these resources can then begin downloading over the same multiplexed HTTP/2 connection before the current round-trip finishes! Note that this works best if you took my earlier advice to avoid third-party content.
|
A TCP packet is 1460 bytes. Your first TCP packet will be partly taken up by a stapled TLS certificate, leaving you with under one kilobyte to work with. Make good use of this golden kilobyte; most or all of it will likely be taken up by HTTP headers.⁹ Ideally, the first kilobyte transferred should inform the client of all blocking resources required, possibly using preload directives; all of these resources can then begin downloading over the same multiplexed HTTP/2 connection before the current round-trip finishes! Note that this works best if you took my earlier advice to avoid third-party content.
|
||||||
|
|
||||||
|
@ -859,13 +859,13 @@ The purpose of a hyperlink is to navigate to a different location. If a button e
|
||||||
|
|
||||||
> Use a clear and recognizable design for controls. Make it clear what elements are controls and how to use them.
|
> Use a clear and recognizable design for controls. Make it clear what elements are controls and how to use them.
|
||||||
> This includes:
|
> This includes:
|
||||||
>
|
>
|
||||||
> Using a common style on controls (for example, links being underlined).
|
> Using a common style on controls (for example, links being underlined).
|
||||||
> Using common design patterns on links and controls (for example, clicking on a link takes you to the page).
|
> Using common design patterns on links and controls (for example, clicking on a link takes you to the page).
|
||||||
> Making the borders of controls clear. Links in text do not need borders if identified properly (for example, a help icon has a border).
|
> Making the borders of controls clear. Links in text do not need borders if identified properly (for example, a help icon has a border).
|
||||||
> Making controls large enough so that users can click on it and not the item next to it.
|
> Making controls large enough so that users can click on it and not the item next to it.
|
||||||
> Ensuring items that are not clickable do not look like links or controls.
|
> Ensuring items that are not clickable do not look like links or controls.
|
||||||
>
|
>
|
||||||
> When this is not possible, provide instructions that explain how to use the control.
|
> When this is not possible, provide instructions that explain how to use the control.
|
||||||
=> https://www.w3.org/TR/coga-usable/#what-to-do-3 Making Content Usable for People with Cognitive and Learning Disabilities, section 4.2.5.2: Clearly Identify Controls and Their Use: What to Do
|
=> https://www.w3.org/TR/coga-usable/#what-to-do-3 Making Content Usable for People with Cognitive and Learning Disabilities, section 4.2.5.2: Clearly Identify Controls and Their Use: What to Do
|
||||||
|
|
||||||
|
@ -1028,7 +1028,7 @@ Ignore the elements specifically required for SVG Tiny PS; your image can be a s
|
||||||
|
|
||||||
This advice might seem daunting, but it’s usually easy to use existing tools to generate an SVG Tiny file and manually edit it to support the SVG secure static mode. SVGs that conform to this subset should be compatible with Qt5's SVG implementation, librsvg (used by Wikipedia and GNOME), and most operating systems' icon renderers. Moreover, tools like usvg can simplify complex SVGs to a tiny subset of the SVG spec.
|
This advice might seem daunting, but it’s usually easy to use existing tools to generate an SVG Tiny file and manually edit it to support the SVG secure static mode. SVGs that conform to this subset should be compatible with Qt5's SVG implementation, librsvg (used by Wikipedia and GNOME), and most operating systems' icon renderers. Moreover, tools like usvg can simplify complex SVGs to a tiny subset of the SVG spec.
|
||||||
=> https://github.com/RazrFalcon/resvg/tree/master/usvg usvg
|
=> https://github.com/RazrFalcon/resvg/tree/master/usvg usvg
|
||||||
=> https://github.com/RazrFalcon/resvg/blob/master/docs/usvg_spec.adoc usvg specification
|
=> https://github.com/RazrFalcon/resvg/blob/6b73d2a2a55be02f4913ef69eb16647623a50f49/docs/usvg_spec.adoc usvg specification
|
||||||
|
|
||||||
Two tools that can optimize the size of an SVG file are SVGO and the now-discontinued svgcleaner:
|
Two tools that can optimize the size of an SVG file are SVGO and the now-discontinued svgcleaner:
|
||||||
=> https://github.com/svg/svgo SVGO
|
=> https://github.com/svg/svgo SVGO
|
||||||
|
@ -1289,7 +1289,7 @@ The edges of a touch screen are often tap-targets (the top edge might toggle nav
|
||||||
On lists with many links, I had to find other ways to ensure adequate tap-target size and provide sufficient non-interactive space for readers with hand-tremors to scroll. Some examples:
|
On lists with many links, I had to find other ways to ensure adequate tap-target size and provide sufficient non-interactive space for readers with hand-tremors to scroll. Some examples:
|
||||||
|
|
||||||
=> https://seirdy.one/posts/2020/11/23/website-best-practices/#webmentions 1. The webmention list after this article separates links with timestamps and some paragraph spacing.
|
=> https://seirdy.one/posts/2020/11/23/website-best-practices/#webmentions 1. The webmention list after this article separates links with timestamps and some paragraph spacing.
|
||||||
2. Some list items have links with extra padding. These include description terms (`<dt>`) and navigation elements, such as the table of contents or the site header and footer,
|
2. Some list items have links with extra padding. These include description terms (`<dt>`) and navigation elements, such as the table of contents or the site header and footer,
|
||||||
=> https://seirdy.one/#posts 3. The homepage posts list separates links with non-interactive text descriptions
|
=> https://seirdy.one/#posts 3. The homepage posts list separates links with non-interactive text descriptions
|
||||||
=> https://seirdy.one/posts/2022/02/02/floss-security/ 4. The list of related articles at the beginning of one of my posts does the same.
|
=> https://seirdy.one/posts/2022/02/02/floss-security/ 4. The list of related articles at the beginning of one of my posts does the same.
|
||||||
|
|
||||||
|
|
|
@ -1091,7 +1091,7 @@ Light and dark variants of legacy formats (PNG, JPG, GIF), WebP, and AVIF can ca
|
||||||
|
|
||||||
I only recommend using SVG in images; avoid using them in embeds, objects, or directly in the body. Remember that users may save images, and open them in a non-browser image viewer with reduced SVG compatibility. To maintain maximum compatibility, stick the subset of the [secure static processing mode](https://www.w3.org/TR/SVG/conform.html#secure-static-mode) of [SVG Static](https://www.w3.org/TR/SVG11/feature#SVG-static). Specifically, the subset that appears in the [SVG Tiny Portable<wbr />/Secure (<abbr title="Portable/Secure">PS</abbr>) spec](https://datatracker.ietf.org/doc/draft-svg-tiny-ps-abrotman/). SVG Tiny PS is a subset of [SVG Tiny 1.2](https://www.w3.org/TR/SVGTiny12/intro.html), which is a supported export format in most vector drawing programs. Ignore the elements specifically required for SVG Tiny PS; your image can be a standard SVG that only utilizes a tiny subset of the full SVG spec.
|
I only recommend using SVG in images; avoid using them in embeds, objects, or directly in the body. Remember that users may save images, and open them in a non-browser image viewer with reduced SVG compatibility. To maintain maximum compatibility, stick the subset of the [secure static processing mode](https://www.w3.org/TR/SVG/conform.html#secure-static-mode) of [SVG Static](https://www.w3.org/TR/SVG11/feature#SVG-static). Specifically, the subset that appears in the [SVG Tiny Portable<wbr />/Secure (<abbr title="Portable/Secure">PS</abbr>) spec](https://datatracker.ietf.org/doc/draft-svg-tiny-ps-abrotman/). SVG Tiny PS is a subset of [SVG Tiny 1.2](https://www.w3.org/TR/SVGTiny12/intro.html), which is a supported export format in most vector drawing programs. Ignore the elements specifically required for SVG Tiny PS; your image can be a standard SVG that only utilizes a tiny subset of the full SVG spec.
|
||||||
|
|
||||||
This advice might seem daunting, but it’s usually easy to use existing tools to generate an SVG Tiny file and manually edit it to support the SVG secure static mode. SVGs that conform to this subset should be compatible with Qt5's SVG implementation, librsvg (used by Wikipedia and GNOME), and most operating systems' icon renderers. Moreover, tools like [usvg](https://github.com/RazrFalcon/resvg/tree/master/usvg) can simplify complex SVGs to [a tiny subset of the SVG spec](https://github.com/RazrFalcon/resvg/blob/master/docs/usvg_spec.adoc).
|
This advice might seem daunting, but it’s usually easy to use existing tools to generate an SVG Tiny file and manually edit it to support the SVG secure static mode. SVGs that conform to this subset should be compatible with Qt5's SVG implementation, librsvg (used by Wikipedia and GNOME), and most operating systems' icon renderers. Moreover, tools like [usvg](https://github.com/RazrFalcon/resvg/tree/master/usvg) can simplify complex SVGs to [a tiny subset of the SVG spec](https://github.com/RazrFalcon/resvg/blob/6b73d2a2a55be02f4913ef69eb16647623a50f49/docs/usvg_spec.adoc).
|
||||||
|
|
||||||
Two tools that can optimize the size of an SVG file are [SVGO](https://github.com/svg/svgo) and the now-discontinued [svgcleaner](https://github.com/RazrFalcon/svgcleaner). Too much lossy SVG compression can sometimes _reduce_ the effectiveness of gzip and Brotli compression. Compress in moderation.
|
Two tools that can optimize the size of an SVG file are [SVGO](https://github.com/svg/svgo) and the now-discontinued [svgcleaner](https://github.com/RazrFalcon/svgcleaner). Too much lossy SVG compression can sometimes _reduce_ the effectiveness of gzip and Brotli compression. Compress in moderation.
|
||||||
|
|
||||||
|
|
|
@ -190,7 +190,7 @@ Food for thought
|
||||||
|
|
||||||
Both of the prior two case studies---Mozilla and Signal---are examples of well-meaning organizations unintentionally leaving users vulnerable to user domestication. The former represents a lack of simplicity but the presence of an open platform. The latter represents a closed platform with a higher degree of simplicity. Intent isn't in the picture when examining the three steps and countermeasures to user domestication.
|
Both of the prior two case studies---Mozilla and Signal---are examples of well-meaning organizations unintentionally leaving users vulnerable to user domestication. The former represents a lack of simplicity but the presence of an open platform. The latter represents a closed platform with a higher degree of simplicity. Intent isn't in the picture when examining the three steps and countermeasures to user domestication.
|
||||||
|
|
||||||
[paulsnar](https://mastodon.technology/@paulsnar) pointed out a potential conflict between simplicity and open platforms:
|
paulsnar pointed out a potential conflict between simplicity and open platforms:
|
||||||
|
|
||||||
> I feel like there's some tension between simplicity and open platforms; to take Signal, in a way it's simple precisely because it's a de-facto-closed platform, or at least so Moxie has argued. In turn, Matrix is superficially simple, but the protocol is actually (imho) fairly complex exactly because it's an open platform.
|
> I feel like there's some tension between simplicity and open platforms; to take Signal, in a way it's simple precisely because it's a de-facto-closed platform, or at least so Moxie has argued. In turn, Matrix is superficially simple, but the protocol is actually (imho) fairly complex exactly because it's an open platform.
|
||||||
|
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
name,prev,home,next,random
|
name,prev,home,next,random
|
||||||
Indieweb,https://xn--sr8hvo.ws/%F0%9F%98%A9%F0%9F%9A%A3%F0%9F%8D%91/previous,https://xn--sr8hvo.ws/,https://xn--sr8hvo.ws/%F0%9F%98%A9%F0%9F%9A%A3%F0%9F%8D%91/next,null
|
Indieweb,https://xn--sr8hvo.ws/%F0%9F%98%A9%F0%9F%9A%A3%F0%9F%8D%91/previous,https://xn--sr8hvo.ws/,https://xn--sr8hvo.ws/%F0%9F%98%A9%F0%9F%9A%A3%F0%9F%8D%91/next,null
|
||||||
Retroweb,https://webri.ng/webring/retroweb/previous?index=3,https://indieseek.xyz/webring/,https://webri.ng/webring/retroweb/next?index=3,https://webri.ng/webring/retroweb/random
|
Retroweb,https://webri.ng/webring/retroweb/previous?index=3,https://indieseek.xyz/webring/,https://webri.ng/webring/retroweb/next?index=3,https://webri.ng/webring/retroweb/random
|
||||||
Miniclub,https://miniclub.amongtech.cc/prev/seirdy.one,https://miniclub.amongtech.cc/,https://miniclub.amongtech.cc/next/seirdy.one,https://miniclub.amongtech.cc/random
|
Miniclub,https://ring.aroace.space/prev/seirdy.one,https://ring.aroace.space/,https://ring.aroace.space/next/seirdy.one,https://ring.aroace.space/random
|
||||||
TheOldNet,https://webring.theoldnet.com/member/ba438275f00f5df1a2e78e547424d05e/previous/navigate,https://webring.theoldnet.com/,https://webring.theoldnet.com/member/ba438275f00f5df1a2e78e547424d05e/next/navigate,https://webring.theoldnet.com/member/ba438275f00f5df1a2e78e547424d05e/random/navigate
|
TheOldNet,https://webring.theoldnet.com/member/ba438275f00f5df1a2e78e547424d05e/previous/navigate,https://webring.theoldnet.com/,https://webring.theoldnet.com/member/ba438275f00f5df1a2e78e547424d05e/next/navigate,https://webring.theoldnet.com/member/ba438275f00f5df1a2e78e547424d05e/random/navigate
|
||||||
geekring,https://geekring.net/site/167/previous,https://geekring.net/,https://geekring.net/site/167/next,https://geekring.net/site/167/random
|
geekring,https://geekring.net/site/167/previous,https://geekring.net/,https://geekring.net/site/167/next,https://geekring.net/site/167/random
|
||||||
no js webring,https://nojs.sugarfi.dev/prev.php?url=https://seirdy.one,https://nojs.sugarfi.dev/,https://nojs.sugarfi.dev/next.php?url=https://seirdy.one,https://nojs.sugarfi.dev/rand.php
|
no js webring,https://nojs.sugarfi.dev/prev.php?url=https://seirdy.one,https://nojs.sugarfi.dev/,https://nojs.sugarfi.dev/next.php?url=https://seirdy.one,https://nojs.sugarfi.dev/rand.php
|
||||||
|
|
|
Loading…
Reference in a new issue