mirror of
https://codeberg.org/fediverse/fediparty.git
synced 2024-11-30 04:01:30 +00:00
20 lines
1.3 KiB
Markdown
20 lines
1.3 KiB
Markdown
|
|
---
|
|
layout: "post"
|
|
title: "Fedicrypt - what would it take? (links updated)"
|
|
date: 2018-06-05
|
|
updated: 2018-06-05
|
|
tags:
|
|
- friendica
|
|
preview: "Hypolite Petovan, Friendica developer, wrote a summary of making private data in Fediverse macroblogging networks truely private"
|
|
url: "/en/post/fedicrypt-what-would-it-take"
|
|
lang: en
|
|
authors: [{"name": "@lostinlight", "url": "https://mastodon.xyz/@lightone", "network": "mastodon"}]
|
|
---
|
|
|
|
Fediverse social networks hugely benefit from federated architecture. However, like centralized platforms, they store all the data "in the cloud". Fediverse trust model implies trust in one's server administrator and hosting provider. Latest [research by Leah](https://chaos.social/@leah/99837391793032137) shows that administrators tend to choose large, popular providers. And judging by network statistics, users tend to flock to large Fediverse instances.
|
|
|
|
Hypolite Petovan, Friendica developer, [wrote a summary](https://blog.mrpetovan.com/web-development/encrypting-private-data-in-a-social-network-web-app) on what it would take to make private data in Fediverse networks truely private. He uses Friendica network as a reference, but this applies to all Fediverse networks that have limited view messages.
|
|
|
|
If you consider this topic important, join the discussion.
|