elf-pavlik commented 1 year ago

It should supersede WebPushSubscription2022

This should follow updates to latest 0.2 of the protocol.

Few suggestions:

reuse notify:sendTo (former target) and just define it as Push Endpoint from the PUSH API
advertise vapidPublicKey in the Subscription Resource description where Subscription Client will make Subscription Request. Discovery Resource also includes that description.

@uvdsl

elf-pavlik commented 1 year ago

so they don't have to be defined by us.

This PR also provides a very generic Terminology section that can be included, it just references the Solid Notifications Protocol where most of the terms are originally defined.

elf-pavlik commented 7 months ago

I will be working on this issue over the following weeks; I'm also working on a workaround for the limitation of having PushSubscription tied to a single Notifications Sender.

https://github.com/janeirodigital/sai-js/issues/83

I have an initial demonstrable implementation doing the following:

sequenceDiagram
  participant App
  participant AA
  participant RS1
  participant RS2
  participant RS3

  App ->> AA: Create Web Push channel
  AA ->> RS1: Create Webhook channel
  loop Every notification
    RS1-->>AA: Deliver notification
    AA -->>App: Forward notification
  end
  App ->> AA: Create Web Push channel
  AA ->> RS2: Create Webhook channel
  loop Every notification
    RS2-->>AA: Deliver notification
    AA -->>App: Forward notification
  end
  App ->> AA: Create Web Push channel
  AA ->> RS3: Create Webhook channel
  loop Every notification
    RS3->>AA: Deliver notification
    AA -->>App: Forward notification
  end

solid / notifications

Create WebPushChannel2023 #140

160 centralizes all custom references in one shared json file, all W3C and IETF references are already available at https://www.specref.org/ so they don't have to be defined by us.