-
Notifications
You must be signed in to change notification settings - Fork 378
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
Matrix >= v1.0.0 limits display name field to 100 chars #4634
Labels
Component / Transport
Transport related issues
Comments
ulope
added
State / In discussion
Component / Transport
Transport related issues
labels
Aug 16, 2019
ulope
changed the title
Matrix >= 1.3 limits display name field to 100 chars
Matrix >= 1.2.1 limits display name field to 100 chars
Aug 19, 2019
ulope
added a commit
to ulope/raiden
that referenced
this issue
Aug 19, 2019
(Not mergable currently because of raiden-network#4634. Temporarily uses the base64 solution mentioned in the issue.) This updates our testing dependency to matrix-synapse 1.2.1. The Synapse config files generated by the integration tests have been updated to align with new / changed options. Additionally this no longer uses local TLS certificates speeding up tests. Fixes: raiden-network#3387 Required for: raiden-network#4292
Good news, the Matrix team increased the length limit to 256 chars: matrix-org/synapse#5906! Now we only need to wait for them to make a new release. I asked in the linked issue if there's an ETA for that. |
ulope
changed the title
Matrix >= 1.2.1 limits display name field to 100 chars
Matrix >= v0.99.5.2 limits display name field to 100 chars
Sep 23, 2019
ulope
changed the title
Matrix >= v0.99.5.2 limits display name field to 100 chars
Matrix >= v1.0.0 limits display name field to 100 chars
Sep 23, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 25, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 25, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 25, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 25, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 25, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 25, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 26, 2019
ulope
added a commit
to ulope/raiden-service-bundle
that referenced
this issue
Sep 26, 2019
ulope
added a commit
to ulope/raiden
that referenced
this issue
Sep 30, 2019
(Not mergable currently because of raiden-network#4634. Temporarily uses the base64 solution mentioned in the issue.) This updates our testing dependency to matrix-synapse 1.2.1. The Synapse config files generated by the integration tests have been updated to align with new / changed options. Additionally this no longer uses local TLS certificates speeding up tests. Fixes: raiden-network#3387 Required for: raiden-network#4292
LefterisJP
pushed a commit
that referenced
this issue
Oct 1, 2019
(Not mergable currently because of #4634. Temporarily uses the base64 solution mentioned in the issue.) This updates our testing dependency to matrix-synapse 1.2.1. The Synapse config files generated by the integration tests have been updated to align with new / changed options. Additionally this no longer uses local TLS certificates speeding up tests. Fixes: #3387 Required for: #4292
We upgraded to synapse 1.4.0rc1 for now. Once 1.4.0 is released we can switch to that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sub issue of: #3387
Problem Definition
synapse >= v1.0.0
introduced (matrix-org/synapse@d16c637) a length limit on the Userdisplayname
field of 100 characters.This breaks our use of this field as a way to publish hex encoded ecrecover signatures since those need
132
characters.Possible solutions
base64
encoding (which would fit at89
chars for a signature)avatar_url
field which has a limit of1000
charsAll but 1. would be backwards incompatible (which currently should be doable) and would need coordination with the light client (ping @andrevmatos).
The text was updated successfully, but these errors were encountered: