iarv/ipfs-blog
0
0
Fork 1
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-03-28 17:32:37 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update src/_blog/2026-01-year-in-review.md

Browse Source
This commit is contained in:
Robin Berjon
2026-01-22 08:29:22 -05:00
committed by GitHub
parent f08e08edb0
commit b011df8875
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/_blog/2026-01-year-in-review.md
View File

@@ -23,7 +23,7 @@ Closer to home, about a year ago we said that we wanted to focus on making the I
In truth, the community was already ahead of us here, quietly shipping tight, purpose-built libraries for CAR, IPLD, and other primitives in the IPFS family. Together, over the past year, we’ve made real progress on modularity through community-wide efforts – spanning standards work, new specifications, and rethinking how our core libraries are structured.
And dawg, how best to show off modularity by giving you a year-in-review post (about Rust IPLD) in this year-in-review post? Check out how we got [a 50% speed improvement](https://bsky.app/profile/marshal.dev/post/3m6wqrij2es2v) in the Python wrapper around the Rust lib and other great boosts from migrating off of the old libipld and to more modular implementations.
And dawg, how best to show off modularity by giving you [a year-in-review post (about Rust IPLD)](https://blog.ipfs.tech/2026-01-ipld-2025-review/) in this year-in-review post? Check out how we got [a 50% speed improvement](https://bsky.app/profile/marshal.dev/post/3m6wqrij2es2v) in the Python wrapper around the Rust lib and other great boosts from migrating off of the old libipld and to more modular implementations.
This year also saw lots of action in the [DASL](https://dasl.ing/) space. If you don't know DASL, it's the part of the IPFS family that's laser-focused on adoption, interoperability, and web-style systems that need to be resilient in the face of dubious code, open-ended systems, and — *gasp* — potentially high volumes of users. DASL is all about modularity and tiny specs that mesh together like small Unix tools. (Read [our introduction to DASL](https://ipfsfoundation.org/dasl-a-simple-way-to-reference-digital-content/) from earlier this year.) In addition to simple subsets of [CIDs](https://dasl.ing/cid.html), [CAR](https://dasl.ing/car.html), and DAG-CBOR (aka [DRISL](https://dasl.ing/drisl.html)), DASL also supports HTTP retrieval ([RASL](https://dasl.ing/rasl.html)), packaging metadata ([MASL](https://dasl.ing/masl.html)), and bigger data ([BDASL](https://dasl.ing/bdasl.html)). And before you ask: yes, we do have a resident acronym expert on staff.