Everyone, I want to say a big thank you! The example you gave me really helped me out. For the sake of clarity, I indeed only need 1 account, and I’ll stick to kbin for now.
The things I still keep in mind, and feel free to comment if any of this is wrong or stupid 😅
- maybe it’s better having 1 login on 1 smaller and more local instance than a huge one like kbin.social. If I get it right, kbin.social is a great instance to minimise the « entry cost », but the best is to keep instances reasonably small. However, the smaller the instance is, the bigger the risk is that it disappears (together with your account).
- on the short term, I will closely follow the developments of those apps!
- on the longer term, I’m curious whether there is a benefit to have 1 single account for all fediverse services (like mastodon AND kbin). On the one hand, it makes perfect sense, with « distributed login ». On the other hand, putting all your eggs in 1 basket seems to be , on the client side, the opposite of what we want to do at server at side: spread! In that aspect, profile backups will probably be key!
Thanks again guys!
The thing is (IMHO), fediverse communities are spread but they are not « fragmented ». That’s the beauty of it, no matter where they are, they’re not isolated from each other.
Forever it’s been like that, even before the internet. Communities come and go, and seeing them go can be sad… but when hosted centrally by large corporations, maybe those communities were not at a healthy place. In that case, the place dies, the communities go someplace else, I do hope they go to a healthy place like the fediverse, and they can live « prosper » (socially instead of financially)?