Capability Trees: Sovereignty Is the Point
This piece argues that DASL introduces security risk when applied to delegations, and that by not using DASL, capability trees avoid that risk.
DASL — Data-Addressed Structures & Links
A small set of simple, standard primitives to work on content-addressed data.
DASL — Data-Addressed Structures & Links
A small set of simple, standard primitives to work on content-addressed data.
DASL: MASL — Metadata for Arbitrary Structures & Links
MASL is a CBOR-based metadata system that is designed to work well with content-addressed and decentralised systems, to enable fully self-contained, self-certified content distribution.
DASL: DRISL — Deterministic Representation for Interoperable Structures & Links
DRISL is a serialization format that is deterministic (so that the same data will have the same CID) and that features native support for using CIDs as links. It is based on CBOR, using a narrow profile of CBOR's "Core" featureset called "[[cborc-42]]", specified formally in this IETF document.
@dasl/weasl - npmx
Warehouse that's Extensible for Arbitrary Structures & Links (WEASL) — @dasl/weasl — DASL store
DASL: Content-Addressable aRchives (CAR)
The CAR format offers a serialized representation of set of content-addressed resources in one single concatenated stream, alongside a header that describes that content.
Cross-Model Evaluation: kaish collection syntax across 7 LLMs (DeepSeek, Gemini, Claude, Gemma, GLM, Qwen)
Cross-Model Evaluation: kaish collection syntax across 7 LLMs (DeepSeek, Gemini, Claude, Gemma, GLM, Qwen) · GitHub
feat: add llms.txt endpoint for LLM-optimized documentation by quantizor · Pull Request #2388 · tailwindlabs/tailwindcss.com
Add /llms.txt endpoint that serves a concatenated, text-only version of all Tailwind CSS documentation pages optimized for Large Language Model consumption. Extract text from MDX files, removing J...
veritiles v0.3 is out 🚀 The proof format is now DASL + AT Protocol compatible from the ground up, using raw/dag-CBOR CIDs, DRISL descriptors and MASL bundles. github.com/guillaumemichel/veritiles @dasl.ing @atproto.com
GitHub - guillaumemichel/veritiles: Verified map tiles: fetch PMTiles byte ranges from any untrusted HTTP host and cryptographically verify every byte against a content identifier before your map renders it. Zero dependencies; drop-in pmtiles Source for MapLibre GL, Leaflet, and OpenLayers.
github.comI feel like using LLMs to flag intent/semantics mismatches (eg do var names seem to match what you actually do) or indirect violations of API contracts or whatever as a supplement to static analysis to produce *better* code would be at least as high impact, and it's like 1% of the discourse
