Long answer to describe a little bit how works push notifications.
Push notifications on a device works with the push provider of the
device vendor (for example, APN for iOS). A notification pass through
this provider and is connected to your phone. Because it uses
authentification, only nodes which have some infos can send
notifications to your phone (like a certificate).
In short, if you want to use notifications, you will ask a node to
listen the DHT for your phone. When a node receives a new value it will
send a wake up notification through a push server (which have infos to
send notifications). This push server will use the API of the push
provider which will send the notification to your phone (and your phone
will wake up and get the value from the DHT)
So, technically, the push provider is a central point.
I wrote a this on the wiki:
https://github.com/savoirfairelinux/opendht/wiki/Push-notifications-support
Have a nice day,
On 01/16/2018 02:21 PM, Maxim Cournoyer wrote:
----- Original Message -----
From: [email protected]
To: "Maxim Cournoyer" <[email protected]>
Cc: [email protected]
Sent: Tuesday, January 16, 2018 1:26:05 PM
Subject: Re: [Ring] Sending failes or takes hours even if my contacts are online
Hi Maxim,
you mean that my Android contact's should check their power settings, right?
Yes, if your contacts are using Ring on Android, they would have to make sure
their Ring client is not "power optimized" by Android.
This isn't very user friendly; we are working on push notifications that should
make things easier in this regard.
Btw. do push notifications work in a decentralised network - without connecting
to servers running in the background?
Short answer: no. The push service frameworks available on mainstream mobile
platforms (Android, iOS) are centralized by nature: a connection is at all
times maintained between them and the push server, AFAIK.
Maxim
