From ef88205eaa2a58be548954a0b505fb5facb83e05 Mon Sep 17 00:00:00 2001 From: Matthias Beyer Date: Sat, 2 Jan 2021 20:20:45 +0100 Subject: Add text in "Content" chapter Signed-off-by: Matthias Beyer --- doc/paper/main.tex | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/doc/paper/main.tex b/doc/paper/main.tex index 068bdab..54b6043 100644 --- a/doc/paper/main.tex +++ b/doc/paper/main.tex @@ -208,6 +208,40 @@ Because of its size, this object type might not be replicated as much as the \subsection{Content}\label{sec:datatypecontent} % What a "content" object is (and what it is not) +The content that a user posts can be added to IPFS directly. +This enables several other possibilities and use-cases: + +\begin{itemize} + \item + Because no meta-data is attached to the content, hosting that metadata + becomes less resource intensive in relation to the size of the actual + content. + + In turn, hosting the content is easier, because a hoster does not need + to attach metadata they do not care about, increasing the distribution + of the content. + + \item + A user can post content that is already on IPFS. + This content does not necessariliy have to be in the social network, but + can of course. + + If a user posts content that is already on IPFS, the post is essentially + what is called a "repost" in regular social networks, although other + methods of reposting might be appropriate + (see also \ref{sec:postreplies:reposts}). + + \item + Recurring posts of the same content are cheap. + + Because IPFS automatically deduplicates content, posting the same + content twice does not result in twice the disk space used. + + Also, if a user posts a set of files and another user posts a subset of + these files, deduplication applies. +\end{itemize} + + \subsection{Data format} % Short note about possible data formats -- cgit v1.2.3