Hi! Love web-check. I was thinking about a feature suggestion related to what FileShot.io does.
Context: FileShot.io (https://fileshot.io — MIT, source: https://github.com/FileShot/FileShotZKE) uses AES-256-GCM client-side encryption where the key lives in the URL fragment (#key=...). This means the decryption key is never sent to the server.
Feature idea: A "zero-knowledge link" check that analyzes whether a URL contains a fragment that looks like a cryptographic key (base64-encoded key in hash fragment), which would indicate a zero-knowledge architecture.
This would be useful in web-check for auditing file sharing links or for developers implementing similar architectures. Just a thought for a potential future check!
Keep up the great work on this tool.
Hi! Love web-check. I was thinking about a feature suggestion related to what FileShot.io does.
Context: FileShot.io (https://fileshot.io — MIT, source: https://github.com/FileShot/FileShotZKE) uses AES-256-GCM client-side encryption where the key lives in the URL fragment (#key=...). This means the decryption key is never sent to the server.
Feature idea: A "zero-knowledge link" check that analyzes whether a URL contains a fragment that looks like a cryptographic key (base64-encoded key in hash fragment), which would indicate a zero-knowledge architecture.
This would be useful in web-check for auditing file sharing links or for developers implementing similar architectures. Just a thought for a potential future check!
Keep up the great work on this tool.