Conversation

Notices

1. Embed this notice
   Axel Rauschmayer (rauschma@fosstodon.org)'s status on Thursday, 21-Nov-2024 03:47:28 JST Axel Rauschmayer

   Mastodon’s weaknesses and how to fix them
   https://2ality.com/2024/11/mastodon-weaknesses.html

   #2ality #Mastodon

   • Embed this notice
     Sergey Shandar (functionalscript@techhub.social)'s status on Thursday, 21-Nov-2024 03:47:27 JST Sergey Shandar

     in reply to

     @rauschma thank you for the good article that highlights the problems! I actively work on the problem (data and identity ownership) with my team. We decided to build from scratch and solve the fundamental flaws in social digital interaction. There are several fundamental rules on which our work is based: 1. Content-addressable. 2. DiD 3. Relative friendly names (everyone is a root).

   • Embed this notice
     Axel Rauschmayer (rauschma@fosstodon.org)'s status on Saturday, 23-Nov-2024 03:18:21 JST Axel Rauschmayer

     in reply to

     • Sergey Shandar

     @functionalscript You may enjoy this blog post (see section “What should the fediverse do?”): https://dustycloud.org/blog/how-decentralized-is-bluesky/

   • Embed this notice
     Sergey Shandar (functionalscript@techhub.social)'s status on Saturday, 23-Nov-2024 03:18:21 JST Sergey Shandar

     in reply to

     @rauschma very insightful! Thank you, Axel! It's a good overview of different strategies and protocols. However, I still have that feeling that social network developers and advocates focus on the wrong things: protocols and servers. IMHO, we need to focus on how we store data in the way that it belongs to users no matter where we store it. That's the reason a content-addressable storage. Protocols are just ways to synchronize the decentralized storages. We can have all sorts of protocols to synchronize our storage work simultaneously, including sneakernet and pigeon mail. As soon as I, as a user, can prove that the message is from my friend (or a friend of my friend), I don't care how I got it. And a hash as an address helps me to ignore duplicates.

   • Embed this notice
     Sergey Shandar (functionalscript@techhub.social)'s status on Saturday, 23-Nov-2024 03:47:46 JST Sergey Shandar

     in reply to

     @rauschma yes, I've seen it. It should be the core and foundation. And the message formats, signatures, private key should be available to users. I have no idea what is my private key in Bluesky account. It doesn't belong to me. I can't communicate using the account using different servers, applications etc.

   • Embed this notice
     Axel Rauschmayer (rauschma@fosstodon.org)'s status on Saturday, 23-Nov-2024 03:47:47 JST Axel Rauschmayer

     in reply to

     • Sergey Shandar

     @functionalscript Quoting the post: “Some of these tasks are quite feasible for the fediverse to pick up today: the content-addressed storage and the portable identity stuff I think would be a major thing to introduce into the system but would be quite doable and would give the fediverse properties of surviving nodes going down better.”

   • Embed this notice
     Sergey Shandar (functionalscript@techhub.social)'s status on Saturday, 23-Nov-2024 03:59:09 JST Sergey Shandar

     in reply to

     @rauschma and we have such infrastructure (where CAS is the main storage and we use cryptographic proofs) then the main question would be: why do we need fediverse at that stage?

   • Embed this notice
     Axel Rauschmayer (rauschma@fosstodon.org)'s status on Saturday, 23-Nov-2024 04:16:47 JST Axel Rauschmayer

     in reply to

     • Sergey Shandar

     @functionalscript Interesting. I’d have thought you’d need a protocol on top of CAS for moderation and managing/distributing data.

   • Embed this notice
     Sergey Shandar (functionalscript@techhub.social)'s status on Saturday, 23-Nov-2024 04:16:47 JST Sergey Shandar

     in reply to

     @rauschma we can still have some nodes, servers, aggregators, search engines, communities on top of content-addressable internet. They can delete, filter messages, ban users. However, they can't delete the content from the internet completely. So, it's freedom for everyone. Users can keep their content forever and publish it wherever they like, servers/communities have freedom to ban any content and any user.

   • Embed this notice
     Sergey Shandar (functionalscript@techhub.social)'s status on Saturday, 23-Nov-2024 04:22:43 JST Sergey Shandar

     in reply to

     @rauschma I'm not saying that we don't need a fediverse, protocols etc. My point is that we should change our focus from "add content addressable infrastructure to fediverse" to "build content-addressable infrastructure and then we can add fediverse to it, if we need it".