Allow more image hosts in the custom CSS content security policy

(#909) Feature Under consideration theming

Thread

Comment by @nesges
RexSystem 1 vote originally by @nesges on GitHub 3 replies
I get that it's inconvinient, but CSP is way to important to deactivate it for arbitrary websites, not in control of fluxer
Comment by @icicle1133
RexSystem 1 vote originally by @icicle1133 on GitHub OP
I get that it's inconvinient, but CSP is way to important to deactivate it for arbitrary websites, not in control of fluxer
i never said anything about deactivating. i simply said add urls to be allowed.
Comment by @zulc22
RexSystem 1 vote originally by @zulc22 on GitHub
What if there were uploads/assets associated with themes? Allowing the user to add their own CSP domains is a very band-aid fix. Current solutions are to either convert everything to data: URIs or upload your files to Fluxer itself via a dump server or Personal Notes, as the CSP policy allows the uploaded-files server.
Comment by @retcinder
RexSystem 1 vote originally by @retcinder on GitHub
What if there were uploads/assets associated with themes? Allowing the user to add their own CSP domains is a very band-aid fix. Current solutions are to either convert everything to data: URIs or upload your files to Fluxer itself via a dump server or Personal Notes, as the CSP policy allows the uploaded-files server.
This does sound like an interesting solution but I personally think CSP domain adding would be better.