That being said, BlueSky is simpler and easier because there's no real federation yet, and even if they have a "Discovery" algorithm, you get many options to control what you want to see. It's feels great, like Twitter before their 2012(ish?) IPO.
That being said, BlueSky is simpler and easier because there's no real federation yet, and even if they have a "Discovery" algorithm, you get many options to control what you want to see. It's feels great, like Twitter before their 2012(ish?) IPO.
Consider using a self-hosting service, like https://togethr.party/ , to have your own instance on your own domain. Much like email, you should never be beholden to another party for your identity; your hosting service should be an invisible detail that can change without anyone interacting with you needing to notice.
I've watched several instances shut down over the years, and have never once regretted the decision to have an instance on my own domain. My social network handle is now the same as my email address, with an extra @ in front.
I'm paying ~$7/month to own my own fediverse identity, which seems cheap to me.
You're right about federation issues, though that's more a limitation of the fediverse protocols and fediverse software that really needs fixing. Fediverse instances don't automatically fetch and show all replies to posts you see, even if it knows they exist, unless your server is already fetching other things from the server hosting those posts. So it's a little harder to see other people's replies, which contributes to the problem of 20 people replying with the same answers because they can't see that other people have already replied.
Large instances work around that because everyone's already talking to at least one account on that server.
I hope those limitations get fixed someday, but for now they're fundamental to the fediverse.
Personally, I think Bluesky is a mix of NIH with a dash of wanting to be a central point of control, that is doomed in the long run - anything that works well for Bluesky can be copied, but the real benefit for the Fediverse in the long run is that Mastodon is just one of many services, or types of services. Every new service gets to hook into an existing network instead of starting from scratch.
I very much agree with you in owning your identity on this sort of thing, but I wouldn't pay $7/mo in order to participate in any social network.
I have my own email domain, and I can host it myself, or have someone else host it for me, on shared infrastructure. Fastmail charges me ~$4/mo, and that's for email, something anyone on the internet requires in order to interact with online services. I think $4/mo for a communications necessity is reasonable, and there are cheaper (even free) providers if I wanted to go that route. $7/mo for a social network is nuts.
I'm not sure how services like togethr.party work, but is it safe to assume that they have to spin up a completely new copy of the server software for each domain? That seems like a big problem, and is probably why this is so expensive.
I recently set up my own Matrix instance (using Synapse) and found it to be pretty wasteful, resource-wise. This is a solved problem with email servers, where one server can host as many domains as you have storage and processing power for; not sure why the chat/social platforms haven't caught up architecture-wise.
I don't believe ATProto has the same issues, and I believe it would take quite a rearchitecture of ActivityPub to solve.
> such that you can import it into a different service later
This is the key issue. There is no way to import posts in Mastodon without manually fudging the database (which I also had to do when running my own instance). As another commenter mentioned, it's a tricky issue, in large part because it's not part of the federation protocol.
Bluesky solves this by separating the storage from the other parts of the distributed system, such that you don't need to move your storage to change your identity, hosting, moderation, etc. Keeping them independent is a smart move.
I host my instance on an always free VM, don't put much work toward maintenence, and haven't had a problem with federation. Post migration is not really a thing from a shared instance, I don't think, so yeah, that sucks.
Honestly, the most expensive part for me is the domain, because I shelled out for a spiffy premium domain. But I'm weird.
Spammers sure love you :)
>> to have your own instance on your own domain
Domain is likely linked to your identity. What might look like an innocent *eet today, might end you on a wrong list down the road.
I was very disappointed to find out that whatever instance you choose can essentially hold your identity and content hostage.
I'd been hoping for something where my identity comes from a private key that I could take elsewhere.
No one there wants to hold your information hostage, you can always export it, and while it doesn't support importing, you can repost it through their API if you really want to.
> You can redirect your old profile to the new one
Is that true even when the reason for the change is because the instance operator wants to silence you? If you can't put up a metaphorical "Go Here Instead" sign, could they also stop you from "proving" that your new home is legitimate and that you're the same author as before?
But you lose all the posts and interactions. Most importantly, you are not keeping your identity, but merely creating a new account with a copy of your follower/following collections.
> No one there wants to hold your information hostage,
Tell that to a friend of mine who got banned from their instance for committing the crime of being an Ethereum developer. The admin suspended his account and didn't let him go back or initiate the migration process.
Most notably people can only follow hashtags from accounts that are on their server so if you insist on joining some micro server please save yourself the hassle of putting hashtags on things.
Instead I join specific interest-related communities that offer what I can't find in real life: the one person in the world that's had and overcome the same problem with their table saw.