more write- and referencing

13 files changed, 155 insertions, 111 deletions

diff --git a/root/articles/mmmfs/abstract/text$markdown+sidenotes.md b/root/articles/mmmfs/abstract/text$markdown+sidenotes.md
index 9ac0894..975fecc 100644
--- a/root/articles/mmmfs/abstract/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/abstract/text$markdown+sidenotes.md
@@ -1,4 +1,4 @@
 abstract
 ========
 
-[tbd]
+<div class="well well-warning">[section under construction]</div>
diff --git a/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md b/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md
index de38bec..45d3bdf 100644
--- a/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/conclusion/text$markdown+sidenotes.md
@@ -1,4 +1,4 @@
 conclusion
 ==========
 
-[tbd]
+<div class="well well-warning">[section under construction]</div>
diff --git a/root/articles/mmmfs/motivation/text$markdown+sidenotes.md b/root/articles/mmmfs/motivation/text$markdown+sidenotes.md
index e178f4a..b8a5cac 100644
--- a/root/articles/mmmfs/motivation/text$markdown+sidenotes.md
+++ b/root/articles/mmmfs/motivation/text$markdown+sidenotes.md
@@ -1,120 +1,126 @@
 motivation
 ==========
 
-The majority of users interacts with modern computing systems in the form of smartphones, laptops or desktop PCs,
+application-centric design
+--------------------------
+
+The majority of users interact with modern computing systems in the form of smartphones, laptops or desktop PCs,
 using the mainstream operating systems Apple iOS and Mac OS X, Microsoft Windows or Android.
 
-All of these operating systems share the concept of *Applications* (or *Apps*) as one of the core pieces of their interaction model.
-Functionality and capabilities of the digital devices are bundled in, marketed, sold and distributed as *Applications*.
+All of these operating systems share the concept of *Applications* (or *Apps*) as one of the core pieces of their
+interaction model. Functionality and capabilities of the digital devices are bundled in, marketed, sold and distributed
+as applications.
 
-In addition, a lot of functionality is nowadays delivered in the form of *Web Apps*, which are used inside a *Browser* (which is an *Application* itself).
-*Web Apps* often offer similar functionality to other *Applications*, but are subject to some limitations:
-In most cases, they are only accessible or functional in the presence of a stable internet connection,
-and they have very limited access to the resources of the physical computer they are running on.
-For example, they usually cannot interact directly with the file system, hardware peripherals or other applications,
-other than through a standardized set of interactions (e.g. selecting a file via a visual menu, capturing audio and video from a webcam, opening another website).
+In addition, a lot of functionality is nowadays delivered in the form of *Web Apps* or *Cloud Services*, which share the 
+limitations of native applications in addition to more specific issues that will be discussed in a separate section
+below.
 
-On the two Desktop Operating Systems (Mac OS X and Windows), file management and the concepts of *Documents* are still central
-elements of interactions with the system. The two prevalent smartphone systems deemphasize this concept by only allowing access to the 
-data actually stored on the device through an app itself.
+This focus on applications as the primary unit of systems can be seen as the root cause of multiple problems.
 
-This focus on *Applications* as the primary unit of systems can be seen as the root cause of multiple problems:
-Because applications are the products companies produce, and software represents a market of users,
-developers compete on features integrated into their applications.
+For one, since applications are the products companies produce, and software represents a market of users,
+developers compete on features integrated into their applications. To stay relevant, monlithic software or software
+suites tend to accrete features rather then modularise and delegate to other software<mmm-link
+path="../references/appliances"></mmm-link>. This makes many software packages more complex and unintuitive than they
+need to be, and also cripples interoperability between applications and data formats.
 
-However this lack of control over data access is not the only problem the application-centric approach induces:
-A consequence of this is that interoperability between applications and data formats is rare.
-To stay relevant, monlithic software or software suites are designed to 
-As a result applications tend to accrete features rather then modularise and delegate to other software [P Chiusano].
 Because applications are incentivised to keep customers, they make use of network effects to keep customers locked-in.
