Yes, even guessed URLs like /t/7. Known limitation
That’s some limitation! ![]()
You’d want to do this properlyTM?
Various publications provide a workable scheme.
I assume they use some cryptographic arrangement where a limited use token is included in the URL and when examined by the server permits access within the boundaries of the tokens scope?
Perhaps you could create a plugin to achieve that? (but yeah, that’s a lot of intimate overriding)
Meantime, save yourself a lot of bother and simply re-organise your Discourse to put the more sensitive/inappropriate stuff away and require login?
Being partially public is good for your general marketing, so I wouldn’t worry about that.
I agree though, it can be frustrating that Discourse will not expose enough html to preview a Topic unless you have full read access to that Topic. You might argue that’s sub-optimal from a marketing perspective. I respect the solution to that is significant effort. Perhaps one day we could have a Read Preview permission?