[GH-ISSUE #7] Support for "up.conversations.im" #9

Open
opened 2026-03-02 03:53:51 +03:00 by kerem · 2 comments
Owner

Originally created by @pepper3k on GitHub (Oct 23, 2024).
Original GitHub issue: https://github.com/draga79/NotiMail/issues/7

Hi there, amazing project you have created here. I have tested it with ntfy.sh and the results are awesome! 😍

I see that you support a large number of push providers, whould it be difficult to support another UnifiedPush provider, namely "up.conversations.im"?

This is an implementation that is compatible with XMPP clients (Conversations and any of its forks).
The significane here is that if I want to use an XMPP client with unified push and also use email with unifiedpush (using your script), I would need to have both conversations and ntfy.sh installed and maintaining connections to 2 separate unifiedpush servers, which would be suboptimal to say the least and defeat the purpose of unifiedpush which is to have everything going through a single connection.

This is the link to the repo:

https://codeberg.org/iNPUTmice/up

The documentation looks excellent to me and after reviewing your code, it seems to me that you have designed this application in such a way that it would be very easy to add this functionality.

Do you think that adding this is possible?

Originally created by @pepper3k on GitHub (Oct 23, 2024). Original GitHub issue: https://github.com/draga79/NotiMail/issues/7 Hi there, amazing project you have created here. I have tested it with ntfy.sh and the results are awesome! :heart_eyes: I see that you support a large number of push providers, whould it be difficult to support another UnifiedPush provider, namely "up.conversations.im"? This is an implementation that is compatible with XMPP clients (Conversations and any of its forks). The significane here is that if I want to use an XMPP client with unified push and also use email with unifiedpush (using your script), I would need to have both conversations and ntfy.sh installed and maintaining connections to 2 separate unifiedpush servers, which would be suboptimal to say the least and defeat the purpose of unifiedpush which is to have everything going through a single connection. This is the link to the repo: https://codeberg.org/iNPUTmice/up The documentation looks excellent to me and after reviewing your code, it seems to me that you have designed this application in such a way that it would be very easy to add this functionality. Do you think that adding this is possible?
Author
Owner

@draga79 commented on GitHub (Nov 3, 2024):

Hi, thanks.
I'll have a look at it as soon as I'll have some spare time. Keeping this open as reference.

<!-- gh-comment-id:2453391078 --> @draga79 commented on GitHub (Nov 3, 2024): Hi, thanks. I'll have a look at it as soon as I'll have some spare time. Keeping this open as reference.
Author
Owner

@pepper3k commented on GitHub (Nov 3, 2024):

As your python is probably better than mine 😸 I would suggest you take a look at this first, while I look at the docker support issue, so you don't need to waste your time with peanuts. 🥜

<!-- gh-comment-id:2453392821 --> @pepper3k commented on GitHub (Nov 3, 2024): As your python is probably better than mine :smile_cat: I would suggest you take a look at this first, while I look at the docker support issue, so you don't need to waste your time with peanuts. :peanuts:
Sign in to join this conversation.
No labels
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/NotiMail#9
No description provided.