I’m fully aware of the design decisions that led to you refusing to budge on integrating with Tapatalk, for example, which would have allowed push notifications on iOS. I don’t blame you for that.
But let’s be completely clear about one thing, it’s not helpful to pretend as though I was demanding you provide the infrastructure necessary for push notifications on iOS. I wasn’t even requesting that. There are other ways of making it happen, which I assume you are aware of. I don’t know if any of them are truly workable technically or financially. I just know that your comment isn’t helpful.
I don’t use Discourse. I did for a short while a few years ago, and I gave back in the little ways I could.
Discourse will become a viable possibility for me to use the moment it stops treating iOS users as second-class citizens for less than $100/month or I can afford $100/month. You can whine all you want about how Apple does things a way you don’t like, but in the end my evaluation is not unfair.
This has the optics of the typical two-tier OSS package, where some important features in the software are locked behind a paywall. If you want to talk up how your software is free to shut me up, go ahead, but it rings a bit hollow when your decision about how to solve push notifications in your “free” software just happens to require people to pay you $100/month (at a minimum.)