Roost

Hey designwise,

Please email me at dan.stever[at]roost.me

I do not fully understand the issues you were having from your above comment and would like the opportunity to try to help you resolve this.

I’d also be glad to help you get your password reset. If you unsubscribed from our initial emails it may have blocked the automated reset email when it went to send.

I do hope you give us at least the opportunity to discuss the concerns you had.

– Dan

Hey everyone!

We have an existing plugin that does this and adds even more functionality to your WordPress site.

You can check it out, download, and start using Roost for Bloggers today with this plugin. – https://www.ads-software.com/plugins/roost-for-bloggers/

It is completely free, and not only adds desktop push notifications for Safari on OS X Mavericks, but includes an auto-push feature for when you post new content.

We are getting ready to release v2.0 of the plugin within the next few days that brings even more awesome.

As a teaser, we’ll be releasing Google Chrome support in the coming months. This will be for Chrome on Windows and OS X.

If you’d like, you can read a third-party review of our service here from The Zinx. https://thezinx.com/2014/01/14/implement-safari-push-notifications-blog.html

As full disclosure, I am one of the the developers for Roost. You can check us out on Roost.me or send me an email. I’ll be glad to answer questions or walk anyone through install and using the plugin. dan[at]roost[dot]me

Cheers!

Hey warholfan,

None at all! Your Roost account is not tied to the domain you register it with. You will be able to log into the plugin with your account from any domain. Also, to update your domain you will just need to log into the Roost dashboard, which is accessible at https://roost.me.

The only disclaimer I will add to this is: If you test environment is on your local system, the auto notifications may not be sent. We do URL validation on posts to our API. Localhost is not a valid URL. The Manual Push from the dashboard will still work.

It depends.

It was not tested with custom post types.

But, the plugin hooks into the publish_post action. So if the custom post type uses the standard actions it should work just the same.

If you have a specific example we could test it out.