I think this is the biggest obstacle to any incoming user, unless there is a way to have the community URL automatically change to whatever instance you’re logged into.
So then could you have, say, a 3D printing “subreddit” on lemmy.ml as well as lemmy.world? And if you had no idea of the one on lemmy.ml, you would never see the posts submitted there, correct?
Edit: I think I understand now. Someone correct me if I’m wrong. You would be able to see it on your instances “all” page only if one other person from your instance went and subscribed to that other community (from the other instance). So it essentially grabs the content from that other instance and shows it on yours, without actually having to go and sign up for that other instance.
I think what threw me is communities on the same server allowed me to just click subscribe but ones on other servers I had to click through, expand the sidebar THEN I could subscribe. That’s a bit cryptic on top of the login only working on the initial server but I figured it out.
There’s an open issue on GitHub where someone was suggesting moving that subscribe button
And in general, you wouldn’t need to login anywhere else
Assuming you’re not trying to access a community from one of the instances that’s blocked, your instance should be enough to access everything
deleted by creator
I think this is the biggest obstacle to any incoming user, unless there is a way to have the community URL automatically change to whatever instance you’re logged into.
So then could you have, say, a 3D printing “subreddit” on lemmy.ml as well as lemmy.world? And if you had no idea of the one on lemmy.ml, you would never see the posts submitted there, correct?
Edit: I think I understand now. Someone correct me if I’m wrong. You would be able to see it on your instances “all” page only if one other person from your instance went and subscribed to that other community (from the other instance). So it essentially grabs the content from that other instance and shows it on yours, without actually having to go and sign up for that other instance.
I think what threw me is communities on the same server allowed me to just click subscribe but ones on other servers I had to click through, expand the sidebar THEN I could subscribe. That’s a bit cryptic on top of the login only working on the initial server but I figured it out.
There’s an open issue on GitHub where someone was suggesting moving that subscribe button
And in general, you wouldn’t need to login anywhere else Assuming you’re not trying to access a community from one of the instances that’s blocked, your instance should be enough to access everything