Calling this "severe" feels overblown. It's a UI mismatch likely caused by using multiple caches that are out of sync. I feel like every engineer on this site has encountered this exact bug at one point or another. It's an easy one to run into, especially in bigger orgs.
The "page two is inaccessible" thing is, imo, severe. I've seen it myself at work, and there are lots of parts of the UI where I'm regularly looking for something on page 2. I didn't even think to try the JavaScript console hack but like, i (my employer) is paying for access to that data, and it's simply not there...
apocalyptic0n3 · · focus · HN ↗
queenkjuul · · focus · HN ↗