Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Disable Registration Config Option #84

Merged
merged 4 commits into from
Feb 20, 2015
Merged

Conversation

erikjohnston
Copy link
Member

No description provided.

@dbkr
Copy link
Member

dbkr commented Feb 19, 2015

Will this not also prevent ASes from registering users?

@erikjohnston
Copy link
Member Author

Probably, it is a very blunt implementation mainly intended as a first cut for people setting up their own HS who are unlikely to be running ASes.

@NegativeMjark
Copy link
Contributor

Might want to say that it blocks AS signup in the help?
Otherwise LGTM.

@dbkr
Copy link
Member

dbkr commented Feb 20, 2015

If it's just a question of adding an "if login_type != LoginType.APPLICATION_SERVICE" and moving the code by a few lines, I think this would make this much more useful and less confusing.

@ara4n
Copy link
Member

ara4n commented Feb 20, 2015

+1 to dave

On 20 Feb 2015, at 11:35, David Baker [email protected] wrote:

If it's just a question of adding an "if login_type != LoginType.APPLICATION_SERVICE" and moving the code by a few lines, I think this would make this much more useful and less confusing.


Reply to this email directly or view it on GitHub.

@dbkr
Copy link
Member

dbkr commented Feb 20, 2015

Perfect. :)

erikjohnston added a commit that referenced this pull request Feb 20, 2015
@erikjohnston erikjohnston merged commit e944b76 into develop Feb 20, 2015
@erikjohnston erikjohnston deleted the disable_registration branch April 27, 2015 14:16
babolivier pushed a commit that referenced this pull request Sep 1, 2021
…h results (#84)

* Add a config option to prioritise local users in user directory search results (#9383)

This PR adds a homeserver config option, `user_directory.prefer_local_users`, that when enabled will show local users higher in user directory search results than remote users. This option is off by default.

Note that turning this on doesn't necessarily mean that remote users will always be put below local users, but they should be assuming all other ranking factors (search query match, profile information present etc) are identical.

This is useful for, say, University networks that are openly federating, but want to prioritise local students and staff in the user directory over other random users.

* Don't mix simple and english psql query types
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants