diff --git a/content/posts/layered-content-blocking.gmi b/content/posts/layered-content-blocking.gmi index e7552ba..e7bdada 100644 --- a/content/posts/layered-content-blocking.gmi +++ b/content/posts/layered-content-blocking.gmi @@ -78,7 +78,7 @@ Another difference is that while declarative filtering does have reduced functio With adblockers, you don't just trust extension developers; you also trust filter-list contributors. Many filter lists have thousands of entries aggregated from other filter lists, so trust-by-proxy ends up covering a lot of ground. This also applies to userstyle extensions: you have to trust the authors of each theme. -CSS injection is a powerful tool that can be used well or maliciously. Remember that it's contributors and extension developers could be well-meaning but still allow a vulnerability to slip through, especially when you account for extensions that alter a site's CSP. +CSS injection is a powerful tool that can be used well or maliciously. Remember that its contributors and extension developers could be well-meaning but still allow a vulnerability to slip through, especially when you account for extensions that alter a site's CSP. I still use these privileged extensions, but I try to limit their scope to sites where they're necessary. diff --git a/content/posts/layered-content-blocking.md b/content/posts/layered-content-blocking.md index d944901..345d639 100644 --- a/content/posts/layered-content-blocking.md +++ b/content/posts/layered-content-blocking.md @@ -86,7 +86,7 @@ I'll update this section as I collect feedback. Watch this space. If we trust our extension developers, is any of this really necessary? : With adblockers, you don't just trust extension developers; you also trust filter-list contributors. Many filter lists have thousands of entries aggregated from other filter lists, so trust-by-proxy ends up covering a lot of ground. This also applies to userstyle extensions: you have to trust the authors of each theme. - CSS injection is a powerful tool that can be used well or maliciously. Remember that it's contributors and extension developers could be well-meaning but still allow a vulnerability to slip through, especially when you account for extensions that alter a site's CSP. + CSS injection is a powerful tool that can be used well or maliciously. Remember that its contributors and extension developers could be well-meaning but still allow a vulnerability to slip through, especially when you account for extensions that alter a site's CSP. I still use these privileged extensions, but I try to limit their scope to sites where they're necessary. diff --git a/content/posts/website-best-practices.md b/content/posts/website-best-practices.md index 597013e..7b21218 100644 --- a/content/posts/website-best-practices.md +++ b/content/posts/website-best-practices.md @@ -1044,7 +1044,7 @@ Where long inline `` elements can trigger horizontal scrolling, consider a ### Keeping text together -Soft hyphens are great for splitting up text, but some text should stay together. The phrase "10 cm", for instance, would flow poorly if "10" and "cm" appeared on separate lines. Splitting text becomes especially painful on narrow viewports. A non-breaking space keeps the surrounding text from being re-flowed. Use the ` ` HTML entity instead of a space: `10 cm`. {{}}{{}} by {{}}, describes [where to use the non-breaking space](https://briefs.video/videos/is-progressive-enhancement-dead-yet/) in more detail. +Soft hyphens are great for splitting up text, but some text should stay together. The phrase "10 cm", for instance, would flow poorly if "10" and "cm" appeared on separate lines. Splitting text becomes especially painful on narrow viewports. A non-breaking space keeps the surrounding text from being re-flowed. Use the ` ` HTML entity instead of a space: `10 cm`. {{}}{{}} by {{}}, describes [where to use the non-breaking space](https://briefs.video/videos/is-progressive-enhancement-dead-yet/) in more detail. One exception to the rules from Practical Typography: don't use a non-breaking space if it would trigger two-dimensional scrolling on a narrow viewport. Between broken text and two-dimensional scrolling, broken text is the lesser evil. I personally set a cutoff at 2.5 cm (1 inch) at 125% zoom.