I understand. It's a darn shame.
We did not anticipate that we would lose the vast majority of the market and our sales volume (to MSFS2020 with their blocking on weather API), nor the other major challenges we are facing, and now we are doing our best to stay in business in order to support products which have been released more recently (i.e. within the past 13 years). Our monetization strategy for our very modest and small business involves new products and users who purchase them, and not having virtually any new purchases while supporting complex high-availability network weather systems for very old products results in this situation. If you do not feel that you received enough value for your $20-40 spent over xx years while receiving our full support and network resources, then I regret that and regret that we could not continue to subject ourselves to significant active user network costs for these very old products without any compensation. We did want to try subscription-based at one point, to address the ongoing cost issue, but user feedback was not amenable to it. If we knew what we would face we would have made different decisions despite that.
Moving forward, if we receive enough feedback indicating a willingness to pay a fee to continue accessing such services to make it viable, we would consider it.
Outside of that, we will have to continue moving forward the best we can, supporting products that we've sold within the past decade.