Michael Telatynski

The instructions were right where you select `Yes/No`:  Please follow those instructions rather than just uploading a tarball.

This happens entirely upstream of us. We just use https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file which Electron translates to the most appropriate mechanism for the given OS & DE.

The issue with upgrading spaces is the room upgrade API might not copy over the room_type field from the m.room.create event, I think Synapse has been updated to fix this...

Nope, I don't believe anyone has made one yet.

The issue is there's no way for a client to know if the server will have the correct behaviour, older Synapse versions and presumably non-Synapse HSes will not correctly copy...

@Mikaela the internals of what a room (/space) upgrade actually do are up the spec & server, the client just hits the /upgrade API. https://spec.matrix.org/v1.2/client-server-api/#post_matrixclientv3roomsroomidupgrade

https://spec.matrix.org/v1.4/client-server-api/#server-behaviour-16

https://spec.matrix.org/v1.4/client-server-api/#server-behaviour-16 still does not unfortunately copy space children over during an upgrade, and lacking a bulk state API and typical rate limits upgrading medium-large spaces is still infeasible.

> would Element be comfortable with exposing an upgrade option? That'd be a question for the product team unfortunately, its something we must be consistent about between the various Element...

This was done by user request in the first place, so now we're in a place where some users want it some don't so at best it may be a...