this post was submitted on 08 Jul 2023
153 points (100.0% liked)

Fediverse

28251 readers
760 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

Why can’t we have federated identity to login into fediverse instead of creating login for each instance?

you are viewing a single comment's thread
view the rest of the comments
[–] muddybulldog@mylemmy.win 16 points 1 year ago* (last edited 1 year ago) (5 children)

There's a difference between a federated identify and single-sign on. Your identity /u/mango_master@lemmy.world IS federated. You don't need to have a separate login for each instance. You can use that identity to interact with any instance much the same way I am using my federated identity to currently respond to you.

[–] mtdyson_01@kbin.social 7 points 1 year ago (1 children)

I do not have the same experience. If I want to interact with a different instance then I have to login to that instance. Granted I'm very new to Lemmy but so far the apps are not quite there yet and exploring the fediverse is difficult. Searches are useless unless you know exactly what instance you need to find what you're looking for.

[–] muddybulldog@mylemmy.win 6 points 1 year ago* (last edited 1 year ago) (1 children)

I understand. It really comes down to your entry point. For example, as long as I'm viewing the community/user/content via my instance I can interact; e.g. I'm replying to a post on https://mylemmy.win/post/114914 ; you, on the other hand are replying to https://kbin.social/m/fediverse@lemmy.world/t/158389/why-can-t-we-have-federated-identity . Since we're viewing from our own instances we can interact. If either of us goes directly to the canonical URL, https://lemmy.world/post/1194109 , we'd be forced to login. It's all the same post, just different points of entry that muddy the user experience.

[–] Rahkshi@lemmy.world 2 points 1 year ago

As a new lemmy user this has made a lot of sense! Thanks.

[–] wetferret@lemmy.world 2 points 1 year ago (1 children)
[–] sab@kbin.social 1 points 1 year ago (1 children)

Should be @mango_master if all is working correctly, actually ;)

The threadiverse is a bit complicated since there needs to be a way of distinguishing between users and groups, but the @user@host.org format is standardized across the fediverse.

[–] muddybulldog@mylemmy.win 2 points 1 year ago* (last edited 1 year ago) (1 children)

It's funny because using the /u/ format seems to work just fine in the web interface, creating the proper link. Typing it out in the @ format doesn't automatically create the hyperlink when I type it, but yours works just fine. ¯\(ツ)

[–] sab@kbin.social 1 points 1 year ago

Also the /u/ format works when viewed in the Lemmy web interface, but not necessarily inside apps or from other federated services. :)

It also probably doesn't count as a mention, so the user won't be notified even if they have that enabled in the settings.

[–] masterspace@kbin.social 2 points 1 year ago

I think what they mean is identity that is coupled to them the person and not whichever instance they choose to sign in on.

[–] something_random_tho@lemmy.world 1 points 1 year ago (3 children)

This works great for apps. But I want to use the web interface to post a reply to content that’s not on my home instance. I can’t do that easily.

[–] muddybulldog@mylemmy.win 2 points 1 year ago

Gotcha. As others have already mentioned it is obtuse. If you end up at the post via your own instance it works but if someone links directly to the canonical post then you get confronted with needing to login. e.g. I see this post as https://mylemmy.win/post/114914, so I can interact just fine whereas if someone sent me the link to https://lemmy.world/post/1194109 (same post, different entry point) I'm stuck.

[–] mmaramara@kbin.social 0 points 1 year ago (1 children)

What interface are you using now? I'm responding to this thread from kbin.social instance usin kbin webclient

[–] something_random_tho@lemmy.world 2 points 1 year ago (1 children)

If you post a link to this, then I click that link, I am unable to reply directly, since I am on lemmy.world. I would need to first track down the equivalent post in my instance to reply. SSO solves this

[–] mmaramara@kbin.social 3 points 1 year ago

Oh I see. Yeah, there could be a feature (a browser addon would work too) that reads the webpage meta data before opening it, and pops a "Open in kbin/lemmy/whatever?" window.

[–] mack123@kbin.social 0 points 1 year ago (1 children)

That should just work. You view the post on your own instance and reply there. That reponse trickles to the other instances.

It may take a while to propagate though. The paradigm is close to that of the ancient nntp news groups where responses travel at the speed of the server's synchronisation. It may be tricky for rapid fire conversation, but works well for comments of articles.

[–] vaguerant@kbin.social 3 points 1 year ago (1 children)

I believe they're talking about a situation where somebody is like ...

Wow, everybody check out this amazing thread! https://someother.instan.ce/post/1194109

Anybody who sees that link and is not already from someother.instan.ce now has to track down that post on their home instance in order to interact with it, which is a bad experience. It's not the absolute worst thing in the world, like the home URL for the discussion we're in right now is https://lemmy.world/post/1194109 and if you paste that URL into your local domain's search it should find you the relevant discussion locally, but it still kinda sucks. In theory this would be sort of solve-able on the server end by having it search for any instance links behind the scenes and re-write other people's links to point to the equivalent page on your own instance, but right now there's no "nice" way to handle that situation.

[–] mack123@kbin.social 3 points 1 year ago

Agreed on your point. We need a way to identify those links so that our browser or app can automatically open them through our own instance.

I am thinking along the lines of a registered resource type, or maybe a central redirect page, hosted by each instance, that knows how to send you to your instance to view the post there.

I am sure it is a problem that can be solved. I would however not be in favour of some kind of central identity management. It is to easy a choke point and will take autonomy away from the instances.