I’ve just noticed that Discourse appears to be misconfigured in a way that allows anyone to insert tracking pixels into postings, or also load very big images.
For example this embedded gif with ![](http://external)
is getting served from an external server.
This allows anyone who embeds images to track IP addresses and user agents of visitors. Technically that could also be a GDPR concern.
If you right click and “copy image URL” you can verify the behavior. On other instances like the one hosted by discourse itself, images embedded the same way would be served from their CDN.
Same goes about link previews. (just right click and check image URL for any image, like the open graph image beneath).
After researching I believe the issue might be resolved by setting up download_remote_images_to_local
to true
, though might need some more investigation (like using CDN or S3, which server would download the image, image size limits, …).
I think there are separate configs that should be checked for onebox
(like allowed iFrames).
Update: @hexa forwarded it to “the admin team”