Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://fietkau.social/users/julian/statuses/113397500852981421">Julian Fietkau (julian@fietkau.social)'s status on Thursday, 31-Oct-2024 06:39:15 JST</a><a href="https://fietkau.social/@julian" title="julian@fietkau.social"><img src="https://gnusocial.jp/avatar/77862-48-20230526103145.webp" width="48" height="48" alt="Julian Fietkau" style="position: absolute; left: 0; top: 0;">Julian Fietkau</a><div><a href="https://gnusocial.jp/notice/7636139" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://digitalcourage.social/@mro">@mro</a> <a href="https://seppo.social/aseppototry/">@aSeppoToTry</a> To test the split-domain handle on a remote actor, you can look up <a href="https://wrong.webfinger-canary.fietkau.software/canary">@canary</a> in your platform and see what handle it shows you. I just gave it a try, see attachment.</p><p>It currently shows the wrong hostname. That means it's using the ActivityPub ID to construct the handle, when the handle domain should be coming from the WebFinger result. See my checklist <a href="https://correct.webfinger-canary.fietkau.software/#developers" rel="nofollow noreferrer">https://correct.webfinger-canary.fietkau.software/#developers</a> or the SocialCG report <a href="https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/#reverse-discovery" rel="nofollow noreferrer">https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/#reverse-discovery</a> for details on how to fix it.</p><p>Btw: very cool project! 👍</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3907390#notice-7636141">In conversation</a><time datetime="2024-10-31T06:39:15+09:00" title="Thursday, 31-Oct-2024 06:39:15 JST">about 8 months ago</time> <span>from <span><a href="https://fietkau.social/@julian/113397500852981421" rel="external" title="Sent from fietkau.social via ActivityPub">fietkau.social</a></span></span><a href="https://fietkau.social/@julian/113397500852981421">permalink</a><h4>Attachments</h4><ol><li><label><a rel="external" href="https://gnusocial.jp/attachment/3377840">Seppo screenshot showing the canary account with the "wrong" handle.</a></label><br><a href="https://fietkau.social/system/media_attachments/files/113/397/486/209/225/313/original/45e05409e28b12a5.png" rel="external">https://fietkau.social/system/media_attachments/files/113/397/486/209/225/313/original/45e05409e28b12a5.png</a></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="http://attachment.It/">http://attachment.It/</a></h5><div></div></header><div></div><footer></footer></article></li><li><article><header><div>Domain not in remote thumbnail source whitelist: correct.webfinger-canary.fietkau.software</div><h5><a href="https://correct.webfinger-canary.fietkau.software/#developers">WebFinger Split-Domain Canary</a></h5><div></div></header><div>A detailed summary of split-domain WebFinger setups: how do they work and what do they mean for ActivityPub implementers?</div><footer></footer></article></li><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/#reverse-discovery">ActivityPub and WebFinger</a></h5><div></div></header><div>Identifiers in ActivityPub tend to be HTTPS URIs. The use of WebFinger (as defined in [RFC7033]) allows for discovery of an actor's identifier given a username and a hostname, which may be more socially salient or otherwise easier to communicate across various contexts and media. The username and hostname are resolved at the WebFinger endpoint of the hostname in order to discover a link to an actor associated with the user's account, and that actor similarly can be back-linked to the username and hostname.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Julian Fietkau (julian@fietkau.social)'s status on Thursday, 31-Oct-2024 06:39:15 JSTJulian Fietkau
in reply to
- Marcus Rohrmoser 🌻
@mro @aSeppoToTry To test the split-domain handle on a remote actor, you can look up @canary in your platform and see what handle it shows you. I just gave it a try, see attachment.
It currently shows the wrong hostname. That means it's using the ActivityPub ID to construct the handle, when the handle domain should be coming from the WebFinger result. See my checklist https://correct.webfinger-canary.fietkau.software/#developers or the SocialCG report https://www.w3.org/community/reports/socialcg/CG-FINAL-apwf-20240608/#reverse-discovery for details on how to fix it.
Btw: very cool project! 👍
In conversationabout 8 months ago from fietkau.socialpermalink
Attachments
1. Seppo screenshot showing the canary account with the "wrong" handle.
  https://fietkau.social/system/media_attachments/files/113/397/486/209/225/313/original/45e05409e28b12a5.png
2. No result found on File_thumbnail lookup.
  http://attachment.It/
3. Domain not in remote thumbnail source whitelist: correct.webfinger-canary.fietkau.software
  WebFinger Split-Domain Canary
  A detailed summary of split-domain WebFinger setups: how do they work and what do they mean for ActivityPub implementers?
4. No result found on File_thumbnail lookup.
  ActivityPub and WebFinger
  Identifiers in ActivityPub tend to be HTTPS URIs. The use of WebFinger (as defined in [RFC7033]) allows for discovery of an actor's identifier given a username and a hostname, which may be more socially salient or otherwise easier to communicate across various contexts and media. The username and hostname are resolved at the WebFinger endpoint of the hostname in order to discover a link to an actor associated with the user's account, and that actor similarly can be back-linked to the username and hostname.

Public

Embed Notice

HTML Code

Corresponding Notice