-This often means re-implementing services and functinality that is already available
-and integrating it directly in other applications produced by the same organisation.
-
-This leads to massively complex file formats,
-such as for example the .docx format commonly used for storing mostly
-textual data enriched with images and videos on occasion.
-The docx format is in fact an archive that can contain many virtual files internally,
-such as the images and videos referenced before.
-However this is completely unknown to the operating system,
-and so users are unable to access the contents in this way.
-As a result, editing an image contained in a word document is far from a trivial task:
-first the document has to be opened in a word processing application,
-then the image has to be exported from it and saved in its own, temporary file.
-This file can then be edited and saved back to disk.
-Once updated, the image may be reimported into the .docx document.
-If the word-processing application supports this,
-the old image may be replaced directly, otherwise the user may have to remove the old image,
-insert the new one and carefully ensure that the positioning in the document remains intact.
-
-Let us take as an example the simple task of collecting and arranging a mixed collection of images, videos
-and texts in order to brainstorm. To create an assemblage of pictures and text, many might be tempted to open an
-Application like Microsoft Word or Adobe Photoshop and create a new document there. Both photoshop files and
-word documents are capable of containing texts and images, but when the files are saved, direct access to the
-contained data is lost. It is for example a non-trivial and unenjoyable task to edit an image file contained
-in a word document in another application and have the changes apply to the document. In the same way,
-text contained in a photoshop document cannot be edited in a text editor of your choice.
-
-
-https://www.theverge.com/2019/10/7/20904030/adobe-venezuela-photoshop-behance-us-sanctions
-
-
-The application-centric computing paradigm common today is harmful to users,
-because it leaves behind "inert" data, as D. Cragg calls it:
-
-[Cragg 2016]
-D. Cragg coins the term "inert data" for the data created, and left behind, by apps and applications in the computing model that is currently prevalent:
-Most data today is either intrinsically linked to one specific application, that controls and limits access to the actual information,
-or even worse, stored in the cloud where users have no direct access at all and depend soley on online tools that require a stable network connection
-and a modern browser, and that could be modified, removed or otherwise negatively impacted at any moment.
-
-This issue is worsened by the fact that the a lot of software we use today is deployed through the cloud computing and SaaS paradigms,
-which are far less reliable than earlier means of distributing software:
-Software that runs in the cloud is subject to outages due to network problems,
-pricing or availability changes etc. at the whim of the company providing it, as well as ISPs involved in the distribution.
-Cloud software, as well as subscription-model software with online-verification mechanisms are additionally subject
-to license changes, updates modifiying, restricting or simply removing past functionality etc.
-Additionally, many cloud software solutions and ecosystems store the users' data in the cloud,
-where they are subject to foreign laws and privacy concerns are intransparently handled by the companies.
-Should the company, for any reason, be unable or unwanting to continue servicing a customer,
-the data may be irrecoverably lost (or access prevented).
-
-Data rarely really fits the metaphora of files very well,
-and even when it does it is rarely exposed to the user that way:
-The 'Contacts' app on a mobile phone or laptop for example does not store each contacts's information
-in a separate 'file' (as the metaphora may have initially suggested),
-but rather keeps this database hidden away from the user.
-Consequently, access to the information contained in the database is only enabled through the contacts applications GUI.
-
-<div class="sidenote">Note that 'creative' here does not only mean 'artistic': this applies to any field, and it limits the
-ability of domain experts to push the boundaries of practice by using technology in innovative ways.</div>
-Creative use of computer technology is limited to programmers, since applications constrain their users to the
-paths and abilities that the developers anticipated and deemed useful.
-
---
-
+This often means re-implementing services and functionality that is already available to users,
+and integrating it directly in other applications or as a new product by the same organisation.
+While this strategy helps big software companies retain customers, it harms the users, who have to navigate a complex
+landscape of multiple incompatible, overlapping and competing software ecosystems.
+Data of the same kind, a rich-text document for example, can be shared easily within the software systems of a certain
+manufacturer, and with other users of the same, but sharing with users of a competing system, even if it has almost the
+exact same capabilities, can often be problematic.
+
+Another issue is that due to the technical challenges of building tools in this system, applications are designed and
+developed by experts in application development, rather than experts in the domain of the tool. While developers may
+solicit feedback, advice and ideas from domain experts, communication is a barrier. Additionally, domain experts are
+generally unfamiliar with the technical possibilities, and may therefore not be able to express feedback that would lead
+to more significant advances.
+<div class="sidenote">Note that 'creative' here does not only mean 'artistic': this applies to any field, and limits
+the ability of domain experts to push the boundaries of practice by using technology in innovative ways.</div>
+As a result, creative use of computer technology is limited to programmers, since applications constrain their users to
+the paths and abilities that the developers anticipated and deemed useful.
+
+The application-centric computing metaphor treats applications as black boxes, and provides no means to understand,
+customize or modify the behaviour of apps, intentionally obscuring the inner-workings of applications and
+completely cutting users off from this type of ownership over their technology. While the trend seems to be to further
+hide the way desktop operating systems work <mmm-link path="../references/osx-files"></mmm-link>, mobile systems like
+Apple's *iOS* already started out as such so-called *walled gardens*.
+
+cloud computing
+---------------
+
+*Web Apps* often offer similar functionality to other *Applications*, but are subject to additional limitations:
+In most cases, they are only accessible or functional in the presence of a stable internet connection,
+and they have very limited access to the resources of the physical computer they are running on.
+For example, they usually cannot interact directly with the file system, hardware peripherals or other applications,
+other than through a standardized set of interactions (e.g. selecting a file via a visual menu, capturing audio and
+video from a webcam, opening another website).
+
+Cloud software, as well as subscription-model software with online-verification mechanisms, are additionally subject
+to license changes, updates modifiying, restricting or simply removing past functionality etc. Additionally, many cloud
+software solutions and ecosystems store the users' data in the cloud, often across national borders, where legal and
+privacy concerns are intransparently handled by the companies. If a company, for any reason, is unable or unwanting to
+continue servicing a customer, the users data may be irrecoverably lost (or access prevented). This can have serious
+consequences<mmm-link path="../references/adobe"></mmm-link>, especially for professional users, for whom an inability
+to access their tools or their cloud-stored data can pose an existential threat.
+
+inert data (formats)
+--------------------
+
+Cragg coins the term "inert data"<mmm-link path="../references/super-powers"></mmm-link> for the data created, and
+left behind, by apps and applications in the computing model that is currently prevalent: Most data today is either
+intrinsically linked to one specific application, that controls and limits access to the actual information, or even
+worse, stored in the cloud where users have no direct access at all and depend soley on online tools that require a
+stable network connection and a modern browser, and that could be modified, removed or otherwise negatively impacted
+at any moment.
+
+Aside from being inaccesible to users, the resulting complex proprietary formats are also opaque and useless to other
+applications and the operating system, which often is a huge missed opportunity: 
+The .docx format for example, commonly used for storing mostly textual data enriched with images and on occasion videos,
+is in fact a type of archive that can contain many virtual files internally, such as the various media files contained
+within. However this is completely unknown to the user and operating system, and so users are unable to access the
+contents in this way. As a result, editing an image contained in a word document is far from a trivial task: first the
+document has to be opened in a word processing application, then the image has to be exported from it and saved in its
+own, temporary file. This file can then be edited and saved back to disk. Once updated, the image may be reimported
+into the .docx document. If the word-processing application supports this, the old image may be replaced directly,
+otherwise the user may have to remove the old image, insert the new one and carefully ensure that the positioning in
+the document remains intact.
+
+disjointed filesystems
+----------------------
+
+The filesystems and file models used on modern computing devices generally operate on the assumption that every
+individual file stands for itself. Grouping of files in folders is allowed as a convenience for users, but most
+applications only ever concern themselves with a single file at a time, independent of the context the file is stored in
+in the filesystem.
+
+Data rarely really fits this metaphora of individual files very well, and even when it does, it is rarely exposed to
+the user that way: The 'Contacts' app on a mobile phone for example does not store each contacts's information in a
+separate 'file' (as the metaphora may suggest initially), but rather keeps all information in a single database file,
+which is hidden away from the user. Consequently, access to the information contained in the database is only enabled
+through the contacts application's graphical interface, and not through other applications that generically operate on
+files.
+
+Another example illustrates how a more powerful file (organisation) system could render such formats and applications
+obsolete: Given the simple task of collecting and arranging a mixed collection of images, videos and texts in order to
+brainstorm, many might be tempted to open an application like *Microsoft Word* or *Adobe Photoshop* and create a new
+document there. Both *Photoshop* files and *Word* documents are capable of containing texts and images, but when such
+content is copied into them from external sources, such as other files on the same computer, or quotes and links from
+the internet, these relationships are irrevocably lost. As illustrated above, additionally, it becomes a lot harder to
+edit the content once it is aggregated as well. To choose an application for this task is a trade-off, because in
+applications primarily designed for word processing, arranging content visually is harder and image editing and video
+embedding options are limited, while tools better suited to these tasks lack nuance when working with text.
+
+Rather than face this dilemma, a more sensible system could leave the task of positioning and aggregating content of
+different types to one software component, while multiple different software components can be responsible for editing
+the individual pieces of content, so that the most appropriate one can be chosen for each element.
+
+<!--
 Chiusano blames these issues on the metaphor of the *machine*, and likens apps and applications to appliances.
 According to him, what should really be provided are *tools*:
 composable pieces of software that naturally lend themselves to, or outrightly call for,
 integration into the users' other systems and customization,
 rather than lure into the walled-gardens of corporate ecosystems using network-effects.
