@jhooks 10. @gwern's sprawling, info-packed wiki with hover previews, TOCs, and a public change log
@jhooks @gwern 11. Speaking of hover previews, @JoshWComeau's experiment with Tippy.js this week is a fanstastic example of adding contextual layers to links -
@jhooks @gwern @JoshWComeau 12. Also related, @swyx's writing on Webmentions and Twitter as a "meta-commentary layer to the internet" follows this same vibe of bi-directional densely-linked knowledge across platforms - swyx.io/writing/twitte…
13. To come back to @tomcritchlow for a moment, as far as I can tell from internet-history-digging they OG coined the term "digital garden" 🌱 and have a wonderful series of reflections on the concept here: tomcritchlow.com/blogchains/dig…
14. Update on the historical origin!
Thanks to @tomcritchlow and @BillSeitz for the backstory insights
The linkbacks flow through Mike Caufield's "The Garden and the Stream: A Technopastoral"
16. Overdue addition to the list, but @swyx has an entire 'Digital Garden Terms of Service' agreement!
A beautifully reflection on what we should expect as readers and gardeners - Epistemic disclosure, proper attribution, and the right to be wrongswyx.io/writing/digita…
@swyx 17. This collection has now matured into a full grown essay documenting the history of "digital gardening" as an ethos 🌲 maggieappleton.com/garden-history
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Hosted the latest edition of Future of Code here in London on Thursday. So many bangers.
Delayed thread with snaps and demo videos!
Oscar (@ocuatrecasas) from @fermat_app built a node and wire interface for chaining language model calls + image identification + multiplayer user inputs
Crowd favourite @MathigonOrg by @PhilippLegner
The shock and awe just kept building and building...
New @tana_inc folks seem hungry for in-depth books on ontologies & schemas.
Initial reaction was... books are overkill? There's not much to know? Just google it? But then tried googling. And it is *noisy* and poorly curated out there.
A few recommendations:
Original semantic web/structured data content does a good job of explaining ontologies in an accessible way.
This paper "Ontology Development 101: A Guide to Creating Your First Ontology" (2001) covers almost all the essentials in ~23 pages cs.upc.edu/~jvazquez/teac…
I inadvertently learned a lot about ontologies by practicing Object-oriented UX (OOUX), similar to the "Conceptual Models" design ethos developed at PARC and built off object-oriented programming
1/ We've been working a new protocol at @hashintel
It's called the block protocol (but NOT about blockchain or NFTs!)
It allows you to build reusable blocks (aka. components) that are interchangeable across website/apps
It takes a minute to explain, but I’ve drawn pictures…
2/ Blocks are the fancy interactive elements you can add to most doc editors and websites nowadays – text, tables, checklists, images, embeds, etc.
You’ve seen these in apps like Notion, Wordpress Gutenberg, and Coda
3/ At the moment most apps create these from scratch and keep them contained within their ecosystem. You can’t move blocks from one app to another. So we keep reinventing the same blocks over and over. Everyone spends more time building. Fewer people get to use what’s been made