this happens because of the rewrite of the url registry, the old builder didn't sanitise/urlencode, the new one does. a manual url decode of the search query should do the job i think so that should be an easy fix

for now just append

after:<last post id>

to search query and it should act the same

Turns out both this and https://fii.moe/ft/1091 / https://fii.moe/ft/1105 were caused by fairly minor oversights, both are fixed.