When using “Hide Read”, the app behaves normally for a couple of pages, then abruptly pops this screen and removes all navigation and UI from the app until it’s restarted.
The UI not showing up is definitely a bug. Will fix in the next release. As for the error itself, this happens if it detects 20 posts being filtered in a row on the client side. This is to protect against cases where your filtering rules are overly sensitive which will cause the client to fetch a very large number of posts just to show any content. If you think the error itself is incorrect please let me know what your filtering rules are. You can DM me if the rules are sensitive.
This appears to be fixed now, thank you so much!
I figured that about the filter, which I would personally love the ability to control the sensitivity of (some days at work are pretty boring). The UI issue was what I was wanting to bring attention to. I browse /all a lot, so I have a ton of sub blocks.
I bumped the limit from 20 to 30 in the next release. Hopefully that will get you over the hump.
I can look into making the value somewhat adjustable but I prefer not to do this since it does negatively impact server performance.
Ahh, I thought it was all client side after loading. It makes sense to have it hard coded if it’s doing the filtering before loading content.