30 karma · joined November 25, 2024
I added a simple CORS check that makes sure the request is coming from the same domain as the request itself is saying it's coming from. Also added rate-limiting.
Good job, will definitely try it. But I know myself, will end up looking for something just a little more advanced. And before I know it I end up staring at graphs trying to figure out what my hours/day solving JS bugs has to do with my weight...
But I have thought about making it self-hosted too. But there already is so many great products for that out there.
I wish there was a perfect way to do this. I despise subscriptions, I dislike pay as you go becasue it's too complicated, and finally, a one-time fee dosent really work when sold as a service as you said. But I guess these are the options for people not willing to self-host.
If you got any interesting reads on this topic please send em my way.
But you're right, might be a good idea to change the name of the key or work it out completely, it does look like it could be a vulnerability from an outsiders persepctive.
Before this I created a website displaying snow conditions for a few hundred locations in Sweden. I love skiing and ski-touring and wanted a better way to find the best conditions.
Right now I don't have much time to work on my projects since I'm doing mandatory millitary service, which is part of the reason Simplytics.dev took so long to launch. But I'm hoping I might soon make my first buck selling zeros and ones.
Id love to recieve feedback, Hugo