I largely agree - the fediverse needs less friction if it wants widespread adoption. That’s part of the reason why I wound up on .world. It was easy. I suspect I’m not alone here.
The other bit challenge is that each instance can have identically named communities, which drives fragmentation and makes each community seem less active. I dabble in photography, so I’ll use some examples from that.
Reddit has this problem too, but there can only be one /r/photography. There are derivative communities like /r/streetphotography and /r/askphotography, but the original sub is unlikely to move/change.
By design the fediverse can have many /c/photography communities. In the case of photography there are three or four “big” ones and a bunch of smaller ones. There are also all the derivative communities, some of which are doing better than the ‘root’ community. One example of this is [email protected].
I’m not sure what a good solution is, especially when you start talking about “the same” community on multi-inatance. One of the design goals of the fediverse was to enable that should some instance go off the rails.
I largely agree - the fediverse needs less friction if it wants widespread adoption. That’s part of the reason why I wound up on .world. It was easy. I suspect I’m not alone here.
The other bit challenge is that each instance can have identically named communities, which drives fragmentation and makes each community seem less active. I dabble in photography, so I’ll use some examples from that.
Reddit has this problem too, but there can only be one /r/photography. There are derivative communities like /r/streetphotography and /r/askphotography, but the original sub is unlikely to move/change.
By design the fediverse can have many /c/photography communities. In the case of photography there are three or four “big” ones and a bunch of smaller ones. There are also all the derivative communities, some of which are doing better than the ‘root’ community. One example of this is [email protected].
I’m not sure what a good solution is, especially when you start talking about “the same” community on multi-inatance. One of the design goals of the fediverse was to enable that should some instance go off the rails.