element-hq / element-hq/element-meta
Riot should do local echo for state events
- Dominant language
- No language data
- Stars
- 112
- Forks
- 25
- Avg merge
- 6h 6m
- Merged PRs (30d)
- 4
Description
[](https://www.bountysource.com/issues/45214922-riot-should-do-local-echo-for-state-events-on-slow-connections?utm_source=45214922&utm_medium=shield&utm_campaign=ISSUE_BADGE)
### Description
If your homeserver is slow (like mine) or your connection is sub-par (like mine), it can be frustrating to change room settings (and other settings, however room settings are more common) because Riot doesn't assume the changes until the event lands in /sync.
With Riot knowing the permission levels required to change settings, and it being the point of interaction for the user, it can be fairly safe to assume that some settings will land successfully on the homeserver, and Riot can represent those changes before hearing about them.
For instance, changing the room name/topic can be frustrating and/or confusing to users on slower connections/servers. By going into the settings, changing the room name/topic, and hitting save it is expected that the room updates itself, not reverts back while Riot waits for it's event. Riot should assume the changes are okay until told otherwise, to not confuse/aggravate the user.
Some of the other settings may be more difficult, such as aliases, however I still feel as though Riot should accept the user's changes blindly for the couple seconds it takes to verify, and alert the user if there's a problem (duplicate alias, wrong format, etc).
### Version information
- **Platform**: web (in-browser)
- **Browser**: Chrome 58
- **OS**: Windows 10
- **URL**: riot.im/develop
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.