Also, per HN guidelines soliciting upvotes [1] is forbidden, which explains why this is in the front page even though no one can understand what this is.
Blog post: "Several months from now is the time."
Part of my problem with the current software toolset is that almost all allow a single view over a document or a webpage. In the physical world, I can have multiple books or papers open in front of me, drawing from a collection of sources concurrently rather than a single one serially. Additionally, if I open something between different apps, there is no integrated way to annotate at a layer above documents.
- What do you envision as a proper interface for digital exploration? - Will it allow for digesting multiple sources at once? - What will annotation, tagging and relations between documents look like?
There are references to "structured content" and the organic "building up [of] knowledge" in the Beam-ifesto. The most ready structure that I have been working with is a network of nodes, each representing a unit of digital data (a document), which can be found by file URL or by http URL. To relate these nodes, one could form "node structures" that abstract multiple nodes into a structure of some form (list, table, group, hierarchal links, etc). This offers abstraction and composability between digital concepts. While this may be private, I'm curious how you are picturing the "database" aspect of your product.
- Are you drawing at all from what we know about neural storage in your development of a "digital database"? - How are you enumerating the possible relational structures for multiple objects?