add sources for Mark Zuckerberg in US Congress and EU Parliament

thesis/bib/bibliography.bib

@@ -355,4 +355,22 @@
   note         = {Online, accessed 21.03.2019},
 }
 
+@Misc{facebook2018eu-parliament,
+  author       = {Guy Verhofstadt},
+  title        = {{Mark Zuckerberg failed to address European concerns about Facebook}},
+  howpublished = {\url{https://edition.cnn.com/2018/05/23/opinions/mark-zuckerberg-european-parliament-facebook-verhofstadt-intl/index.html}},
+  month        = may,
+  year         = {2018},
+  note         = {Online, accessed 21.03.2019},
+}
+
+@Misc{facebook2018us-congress,
+  author       = {Seth Fiegerman},
+  title        = {{Congress grilled Facebook's Mark Zuckerberg for nearly 10 hours. What's next?}},
+  howpublished = {\url{https://money.cnn.com/2018/04/12/technology/facebook-hearing-what-next/index.html}},
+  month        = apr,
+  year         = {2018},
+  note         = {Online, accessed 21.03.2019},
+}
+
 @Comment{jabref-meta: databaseType:bibtex;}

thesis/content/05-proof-of-concept/osn-selection.tex

@@ -1,4 +1,4 @@
-When selecting a suitable \ac{OSN} for the development of a hybrid client, Facebook was the obvious first choice due to the numerous negative headlines about data protection. With over 2.3 billion users per month (average Q4 2018), it is currently the most widely used social network in the world \cite{facebook2019reportq4}. In the recent past, it has often been criticized for its handling of its users' data. In particular, the scandal surrounding the data analysis company Cambridge Analytica, which had access to the data of up to 87 million users, hit Facebook hard \cite{facebook2018cambridge-analytica,facebook2018api-restriction}. As a result, CEO Mark Zuckerberg had to face the US Congress and the EU Parliament in question rounds and did not leave a good impression by avoiding many questions. As a result of this scandal, there were further restrictions to the Facebook \ac{API} \cite{facebook2018api-restriction}.
+When selecting a suitable \ac{OSN} for the development of a hybrid client, Facebook was the obvious first choice due to the numerous negative headlines about data protection. With over 2.3 billion users per month (average Q4 2018), it is currently the most widely used social network in the world \cite{facebook2019reportq4}. In the recent past, it has often been criticized for its handling of its users' data. In particular, the scandal surrounding the data analysis company Cambridge Analytica, which had access to the data of up to 87 million users, hit Facebook hard \cite{facebook2018cambridge-analytica,facebook2018api-restriction}. As a result, CEO Mark Zuckerberg had to face the US Congress and the EU Parliament in question rounds and did not leave a good impression by avoiding many questions \cite{facebook2018us-congress,facebook2018eu-parliament}. As a result of this scandal, there were further restrictions to the Facebook \ac{API} \cite{facebook2018api-restriction}.
 
 However, the Facebook \ac{API} is not suitable for developing a new client. The functionalities provided by the \ac{API} offer the possibility to develop an app that can be used within Facebook, for example for a game. So, it is not possible to give a \enquote{Like} for a post through this \ac{API}, which is part of the core functionality of a Facebook client. As discussed in Chapter \ref{ch:concept}, it is possible to access the data through crawling. However, the constant and rapid development would make this an arduous undertaking. Facebook writes in a blog post that the code changes every few hours \cite{facebook2017release}. Therefore it is almost impossible to adjust the crawler fast enough and roll out the adjusted code.