Oh, you'll be reversing this choice VERY quickly if your product gets any traction, I assure you...
Oh, you'll be reversing this choice VERY quickly if your product gets any traction, I assure you...
Yes, the pages can publish illegal information, be set up as phishing hubs, but none of that is as a result of JS being executable. Web hosts all have exactly the same risks to deal with, their users can also host anything they wish.
The owner's challenge is with the content they are opening up to hosting, and it will become an overhead to police that. If they decide to add buttons like "report content" then those will be able to be hijacked by the publisher and become useless.
- You have no CSP header that I can see.
- You do expose the server version in the headers, though.
- The site is available at a non-SSL-secured domain.
- There's no X-Frame-Options, X-Permitted-Cross-Domain-Policies, etc.