New note: Containing web bloat

content/meta/_index.md

@@ -52,7 +52,7 @@ This site is featured in some cool directories.
 - [Nixers](https://github.com/nixers-projects/sites/wiki/List-of-nixers.net-user-sites)
 - [Smooth Sailing](https://smoothsailing.asclaria.org/)
 - [Ye Olde Blogroll](https://blogroll.org/)
-- [Nerd Listings](http://nerdlistings.info/category/personalsites/)
+- [Nerd Listings](http://nerdlistings.info/)
 
 <details>
 <summary>Pending directories</summary>

content/notes/containing-web-bloat.md

@@ -0,0 +1,19 @@
+---
+title: "Containing web bloat"
+date: 2022-10-20T13:20:11-07:00
+replyURI: "https://mastodon.sdf.org/@khm/109201860585444737"
+replyTitle: "Web technology has gotten bigger because web engineers just don’t care"
+replyType: "SocialMediaPosting"
+replyAuthor: "khm"
+replyAuthorURI: "https://sciops.net/"
+---
+Here is how I propose browsers address web bloat:
+
+1. [Stop adding features](https://seirdy.one/notes/2022/06/18/browser-development-moratorium/) unrelated to accessibility, security, privacy, and internationalization.
+
+2. Adopt a default [document policy](https://github.com/wicg/document-policy/blob/main/document-policy-explainer.md) that [restricts oversized assets and download size](https://github.com/WICG/document-policy/issues/44).
+
+3. Make JIT-compilation a per-site opt-in permission. That should rein in over-reliance on JS.
+
+This should mostly contain the bloat problem without significantly inconveniencing most users, which is why it will never happen.
+

content/notes/state-of-the-tor-uplift.md

@@ -9,3 +9,5 @@ The [Tor Uplift project](https://wiki.mozilla.org/Security/Tor_Uplift) is an ini
 On <time datetime="2022-06-28">2022-06-28</time>, Firefox 102 ESR was released. Today, on <time datetime="2022-09-20">2022-09-20</time>, Firefox 91 ESR will lose support. That gave a window of about three months (the duration of three Firefox stable releases) to re-base Tor Browser patches.
 
 The first stable release of the Tor Browser based on ESR 102 hasn't yet shipped (it's close; [an alpha version is available](https://blog.torproject.org/new-alpha-release-tor-browser-120a2/)). Seven years into the Tor uplift, the Tor Project isn't able to keep up with the Firefox ESR release calendar. I don't think the Tor Uplift will succeed at getting the Tor Browser to track Firefox's stable channel; at best, it's keeping the Tor Browser from falling too far behind ESR.
+
+<ins>Update <time>2022-10-20</time>: 30 days since Firefox ESR 91 reached end-of-life, the latest stable Tor Browser release (11.5.4) is still based on v91. [Five CVEs fixes from v102 have already been backported](https://blog.torproject.org/new-release-tor-browser-1154/). It's reasonable to assume that v91 has issues of its own that won't be addressed. Until the v102-based 12.x hits stable: if you don't use "safest", you might want to re-consider that with this information in mind.</ins>

linter-configs/htmltest.yml

@@ -24,7 +24,7 @@ IgnoreHTTPS:
   - "http://www.nathanmyhrvold.com/"
   - "http://www.tuxmachines.org/"
   - "http://xmlns.com/"
-  - "http://nerdlistings.info/category/personalsites/"
+  - "http://nerdlistings.info/"
 CheckExternal: true
 IgnoreURLs:
   - "../music.txt"
@@ -37,7 +37,6 @@ IgnoreURLs:
   - "https://seirdy.one/webmentions/"
   - "http://creativecommons.org/ns"
   - "https://seirdy.one/search/"
-  - "https://nerdlistings.info/category/personalsites/" # I reached out about the expired cert and mentioned the issue on the page.
   - "https://www.reddit.com/user/Seirdy" # reddit doesn't like htmltest
   # - "https://i.reddit.com/r/web_design/comments/k0dmpj/an_opinionated_list_of_best_practices_for_textual/gdmxy4u/"
   - "https://i.reddit.com"