schmittlauch/paper_hashtag_federation
1
0
Fork 0
Code Issues 1 Pull requests Releases Wiki Activity

fix "can not" -> "cannot" writing

Browse source
This commit is contained in:
Trolli Schmittlauch 2018-12-23 00:54:28 +01:00
parent 87dd12c39b
commit 2b65419fa6
3 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
expose.html
View file

@ -19,7 +19,7 @@
</header>
<h2 id="motivation">Motivation</h2>
<p>With the final standardization of the ActivityPub<a href="#fn1" class="footnoteRef" id="fnref1"><sup>1</sup></a> protocol by the W3C, federated social networks seem to have gained traction again with several new social servers implementing it<a href="#fn2" class="footnoteRef" id="fnref2"><sup>2</sup></a>.</p>
<p>But even these current implementations still suffer from a limitation all social networks based on push-federation still have: They can not provide a consistent network-wide view on all public posts including a certain hashtag. Such a search currently only returns posts from the instance's<a href="#fn3" class="footnoteRef" id="fnref3"><sup>3</sup></a> local database which have been delivered to the instance anyways due to other subscriptions. This limits the user experience compared to centralized mainstream social networks like Twitter, Tumblr or Facebook.</p>
<p>But even these current implementations still suffer from a limitation all social networks based on push-federation still have: They cannot provide a consistent network-wide view on all public posts including a certain hashtag. Such a search currently only returns posts from the instance's<a href="#fn3" class="footnoteRef" id="fnref3"><sup>3</sup></a> local database which have been delivered to the instance anyways due to other subscriptions. This limits the user experience compared to centralized mainstream social networks like Twitter, Tumblr or Facebook.</p>
<p>For the Diaspora* network there exists an implementation of a centralized federation relay, where federation servers send all their public posts to and can register to receive all messages containing a certain hashtag. But this centralized approach is against the spirit of federation and decentralization as it forms a single point of failure and potential bottleneck.</p>
<h2 id="planned-work">Planned Work</h2>
<p>The push-federation principle of current federated social networks works on the basis that user identifiers always include their home instance. Thus the server responsible for managing subscription requests and delivering new posts to all subscribers is always known. But there is no such place for all messages containing a certain hashtag, as these can originate from any instance. In federated social networks it is even not necessary for all instances to know each other.</p>

2
expose.md
View file

@ -6,7 +6,7 @@
With the final standardization of the ActivityPub^[<http://activitypub.rocks>] protocol by the W3C, federated social networks seem to have gained traction again with several new social servers implementing it^[[Mastodon](https://joinmastodon.org), [Pleroma](https://pleroma.social), [PixelFed](https:pixelfed.org) are examples for general social networks, with several special-interest software like FunkWhale adopting the protocol as well].
But even these current implementations still suffer from a limitation all social networks based on push-federation still have: They can not provide a consistent network-wide view on all public posts including a certain hashtag. Such a search currently only returns posts from the instance's^[a federation server domain] local database which have been delivered to the instance anyways due to other subscriptions. This limits the user experience compared to centralized mainstream social networks like Twitter, Tumblr or Facebook.
But even these current implementations still suffer from a limitation all social networks based on push-federation still have: They cannot provide a consistent network-wide view on all public posts including a certain hashtag. Such a search currently only returns posts from the instance's^[a federation server domain] local database which have been delivered to the instance anyways due to other subscriptions. This limits the user experience compared to centralized mainstream social networks like Twitter, Tumblr or Facebook.
For the Diaspora* network there exists an implementation of a centralized federation relay, where federation servers send all their public posts to and can register to receive all messages containing a certain hashtag. But this centralized approach is against the spirit of federation and decentralization as it forms a single point of failure and potential bottleneck.

BIN
expose.pdf
View file

Binary file not shown.