You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
about Android Windows clients.
I encountered some problems when deploying the project in China:
I want the client to be able to start up without network at any time,
because it is very necessary in some special regions. For example,
the current client will connect to the default home server at startup,
but it will fail to start when used in an area with limited network access.
If offline startup is supported, I can easily switch home servers,
instead of building a new client (which is difficult and troublesome for an ordinary user)
I want to support custom service address of jitis call parts in the Settings (such as self-deployment),
because the default service cannot be accessed normally in special regions.
While this configuration is supported for self-deployment on the web, it is not available on the client.
Again, services such as widgets and identity servers are not accessible due to network issues and should require a self-deployed solution.
Up to now, in addition to the web self-deployment can solve part of the problem,
but there is no effective enough help on the client side.
There are legal problems in building mirror agent services in China,
so supporting more optional self-deployment is undoubtedly a better choice.
I would submit the same issues to other element client projects as well,
but let me know if this causes confusion or is unnecessary.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
about Android Windows clients.
I encountered some problems when deploying the project in China:
I want the client to be able to start up without network at any time,
because it is very necessary in some special regions. For example,
the current client will connect to the default home server at startup,
but it will fail to start when used in an area with limited network access.
If offline startup is supported, I can easily switch home servers,
instead of building a new client (which is difficult and troublesome for an ordinary user)
I want to support custom service address of jitis call parts in the Settings (such as self-deployment),
because the default service cannot be accessed normally in special regions.
While this configuration is supported for self-deployment on the web, it is not available on the client.
Again, services such as widgets and identity servers are not accessible due to network issues and should require a self-deployed solution.
Up to now, in addition to the web self-deployment can solve part of the problem,
but there is no effective enough help on the client side.
There are legal problems in building mirror agent services in China,
so supporting more optional self-deployment is undoubtedly a better choice.
I would submit the same issues to other element client projects as well,
but let me know if this causes confusion or is unnecessary.
Beta Was this translation helpful? Give feedback.
All reactions