fix "can not" -> "cannot" writing
This commit is contained in:
parent
87dd12c39b
commit
2b65419fa6
3 changed files with 2 additions and 2 deletions
|
|
@ -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.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue