“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?
Federated logins make sense for forums and websites where you have access to content such as PeerTube.
For forums, logging into the forum with your fediverse account would actually be ideal since you can use a forum-style interface to navigate the topics, which would be easier than trying to navigate the same topics on Mastodon. Same thing with PeerTube. You may want to watch videos on PeerTube and comment right on their website without creating a PeerTube account. With federated single sign on, you can post with your existing fediverse account.
We have that on Hubzilla and it is called OpenWebAuth. We can log into other instances and comment directly on their instance as ourselves after logging in.
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?
Federated logins make sense for forums and websites where you have access to content such as PeerTube.
For forums, logging into the forum with your fediverse account would actually be ideal since you can use a forum-style interface to navigate the topics, which would be easier than trying to navigate the same topics on Mastodon. Same thing with PeerTube. You may want to watch videos on PeerTube and comment right on their website without creating a PeerTube account. With federated single sign on, you can post with your existing fediverse account.
We have that on Hubzilla and it is called OpenWebAuth. We can log into other instances and comment directly on their instance as ourselves after logging in.