2) A free form space (or set of spaces) that are alive, without time-stamp and look more like Figma, Roam, Mindmap than blogpost. Ready for a post-writing, post-publish world.
Conversation
Some things this enables:
- A more vibrant community and interaction model (a speed up of the community feed)
- A shift from making sense to community making their own sense of raw materials
2
4
And finally the Big One (tm) that this enables is the ability to do "just in time" insights (perfect for feed based worlds) where can snapshot parts of the open canvas (figma, mindmap, roam whichever) to make a point in real time without breaking stride
3
1
4
Does something like what Substack enables with a newsletter + threaded conversations with the same readership point in the right direction?
1
not really - substack doesn't change the received experience of author -> community. It simply enables in different ways.
1
1
Agreed. Substack is a point solution for harvesting the end-of-life blog market into the email ecosystem, which seems more robust/long-lived. It is less a successor to blogging than a sort of upmarket retreat for blogging being disrupted by threaded open media
2
4
Really, that's what you're talking about Tom. My elderblogging personal phase just happens to synchronize with the elder stage of the medium itself. Of the 2 dynamics (me getting old, blogging getting disrupted by threading), the latter is the more important one obviously.
1
1
For sure - but you're "crashing" first as the canary in the coal mine for the rest of us. A useful point of study.
2
3
I think what I'd *like* to do is port ribbonfarm to a site where pre-blogchain stuff is rendered as a bunch of legacy static pages forming a sort of background, blogchains are rendered as native threads weaving through it, and there's support for a new roam-like thing
1
4
What we're running into here is a need for a multi-architecture publishing: books, blogs, wikis, threads, and my latest obsession, short glossary-like log-level entries. Kinda like Intel's OneAPI is trying to make a single interface for many architectures. software.intel.com/en-us/oneapi
Yeah - aligns with the "headless CMS" idea except that world is deficient in imagination. It's not headless CMS so that you can reskin the front end it's headless cms so you can merge blogs, books, wikis, threads, roam etc
1
2
unfortunately, all this is technically way beyond me to set up on an experimental basis so I'd need someone to invent a scheme basically. Until then, I'm sitting around in wordpress.
1
1
Show replies


