From 6127122da2768b65dcc405e67c3ab5515a8a8a6e Mon Sep 17 00:00:00 2001
From: Trolli Schmittlauch <t.schmittlauch@orlives.de>
Date: Sat, 7 Sep 2019 17:36:29 +0200
Subject: [PATCH] add ActivityPub Conf slides to Readme

---
 Readme.md       | 3 ++-
 talk-slides.pdf | 4 ++--
 talk-slides.tex | 2 +-
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/Readme.md b/Readme.md
index 7791f12..81002ad 100644
--- a/Readme.md
+++ b/Readme.md
@@ -1,7 +1,8 @@
 # Paper: Decentralised Hashtag Search and Subscription for Federated Social Networks
 
 This paper has been written during my Computer Science studies at [TU Dresden](https://inf.tu-dresden.de/) as a *Großer Beleg*.  
-A pre-compiled PDF of the paper can be found in [paper_hashtag_federation.pdf](paper_hashtag_federation.pdf).
+A pre-compiled PDF of the paper can be found in [paper_hashtag_federation.pdf](paper_hashtag_federation.pdf).  
+The slides of my talk at [ActivityPub Conf](https://redaktor.me/apconf/) can be found in [talk-slides.pdf](talk-slides.pdf).
 
 ## Building
 
diff --git a/talk-slides.pdf b/talk-slides.pdf
index 93aef81..7646d04 100644
--- a/talk-slides.pdf
+++ b/talk-slides.pdf
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:59eb268b9672d602ce51cc1a04a2c1e07f9d70f84152246d1aaa6d578078b88f
-size 1876781
+oid sha256:feac4a9baf285b984ba9d753913d55af327d1f2cb7ee207fc9dd8fc99ff5ab06
+size 1876877
diff --git a/talk-slides.tex b/talk-slides.tex
index 7041068..86fc4f1 100644
--- a/talk-slides.tex
+++ b/talk-slides.tex
@@ -456,7 +456,7 @@ Do we even want global hashtags in the Fediverse?
  
 \begin{itemize}
  \item intended as opt-in, domain-based push federation still better for user subscriptions
- \note[item]{optional mechanism}
+ \note[item]{optional mechanism, let's keep C2S communication for mobile friendliness and PushFed for simplicity}
  \item assumption: instances offer \(5.5\times\) the storage \& \(2.5\times\) the bandwidth of own posts
  \note[item]{assumptions: 5.5x storage, 2.5x bandwidth}
  \item performance: Can this be implemented efficiently enough to not DDoS popular hashtag nodes?