Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User Directory documentation is confusing and misleading. #1108

Closed
Half-Shot opened this issue Jan 25, 2018 · 8 comments
Closed

User Directory documentation is confusing and misleading. #1108

Half-Shot opened this issue Jan 25, 2018 · 8 comments
Labels
spec-bug Something which is in the spec, but is wrong

Comments

@Half-Shot
Copy link
Contributor

Half-Shot commented Jan 25, 2018

73118b6#diff-a9b4f5ce35bb739be9f3fe515413e401R34

This API performs a server-side search over all users registered on the server.

Implies that the search will cover the whole server, including the users I have not met.

It searches user ID and displayname case-insensitively for users that you share a room with or that are in public rooms.

Implies that the search will cover only users I have met, including those from other servers.

From what I can see, the synapse implementation does the latter of the two things but maybe it's a combination of both. Either way, the two sentences seem contradictory to me and I think it warrants further explaining.

As a person reading the spec, I'd assume it would be searching only my local server for users I have met.

@ghost
Copy link

ghost commented Jan 25, 2018

It searches user ID and displayname case-insensitively for users that you share a room with or that are in public rooms.

My reading of this says that as soon as you're in a room which is not invite-only, you can be found, even by people not in the room. I agree it could be clearer though.

@Half-Shot
Copy link
Contributor Author

@Matrixcoffee The statement on it's own makes sense. It's the fact that you've also got "
This API performs a server-side search over all users registered on the server.
" which says something entirely different

@t3chguy
Copy link
Member

t3chguy commented Jan 30, 2018

/me is bad at wording - sorry :(

@maxidorius
Copy link
Contributor

And technically, only synapse perform the search that way, it doesn't have to be done that way.
It can be any algorithm or any policy in effect to decide what will be returned exactly, surely?

@richvdh
Copy link
Member

richvdh commented Feb 6, 2018

if anyone can suggest better wording, that would be appreciated.

Certainly what synapse does is not necessarily definitive here and details may be up to implementation or policy - so some aspects may be better phrased as recommendations or suggestions in the description.

@richvdh richvdh added the spec-bug Something which is in the spec, but is wrong label Feb 6, 2018
@Half-Shot
Copy link
Contributor Author

(I seem to be forever finding GH issues that I have missed)

@maxidor I would very much like for this to define the behavior we should expect. If I write a client that says "this is a list of all known users" I would like for that to be the case. If you want to deviate from a behavior, use a parameter.

@maxidorius
Copy link
Contributor

@Half-Shot then I think you should be very specific about list of known users - known to whom? the user? the sysadmin? the hosting system?
And do you include bridged networks? if not, why? etc.

@t3chguy
Copy link
Member

t3chguy commented Feb 26, 2018

That's made more difficult by even synapse having a config toggle for what that means.

@turt2live turt2live added this to To do: client-server (prioritized) in August 2018 r0 Aug 14, 2018
turt2live added a commit to turt2live/matrix-doc that referenced this issue Aug 27, 2018
The homeserver can implement its own algorithm, but is suggested to ensure the requesting user can reasonably see the other users.

The text is intentionally left vague for whether or not the API is local users only to give the homeserver some flexibility in this area.

General cleanup is also included in this commit.

Fixes matrix-org#1108
@turt2live turt2live moved this from To do: client-server (prioritized) to In review (just the issues) in August 2018 r0 Aug 27, 2018
August 2018 r0 automation moved this from In review (just the issues) to Done (this list will be incomplete) Aug 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec-bug Something which is in the spec, but is wrong
Projects
No open projects
August 2018 r0
  
Done (this list will be incomplete)
Development

No branches or pull requests

4 participants