tex: add conclusion

tex/text.tex

@@ -1721,4 +1721,39 @@ a testing instance; therefore, limits to prevent abuse might be imposed.
 % =========================================================================== %
 \nn{Conclusion}
 
+This thesis opened by introducing common terminology and continued with a dive
+into cryptography topics such as encryption, mentioned Diffie-Hellman key
+distribution scheme and briefly mentioned TLS. Further, it discussed the inner
+workings of browsers and the protocols that underpin them.
+
+Additionally, security mechanisms such as Site Isolation and Content Security
+Policy, that are commonly employed by mainstream browsers of today were
+introduced and the reader learnt how Content Security Policy is easily and
+dynamically configured.
+
+The large part of the thesis then revolved around the practical part, described
+everything from tooling used through application high-level-view architecture
+to implementation of specific parts of the application across the stack.
+
+Finally, the practical part concluded by extensively describing validation
+methods used to verify the application worked correctly.
+
+Of course, there are things that the author wishes were done differently or
+engineered better, but not everything could realistically be realised in the
+limited timespan and scope that had to be imposed on the project to prevent
+diverging. This constitutes clear candidates for future work that improves on
+the existing state, for example accessibility-wise. Author's unfamiliarity with
+the accessibility tooling sometimes compromising on the quality in this segment
+of the application, but it is a known deficiency. Further, on the list of tasks
+for the future also remained adding \emph{fuzzing} tests for the program,
+producing Software Bill of Materials, utilising additional immutable database
+or unifying the frontend design language across the pages.
+
+The program does have a very solid core that for instance listens for OS
+signals, handles graceful shutdown and supports structured logging but still
+has room for improvements, despite the fact that its creation really was
+best-effort. Due to the list of things mentioned earlier, it cannot really be
+called a \emph{finished} project yet, but it can already serve a purpose.
+
+
 % =========================================================================== %