cross-posted from: https://lemmy.world/post/4374751
I think this has negative effects on the threadiverse because it tends to keep user’s focus at lemmy.world and in general keeps users to stay in their bubbles
cross-posted from: https://lemmy.world/post/4374751
I think this has negative effects on the threadiverse because it tends to keep user’s focus at lemmy.world and in general keeps users to stay in their bubbles
The ideal flow isn’t people making “lemmy” accounts like reddit accounts. Take an Arsenal fan. When he finds out the lemmy instance called arsenal.club, he doesn’t have to immediately know what lemmy is or what federation is. He can sign up, view and participate in his local feed, which will be full of Arsenal related stuff. And then he can stick with it or find the full capabilities of federation
If they default to “All”, random news is gonna fill all the default feeds which is weird for a general user
If you are e.g. on lemmy.world, random news will also fill your feed with “Local”. Content-specific lemmy-instances are not the rule. The person you describe would sign up for an Arsenal-community and then yes, All as default would be confusing, but Local also. It should be Subscribed as default and All as next choice.
The subscribed feed would be empty and the All feed would be irrelevant in the Arsenal fan’s case.
Local would be full of posts from communities inside the Arsenal instance. Why would that be confusing?
It would be fine. Thing is there aren’t that many content-specific instances. The Arsenal-Lemmy-Server is a bad example to generalize upon
This is where we disagree. I have active accounts in 3 instances and none of them are general-purpose. I need local feed in all of them.
We don’t really need more general-purpose instances. There’s <10 right now and that’s good enough. But there’s >100 content-specific instances. I may be wrong on the numbers, I’ll run some analytics and get back
@_thisdot @blue_berry If you use IceCubes you can add multiple local feeds.