Chrome Push need https ($$)

  • It’s not the Roost fault, but after the plugin install, the Roost account creation, confirmation, the ftp upload for the missing file for Chrome push and the configuration of setting, I discovered I need to use https. So, for that I need to buy a SSL certificat, for my little personnal blog. It will be the first time I’m going to pay for something related to this blog. The pluging description should talk about this https things before. At lease I had the solution now.

    I’m not sure if it’s possible, but why Roost dosen’t manage the Push notification directly? I can have a button on my site to the Roost website and Roost can possibly send after that my Push notification when my blog give a new post. I don’t know, but this https things are not funny.

Viewing 1 replies (of 1 total)
  • Plugin Author Roost

    (@noticesoftware)

    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].

Viewing 1 replies (of 1 total)
  • The topic ‘Chrome Push need https ($$)’ is closed to new replies.