The thing to get across to people is that you don't need to understand it to use it. Hell, that goes for most things. The average person has no idea how an internal combustion engine works but can drive a car just fine.
Coelacanth
Not really. Also by your logic you can't trust anyone ever because there is always a risk they turn bad at some point in the future. All we can do is evaluate what we have in front of us at the moment. Current evidence suggests Ruud is trustworthy, committed and capable of running a large Fediverse instance.
Well Ruud who runs .world also runs Mastodon.world which is a fairly large mastodon instance, so he is somewhat of a known quantity and has experience running large Fediverse servers. His mastodon server has handled a large population and donations happen through Open Collective for transparency as well. He also runs Calckey.world though that is much smaller.
The danger in randomizing servers is that some smaller servers not only have less than 99% uptime but are also just run by random regular people who couldn't handle the increased load and/or have no desire or ability to keep the servers running long term. It could maybe work if the randomization occurs from within a vetted list.
Account migration is a feature that has been noted for the future and would indeed be very important since it would essentially make the entire network bulletproof. Being able to move instances and/or link accounts across multiple instances would create the necessary redundancy and reduce fears of choosing a smaller instance as home.
In addition to the backend, I'm not sold on the terminology used in the front end either, though visually it does look good.
Why call communities Magazines? Why am I starting a microblog when I press new Post? Why is upvote called Favorite and what does Reduce mean? And what the hell is Boost and how is it different from Favorite?
Still, the number one issue at the moment for sure is the slow federation and syncing with Lemmy. Communicating across different Lemmy instances is no problem, but Kbin<->Lemmy seems incredibly slow, with threads from Lemmy often lagging many hours behind when viewed from Kbin which makes it impossible to participate in conversations.
Oh man. You're breaking my heart here.
While this is always part of it, I've replayed them a couple of years ago and they still hold up. So much of their charm hasn't aged at all: writing, characters, story and voice acting. Irenicus is just as sick of a villain as he was 23 years ago.
I have no doubt in my mind this will be an amazing RPG, I just hope it will also be a great Baldurs Gate. I have so many memories of those games, and they have such a legacy that I hope this will be an actual sequel with a real connection and real returning characters (playable or at least prominent, not just mentions and references). No matter how great it plays, I will still be disappointed if this ends up being Divinity: Dungeons and Dragons.
Kbin doesn't have an API and so it's probably less straightforward to dev for. Plus Lemmy is older and more established. I believe ljdawson said in a comment somewhere that he'll work on Kbin integration somewhere down the line. I think that's the way it will go for most of the apps.
Yeah, keeping the content flowing will be the most important thing, and it's much less daunting than taking on moderator duties. Everyone on Kbin/Lemmy right now is basically an early adopter, so they might need to take more responsibility to keep momentum up. It's too much to ask people who usually just read news on their niche subreddits to suddenly start up their own community here, but everyone can take one step "up the ladder" so to speak, and we're already seeing this to some extent I think. Lurkers trying their best to be commenters, commenters putting up their own posts and regular posters starting their own communities.
Exactly. It's harder than it sounds to ask the right "why".