Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

smartphone notification service #1547

Closed
ghost opened this issue May 20, 2018 · 4 comments
Closed

smartphone notification service #1547

ghost opened this issue May 20, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented May 20, 2018

I think it would be useful to have a notification service available for important events occuring in desktop application (offer taken, payment sent, etc) when the user is away.
For example, Pushover is a great service, allowing the user to receive notifications on your devices (phones, tablets, etc) from any application using an API which is basically an URL post to their servers.

@ghost ghost changed the title notification service smartphone notification service May 20, 2018
@ManfredKarrer
Copy link
Member

Pushover sounds good but it is not clear to me how the complete process would work exactly.
We don't want that users need to register at their service (usability and privacy issue) or that the Bisq app connects directly to their service (privacy issue, all runs over Tor by default in Bisq - those services often don't support API calls over Tor).

Can you define more detailed the model in a proposal?
There are some rough ideas how it can work also without any 3rd party service...

@ghost
Copy link
Author

ghost commented May 21, 2018

Right, I missed the strong privacy requirements... In that context, my proposal does not work obviously:

  • it requires an account on their website
  • app must perform an API call to their website (no idea if it would work with Tor)

I'll check about no-3rd-party solutions...

@blabno
Copy link

blabno commented May 21, 2018

https://github.com/mrosseel/bisq-api/issues/67

The problem with notifications, be it FCM, GCM, or any other is that it requires registering an account with Google or other provider and set those credentials up with the backend (desktop or bisq-api).
Obviously, we cannot have the same credentials stored in the source code as it would be abused.

@ManfredKarrer
Copy link
Member

Close that issue as a notification app is in development:
See: bisq-network/proposals#25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants