-
Notifications
You must be signed in to change notification settings - Fork 83
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
Remove unspecified 'success' parameter from requestToken responses #302
Conversation
11beb84
to
fd385c5
Compare
My personal theory is that this was just an accidental inclusion due to Ideally we would poke a tendril out and ask if any other clients/servers are using this before we remove it. Edit: I've asked in |
Is this waiting for a response or just someone to review the code (or are you already handling that @anoadragon453 ?) |
afaict folks in these rooms have said that they weren't using this parameter so I think this is just waiting for a review. |
Community people have already clarified that it's not being used in both clients nor servers, and it's been some time since we've asked now, so I think it's fine from that perspective. I forget if we asked Riot people though? |
I don't think we have, I'm asking internally rn. |
It looks fine for Riot Web at least, we don't use this parameter. |
The mobile apps' devs shared that it looks fine from their pov as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems that this won't break anything, and it is indeed not in the spec.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, actually, last thing. Could you specify when this was introduced in the newsfile? :)
It's always been there apparently, not sure it makes much sense to say so in the changelog. |
It doesn't look like it's ever been a thing in the spec, and we don't seem to be checking this parameter in Synapse.
It can be an issue to have this parameter around for servers that have the setting from matrix-org/synapse#7315 turned on and are delegating emails to an IS, because then you can figure out whether the server is lying to you just by checking on whether there's a
success
in the response.