I have a feeling that some more recent Scatter versions are more buggy than previous versions. It can be hard to tell just from personal and anecdotal evidence in the Telegram channel channel or support tickets.
Suggestion:
To get a sense of the stability of a release it is required to collect metrics on things like how many transactions are failing. Scatter does not want to just silently collect data from users, but it could provide an explicit, optional "Report a bug" button, maybe even with 2-3 categories to increase a number on a server.
And then a report could display the amount of bugs over time and potential patterns of bad releases might get detected.
Additional notes:
When submitting a bug report a web page could be displayed with general debugging tips and maybe another highlighted warning of scammers posing as helpers in e.g. Telegram.
I've been thinking about this, too. Bug tracking is a big problem, and requires a comprehensive solution that isn't as straightforward as just adding a button (where does it go? github? is that good for users?)
Problem:
I have a feeling that some more recent Scatter versions are more buggy than previous versions. It can be hard to tell just from personal and anecdotal evidence in the Telegram channel channel or support tickets.
Suggestion:
To get a sense of the stability of a release it is required to collect metrics on things like how many transactions are failing. Scatter does not want to just silently collect data from users, but it could provide an explicit, optional "Report a bug" button, maybe even with 2-3 categories to increase a number on a server.
And then a report could display the amount of bugs over time and potential patterns of bad releases might get detected.
Additional notes:
When submitting a bug report a web page could be displayed with general debugging tips and maybe another highlighted warning of scammers posing as helpers in e.g. Telegram.