Security
This site is written largely by AI, and I then go through it as a security person. If you run into a bug or a vulnerability here, I would genuinely appreciate you letting me know.
Found a bug? Report it
If you find anything from a small glitch to a real vulnerability, reach me at the contact below. It helps most if you describe what it affects, how it can be reproduced, and what the impact is. For anything sensitive, feel free to write to me encrypted with my PGP key. Let us stick to fair responsible disclosure: give me a reasonable window to fix it before you make it public. Do not expect a bug bounty, this is a one-person project built in my spare time, but I am happy to credit an honest reporter if you want.
Why this site is vibecoded
The code of this site is largely vibecoded, meaning written by AI from my instructions. I am not a frontend developer or a designer, and I did not want to spend hours fiddling with buttons, margins and CSS. I would rather put that time into the content and into security. If you want proof, look up the previous version of this site on the Wayback Machine. It should become clear fairly fast that frontend is not my thing. I treat it as a deliberate trade-off, not as blind trust in the AI.
I audit it myself
AI-generated code does not mean it ships unchecked. The parts that touch security I read and test myself after the AI. Even so, I am only human and something can slip past me. That is exactly why this page is here: if you spot something I missed, do not keep it to yourself, drop me a line.
Contact: em.notorp@22.norh.hcetjov
Last updated: August 2026