repo: fmrl_spec
action: commit
revision: 
path_from: 
revision_from: d78effe886146a1889b11c9160238119b4001f68:
path_to: 
revision_to: 
git.thebackupbox.net
fmrl_spec
git clone git://git.thebackupbox.net/fmrl_spec
commit d78effe886146a1889b11c9160238119b4001f68
Author: makeworld 
Date:   Thu Jan 6 17:52:15 2022 -0500

    Ban duplicate usernames

diff --git a/spec.md b/spec.md
index fe4f4d2235e25214c6aa935eb612ead4d2dacb64..
index ..0558fde2243a97093cd123fea4129f7c36be8f66 100644
--- a/spec.md
+++ b/spec.md
@@ -233,6 +233,8 @@ The server returns the schema described in [§User data](#user-data), but multip
 }
 ```

+Clients MUST NOT include usernames more than once, such as `?user=bob&user=alice&user=bob`. Servers MAY deduplicate usernames to avoid setting duplicate keys in the returned JSON. Servers MAY also generate the JSON normally, including duplicate entries.
+
 If the client makes the request with an `If-Modified-Since` header, the server MUST only return data for users that have been updated since the time in that header. Users whose status was updated previous to that time MUST NOT appear in the dictionary.

 The client can ensure no users will be removed simply by not including the header.

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