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

Centralise pushing entries to third parties via apprise #1970

Closed
1 task done
jeankhawand opened this issue Jul 8, 2023 · 1 comment · Fixed by #1971
Closed
1 task done

Centralise pushing entries to third parties via apprise #1970

jeankhawand opened this issue Jul 8, 2023 · 1 comment · Fixed by #1971

Comments

@jeankhawand
Copy link
Contributor

Currently miniflux support pushing entries to telegram and matrix. I was thinking if we can centralise this using https://github.com/caronc/apprise-api this will ensure covering 50+ notification / messaging service.

Reflections

will have 2 input texts in Integrations section:

  1. text area where user add services uri separated by new line as documented over here.(https://github.com/caronc/apprise/wiki/URLBasics)
  2. host url e.g. apprise:8080 (in case user is running apprise-api in a docker-compose and exposing it to same network as miniflux) we have to validate if apprise is accessible or not

Practical implementation

a post request to /notify/ will reach apprise-api as follows:

{
"_comment1":"service url are sepearted with comma or spaces"
"urls": "mailto://user:[email protected],tgram://123456789:abcdefg_hijklmnop/12315544/?topic=1234567,matrixs://nuxref:[email protected]/#general/#apprise", 
"title": "Entry Title",
"body":"entry.summary - [Read more](https://entry.url)"
}

CC @fguillot

I am willing to work on it just need to check if it will comply with opinionated approach (I would say yes cause at this stage we don't have to integrate every notification / messaging service)

@jeankhawand
Copy link
Contributor Author

#1490

@jeankhawand jeankhawand mentioned this issue Jul 9, 2023
2 tasks
@fguillot fguillot linked a pull request Aug 1, 2023 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant