Do you want those people who can't even make an account here anyway? Lol
In all seriousness, SSO is a thing and maybe the devs are already looking into it. Google, Facebook. Git, and more all have ways to sign in to services for you. I wouldn't vote to use them given the ideals of why people are moving to these platforms, but if someone wants to use their apple account to sign in here and that makes it easy for them. I'd be happy for it's implementation.
this post was submitted on 20 Jun 2023
0 points (NaN% liked)
Reddit Migration
2 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
I guess that is the silver-lining, we can weed out people that wouldn't be able to contribute anyway. It's just maddening that there are even people like that out there. I kind of gave up on helping people bridge the gap from reddit to here.
I think the basics of posting a few links and then leaving it at that is good enough. Eventually it will get easier and we will get more users, best to not overload the servers now anyway
Ok, I get that the fediverse is complicated if you think deeply about all the interconnectivity and federation etc, but there is no reason you even have to think about any of it
you must be kidding. there is no reason to think about that?
to find communities/magazines you have to use some 3rd party tools (you may be lucky and see something in the "all" feed, but that is not guaranteed), then when you find it, you can't just click subscribe, you have to grab the url, go back to another tab where you are logged into your instance and subscribe by manually constructing the url, or pasting the url somewhere (maybe, haven't tried that way).
don't take me wrong, i am fan of open source, which is why i am here, but if you don't see how this is complicated for average non-tech-savy user, then i am not sure what to tell you.
I don't see how it's hard for a non-tech-savvy user to use. The actual usage is near-identical to reddit. Pretty much the only hurdle in that regard is trying to subscribe to magazines on other instances that haven't been synced yet. Other than that? It works the same as reddit. If you think kbin is too hard, how tf were you using reddit?
It is confusing. Simple as. I have an account on lemmy dot ca, but I don't understand how to view or participate in kbin content so I just don't
The funny part is, you're viewing and participating in kbin content right here. This is a thread posted to kbin. My reply will look to you as if it was made in lemmy, but it's not. I have a kbin account, and that's the magic at work.
The best analogy I heard so far is email; everyone gets that you can send an email from gmail to outlook. We are just not used to that websites can interconnect with each other but give it some time and it will be second nature to people
Please stop with the email analogy. It really doesn't help with anything. You send emails to an email address, people don't think of the back end of that process at all and can't make an analogy to social media where posts just... go out into the ether.
The only reason this is confusing is that tech-heads in these services can't shut up about federation despite federation being largely irrelevant to the experience. The fact that the poster above didn't even notice that the interaction is happening cross-service but still was confused about how to interact cross-service tells you that the way to help people get over how "hard" understanding federation is would be to shut up about it.
I mean, that won't help with people not being willing to just make an account on a place at all, but yeah, everybody is so pleased about the interoperability thing that they make the day-to-day use of federated services seem a lot more convoluted than it is in practice.
I actually agree. Nobody explains DNS to people trying to understand how mail works. They don't need to understand MX records, SPF records, DMARC, DKIM, or anything. All they need to know is sign up and how to use the To: field to start sending emails. Hell - you don't even need to and probably don't want to explain the purpose of the CC or BCC fields at this point either.
If a user is trying to actually understand the underlying technology then the email analogy can be a first introduction. But if someone is technical enough to be trying to learn it's better to just teach them about ActivityPub.