From 12f2551161f779fda5eebf07e81bd9aeae653b38 Mon Sep 17 00:00:00 2001
From: Lyudmila Vaseva <vaseva@mi.fu-berlin.de>
Date: Thu, 6 Jun 2019 16:40:48 +0200
Subject: [PATCH] Add feedback from presi

---
 meeting-notes/20190606.md | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 meeting-notes/20190606.md

diff --git a/meeting-notes/20190606.md b/meeting-notes/20190606.md
new file mode 100644
index 0000000..732b3f2
--- /dev/null
+++ b/meeting-notes/20190606.md
@@ -0,0 +1,26 @@
+# Meeting 06.06.2019 -- Research Group 2nd presi
+
+## Questions
+
+* Talk to people? --hellya
+
+## Feedback
+
+slide 13
+* possible explanation of the surge of filter hits in 2016: Trump came to power, Brexit happened and the first large-scale suspicion of manipulated elections was voiced
+* modify the diagram (num filter hits/month) in such a way, that we can identify the number for each month (stretch the x-axis); maybe also plot a regression line through it
+
+* split descriptive stats/visualisations in filters characteristics and filter activities (one bunch which focuses on filter themselves and one that takes the number of hits into account)
+
+* talk to Mariam about methodology and coding
+
+* Till now the whole inquiry is largely descriptive. It's fine the status quo is captured but then we should go a step further and ask "so what"? What do we have from that? Explain the data
+  * maybe we won't be able to explain a lot of it and we can open it further as interesting questions to be looked into by ethnographers
+
+* think about what values we embed to what systems and how; --> Lessig
+* to answer the question about evolution over time, I really do need the abuse_filter_history table
+* modify 3rd question to: why are regexes still there when we have ML; answering it most probably involves talking to people
+
+* check what questions the first bot papers asked, may serve as inspiration
+* another difference bots/filters, it's easier to ddos the bot infrastructure, than the filters: buy a cluster and edit till the revert table overflows
+
-- 
GitLab