As detailed in #599, Read You's "Mark All As Read" button doesn't work when connected to Miniflux via the Fever API.
It turns out the fix is pretty simple: before, Read You was sending a before: timestamp of Long.MAX_VALUE. This produced a truly enormous epoch value, and it's possible Miniflux was just not interpreting it properly.
Changing the value to the current Unix time fixes the issue on Miniflux, and should remain functional for all other backends too. (It also just makes more logical sense.)
As detailed in #599, Read You's "Mark All As Read" button doesn't work when connected to Miniflux via the Fever API.
It turns out the fix is pretty simple: before, Read You was sending a
before:
timestamp ofLong.MAX_VALUE
. This produced a truly enormous epoch value, and it's possible Miniflux was just not interpreting it properly.Changing the value to the current Unix time fixes the issue on Miniflux, and should remain functional for all other backends too. (It also just makes more logical sense.)
Tagging @Ashinch @JunkFood02 for review.