- 
-Data is inert [Cragg 2016]
-
-Key points:
-- data ownership  
-  data needs to be freely accessible (without depending on a 3rd party) and unconditionally accessible
-- data compatibility  
-  data needs to be usable outside the context of it's past use (in the worst case)
-- functionality  
-  user needs many, complex needs met
-
-
-Today, computer users are losing more and more control over their data. Between web and cloud
-applications holding customer data hostage for providing the services, unappealing and limited mobile file
-browsing experiences and the non-interoperable, proprietary file formats holding on to their own data has
-become infeasible for many users. mmmfs is an attempt at rethinking file-systems and the computer user
-experience to give control back to and empower users.
-
-mmmfs tries to provide a filesystem that is powerful enough to let you use it as your canvas for thinking,
-and working at the computer.  mmmfs is made for more than just storing information. Files in mmmfs can interact
-and morph to create complex behaviours.
+-->
diff --git a/root/articles/mmmfs/references/$order b/root/articles/mmmfs/references/$order
index 96b5c98..4fd79ec 100644
--- a/root/articles/mmmfs/references/$order
+++ b/root/articles/mmmfs/references/$order
@@ -1,3 +1,8 @@
+appliances
+osx-files
+ios-files
+super-powers
+adobe
 xerox-star
 memex
 hypercard
