Anonieme gebruikers verhinderen bestanden te downloaden instelling

AI-generated summary

The discussion revolves around the “Prevent anons from downloading files” setting and its implications. AndyBr questions the warning associated with the setting, which states it may break non-image site assets posted as attachments. AndyBr also asks if it’s possible to restrict attachment downloads for new users until they reach trust level 1. simon notes that one known issue is custom fonts in site themes failing to load for anonymous users, and suggests improving the setting’s description. Heliosurge proposes using Category Settings to restrict downloads by setting visibility to trust level 1 or higher — though this hides the category from anons and TL0 users. codinghorror responds to simon, noting that since Discourse now encourages using Google Fonts CDN (reducing reliance on embedded post attachments), the warning may be outdated and could be removed entirely. The consensus leans toward revisiting and possibly simplifying the warning, as modern practices minimize the risk it was meant to address.

This setting comes with this warning:
WARNING: this will prevent any non-image site assets posted as attachments from working.

What does this mean exactly?

Also, is there a way to stop new users from being able to download attachments until they are at trust level 1?

One case I’ve come across is that the setting may prevent custom fonts that have been added to a site’s theme from loading for anonymous users. Other than that, I haven’t been able to find unexpected issues with the setting.

If possible, it would be good to improve that setting’s description. If anyone has more details about issues that it causes for anonymous users, please let me know.

One option is to use Category Settings on areas where things can be downloaded.

Setting
TL1 See/create/reply

Only downside is this category will not be visible to outside anons and users whom are less than TL1.

But don’t we encourage people to use the Google Fonts CDN for that reason? I think we can possibly remove this warning entirely, now that we almost completely removed reliance on “post content to a hidden topic, then copy the URL”.. yeah, let’s do that.