Skip to content
oversizedcanoePublic

About

An anonymous survey/feedback web application.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Latest commit

 

History

23 Commits

Folders and files

Repository files navigation

sealed

An anonymous survey/feedback web application.

Tech Breakdown

  • The backend is a .NET Web API Project which uses EFCore as an ORM and to manage migrations.
    • The API is RateLimited to 10 requests to any POST endpoint per IP Address per day. In a production application, a more strict rate limiting approach would be needed, but this is just a hobby project.
  • The database I used is Postgres.
  • The frontend is an Angular18 project
    • I used PureCSS, an extremely minimal CSS framework, as the CSS library.
    • I never claim to be a desginer :)

Functionality

  • Users can create a pair of keys -- one private and one public.
  • They can share the public key link with anyone, and anyone with the public link can submit anonymous data (feedback, reviews, etc.).
  • Only the person with the private key can see the submitted data.
  • Each key is a GUID, so it's guaranteed unique (for the next trillion years or so).

Screenshots

Home page image

After clicking "Generate Codes", the user can copy the Private Code for safe keeping, or copy the Public Code/Link for distribution. image

After navigating to the created Public link, or entering the Public code on the home page, user can enter entries. image

After entering a few values. These are only held in page memory as confirmation to the user; they disappear on page refresh. image

After entering the Private code on the home page, user can see entries. image

Future Goals/Improvements

  • The Keys and UserEntry data should purge itself after a month.
  • The user should be able to save their created private keys to browser storage. By default the application is as secure as possible with respect to private keys (it removes them from storage immediately and purposely does not place them in the URL).
  • The user should be able to permanently delete a private key/pair/it's associated entries -- for example if it is leaked.
  • The Key and KeyPair table could be broken into a PrivateKey and PublicKey table, where each has a reference to eachother. This could improve query speed if the table ever got large.
  • Deploy to AWS for fun. Should try to implement a reverse proxy.

About

An anonymous survey/feedback web application.

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages