6
61
Fork
You've already forked android
5

Element X does not work #8

Closed
opened 2025年01月25日 18:32:08 +01:00 by Atemu · 8 comments

According to its debug menu, it gets a 404. (See attached screenshot.)

I tried changing the UP provider to https://ntfy.sh but sunup somehow doesn't recognise it as a UP provider?

According to its debug menu, it gets a 404. (See attached screenshot.) I tried changing the UP provider to https://ntfy.sh but sunup somehow doesn't recognise it as a UP provider?

I have the same issue. Mercurygram doesn't work either.

I have the same issue. Mercurygram doesn't work either.
Owner
Copy link

@Atemu wrote in #8 (comment):

According to its debug menu, it gets a 404. (See attached screenshot.)

I tried changing the UP provider to https://ntfy.sh but sunup somehow doesn't recognise it as a UP provider?

There is a bug in Element-X, the patch is merged but not yet released. Shildinext has already the fix

@Atemu wrote in https://codeberg.org/Sunup/android/issues/8#issue-959745: > According to its debug menu, it gets a 404. (See attached screenshot.) > > I tried changing the UP provider to https://ntfy.sh but sunup somehow doesn't recognise it as a UP provider? There is a bug in Element-X, the patch is merged but not yet released. Shildinext has already the fix
Owner
Copy link

@balint wrote in #8 (comment):

I have the same issue. Mercurygram doesn't work either.

They don't use webpush, which is now required. Maybe they can use a gateway for that

@balint wrote in https://codeberg.org/Sunup/android/issues/8#issuecomment-2655061: > I have the same issue. Mercurygram doesn't work either. They don't use webpush, which is now required. Maybe they can use a gateway for that
Author
Copy link

Indeed Schildichat Next does work!

It's still weird that I can't switch to ntfy.sh as the UP server though; what's up with that?

Indeed Schildichat Next does work! It's still weird that I can't switch to ntfy.sh as the UP server though; what's up with that?
Owner
Copy link

Because sunup isn't a ntfy client. It uses mozilla's autopush server

Because sunup isn't a ntfy client. It uses mozilla's autopush server

Intro:

Matrix does not support UnifiedPush or WebPush native.
Here is a MSC to support WebPush (and with it UnifiedPush) in there protocol Standard: https://github.com/matrix-org/matrix-spec-proposals/pull/4174

Current state:

We need a transformation between the Matrix Push to the UnifiedPush API format.
Therefore was common-proxy from UnifiedPush developed: https://codeberg.org/UnifiedPush/common-proxies

SchildiChat run this proxy (but Mozilla not).

This translation from matrix to UnifiedPush is native implemented into ntfy.sh (so you do not need common-proxy to run, if you run ntfy.sh).

Other matrix-client like Element(-X) has to solutions:

  • wait till MSC4174 is defined and implemented
  • run a own autopush-rs (the WebPush server from Mozilla) with common-proxy (or use my one https://push.chaos.fyi)
  • use a different UnifiedPush-Provider till MSC4174 is ready

Maybe more details here: https://github.com/element-hq/element-x-android/pull/3388#issuecomment-2451406904

## Intro: Matrix does not support UnifiedPush or WebPush native. Here is a MSC to support WebPush (and with it UnifiedPush) in there protocol Standard: https://github.com/matrix-org/matrix-spec-proposals/pull/4174 ## Current state: We need a transformation between the Matrix Push to the UnifiedPush API format. Therefore was common-proxy from UnifiedPush developed: https://codeberg.org/UnifiedPush/common-proxies SchildiChat run this proxy (but Mozilla not). This translation from matrix to UnifiedPush is native implemented into ntfy.sh (so you do not need common-proxy to run, if you run ntfy.sh). Other matrix-client like Element(-X) has to solutions: - wait till MSC4174 is defined and implemented - run a own autopush-rs (the WebPush server from Mozilla) with common-proxy (or use my one https://push.chaos.fyi) - use a different UnifiedPush-Provider till MSC4174 is ready Maybe more details here: https://github.com/element-hq/element-x-android/pull/3388#issuecomment-2451406904
Owner
Copy link

Element-X is supposed to use the gateway hosted on unifiedpush.org, but they have introduced a bug a few versions ago that prevented to use it. It has been fixed here: https://github.com/element-hq/element-x-android/pull/4101 but this is not released yet

Element-X is supposed to use the gateway hosted on unifiedpush.org, but they have introduced a bug a few versions ago that prevented to use it. It has been fixed here: https://github.com/element-hq/element-x-android/pull/4101 but this is not released yet
Owner
Copy link
It has been released: https://github.com/element-hq/element-x-android/releases/tag/v25.02.0
Sign in to join this conversation.
No Branch/Tag specified
main
1.2.3-rc1
1.2.2
1.2.1
1.2.0
1.1.0
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
0.2.2
0.2.1
0.2.0
0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
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
Sunup/android#8
Reference in a new issue
Sunup/android
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?