“Maybe if I click login it will somehow do federated login?” Nope.
Ok what if I copy the /post/<id> from the URL and paste it in my instance. Nope 404.
Yeah, these two are major pain points. They are unintuitive, i would argue. If you click “login”, it should ask you for your username. If your username is lisa@bumblebee.com, it takes you to bumblebee.com and lets you finish the login process there.
The /post/<id> should have been fixed a while ago. I don’t know why it wasn’t.
I don’t think the lack of “federated login” is unintuitive. You wouldn’t expect going to gmail.com and logging in with your Yahoo credentials to work, right?
Having a “federated login” service would probably either add a ton of complexity for instance owners, or someone would implement some super naive and insecure centralized solution, leading to a bunch of people’s creds getting stolen.
Getting the post/<id> thing to work across instances would be a pain too, because it would require instances to all coordinate post IDs to ensure collisions don’t happen, since far as I can tell, the id in the URL isn’t globally unique.
The motivation for federated logins would be that often you’re linked to a post on another instance, such as https://someinstance.net/post/12345 now when i click on that, in the web browser it opens on the other instance, and now what if i want to comment?
I agree that that specific use case is a pain, but I don’t think federated logins are the fix for it. Rather, links to posts on other instances should be automatically translated to a link to the federated version of that post on your home instance, such that you can interact with that post without having to re-log-in. There’s a bunch of issues in the Lemmy GitHub project related to this, so hopefully it gets implemented soon.
In my opinion, federating logins kind of defeats one of the main purposes of federation though, which is to give the user control over where their user information lives.
Yeah, these two are major pain points. They are unintuitive, i would argue. If you click “login”, it should ask you for your username. If your username is
lisa@bumblebee.com, it takes you tobumblebee.comand lets you finish the login process there.The
/post/<id>should have been fixed a while ago. I don’t know why it wasn’t.I don’t think the lack of “federated login” is unintuitive. You wouldn’t expect going to gmail.com and logging in with your Yahoo credentials to work, right?
Having a “federated login” service would probably either add a ton of complexity for instance owners, or someone would implement some super naive and insecure centralized solution, leading to a bunch of people’s creds getting stolen.
Getting the
post/<id>thing to work across instances would be a pain too, because it would require instances to all coordinate post IDs to ensure collisions don’t happen, since far as I can tell, the id in the URL isn’t globally unique.The motivation for federated logins would be that often you’re linked to a post on another instance, such as https://someinstance.net/post/12345 now when i click on that, in the web browser it opens on the other instance, and now what if i want to comment?
I agree that that specific use case is a pain, but I don’t think federated logins are the fix for it. Rather, links to posts on other instances should be automatically translated to a link to the federated version of that post on your home instance, such that you can interact with that post without having to re-log-in. There’s a bunch of issues in the Lemmy GitHub project related to this, so hopefully it gets implemented soon.
In my opinion, federating logins kind of defeats one of the main purposes of federation though, which is to give the user control over where their user information lives.