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
Still need to find out what's going on here or even what the related requests are, but can't see an issue about it and this is surely something we ought to resolve if we want people to enjoy using spaces.
Description
The 'Explore Space' screen in Element is very slow, even if typing in a search term.
Steps to reproduce
go to a (decent size?) space: my example is Element's space
I suspect this issue may not be visible from the matrix.org homeserver since I expect someone would have said something by now!
open the 'Explore rooms' view in Element
type in a keyword
watch spinner for 2 minutes (in my case; probably varies depending upon how far down the room is in the tree?)
a result appears (spinner is still going, so it's probably not a complete result set. However this was the room I wanted in my situation so I could finish here.)
I would expect searching to be much faster than that; let's say 10 seconds or less to be generous given that I suppose I can understand that it may be making a few round trips to remote homeservers.
Version information
Homeserver: librepush.net
Version: 1.49.0, but this issue has been here for as long as I can remember the feature existing
Install method: pip from PyPI
Platform: amd64 VPS
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #11694.
Still need to find out what's going on here or even what the related requests are, but can't see an issue about it and this is surely something we ought to resolve if we want people to enjoy using spaces.
Description
The 'Explore Space' screen in Element is very slow, even if typing in a search term.
Steps to reproduce
I would expect searching to be much faster than that; let's say 10 seconds or less to be generous given that I suppose I can understand that it may be making a few round trips to remote homeservers.
Version information
The text was updated successfully, but these errors were encountered: