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

Is there something like Apprise for pulling notifications? #420

Open
regisb opened this issue Aug 8, 2021 · 4 comments
Open

Is there something like Apprise for pulling notifications? #420

regisb opened this issue Aug 8, 2021 · 4 comments
Labels

Comments

@regisb
Copy link

regisb commented Aug 8, 2021

Question

Hi all! 👋 First of all, apologies if this is not the right place to ask this question. Feel free to close immediately ;)

I am looking for the equivalent of Apprise, but for pulling existing notifications instead of pushing new ones. I would love to be able to centralise notifications from all social networks and data sources that I am subscribed to and store them in a single data store. Does such as service already exist?

Thanks!

@regisb regisb added the question label Aug 8, 2021
@caronc
Copy link
Owner

caronc commented Aug 8, 2021

What an awesome question. 🚀 ❤️ That sounds like a fantastic idea! I love it!

This solution could technically fit within this project as all of the underlining calls eventually group each service apart from another and leverage a single send() function. There is no reason not to leverage all of the API connectivity the Apprise Notification Plugin modules don't already handled here and just additionally support a get() function as well (just thinking out loud here).

One would have to go back through all of the API end points of each (Apprise) service and improve upon it. I could envision opening a thread/async (live) connection to each end point. Some services (like Twitter for example) provide a live-streaming mechanism that could just be passed along. Others would require a type of polling loop and frequent check for updates. But to convert all of those crazy API's back into a simple to handle/ingest API would be awesome.

Quite honestly, I'm not sure if I can/will take on the task; at least not yet anyway, It's quite an undertaking; but I would certainly consider it. Kudo's again for such a fantastic idea.

I'm worried this ticket is going to be one that stays open for a while, but I simply refuse to close it. Maybe some brave soul will consider tackling it themselves. 🙂

@mgray88
Copy link

mgray88 commented Jan 22, 2022

As an addendum to this as I feel it's related, would be the ability to wire the two systems to each other. i.e. get()ing a message could cause 1 or more send()ers to either forward the message or create a new one.

I was originally looking for some way to have Apprise subscribe to a local MQTT topic and forward that message to other services, when I found this issue

@caronc
Copy link
Owner

caronc commented Jan 22, 2022

I really love that idea too @mgray88. Would have to think how to tie the configuration together.

Something like further leveraging the tagging already in place for send() calls. A tag that matched a get() would handle the route (to the corresponding send that is)

@clach04
Copy link

clach04 commented Apr 30, 2022

Not 100% what was asked for but take a look at https://github.com/jpmens/mqttwarn / - Mqtt relay to XYZ. It only source is mqtt but it can emit to others

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

No branches or pull requests

4 participants