Mastodon API's pagination IDs are not guaranteed to be in a numeric format.
This happens to be the case for the tootsuite implementation, but others
use UUIDs or flake IDs for pagination.
This also simplifies the code a bit and luckily shouldn't break backwards
compatibility since they're already of type ID in the Pagination struct.
Coverage decreased (-0.3%) to 90.643% when pulling 478dc913c0a9ca10da1ded8090b89a3ab07c3c35 on muesli:pagination into f51571807ddabd3db787bc03a012e1b90ae1d4c0 on mattn:master.
Mastodon API's pagination IDs are not guaranteed to be in a numeric format. This happens to be the case for the tootsuite implementation, but others use UUIDs or flake IDs for pagination.
This also simplifies the code a bit and luckily shouldn't break backwards compatibility since they're already of type ID in the Pagination struct.