- From: Manton Reece <manton@micro.blog>
- Date: Tue, 26 Mar 2024 13:04:21 -0500
- To: "public-swicg@w3.org" <public-swicg@w3.org>
- Message-ID: <ec18182acb960d864e41d4c14b1840a7c52eaa46@hey.com>
I agree it does seem straightforward to just pass the URL for the domain name to WebFinger. I don't think that is redundant, because an actor ID might still be a unique, longer URL than just the domain name. In other words, you might have: Fediverse handle: @user.com WebFinger: resource=https://user.com Actor: https://user.com/activitypub This is convenient because it moves the content-negotiation pieces away from the user's home page, which might be a blog or something not entirely ActivityPub-powered. That still leaves what to do about "preferredUsername". Should it be blank? Should it be "_" as Nostr uses? Should it be the domain name itself, similar to how Bridgy Fed uses @user.com@user.com fediverse handles? — Manton On March 26, 2024, Marius <marius@federated.id> wrote: > That should already possible if you use[1] ?resource=https://user.com > (and > in my opinion could be used also for passing full actor IDs[2]). > > However I think this mechanism is somewhat redundant because if > the actor id is already known as https://user.com (from the > perspective > of the service/client) discovery should not really be needed. > > /Marius >
Received on Tuesday, 26 March 2024 18:04:28 UTC