123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990 |
- % Replace the following information with your document's actual
- % metadata. If you do not want to set a value for a certain parameter,
- % just omit it.
- %
- % Symbols permitted in metadata
- % =============================
- %
- % Within the metadata, all printable ASCII characters except
- % '\', '{', '}', and '%' represent themselves. Also, all printable
- % Unicode characters from the basic multilingual plane (i.e., up to
- % code point U+FFFF) can be used directly with the UTF-8 encoding.
- % Consecutive whitespace characters are combined into a single
- % space. Whitespace after a macro such as \copyright, \backslash, or
- % \sep is ignored. Blank lines are not permitted. Moreover, the
- % following markup can be used:
- %
- % '\ ' - a literal space (for example after a macro)
- % \% - a literal '%'
- % \{ - a literal '{'
- % \} - a literal '}'
- % \backslash - a literal '\'
- % \copyright - the (c) copyright symbol
- %
- % The macro \sep is only permitted within \Author, \Keywords, and
- % \Org. It is used to separate multiple authors, keywords, etc.
- %
- % List of supported metadata fields
- % =================================
- %
- % Here is a complete list of user-definable metadata fields currently
- % supported, and their meanings. More may be added in the future.
- %
- % General information:
- %
- % \Author - the document's human author. Separate multiple
- % authors with \sep.
- % \Title - the document's title.
- % \Keywords - list of keywords, separated with \sep.
- % \Subject - the abstract.
- % \Org - publishers.
- %
- % Copyright information:
- %
- % \Copyright - a copyright statement.
- % \CopyrightURL - location of a web page describing the owner
- % and/or rights statement for this document.
- % \Copyrighted - 'True' if the document is copyrighted, and
- % 'False' if it isn't. This is automatically set
- % to 'True' if either \Copyright or \CopyrightURL
- % is specified, but can be overridden. For
- % example, if the copyright statement is "Public
- % Domain", this should be set to 'False'.
- %
- % Publication information:
- %
- % \PublicationType - The type of publication. If defined, must be
- % one of book, catalog, feed, journal, magazine,
- % manual, newsletter, pamphlet. This is
- % automatically set to "journal" if \Journaltitle
- % is specified, but can be overridden.
- % \Journaltitle - The title of the journal in which the document
- % was published.
- % \Journalnumber - The ISSN for the publication in which the
- % document was published.
- % \Volume - Journal volume.
- % \Issue - Journal issue/number.
- % \Firstpage - First page number of the published version of
- % the document.
- % \Lastpage - Last page number of the published version of
- % the document.
- % \Doi - Digital Object Identifier (DOI) for the
- % document, without the leading "doi:".
- % \CoverDisplayDate - Date on the cover of the journal issue, as a
- % human-readable text string.
- % \CoverDate - Date on the cover of the journal issue, in a
- % format suitable for storing in a database field
- % with a 'date' data type.
- \Title{Hybrid Online Social Networks}
- \Author{Carsten Porth}
- \Copyright{Copyright \copyright\ 2019 Carsten Porth}
- \Keywords{Hybrid App\sep Online Social Network\sep Peer 2 Peer\sep OOP\sep Twitter}
- \Subject{Despite numerous scandals about data protection in established social networks (Facebook, Google+), the platforms still enjoy great popularity. Alternative social networks, which have focused on protecting the data of their users, lack attractiveness, so they regularly fail. If users remain loyal to social networks despite poor data protection, ways must be found to protect their data. A hybrid approach enables the natural use of the platform and uses another communication channel to exchange sensitive data. The goal of this thesis was to work out a concept for a hybrid social network and to validate it with a prototype. Within the scope of the concept, the interests of the stakeholders were identified, and requirements for the hybrid solution were defined. For the implementation, concrete solution strategies for architecture and client were mentioned. The prototype was created as an Android app for Twitter. For secure data exchange, the IPFS protocol for decentralized data storage in combination with the distributed GUN database was used. The result shows that the concept is implementable and that the defined goals lead to a high-quality solution. The Hybrid Online Social Network prototype meets the previously defined requirements almost entirely. For Likes and Tweets, the user can decide if the official Twitter network or the private network should be used for data exchange with other users. The solution is user-friendly and requires minimal configuration effort.}
|