I haven’t heard of the PushUp, but they seem to have very limited notifications and only one notification type - browser notification.
At what point (let’s say, by notifications per hour) is it no longer feasible to be pushing notifications from the same web server you’re serving your website from?
My favorite answer - it depends if you have good infrastructure you can send thousands of emails per hour, I cannot see a problem. For cheap shared hosts I think the 100 emails per hour could be considered as sending spam. But this is of course applicable for email notifications, I think you can send as many webhooks you like. Please note that you can use SMTP and not send the emails via wp_mail() but ie. via Sendgrid.
Is there any way to serve notifications with your plugin from another server to lighten the load on the “main” server, if necessary?
Not possible at the moment, but I think it would be a matter or creating REST endpoint and securing it.
I sometimes see people on Twitter complain about being asked to agree to push notifications, but the people I follow on Twitter tend to be easily-annoyed techy people who run ad blockers. Do you have any numbers of “actual” users you can share that agree to notifications and interact with them?
The plugin doesn’t support browser notifications yet, and unfortunately, I don’t have such insights.
Is there any sort of “opt-in” tracking system in your plugin to anonymously share such data with you?
I’m using Freemius Analytics, but they don’t provide such data. Only information about the install.
If you are curious about the plugin name story, I’m posting press release from a year ago, which was never published anywhere
So I came into an idea about a plugin which would replace all other email notification plugins. It has some core triggers implemented (like published post, post sent for review, comment approved etc.) and you can define any trigger by yourself. Literally any action in WordPress can trigger a notification. While having trigger you can compose actual notification using merge tags and define its recipients. Simple engine but endless possibilities.
I had a plugin but I hadn’t a name. This is a free plugin so obvious choice was WordPress.org repository. I wanted something simple, but there are so many other notification plugins and I expected this will be not an easy task to find my perfect name. I tried few slugs by simply typing it into the address bar at the end of the https://wordpress.org/plugins/ url. And here it was, I saw magic “We couldn’t find that plugin” after trying “notification” slug. How cool name is that?
Quick last checks, plugin zip and https://wordpress.org/plugins/add/ form. I typed all details in, press “Send Post” and… “That name already exists. Please choose another name”. WHAT?
As you may know everyone can download the SVN plugin repository so this is what I done. I looked into the log and there I saw one commit by plugin-master sent on 20th December 2011 that created the repository. And that’s it, nothing more, just first commit generated by the system. Repository was empty for almost 5 years.
Without loosing hope I dropped an email to firstname.lastname@example.org and I asked if there’s any chance to take this plugin repository. Mika Epstein was very helpful with that, she checked the repo and my plugin and simply transferred the ownership to me. It took few days and was quite stressful but on the end of the day I had my perfect name and plugin available for download at https://wordpress.org/plugins/notification/