Great to see “better mobile experience” already on the roadmap — really looking forward to reddit-style indented threads landing on mobile.
Quick SEO question about nested replies: I noticed nested topics use a /n/ URL, and when I fetch one without JS it returns an empty shell, plus the canonical points to the /n/ URL itself rather than the regular /t/ topic URL. Do crawlers still get the full server-rendered post content on /n/ routes, or should canonical resolve back to /t/? Just want to make sure enabling nested won’t hurt indexing. Thanks!
upd
Tested on 2026.5.0 + Horizon: flipped a topic to nested and checked with a Googlebot UA. Crawlers still get the full flat HTML on /n/ (all posts, microdata intact, canonical → /t/, no noindex), and /n/ stays out of the sitemap. The only redirect is /t/ → /n/
as a 302, and that’s just for JS users — bots never get redirected. So for SEO it’s a non-issue, indexing-wise nothing changes.