this post was submitted on 29 Jun 2023
98 points (100.0% liked)
Reddit Migration
145 readers
1 users here now
### About Community Tracking and helping #redditmigration to Kbin and the Fediverse. Say hello to the decentralized and open future. To see latest reeddit blackout info, see here: https://reddark.untone.uk/
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It isn't hard to sign up for. No one is saying that is the case. It gets confusing when people start talking about adding subscriptions from other instances and how you can copy and paste the link and subscribe. That right there is where 95% of the people on the internet stop caring.
If the developers of Lemmy and the wider Fediverse ever get that fleshed out in an intuitive way I think popularity will go pretty fast.
That and long term if there is a way for information to be collectively backed up so that if some owner shuts down an instance everything isn't gone.
The first step is completely different from anything else you've ever done
"Pick an instance to sign up for"
This does not compute. What is an instance? Why do I have to pick? Which one should I pick? Compared to
"Create an account at reddit.com" makes sense and is something everyone has done before.
It doesn't matter how simple the answers to those questions are, the fact that the very first step requires multiple explanations is huge, and will always be a barrier to entry.
This isn't really true, you already had to do this for email. Never heard of that being a barrier of entry.
My parents prefer to opt for local privacy/security focused email providers, while I go with gmail for the feature set and design. But I used to try out a few different ones to figure out which one works best for me. Still use a hotmail email for my Windows account.
I fail to see how this is different to the situation with lemmy/kbin instances.
99.9% of people just use gmail, and before that 99.9% used hotmail, etc. There's always been 'the one' that effectively everyone is on.
You're describing an internet that doesn't exist anymore and hasn't for decades.
Even a low barrier to entry tends to significantly improve the signal-to-noise ratio in discussions.
So, I'm fine with people that can't get past making a simple, almost irrelevant, decision as step 1 of gaining access... not gaining access.
Agreed. It still is a pain to follow subs on other instances, especially within Jeroba. I know you're supposed to copy the !sub@instance into the search field, but it never comes up.
For Lemmy, if nobody is subscribed to that community on your instance you have to copy the entire URL. E.g. you need to search for
https://instance.social/c/subin order to find [email protected].Once one person on your instance searches for it, then you can find it by searching [email protected].
I don't know why Lemmy works like that. Kbin doesn't have the problem; you can find things by searching
@[email protected]no matter what.Kbin doesn't presently auto-hyperlink the !sub@instance text.
I expect that it will in the future.
It will in the next update. See https://codeberg.org/Kbin/kbin-core/pulls/317
You don't need to do that if that community is already federating with your instance. If its not, it might take a little while for the federation to actually start after you make the search (based on the server infrastructure of your instance and the remaining queue). Try searching again after a bit and it should be there. These quriks should be solved as instances become more stable, and Lemmy/kbin gets further developed.
What is this about having to copy and paste a link to find subscriptions from other instances? I literally just pull up the community browser and set it to "all" and then search.
On Lemmy, if nobody is subscribed to a community on your instance, it doesn't appear in that view.
In order for it to appear, someone with an account has to go to the search bar at the top right of the page and type in the URL to the community manually. Then it'll appear after an initial search.
On large instances like Lemmy.world, you can almost guarantee someone has already done this for most popular communities - but newer/smaller communities may not appear because nobody on your instance has searched for them yet.
For smaller instances, there are likely multiple communities missing and you'd have no idea until you went to look for them.
Yes, that will show you all the communities/magazines that your instance has already discovered and have started federating with. But if it is a community that hasn't been discovered by your instance yet, you will need to search with the link for it to start federating. And once even a single user from an instance does that, the community will be visible to everyone else as well.
Yeah. Really, new admins should understand that they should be seeding their new instance, but the last couple of weeks have been... Kinda nuts? So, this won't really be an issue for most users long term. It'll be a thing for admins on small or niche sites that want to ensure they're discoverable and that their users can access the best communities.
Just be careful. That only works because your instance already knows about those other instances because someone already interacted with them. If you ever want to join a community on a non-popular instance, you might have to be the first person to search for it by copying and pasting.
That's cause over time people have added communities to your instances repitoire over time. Network effect, essentially, making it easier for each new user. Tbh, if new users are on a bigger instance this should be a non issue.
@sota2077 When I first came over to Kbin that's the thing I got hung up on, everything else I got used to quickly. There's plenty of smart people in the Fediverse, I'm sure someone will come up with a solution.
@metic
The question everyone was really asking was if will they will be able to make these quality of life changes before the Reddit API changes come into effect. The answer seems to be "no" unfortunately. It's a huge missed opportunity that may never come again.
Oh I have all the faith in the world that someone will come up with a solution eventually. I just assume it was never a major priority because of the userbase. With an explosion of users I'm sure they have a 100 things they want to improve and it is just a matter of time.
This can be alleviated a bit. If one person searches for an other-instance community by URL, it will become available for all other users through a normal search. So over time this becomes less of an issue, particularly if someone takes out some time to seed a bunch of these for their instance.