Thank you for your reply. I am worried, that – probably because of a language barrier – I did not explained my concerns clearly. So please, give me an another try:
Assuming that indexing crawler is not using a JavaScript, it seems for me that without next and prev links to follow, there is no way for it to index posts and discussions beyond the first page... BTW, from what I read, as some people conducted tests of how Google is indexing SPA/dynamic pages, we have got only about 50% of chances that Google bot will trigger generation and/or index content generated by a JS - it sounds legit as I guess it may depend on limitations how much time in a particular moment the bot has for "scanning" the website, how fast the page is responding and so on.
Nevertheless, I suppose that bot cannot scroll the document, so it will not index lazy paginated content. I also suppose that adding links (in the "no-js" content section) to the next pages of paginated content will solve this problem. Following this idea I wanted to add those links in my implementation of Flarum, but it seems that someone thought about that already as I found those links in templates mentioned above. But strangely I did not spot any other code which may fill appropriate parameters in those templates with data which will cause those elements to render... Feeling that solving that mystery is beyond my imagination I asked if someone involved in this project longer than me 😉 could explain that?
Regarding shape of those URL-s, on every paginated page I noticed there is a canonical URL containing the "near" parameter. I thought it may be used as it does not generate repeated content (EDIT: after a research it comes out not to be exactly true and I think that has to be revised).
You wrote that in "no-js" mode there is a pagination (with "page" parameters), but I cannot find any trace of it - on my freshly installed instance of Flarum, but also here - on the official one. Could you direct me to those links (in static document code)?
Taking opportunity - thank you for your extensions and podcasts. 🙂