Discord RPC timestamp continuously resets
On every presence update, the timestamp given to Discord for RPC continuously resets to the current time. This occurred after the rewrite, suggesting that perhaps some collateral from the restructure might be at play here.
Apologies for the accidental closure; this is still an open issue. The aforementioned commit was partially reverted in a785e643520d8b5cbae2ed09acfe5d448b8f8353 due to oddities on Discord's side.
This was originally intended in development as Discord shows the correct timestamp visually on the client despite not being updated correctly. In addition, implementation of a correct timestamp was difficult and had unexpected issues that arose from it. Until the Discord backend is rewritten (and possibly some of the Nintendo/Pretendo backends, too), this issue will remain troublesome to solve.