Describe the bug
When you type the "@" after a username in the search field, a search request is generated for each letter of the hostname, generating an error for each letter, and eventually causing you to be temporarily blocked from your server with "too many requests".
To Reproduce
Steps to reproduce the behavior:
Go to the "Explore" pane
Begin entering user name (ex. @sirmarksalot@teh.entar.net)
Type "@sirmarksalot@"
Type "t"
Dismiss "Remote data could not be fetched" notification
Type "e"
Dismiss "Remote data could not be fetched" notification
Type "h"
Dismiss "Remote data could not be fetched" notification
Type "."
Dismiss "Remote data could not be fetched" notification
Type "e"
Dismiss "Remote data could not be fetched" notification
Type "n"
Dismiss "Remote data could not be fetched" notification
Type "t"
Dismiss "Remote data could not be fetched" notification
Type "a"
Dismiss "Remote data could not be fetched" notification
Type "r"
Observe "Too Many Requests" notification. You have been blocked.
Expected behavior
Client should not aggressively request incomplete host names. Add (or increase) a debounce time on the text input to accommodate slower text entry on phones. Alternatively, add a separate flow specific to user lookup with a manual "search" button.
(please complete the following information):
Device: iPhone 13 Mini
OS: iOS 16
App Version: 1.6.0 (1)
Additional context
Manually entering addresses is required when migrating from other platforms. The default Twitter app does not allow you to copy text, for example. When trying to predict a good debounce time, keep in mind that certain text inputs take longer than others. The "." key is not on the key layout that Metatext presents by default, so the user has to click "123" and "ABC" before and after entering it. You could potentially work around this by finding a key layout that has both a "@" and a "."
Describe the bug When you type the "@" after a username in the search field, a search request is generated for each letter of the hostname, generating an error for each letter, and eventually causing you to be temporarily blocked from your server with "too many requests".
To Reproduce Steps to reproduce the behavior:
Expected behavior Client should not aggressively request incomplete host names. Add (or increase) a debounce time on the text input to accommodate slower text entry on phones. Alternatively, add a separate flow specific to user lookup with a manual "search" button.
(please complete the following information):
Additional context Manually entering addresses is required when migrating from other platforms. The default Twitter app does not allow you to copy text, for example. When trying to predict a good debounce time, keep in mind that certain text inputs take longer than others. The "." key is not on the key layout that Metatext presents by default, so the user has to click "123" and "ABC" before and after entering it. You could potentially work around this by finding a key layout that has both a "@" and a "."