diff --git a/root/articles/mmmfs/references/acm-dl/text$bibtex b/root/articles/mmmfs/references/acm-dl/text$bibtex
index 97b053f..ab7b9db 100644
--- a/root/articles/mmmfs/references/acm-dl/text$bibtex
+++ b/root/articles/mmmfs/references/acm-dl/text$bibtex
@@ -1,4 +1,4 @@
-@web{acm-dl,
+@online{acm-dl,
   title = {ACM Digital Library},
   url = {https://dl.acm.org},
 }
diff --git a/root/articles/mmmfs/references/adobe/text$bibtex b/root/articles/mmmfs/references/adobe/text$bibtex
new file mode 100644
index 0000000..3a83038
--- /dev/null
+++ b/root/articles/mmmfs/references/adobe/text$bibtex
@@ -0,0 +1,7 @@
+@online{adobe,
+  title = {Adobe is cutting off users in Venezuela due to US sanctions},
+  url = {https://www.theverge.com/2019/10/7/20904030/adobe-venezuela-photoshop-behance-us-sanctions},
+  publisher = {The Verge},
+  year = {2019},
+  visited = {2019-12-18},
+}
diff --git a/root/articles/mmmfs/references/appliances/text$bibtex b/root/articles/mmmfs/references/appliances/text$bibtex
new file mode 100644
index 0000000..56fa8c8
--- /dev/null
+++ b/root/articles/mmmfs/references/appliances/text$bibtex
@@ -0,0 +1,7 @@
+@online{appliances,
+  title = {The future of software, the end of apps, and why UX designers should care about type theory},
+  url = {http://pchiusano.github.io/2013-05-22/future-of-software.html},
+  author = {Chiusano, Paul},
+  year = {2013},
+  visited = {2019-12-18},
+}
diff --git a/root/articles/mmmfs/references/inkandswitch/text$bibtex b/root/articles/mmmfs/references/inkandswitch/text$bibtex
index 48fe03c..8b5f298 100644
--- a/root/articles/mmmfs/references/inkandswitch/text$bibtex
+++ b/root/articles/mmmfs/references/inkandswitch/text$bibtex
@@ -1,4 +1,4 @@
-@web{inkandswitch,
+@online{inkandswitch,
   title = {End-user Programming},
   url = {https://inkandswitch.com/end-user-programming.html},
   publisher = {Ink & Switch},
diff --git a/root/articles/mmmfs/references/ios-files/text$bibtex b/root/articles/mmmfs/references/ios-files/text$bibtex
new file mode 100644
index 0000000..7ec911c
--- /dev/null
+++ b/root/articles/mmmfs/references/ios-files/text$bibtex
@@ -0,0 +1,6 @@
+@online{ios:files,
+  title = {Use the Files app on your iPhone, iPad, or iPod touch},
+  url = {https://support.apple.com/en-us/HT206481},
+  publisher = {Apple},
+  visited = {2019-12-27},
+}
diff --git a/root/articles/mmmfs/references/linux-exec/text$bibtex b/root/articles/mmmfs/references/linux-exec/text$bibtex
index 4f39fef..d514613 100644
--- a/root/articles/mmmfs/references/linux-exec/text$bibtex
+++ b/root/articles/mmmfs/references/linux-exec/text$bibtex
@@ -1,4 +1,4 @@
-@web{linux:exec,
+@online{linux:exec,
   title = {How does Linux execute a file?},
   url = {https://stackoverflow.com/a/23295724/1598293},
   publisher = {stackoverflow.com},
diff --git a/root/articles/mmmfs/references/osx-files/text$bibtex b/root/articles/mmmfs/references/osx-files/text$bibtex
new file mode 100644
index 0000000..f0b28cb
--- /dev/null
+++ b/root/articles/mmmfs/references/osx-files/text$bibtex
@@ -0,0 +1,6 @@
+@online{osx:files,
+  title = {Where is "Show Package Contents"},
+  url = {https://discussions.apple.com/thread/6740790},
+  publisher = {Apple Communities},
+  visited = {2019-12-27},
+}
diff --git a/root/articles/mmmfs/references/super-powers/text$bibtex b/root/articles/mmmfs/references/super-powers/text$bibtex
new file mode 100644
index 0000000..5eabda8
--- /dev/null
+++ b/root/articles/mmmfs/references/super-powers/text$bibtex
@@ -0,0 +1,7 @@
+@online{super:powers,
+  title = {Super-powers, but not yours},
+  url = {http://object.network/manifesto-negative.html},
+  author = {Cragg, Duncan},
+  year = {2016},
+  visited = {2019-12-18},
+}
diff --git a/root/articles/mmmfs/references/wikipedia/text$bibtex b/root/articles/mmmfs/references/wikipedia/text$bibtex
index c83b72c..0fa3437 100644
--- a/root/articles/mmmfs/references/wikipedia/text$bibtex
+++ b/root/articles/mmmfs/references/wikipedia/text$bibtex
@@ -1,4 +1,4 @@
-@web{wikipedia,
+@online{wikipedia,
   title = {Hyperlink - Wikis},
   url = {https://en.wikipedia.org/wiki/Hyperlink#Wikis},
   publisher = {wikipedia.org},