You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's too many steps. Moreover, I do not understand (yet) what 4) is for. So I'd like to start brainstorming how we can reduce the number of steps.
Could we, for instance, merge steps 2) and 4) into a single operation along the lines of:
{
"select": {
"id": "setter:[email protected]"
},
"value": {
"RegisterWebPushApplication": {
"human_readable_name": "Monitoring for intruders in the bedroom",
"push_uri": "https://updates.push.services.mozilla.com/push/v1/gAAAAABXDpIsS-SyN3cuMTcGjUnizYkahEmsHvEWYlfFFEuSoHQWEYEvgTSyXf7jguYpvEZiclBK4CzgUv9CPbZoIJ8O4dVXnP1jFQC0Y7UoMqaT0Aut68nLbTI2w09kYsgiabe3qQIL",
"public_key": "BFzTzpsvbLyHmUdqSKV7NDJlsOaE8L9R7eTBf9f43XN4-EcP5BTL0SBYsHC3hsA9XarWgYP46TpLcACht-uz778"
}
}
}
this operation would create a new channel foo with kind WebPushNotification. Future Recipes would then be able to send notifications directly to foo.
Will probably want some kind of mechanism to be able to return values (in this case, channel ids) from send requests. I can add that as part of Decentralized Taxonomy, if necessary.
I also don't understand step 4 too much, but sure @aosmond come with an excellent idea.
Regarding the alternative proposal, just comment that we cannot as for as many registration as possible. We register for web push once, meaning one push uri, that we will need to multiplex via the messages that we send to the app.
If I understand correctly, for the moment, if I want to create a Recipe that sends a WebPush notification, I need to go through the following steps:
Register a push subscription online, e.g. https://mozilla-services.github.io/WebPushDataTestPage/
Register a push subscription on the Foxbox
Write an app using this
push_uri
and a key corresponding topublic_key
.Setup a
resource
(FIXME: How is the resource connected to this uri?)res1
.That's too many steps. Moreover, I do not understand (yet) what 4) is for. So I'd like to start brainstorming how we can reduce the number of steps.
Could we, for instance, merge steps 2) and 4) into a single operation along the lines of:
this operation would create a new channel
foo
with kindWebPushNotification
. Future Recipes would then be able to send notifications directly tofoo
.Will probably want some kind of mechanism to be able to return values (in this case, channel ids) from send requests. I can add that as part of Decentralized Taxonomy, if necessary.
What do you think, @ferjm , @aosmond?
The text was updated successfully, but these errors were encountered: