Namaste esteemed Enola.dev listeners,
I've recently had some fun going down the Hash-landia & Encoditis rabbit holes.
Just in case you haven't
digested yourΒ π«Β from the holidays yet,
Enola.dev can now digest MACsΒ π. And just because hard-coding
Base64 and
SHA-2_512 felt a bit boring, it supportsΒ
Multiformats. You can (for now) use this to
validate fetched resource, and thanks to the #troll
Base256Emoji encoding, check the
integrityΒ of a greeting from an URL is as expected, like this:
$ enola fetch --http-scheme "https://www.vorburger.ch/hello.md?integrity=ππ₯πππππ€ππππππͺππ©π§‘ππππ₯΄ππ©πββπππ»πΊππππππΎπβ¬ππΎπ€πππ·πΆπ±ππππππ©ππβπβΆππ€«ππΊβπΌπ£βππ₯³πΏ"hello, world
What does any of this have to do with Enola'sΒ
Knowledge ManagementΒ
vision, you ask? Great question - because nothing much; except ifΒ I ever wanted toΒ calculate hashes of (RDF) Things to distribute them on some content-addressable storage (CAS), likeΒ
perhaps on IPLD & IPFS one fine day...Β then this groundwork may come in handy as foundation to build upon.
Other recent new features include direct
ipfs:Β and
data: URL schemesΒ support, some
JBang fun, version bumps & Bazel clean-up. I've also explored an ultimately #failedΒ
Graph Commons integration; and next up might be some other Network Graph visualization related work.
Best wishes for 2025,
M.