Add motivation for pushpin

thesis.tex

@@ -201,12 +201,12 @@ Then, client B executes the commands from \autoref{cmd:dat_store_example_B}.
 
 Changes from A to the folder \emph{mydat} will be replicated by B, even if A is not connected at the same time.
 
-\section{Beyond}
+\section{Beyond Dat}
 
-We also experimented with Pushpin\footnote{\url{https://github.com/automerge/pushpin}}, which is a collaborative coarkboard app. It is based on hypermerge\footnote{\url{https://github.com/automerge/hypermerge}}, a library providing a JSON-like structure that can be edited concurrently, without worrying about conflicts. And hypermerge is itself based on the Dat protocol.
+We also experimented with Pushpin\footnote{\url{https://github.com/automerge/pushpin}}, which is a collaborative coarkboard app. We wanted to showcase a peer-to-peer application with a real-time interface. It is based on hypermerge\footnote{\url{https://github.com/automerge/hypermerge}}, a library providing a JSON-like structure that can be edited concurrently, without worrying about conflicts. And hypermerge is itself based on the Dat protocol.
 
-However, while using it we suffered from a few instabilities, among them Electron crashes from time to time, and the synchronization stops until the window is reloaded. \\
-On top of that, we were unable to install Pushpin on the Raspberry Pi to have a replicating node as it requires compiling Node 14 and the Raspberry Pi ran out of memory while doing the compilation.
+However, Pushpin was quite unstable, and Electron was crashing from time to time, and the synchronization also stopped until the window was reloaded. \\
+On top of that, we were unable to install Pushpin on the Raspberry Pi to have a replicating node as Pushpin requires compiling Node 14 and the Raspberry Pi ran out of memory while doing the compilation.
 
 \section{Possible improvements and future work}