Defines the <<<Item>>>s as the unit of user-managed data. Items may be created by the user or by a <<<service>>>.
Alexander Obenauer notes
blognotesUrl
Homepage
Self-description
These Lab Notes document my research in progress. My research area is in the future of personal computing.
Has multiple posts related to methodologies like Zettelkasten.
Might be interesting for people that thinks about personal productivity or new models of personal knowledge organization.
The Graph OS
blogpostUrl
Related
Previous work, by the same author
The Potential Merits of an Itemized OS
blogpostServices & Item Drives
Defines the <<<Item>>>s as the unit of user-managed data. Items may be created by the user or by a <<<service>>>.
When the user manually creates a new item, or adds information to a service's item. That data gets saved to an <<<item drive>>>.
When the user creates an item not associated with a particular service (such as a note), or adds data to an item beyond its service’s own offering (such as adding a note to an email), this item data is saved in an /item drive/.
Item drives are a special kind of service. The user needs at least one, because they are responsible for the system’s item storage. But users might have additional item drives for specific purposes: an additional item drive might be shared with collaborators, or provide specific functionality around the syncing of their data (for example, by offering end-to-end encryption).