🛡️ Advanced Privacy: Perchance Custom CSP Mode

🔒 What is Perchance CSP?

Perchance allows users to apply a Content Security Policy to any generator by adding ?$csp to the URL. This limits external requests, blocking the generator from communicating with unknown servers.

Example:
https://perchance.org/animal → No restrictions
https://perchance.org/animal?$csp → Can only talk to trusted domains

⚙️ How To Use

• Add ?$csp to any generator URL to activate default CSP rules
• Use ?$csp=domain.com *.domain.com to create a custom rule
• Combine with other parameters like ?foo=1&$csp or ?$csp&foo=1
• Default CSP allows these domains: perchance.org text-generation.perchance.org image-generation.perchance.org user.uploads.dev aigc.uploads.dev esm.sh cdn.jsdelivr.net cdnjs.cloudflare.com

🧪 Test It Yourself

Try these:

• Upload Plugin
• Example with Default CSP
• CSP with Comments Plugin Allowed

📦 CSP in Depth

With CSP, Perchance prevents generators from secretly stealing your data. By restricting server communication to known-safe domains, it blocks exfiltration attempts via JS or form submission.

Use browser dev tools (Ctrl+Shift+J) to see blocked requests under the Console tab.

💡 Pro Tips

• Use ?$csp before #edit if using editor view
• If you want to build a browser rule to block unsafe Perchance generators, only allow those ending in ?$csp
• Sandboxing ensures ad networks like Google Analytics can't access generator input
• Use MDN CSP Docs to learn more about policy syntax

🚫 Limitations

- Comments and super-fetch plugins are not allowed by default CSP due to possible misuse.
- comments-plugin and super-fetch-plugin must be manually whitelisted.
- Try creating your own CSP setup here.

References:
perchance.org/upload | MDN: Content Security Policy | comments-plugin | super-fetch-plugin