This week was a coding week, and I managed to release a feature folks have been asking for, as well as some businessy things that aren't quite marketing, and aren't quite coding:
I was never sure OnlineOrNot would attract any users. As a result, early on OnlineOrNot ran uptime checks entirely on AWS Lambda (with serverless products like AWS Lambda, you only pay for what you use, so if no one uses your product, you pay nothing).
Another benefit of using AWS Lambda is that running an uptime check in Tokyo, Paris, and LA simultaneously is effortless after you deploy - all you have to do is specify where your code should run.
After enough folks started using OnlineOrNot, it made sense to move off AWS Lambda in favour of a server that runs 24/7, and in doing so, OnlineOrNot lost the ability to easily pick where to run. This week, after a bit of work, I now have constantly running servers in:
In the original design, I wanted to keep it short so folks could skim the page, as well as get an understanding of what each plan lets you do. In reality, I made a page too long to glance at, and too short to properly sell all of OnlineOrNot's features.