@nitram there is a campaing going on which is about to buy twitter be a collective coop. It might be good start to engage with those ppl. #buytwitter #buymedium
Also writing an article pointing out why the idea of buying twitter isn#t that great then hyped.
The main argument for twitter sofar is the userbase.
...so something which can be fixed through just starting to use it. I could imagine that behind the campaign might be nothin but financial interest.
...or to show the world what big coups a #coop can do. ....not shure
@paulfree14 @nitram a lot of this is just due to people living in a limited paradigm, the assumption being that there must be some central company or organisation running the show. Instead of buying Twitter they could just have a campaign to move to !gnusocial or #Hubzilla or even #ZeroMe. ZeroMe doesn't even require servers.

But there are no technocelebs breathlessly extolling the virtues of any of these genuine Twitter alternatives.
@bob @paulfree14 @nitram here, ease of use and consistency is one of the most relevant issue. I guess that given the current status of the fediverse, we're not "there" yet.
Fragmentation is not a bad thing per se but every instance with the goal of shifting the public use should aim to a consistent experience.
@olistik @nitram @paulfree14 that's another of those paradigm things. In a closed centralized system such as Facebook or Twitter total consistency can be imposed at all times. But in a federated or peer-to-peer system users can customize their installs such that there might not be global consistency.
@bob @paulfree14 @nitram this is why I don't consider fragmentation an absolute issue. There's space for strong customizations but also for instances, like IMHO Mastodon, that tries to appeal those people more used to the ease of use of centralized systems.
@paulfree14 @bob @nitram In the context of such instances it's better to provide a transition as smooth as possible so that people just have to take into account *only* that they could use the same credentials across different instances, preserving a consistent experience.
@olistik @paulfree14 @bob the consistency really is an issue that needs to be tackled, so far what i dislike the most is for ever gnusocial instance i need to make a new account, i would love to be able to use my account from @gnusocial.de to comment follow, requip on other instances. I think a great solution would be if the gnusocial instance automatically selects the most recently used gnusocial account from the entire network and to have a simple gnusocial account selector where you can select your accounts of different instances like a dropdown menu. like:
@ nitram @ gnusocial.de
@ nitram @ gnusocial.net 
......
@nitram @olistik @paulfree14 You don't need to create an account for each gnusocial instance. Just remote follow.
@nitram Here's @jcaktiv's #remotefollow #HowTo qttr.at/13b6 Remote posts will appear in your TL where you can fave them. @bob
@mcscx @jcaktiv @bob i understand that, it would be nice to simplify this process and be able to use the same account on ever gnusocial instance :D and have a universal account selecter where you can easily switch between other gnusocial accounts that could be from other instances
@nitram @bob @olistik  I would love to see a SSO or something simliar (https://en.wikipedia.org/wiki/Single_sign-on)
@paulfree14 @bob @olistik disroot uses something like that, they use https://github.com/pwm-project/pwm im not exactly sure if this could be comparable to the #fediverse or even posible to implement