repo: fmrl_spec
action: commit
revision: 
path_from: 
revision_from: 761c692ef9248adbf46ab4db09b878810a2b7767:
path_to: 
revision_to: 
git.thebackupbox.net
fmrl_spec
git clone git://git.thebackupbox.net/fmrl_spec
commit 761c692ef9248adbf46ab4db09b878810a2b7767
Author: makeworld 
Date:   Sun Jan 16 00:49:24 2022 -0500

    Support fmrl URIs

diff --git a/spec.md b/spec.md
index 814e0b0d57f4b911905a11d7f2401d4024e4539e..
index ..8288cf63985bd33f7882d4217496e63c634c6339 100644
--- a/spec.md
+++ b/spec.md
@@ -57,7 +57,9 @@ Servers MUST reject attempts for account creation with usernames that are invali

 ## Global Usernames

-To refer to an fmrl user, their full username must be used. Like email, this includes the server. The canonical way of doing this is as follows: `@username@example.com`, where `example.com` is the fmrl server that the user `username` has an account on.
+To refer to an fmrl user, their full username must be used. Like email, this includes the server. The canonical way of doing this is as follows: `@username@example.com`, where `example.com` is the fmrl server that the user `username` has an account on. Note the leading `@`, which differentiates it from email, and is more similar to social media handles.
+
+The other valid way of doing this is: `fmrl:username@example.com`. Note the leading `@` is dropped. This is a URI, so this can be used to link to fmrl users in Web pages or other hyperlinked media. fmrl clients can then choose to support opening these kinds of URIs, to display the user's status, and/or ask if you'd like to follow them.

 Clients MUST accept these kinds of strings for following or viewing users, and MUST NOT accept other methods.

-----END OF PAGE-----