this seems so messed up. I like kbin, don’t get me wrong, but I consider this to be a bug, not a feature. When you have upvotes and downvotes one next to the other, you (a user) expect these 2 to do the exactly opposite action. Not one of them just add something in your favourites while the other starts negating another user’s karma.
you missed the point where the open source devs were in a constant race to adapt to all the google-“innovations” and actually troubleshoot on them which ends up demotivating
True. But in due time you’ll end up in situation where few of these (or maybe even one) becomes the “go to” community, because it has best/largest discussions - just like on Reddit. We’re still at the start of this journey. Also, the other instances are their “own thing”. Maybe that’s fragmentation, but essentially they might be aimed for completely different demographic (the users of that particular instance).
while technically you’re correct, what I see as different that I think needs improvement, is the discoverability. It is needed to somehow when I search for e.g. technology to also see the various federated “technology” communities. If I have to manually search for an instance, find the correct handle, then go search for this handle in my own instance and only after that to be able to subscribe, it adds a difficulty on the level that I may never manage to know about the existence of some other communities (magazines). Apart from that, I agree it is totally fine to just let them organically grow and it will sort itself out on which one I may want to participate more.
kind of agree. I cannot think of any way that this could be overcome. Something like having “default” communities but then this breaks the federalization. Where would this community be hosted and does this mean that there is a central entity? But still need at least a better search where one can easier discover communities from other instances. It is very tricky indeed
its not that simple. If for example you want to join m/technology and the community in your own instance is empty, a new user will think that there are not users/traffic. You need to explain them somehow that the m/technology@another-instance is different community even though that they share kind of the same name (first part of the name).
I don’t think this is realistic at all. It breaks the current philosophy of the fediverse where each instance can be both autonomous and federated. What would happen if for example an instance wanted to federate after they already had a couple accounts. Would they need to delete these users because the username exists? This is the reason that the second part (after the “@”) exists.
Also look at the email. Ofcourse it is possible to have the same name with users in other email services. It would be very weird not to be allowed to get the [email protected] because the [email protected] already exists.
What you are suggesting introduces and requires a central authority that would be responsible for that, but this again, breaks the philosophy of the fediverse itself.