The discussion revolves around disabling OpenGraph tags on private Discourse sites to prevent unwanted link previews in services like Slack and Dropbox Paper. deviantintegral explains that their authenticated site still generates link previews, which are useless and disruptive. Lilly suggests disabling oneboxes via max oneboxes per post setting, but mcwumbly clarifies that the issue is about preventing external services from unfurling links, not disabling oneboxes. sam shares that their login-protected site redirects to /login with a 200 status and notes that unfurling isn’t occurring in Slack, possibly due to admin settings, but is visible on Twitter. deviantintegral provides an example of Dropbox Paper replacing the URL entirely, highlighting the problem. Moin comments on the image posting limit, suggesting the user may need to reach trust level 1 to post more images.
Our Discourse community at is set to require authentication to view any content. This works great - except for services like Slack or Dropbox Paper where they generate link previews without any useful information.
Since our link previews will never be functional, can there be a way to disable or remove the OpenGraph tags from generated pages? That way, tools like Dropbox should just show a basic link instead of replacing it.
I think if you set max oneboxes per post = 0 in admin-settings, then oneboxes should be disabled and show as links.
I think he’s thinking of things the other way around, e.g how to stop Slack from trying to unfurl a link that is shared to his Discourse site.
On sites that require login, we redirect to /login and return a 200 on secure pages.
https://testsamsam.discourse.group/t/this-is-a-test-topic/9
However I am not reproducting this issue on Slack?
Not seeing unfurling here…
On Twitter I am seeing:
But this feels correct no? I should not be sharing this there anyway.
Here’s what we get with Dropbox Paper (redacted the URL):
I would have posted the Slack example, but my account is blocked from posting more than one image which seems a little restrictive for feature and bug reports 
.
Is it possible that your Slack admin has globally disabled unfurling for the domain? We can do that too, but not for other services like Paper.
Edit: Paper is actually pretty bad, because it fully replaces the URL. At least with Slack, you can read topic titles from the URL.
You’re likely already aware, as every new member receives a link to the blog post about trust levels upon joining Meta: Once you achieve trust level 1, you have the privilege of posting multiple images. It appears you are close to fulfilling those criteria.
