Roost

Hey pmigneault,

Appreciate your honest feedback. We have not tried to hide the fact that SSL is required but as you stated, may need to look at how we are presenting the information.

Google designed Chrome to require SSL / HTTPS for push notifications. We tried a few ideas, but in the end it’s a requirement we couldn’t remove.

The plugin does handle inserting the files automatically. One catch to this may be if your plugin directory does not have standard permissions or if your WordPress install is a slave of another application. Again, something we are working on daily to improve the process.

You do have an interesting idea on this managed notification idea. Something I will put on our internal discussion list.

If you have any questions or ideas, please do hit is up at [email protected].

Sure, I know CTR has been in the context of Safari.

Again, I understand the https concerns. I assure you, if there is a way to use Chrome notifications non-https, we will support it as well. Anything we can do to provide a great service and make it easy to use.

The HTTPS thing is a slight catch but one that we have no control over.

We had a question in another thread on this earlier. I’ll quote what I said there for ease so you don’t have to dig:

We wrote a post about this on our blog called Chrome Security – SSL Keeps You Safe. In the post we reference a post by Matt Gaunt, Google Developer Advocate, where he expands a bit more as to the why of the requirement. For brevity, here is his post: Push Notifications on the Open Web.

Re the CTR: This is something we are very focused on optimizing. We are limited with the Safari implementation as to the control we have for some things, but with Chrome have a whole new world of possibility. We are watching this closely and have some ideas to test.

Hey Qobalt and Shmoo,

We’ve been looking at this again and think we’ll explore it in the coming weeks. May be reaching out to you.

Hey Mayne123,

We released support for Chrome late last week!!! Boom!

The latest version of our plugin v2.3.2 supports Chrome (and has already been through a few bugfixes.)

Glad to answer questions if you have any. Let us know your thoughts!

Hey C,

I totally understand where you are coming from, and wish I had a better answer for you on this, but SSL / HTTPS is a requirement that Google has put in place to use Chrome notifications.

We wrote a post about this on our blog called Chrome Security – SSL Keeps You Safe. In the post we reference a post by Matt Gaunt, Google Developer Advocate, where he expands a bit more as to the why of the requirement. For brevity, here is his post: Push Notifications on the Open Web.

We are doing everything we can to make this as simple and straight-forward of a process for our Roosters. I hope that you understand and that we can eventually help you out with Chrome notifications.

– Dan

Hello Kostas,

I can not speak for the Push Monkey guys, but the Roost Web Push plugin will have support for Chrome push notifications in just a few days.

What is really cool about this is that it will support multiple OSes, such as Windows, Linux, Mac, and Android.

On Android it acts and feels just like push from native apps. It’s pretty slick. On versions 5.x it even shows on the lock screen.

If you want to try push notifications in Chrome today, we have a test page on the Roost site.

If you have any questions hit us up at [email protected]

Would like to hear your thoughts.

– Dan

We did push an update on our servers to resolve this issue. You should be good now. The updates to the plugin will also take this into context so that it will work as expected.

Ah! There we go. Makes complete sense now.

Integration with Chrome is not yet into the plugin or our public JS. Watch for an update in the next few days for both.

The reason this error is thrown is your browser and the plugin are in a mixed state.

If the browser can not receive push, we do not load the Roost script completely.

But since Chrome beta DOES support push, Roost JS loads, but the prompt function throws an error as the beta support is not there in the code.

Thus, what you are experiencing.

Thanks for the details. It clears the picture up.

Again, just watch over the next few days. This is going to get fun.

– Dan

We’ll take a look at this benoitd. There should be no reason that would happen or trigger.

Just to make sure, I am assuming you are using the Auth Push feature? Are you setting a custom headline below in the “Custom Notification Headline” field, or just letting the plugin pick up the post title?

Does it work for you for other posts fine?

– Dan

(Sorry for the delay in response. Did not get an email on a new issue. Would have worked great with notifications… Too much?)

Hey mayne123,

We’ll look into this. Can you give me a URL to the site you are using this on and let me know the version of the browser you are using?

– Dan

Hey shibbymintay,

Wanted to follow up on this as we have finally pushed a release that supports category filters.

Version 2.2.0 of the plugin allows the site admin to select categories that are excluded from auto push. I know it’s not exactly what you referred to in the first post, but it’s a step in that direction.

Minor version update slated for the next few days. This text has been completely removed, including the support link.

Watch for v2.2 in the coming days.

Again, understand the concerns.

Here is a post from Matt Cutts addressing hidden links. In the comments (linked here) he talks about noscript tags. I believe his answer should adequately ease your concerns with it.

https://www.mattcutts.com/blog/hidden-links/#comment-42427

Oh yes. Sorry. It is included with v2.1.8. This is why we rushed it to the plugin directory.