Go up/down and trigger the fetch of the former/latter page.
Then the page will stuck in an infinite loading, with the console showing 403 forbidden getting /t/${this.topic.id}/posts.json. And if the website is protected by a waf, then the user will be banned from visiting it.
Yes, users will see message like this.
Just as what is on a normal 404 page.
(The user can’t access the topic, so I think the 404 logic is reasonable.)
Oops! The page does not exist or is not publicly accessible. Take me home