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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: chrome notifications #91

Open
dburner opened this issue Aug 12, 2022 · 3 comments
Open

Request: chrome notifications #91

dburner opened this issue Aug 12, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@dburner
Copy link

dburner commented Aug 12, 2022

馃挕 The Idea
The ideea is simple, add support for chrome notifications.

The implementation might not be possible l, didnt look into these too much but apparently they require some keys/ token exchange, and possibly a persisted state.

If this could be done it could prove useful.

Maybe use the url format to pass the tokens to apprise, and let the parent app generate the tokens.

馃敤 Breaking Feature
Probably none.

@dburner dburner added the enhancement New feature or request label Aug 12, 2022
@caronc
Copy link
Owner

caronc commented Aug 16, 2022

I had a quick look at the notifications. Chrome/Firefox/Etc all support notification from within websites after you accept/agree to allowing it to send a notification, but not from outside (where Apprise resides).

Maybe something for the Apprise API?

@WebKenth
Copy link

@caronc it's pretty easy to solve

Launch apprise as a PWA with notifications enabled ( the webinterface could be modified to serve as a notification hub for browsers )

now the PWA can send as many notifications in the background as you want

@caronc caronc transferred this issue from caronc/apprise Aug 17, 2022
@caronc
Copy link
Owner

caronc commented Aug 17, 2022

Issue transferred to apprise-api repo

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

No branches or pull requests

3 participants