diff --git a/thesis/4-Edit-Filters.tex b/thesis/4-Edit-Filters.tex
index 430432ebfc1195ade2cdc7b80387ce42d9d35022..e5514ff76d11f9df0e60f48b0f184d122a33ab41 100644
--- a/thesis/4-Edit-Filters.tex
+++ b/thesis/4-Edit-Filters.tex
@@ -343,6 +343,44 @@ If such an account is compromised, it loses its edit filter manager rights and g
\section{Edit filters' role in the quality control frame}
+
+ | Filters | Bots | Semi-Automated tools | ORES
+--------------------------------------------------------------------------------------------------------------------------------------------
+ | | | |
+ | - based on REGEXes | - rule/ML based | - rule/ML based | - ML framework
+properties | - part of the "software"/ | - "bespoke code": run on | - heuristics obfusca- | - can be used by other tools
+ | platform (MediaWiki ext) | user's infrastructure | ted by the interface |
+ | - public filters are directly | - no requirement for the code | (but often configura- |
+ | visible for everyone | to be made public | ble) |
+ | interested | - you can relatively easily | |
+ | | get all the filters; you | |
+ | | easily get all the bots | |
+ | | | |
+---------------------|-------------------------------------------------------------------------------------------------------------------------
+ | | | |
+ | - edit filter managers | - no special persmissions/ | - *rollback* perm | - mostly Scoring platform
+ | group (EN Wiki) | rights needed | | team (?)
+Who does this? | (abusefilter-modify perm) | - a bot gets a bot flag | |
+ | | | |
+---------------------|-----------------------------------------------------------------------------------------------------------
+ | | | |
+ | - become an edit filter manager | - get an approval to run the | - learn the tool | - understand ML
+What are the hurdles | - you have to *only* understand | bot from the BAG | - install Windows^^ | - formal requirements to
+to participate | REGEXes (relatively simple? | - programming knowledge | (some don't support | develop ORES?
+ | although relatively fast quite | - understand APIs, .. | other OS) |
+ | confusing) | - (but there is a lot to | - get the rollback perm |
+ | | understand with all the | |
+ | | mechanisms) | |
+ | | | |
+-------------------------------------------------------------------------------------------------------------------------------------
+ | | | |
+ | - censorship infrastructure? | - "botophobia" | - gamification |
+Concerns | - powerful, can in theory block | | |
+ | editors based on hidden | | |
+ | filters | | |
+ | | | |
+-----------------------------------------------------------------------------------------------------------------------
+
\subsection{Alternatives}
%TODO: where should this go? Already kind of mentioned in the introducing a filter part
diff --git a/thesis/6-Discussion.tex b/thesis/6-Discussion.tex
index 4dc6afc8fde705143d739fc4eb511ec04d446156..0641f3b9f2e8c7faee456a255f98c5a424ae3665 100644
--- a/thesis/6-Discussion.tex
+++ b/thesis/6-Discussion.tex
@@ -3,12 +3,19 @@
\section{Discussion}
+* 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
+
Difference bot/filter: filters are part of the "platform". (vgl also ~\cite{Geiger2014} and criticism towards the view of a hollistic platform)
They are a MediaWiki extension, which means they are run on official Wikimedia infrastructure. (vgl \cite{Geiger2014} and "bespoke code")
This makes them more robust and bestow them another kind of status.
Bots on the other hand are what Stuart Geiger calls "bespoke code": they are auxiliary programms developed, mantained and run by single community members, typically (at least historically?) not on Wikimedia's infrastructure, but instead on private computers or third party servers.
A key difference is also that while bots check already published edits which they eventually may decide to revert, filters are triggered before an edit ever published.
+* 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
+
% Aim: I want to know why are there filters? How do they fit in the quality control ecosystem?
Distinction filters/Bots: what tasks are handled by bots and what by filters (and why)? What difference does it make for admins? For users whose edits are being targeted? %TODO: good question, but move to analysis, since we won't be able to answer this on grounds of literature review only
diff --git a/thesis/introduction.tex b/thesis/introduction.tex
index f94b63a1d1f88d1359a8f149040e51fdb6674f6f..840551950b55cb3119df4bc369c290053a12ce64 100644
--- a/thesis/introduction.tex
+++ b/thesis/introduction.tex
@@ -63,6 +63,12 @@ Questions from Confluence
Q1 We wanted to improve our understanding of the role of filters in existing algorithmic quality-control mechanisms (bots, ORES, humans).
Q2 Which type of tasks do these filters take over in comparison to the other mechanisms? How these tasks evolve over time (are they changes in the type, number, etc.)?
Q3 Since filters are classical rule-based systems, what are suitable areas of application for such rule-based system in contrast to the other ML-based approaches.
+
+Note:
+* 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
+
\begin{itemize}
\item Was sind die mit dieser Arbeit verfolgten Ziele? Welches Problem soll gelöst werden?
\item Eine Beschreibung der ersten Ideen, der vorgeschlagene Ansatz und die aktuell erreichten Resultate