Matthieu Lemoine

In electron-push-receiver we use [electron-config or now electron-store](https://github.com/sindresorhus/electron-store)

You want to have access to the encryption keys for sending notification ? You don't need those if you are sending notifications using FCM. FCM is handling the encryption part....

And if you're talking about FCM registration. It's already taken care of by push-receiver that's why you only need the FCM token.

Ok I see the use case. For now electron-push-receiver & push-receiver only supports sending notifications through FCM using the FCM serverKey provided by the [Firebase console](https://console.firebase.google.com). What I understand is...

There are several ways to fix this issue. In the exec.js source file, you can either : - Pipe process.stdin to childProcess.stdin `process.stdin.pipe(childProcess.stdin);` - Use spawn instead of exec in...

I don't think so telling google that you have received a message does not mean you have received the previous ones.

@wootwoot1234 What do you mean by 3rd party app ? Do you have an example ? Sure I'm available for freelance work.

You're right. This module could use a clever retry strategy.

Hi Luke, It's a good idea! Never thought of it. Well, first FCM doesn't guarantee to deliver a push notification but it almost always does 😄 About `push-receiver` specifically, we...

I don't have numbers but it's a matter of seconds