The idea was to try not to send sensitive information through untrusted
media... that was why it was not sent from the beginning.
If we plan to replace GCM in the near future, I would go for sending the
payload for now so we don't get stuck... And sort it out down the road.
If we don't plan to replace GCM soon, then we need to implement our own.
Either way, would do the cheapest now, And then iterate from there.
On March 1, 2018 11:23:21 AM GMT-03:00, k@xxxxxxxxxxxxxxx wrote:
On 01/03/18 15:15, Emil Kroymann wrote:
Sending a payload seems to make sense to me, but I'm not that familiar
I can work on this, but I wanted to know what is the preferred way to
I think, when changing the backends, we will have some problems with
testing, since we need a new version of the backend deployed
somewhere, along with the old version of the backend for the previous
versions of the app.
I just wanted to clarify that from a backend point of view, rhizomatica
has not yet deployed this app to users publicly. There is no expected
uptime/service guarantee, or users really, to worry about. We are free
to deploy anything we want. However, pearl lagoon might want to make
sure something is running.
Rhizomatica has a server earmarked for this (called "cenizo")
Stefan has access, feel free to setup anything you want on it.