Overhaul HTTP logging, and error reporting UX
Tokodon desperately needs better ways to log and display network errors, and hopefully this is a step in the right direction. Currently, network errors are only displayed when they happen and they're easy to miss depending on which page you're on. If you're not sure where Tokodon keeps it's logs (unlike NeoChat, it doesn't keep it's own) you're solely out of luck until you come across what caused the error in the first place.
To solve that issue, the most recent network errors are displayed in Settings:
Additionally, you're able to copy each error and can easily paste it into a Bugzilla ticket.
A couple of other things that are changed but not visible:
- Instead of unhandled errors being logged, all errors are now logged. Handled errors need to decide whether to show themselves in the UI, instead of that being the default. This should stop harmless things like unread notification counts, notification policies, and other recent Mastodon features which are unimplemented in other server software from spamming you with errors.
- Custom emojis are now requested with authorization, reducing the amount of errors for GoToSocial servers.
- Websocket errors are now logged
- Secrets should now be cleansed properly from logs
Edited by Joshua Goins