this post was submitted on 20 Jun 2023
185 points (100.0% liked)
Fediverse
52 readers
1 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 2 years ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think one limiting factor that has yet to be addressed is that you can move your profile, but you can't move your content. Another is identity. How do you know which Mastodon server has an authoritative (i.e. "blue-check") profile for a given person/entity?
edit: Search indexing is also a huge problem. While it's possible to create a search index over all content local to a given server, maintaining an index over all content on all servers that you federate is a much bigger problem.
Mastodon has the seeds of this authority in that you can put links on your profile and then have them flagged by putting code on the website. So my Mastodon account could have a link to kazuyadarklightofficial.com and the flag proves I own/control that site. So if you know/can determine that site is THE KazuyaDarklight site, then you know you have the right Mastodon account.
I guess for the privacy conscious and content creators, one solution of this would be to host your own instance just for yourself. You control the domain and what's hosted. I could setup @thorned@rose.social and store my content on my server. In much the same vein as custom emails - hello@rose.social could be my email (technically I could have thorned@rose.social but that could be confusing with only a dropped @ but anyways).
Obviously this is not going to be a solution for everyone and it would be good to have a way to backup your content and be able to move it between servers. But in the mean time, it's a workable solution for those who find it important enough to go down that route. 🤷🏻♀️
That's exactly what I did. Have it running in docker containers at a VPS provider for $5/month and ship backups off to Backblaze nightly.
Never have to worry about my "home" instance dying/suddenly disappearing or defederating other instances. I like to self-host when it makes sense to, and this is definitely a situation where it makes sense.