What I don't understand is why they would turn off the push notifications before the new solution is in place... that sounds like a sure-fire way to upset your entire user base. Given the history of schedule slips for the next version of the product, it seems REALLY risky to set a turn-off date before the new product is out and tested.
For the record, as long as the new product is decent, I have no problem paying for another version. The Space release was obviously a huge disappointment, but I'm not going to complain about the money I lost on that product if it helps them get to a truly worthy successor to Haiku. What I will get upset about is losing my very important push notifications before the new product is ready for prime time. Even if the new product was released tomorrow, it's going to take time to move all of the scripts and current Haiku Helper functionality to the new platform, so I can't see how this ends well for any of us who currently rely on HH's push notifications for critical security and automation functions. Best case scenario has us scrambling to port and test our setups in a very short time window. Worst case is that we're stuck with no notifications for some number of weeks or months and forced to ditch the entire product line in favor of some other solution that's available now.
Lupinglade, would you consider moving the push notification termination date to some time AFTER the new product is out and shown to be running well? It would let us sleep a lot better knowing we're not driving off a cliff in 27 days.