-
Notifications
You must be signed in to change notification settings - Fork 251
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
appservice: Rename virtual user to appservice user #1109
Comments
There's also the option of renaming to |
They're not really users, though, until they have been registered, right? So I suspect that just calling them "users" would be misleading. I have no problem with "virtual user" or "puppet user", as long as there is something making it clear that it's not completely a user out of the box. |
"Puppet" is an ecosystem term, not something in the spec – and the "virtual user" is mentioned twice in the spec, but it collides with the Hence the most fitting term is "appservice user", which makes it just "user" in the context of the appservice crate. |
virtual_user
to just user
Agree with @johannescpk. The other terms are more bridge terms than AS terms. I would call them appservice users. |
Currently the appservice crate calls the users for which identity assertion is performed "virtual users". There's no clear terminology how those users are called in the spec. The homeserver itself just sees them as users belonging to a specific appservice. So it would make sense to just call them users in the scope of the appservice crate, which would also remove the confusion around the difference of "virtual users" (identity assertion) and the "main user" (
sender_localpart
).The text was updated successfully, but these errors were encountered: