Replying to on mastodon.matrix.org
@matrix@mastodon.matrix.org This: https://discord.com/press-releases/discord-launches-teen-by-default-settings-globally
Remote
Yorusaka Miyabi
@ShadowRZ@miruku.cafe
sharkey 2025.4.7
Alt for @ShadowRZ@boiledscript.com@miruku.cafe
This account is used for vast majority of FOSS conversations on the fediverse.
8 Followers
6 Following
6 Posts
Replying to
@Frisk@woof.tech @matrix@mastodon.matrix.org
At least one point I do have to grant to Soatok though even with my expertise, despite terrible choice of repositories he has chosen as representation for his blog post, Matrix ecosystem does have an issue with using depreciated Olm library which again, is a security library still used in clients such as nheko and Neochat (both of which are the only ones I currently consider using).Migrating off libolm is these clients' developers' responsibility, I'm not sure where foundation can help here.
Ping @iamtakingiteasy@eientei.org What's your take on matrix-authentication-service and will you deploy it? This belongs to an ongoing effort to make authentication in Matrix OIDC based (seealso Are We OIDC Yet?)
Asking 'cause someone posted on Element X Android's issue based on the fact this application can't be used to login to your homeserver, due to Element X only supports SSO only instances using MAS for such authentication.
Personal note:
On Android, any invalid proxy configuration in http_proxy settings string would be sliently ignored and thus would meant direct connection 🙃
If you want to take this proxy string across FFI, either make sure the native code side throws away invaild proxy strings, or just don't try to feed this proxy string if the system told us we don't have proxy
Background: element-hq/element-x-android#4744 No more dangling :0 proxy breaks EXA ~
Replying to
@iamtakingiteasy@eientei.org To be fair, actually what Element X Android wants to talk to is the Matrix Authentication Service, it explictly doesn't support the SSO method you linked.
It links like this: Element X <-> Matrix Authentication Service <-> Synapse <-> Upstream IdP
Additionally The eventural plan is to inline MAS to be a part of Synapse (currently it's deployed alongside Synapse)
Replying to
@thibaultamartin@mamot.fr @lutindiscret@mastodon.libre-entreprise.com @matrix@mastodon.matrix.orghttps://github.com/matrix-org/matrix.org/issues/1000#issuecomment-1602556515 A issue was already opened before so I guess this is canonical response