I think you should wrap the comments into an element and apply overflow:hidden to them to prevent the contents from obscuring other comments as I did in one of my tests
It's okay, thanks for feedback. Current XSS protection is really primitive, that's why characters like "&,<,>" turn to *, that's temporary. Backend is pretty simple actually, it's just basic KV storage getting data from POST requests and sends them to the client with GET requests, i could've used a different database structure, but this is more than enough considering the required complexity.
![(:̲̅:̲̅:̲̅[̲̅:♡:]̲̅:̲̅:̲̅:̲̅):before you go avatar](/site_screenshots/29/74/enmitized/index.html.50x50.webp)
It's just a tiny project but I'm really proud of it. Once completed, I will integrate it into my main website
Cool! I've made the same thing for my website. What's the backend stack?
I'll do some testing for the most common vulnerabilities I can think of
I think you should wrap the comments into an element and apply overflow:hidden to them to prevent the contents from obscuring other comments as I did in one of my tests
An apostrophe gets turned into an asterisk. Probably not desireable.
Sorry for this spam but I assume if it's for testing I'm welcome to test!
It's okay, thanks for feedback. Current XSS protection is really primitive, that's why characters like "&,<,>" turn to *, that's temporary. Backend is pretty simple actually, it's just basic KV storage getting data from POST requests and sends them to the client with GET requests, i could've used a different database structure, but this is more than enough considering the required complexity.