yupitszac
Joined 9 years ago
Joined 9 years ago
In the case of Form King, all transport is over TLS, with the RDS instances being encrypted at rest. When a form is submitted, the data is encrypted and uses the AES-256-CBC cipher prior to storage. I just didn't want to store other people's data in plain text. Form could include names, and emails, and addresses. It's also signed with a MAC to ensure the data isn't modified.
This is probably some information I should include on the website as well (It's a personal project that I just work on in the evenings and weekends, so I had to prioritize stuff and the marketing website was one of the lowest :) )
Now, keeping in mind that I'm no security expert beyond what's standard for production applications, this is the area of any service that worries me the most and it'll remain a top priority to continue enhancing the security of the app.
As for user counts, one of the benefits of it being a personal project is that I don't have to share or defend that. It's a service that's there, if you want it feel free to use it. If not, that's completely okay too
I'll add that form to my list for conversion though, so at least thanks for that :)
This was just a personal project that I made available in case anyone else had a need for it :)
It's a personal project that I built because I didn't want to keep paying for a service to process forms for my static websites (though as mentioned by someone in one of the threads above I still have some forms to convert)
Maybe I'll record a video explaining that and put it on the front page
I'm by no means a UI or UX expert :)
I literally just made it because I didn't want to pay for a service anymore for my static sites that need to collect information.
Maybe solidifying some of the verbiage on the website, and giving it time to not be so new are the two biggest things I can do to solve this?
A live form, of course. People want to see how it works and play with it. I'll get these put together and up soon! Thanks again for taking a look :)
GO is super interesting, and I like that you wanted total control over your process. I've never used Google Cloud Functions but that's similar to Azure Functions or AWS Lambda, yea?
Privacy policy, yea. I gotta get one of those up. Incredibly important things like that and terms of use should be sorted right away. This is one of the things I forget about in my personal projects (like FormKing) that I really should stop forgetting :)
As for monetization, that's not my goal. One thing I don't think I communicated well is that this isn't a business. It's a personal project that I intend to open source shortly. The cost for the service (hosting, domains, etc) is super low so for right now I'm not looking to monetize.
Form King was literally just something I built for use with my websites that I had a lot of fun working on. So I made it public