diff --git a/assets/csv/webrings.base.csv b/assets/csv/webrings.base.csv
index 3544b37..9213849 100644
--- a/assets/csv/webrings.base.csv
+++ b/assets/csv/webrings.base.csv
@@ -1,6 +1,7 @@
 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
 a11y-webring,https://a11y-webring.club/prev,https://a11y-webring.club/,https://a11y-webring.club/next,https://a11y-webring.club/random
+envs,https://envs.net/ring/?action=prev&me=seirdy,https://envs.net/ring/,https://envs.net/ring/?action=next&me=seirdy,https://envs.net/ring/?action=random&me=seirdy
 Meta,https://meta-ring.hedy.dev/previous,https://meta-ring.hedy.dev/,https://meta-ring.hedy.dev/next,https://meta-ring.hedy.dev/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
 CSS,https://webri.ng/webring/cssjoy/previous?via=https://seirdy.one/,https://cs.sjoy.lol/,https://webri.ng/webring/cssjoy/next?via=https://seirdy.one/,https://webri.ng/webring/cssjoy/random/
diff --git a/content/notes/why-i-choose-microdata.md b/content/notes/why-i-choose-microdata.md
index b239e3c..eafa13a 100644
--- a/content/notes/why-i-choose-microdata.md
+++ b/content/notes/why-i-choose-microdata.md
@@ -10,6 +10,6 @@ syndicatedCopies:
 
 The four most popular ways to use RDF-based metadata on websites are RDFa-Core, RDFa-Lite, Microdata, and inline JSON-LD.
 
-I can't use RDFa-Lite because I need `rel` HTML attributes. [`rel` silently upgrades RDFa-Lite to RDFa-Core](https://www.ctrl.blog/entry/rdfa-link-attributes.html), which parses differently. I doubt all parsers upgrade correctly; some will try to parse RDFa-Core as RDFa-Lite. Conformant RDFa parsers upgrade RDFa-Lite pages to RDFa-Core despite many authors only being familiar with RDFa-Lite. I suppose resources like Schema.org and Google's documentation only documenting RDFa-Lite markup worsens the confusion.
+I can't use RDFa-Lite because I need `rel` HTML attributes. [`rel` silently upgrades RDFa-Lite to RDFa-Core](https://www.ctrl.blog/entry/rdfa-link-attributes.html), which parses differently. I doubt all parsers upgrade correctly; some will try to parse RDFa-Core as RDFa-Lite. Conformant RDFa parsers upgrade RDFa-Lite pages to RDFa-Core despite many authors only being familiar with RDFa-Lite. I suppose resources like Schema.org and Google's documentation only documenting RDFa-Lite markup worsens the confusion. <ins itemprop="correction" itemscope="" itemtype="https://schema.org/CorrectionComment" cite="https://w3c.social/@csarven/113658498996285762">Update <time itemprop="datePublished">2024-12-16</time>: <span itemprop="text">{{<indieweb-person first-name="Sarven" last-name="Capadisli" itemprop="mentions" url="https://csarven.ca/#i">}} has [clarified on the Fediverse](https://csarven.ca/#i) that this is the behavior of one faulty parser; `rel` only triggers an upgrade when used with an RDFa namespace. I may re-evaluate RDFa.</span></ins>
 
 With RDFa split between two incompatible alternatives with a confusing upgrade mechanism, the alternatives are Microdata and JSON-LD. I use structured data extensively; JSON-LD would duplicate most of the page. Let's use [this relatively short article]({{<relref "/posts/google-document-warehouse-api-docs-leak/">}}) as an example. [Exruct](https://github.com/scrapinghub/extruct) can convert the embedded Microdata into a massive JSON document featuring JSON-LD. [Take a look at the JSON-LD and HTML side by side](https://paste.sr.ht/~seirdy/7db88ad2405d4ab685130cd513cd9defafd9d2cf). Microdata attributes take a fraction of the footprint, encode the same information, and don't require duplicating nearly the entire page.