The current functionality of the routing and template doesn't allow the author to view the secret they just created. This is done by checking their cookie to see if the secret id is present. The route and template then see them as the author and doesn't present them the option to decrypt and view the secret.
Looking at the web server logs, there are a lot of people who create a secret but never decrypt it. I suspect they're just testing it out and don't see the option to view it, and maybe think it doesn't actually work.
Adding the option to decrypt a message you just created doesn't make a lot of sense to me, but I could see how someone unfamiliar with the codebase might think the application doesn't actually work. For that, adding the ability to view your own secret makes sense to add.
renderorange
commented
2 years ago
The current functionality of the routing and template doesn't allow the author to view the secret they just created. This is done by checking their cookie to see if the secret id is present. The route and template then see them as the author and doesn't present them the option to decrypt and view the secret.
Looking at the web server logs, there are a lot of people who create a secret but never decrypt it. I suspect they're just testing it out and don't see the option to view it, and maybe think it doesn't actually work.
Adding the option to decrypt a message you just created doesn't make a lot of sense to me, but I could see how someone unfamiliar with the codebase might think the application doesn't actually work. For that, adding the ability to view your own secret makes sense to add.