Default Description
Permissioned Data Interlude: Spaces - Daniel's Leaflets
In which I retcon the naming of everything.
Component Description Manager
Manage description of all your components in one place! Each main component (and its variants) can have a description that might be useful for you, other designers and developers. Descriptions can provide tips for using particular component, important dev notes or act as tags for better searchin...
Descriptions Aren’t Prescriptions
When we look at a representation of reality, we can choose to either see it as descriptive, meaning it tells us what the world is currently like, or as prescriptive, meaning it tells us how the world should be. Descriptions teach us, but they also give us room to innovate. Prescriptions can get us stuck. One place this tension shows up is in language.
Customer Commons
We are planning to release more agreements as we approach the finalization of the IEEE P7012 Standard for Machine Readable Personal Privacy Terms . This initiative is currently has a demo #NoStalking, and we encourage your participation and feedback to help shape its development.
Details That Make Interfaces Feel Better
A collection of details that make your interfaces feel better.
Tracking NixOS option values and dependencies | oddlama's blog
oddlama's personal web page and blog
i was annoyed that this isn't explained how i want in the docs so i wrote my own mini-guide to publishing lexicons:
atproto made simple: publishing lexicons
underreacted.leaflet.pubLabelers v2 in Standard Reader: we deleted our own labelers. Any atproto labeler now works with zero setup, and your installed Bluesky labelers follow you to our app! The directory is the whole network, ones we think are for @standard.site near the top.
Have you seen my homepage as a PDF? Not this .pdf, the Personal Data Feed jvuillermet.eu Custom cards and links (I tried to maintain branding) for @standard.site, @bookhive.buzz, @popfeed.social, @bsky.app, @pckt.blog and inspiredby.social records.
jvuillermet.eu
jvuillermet.euI think this breaking change for standard.site needs to become an ecosystem-wide conversation and convention. Any web page that represents a corresponding AT record needs to include a meta tag that includes that record. <meta name=“at:uri” content=“at://…” \>
rich harris
atproto/@standard.site friends: any thoughts on this issue? This... <link rel="site.standard.publication" href="at://..."> ...is invalid HTML, per html.spec.whatwg.org/multipage/semantics.html#the-…, because DIDs aren't hostnames. This causes problems with some tools. Issue here: github.com/sveltejs/kit/issues/15935
Also with the obligatory basic bugs common to LLMs "The author of this library would like everyone to know that he was, in fact, well-aware of this requirement, thought about it a lot while designing the library, and then, somehow, forgot" nvd.nist.gov/vuln/detail/cve-2025-4143 nvd.nist.gov/vuln/detail/CVE-2025-4144
NVD - cve-2025-4143
nvd.nist.gov
