From b609a5b4b756652e21f6849d72f90878808783e1 Mon Sep 17 00:00:00 2001 From: Charles Iliya Krempeaux Date: Fri, 17 Nov 2023 10:24:12 -0800 Subject: [PATCH] acct URI --- acct-uri.html | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/acct-uri.html b/acct-uri.html index b4b8b03..3cd6907 100644 --- a/acct-uri.html +++ b/acct-uri.html @@ -49,6 +49,58 @@ acct:reiver@changelog.ca If you are a programmer / software engineer / software developer / etc, then you may need to be aware of acct URIs, and have some level of understanding of them.

+
+

Resolving

+

acct URI

+

+ Part of the process of resolving a Fediverse ID transfomrs a Fediverse ID into an acct URI. + (And then using that acct URI version of the Fediverse ID makes a request to WebFinger.) +

+

+ Here is an example of transforming a Fediverse ID into an acct URI: +

+
+
+     at sign
+       ↓
+       @joeblow@example.com ← Fediverse ID
+
+   acct:joeblow@example.com ← acct URI
+       ↑
+  no at sign
+
+
+

+ A client would then make a request to: +

+
+
+https://example.com/.well-known/host-meta
+
+
+

+ To discover what the (template) URL for WebFinger is. + And then, for example, if it is at: +

+
+
+https://example.com/.well-known/webfinger?resource={uri}
+
+
+

+ Then make a request to: +

+
+
+https://example.com/.well-known/webfinger?resource=acct:joeblow@example.com
+
+
+

+ This WebFinger implementation could accept whatever it wants. + It doesn't have to restrict itself to what is specified by the IETF RFC-7565 (The 'acct' URI Scheme) specification. + BUT — +

+

See Also