hypothesis: if too many early users sign up on mastodon.social instead of other instances, federation will end up becoming a second-class feature. (imagine what email today would look like if gmail had existed in the 90s.)

other instances need to be able to compete with mastodon.social for growth, or https://github.com/tootsuite/mastodon/issues/177 should be implemented.

@bcrypt Federation will never be 2nd class feature for me.

@Gargron @bcrypt I think that "too many users" is subjective (apart from scaling). If anyone thinks there are too many users around here, or too many douches, they can either move one, or run their own instance. This way, putting more pressure on any system, could help to balance the power over the federation as a whole.

Thoughts?

@tim @Gargron i am reminded of https://mako.cc/copyrighteous/google-has-most-of-my-email-because-it-has-all-of-yours as an example of too-many-users-on-one-node-of-a-supposedly-federated-system
@bcrypt @tim I have closed down registration on this instance to prevent this
@Gargron @tim i feel that was the right choice. i would like to run an instance but don't want the burden of maintaining it forever; giving users a migration strategy is a deal breaker for me running one
@bcrypt @tim @Gargron for me I would like to see a way to port follower-lists to other instances, I don't know if that's feasible but it would help being able to move and prevent supremacy of any one node
@tim @bcrypt @Gargron very cool to hear!
@bcrypt Late to the convo, but that's exactly what happened the first time OStatus went big-ish. Everything centralized around status.net, then identi.ca, which then turned into pump.io when Evan wanted to make his New And Improved thing (ironically just as W3C WG got underway iirc).