Yeah, I definitely agree that open communities was/is a mistake. If a server is that large, it should be admin only. They can always run polls to gauge interest before making new communities.

Communities are the biggest problem. One solution would be to make community names more like a federation signature that only allows one community to have that exact name. Example: if lemmy.world has a community called !AITA, and you try to make a community on beehaw with the same !AITA name, it would not allow it and say “sorry that community name has already been registered by another instance”.

Of course, the major issue with this idea is that one could defederate with lemmy.world, in this example, and make the community name anyway, then refederate. Who would keep the name? That’s why I don’t think this solution is ideal, but it’s fun to share ideas and something to think about.

Why wait? Can’t you just deploy now and upgrade when .18 hits?

Ha! Love it when people post troubleshooting in real time. I have both undetermined and english selected, so I don’t think that’s it.

Thoughts so far? :)

Hm, that’s very interesting. I wonder if the platforms will build upon each other with future updates or if they’ll continue to remain “seperate” in terms of formatting and QoL. Very interested in the future of cross platform federation accounts.

I tried my best to use mastodon as a platform to post to lemmy/kbin but ran into a major problem: nested comments get lost to the ether, and there’s no way for you to reply to them using the same account.

Because of this, and basically this alone, I decided to forfeit mastodon all together and opt for a self hosted lemmy instance. I just got it set up and running this evening and so far, I’m not looking back.

Might set up another mastodon instance later, but that’s if I start to miss it.