Hallo Fediverse!
Wie kann ich bei Tusky erkennen, ob Unified Push korrekt arbeitet?
Ich nutze die F-Droid Version, finde aber keinerlei Einstellungen hierzu.
Nutze Conversations als Distributor und die UP Example App funktioniert.
Sachdienliche Hinweise willkommen.
#tusky #UnifiedPush

https://media.ccc.de/v/wicmp11-19-pushbenachrichtigungen-ein-blocker-fur-freie-smarthphones

Push notifications a blocker for free smartphones (DE/EN) : Great talk from Schabi to expose the necessity of a free push notifications system if we want a FOSS mobile ecosystem.

With 2 comments nevertheless ⬇️

#UnifiedPush

Pushbenachrichtigungen ein Blocker für freie Smarthphones

media.ccc.de

I started to try to make an @unifiedpush extension for @gnome on the basis of @kde's kunifiedpush.

Here is the repo on @Codeberg: https://codeberg.org/gelbphoenix/unipush

#UnifiedPush #Gnome #Development

unipush

Unified Push for GNOME

Codeberg.org

Ich habe in der APP 'ntfy' einen einzelnen Eintrag, kann ihn aber nicht zuordnen. Ich sehe nur die kryptische und vermutlich nutzerspezifische Themen-URL. Wie finde ich heraus, welche meiner Apps ntfy diesen Kanal für UnifiedPush benutz?

Unterstützt tusky ntfy?

#ntfy #UnifiedPush #tusky

RE: https://gultsch.social/@daniel/116199908378698603

I used the post from @daniel as a reminder to finally fix my #unifiedPush setup. In the journey to get rid of big tech dependencies a unified push service is really useful and I'm grateful about every app supporting unified push. (For me thats mainly Fedilab @apps and @davx5app)

The problem with my setup was that I run the HTTP(S) part behind caddy, since the host also has web services running. For that I had globally http_external_url = "https://xmpp.example.com/" set. The external URL for the UP component got overwritten by that and was wrongly reported. I now have the following snippet in my VirtualHost and it works:

Component "notify.xmpp.example.com" "unified_push" unified_push_secret = "randomstuff" unified_push_acl = { "@example.com" } http_external_url = "https://notify.xmpp.example.com/"

In caddy this works:

notify.xmpp.example.com { reverse_proxy localhost:5280 { header_up Host "notify.xmpp.example.com" flush_interval -1 } }

(Open in browser if your fedi client struggles with the formatting)

Daniel Gultsch (@[email protected])

If you are concerned about ntfy.sh recently turning into AI-slopware, you can replace both the #UnifiedPush Distributor and the curl-based status messaging with XMPP. You can keep your existing XMPP account and simply replace ntfy's functionality with a self-hosted Prosody instance. https://gist.github.com/iNPUTmice/4f58f15d9a8d2d09cfc586074184decb

Mastodon

Actually, even if you don’t care about #UnifiedPush, having this minimal #Prosody server that just accepts messages via a simple REST API and sends them out via #XMPP is great alternative to the various sendxmpp scripts out there.

https://gultsch.de/posts/xmpp-via-http/

Sending Jabber/XMPP Messages via HTTP

The goal of this tutorial is to set up a simple REST API that allows you to send XMPP messages to an existing XMPP account. This can be easily integrated into monitoring solutions or other scripts that send out status information. While there are command-line tools like go-sendxmpp that send messages by connecting to an XMPP server directly, this guide is specifically about providing an HTTP interface. curl "https://ntfy.stdmsg.tech:5281/msg/[email protected]" \ -u [email protected]:secret \ -H "Content-Type: text/plain" \ -d "Your flat white is done" Hint: If you don’t have an XMPP account to receive these messages, you can create one on a public server from within Conversations (F-Droid, Google Play) or another XMPP client of your choosing.

Daniel Gultsch

If you are concerned about ntfy.sh recently turning into AI-slopware, you can replace both the #UnifiedPush Distributor and the curl-based status messaging with XMPP. You can keep your existing XMPP account and simply replace ntfy's functionality with a self-hosted Prosody instance.

https://gultsch.de/posts/self-hosting-up/

Self-hosting UnifiedPush with Conversations as Distributor

You might have heard that XMPP in general, and Conversations in particular, make a great UnifiedPush Distributor. That is correct! However, you might find yourself in a dilemma: you already have an XMPP account with a trusted provider that you want to keep using, and you don’t want to host and maintain your own XMPP server. Furthermore, you may not feel comfortable using the publicly accessible Rewrite Proxy up.conversations.im. Luckily, you can easily self-host just the Rewrite Proxy component (the part that would otherwise default to up.conversations.im in Conversations).

Daniel Gultsch
Did you know that most Android #XMPP apps also work as a #UnifiedPush distributor and thus can easily replace apps like #ntfy (recently became vibe-coded) for this? Find our tutorial here: https://joinjabber.org/tutorials/service/unifiedpush/
Unified Push

UnifiedPush (UP) is an alternative for mobile push-notifications on Android that does not depend on the centralized Google FCM infrastructure for delivering notifications to your smart-phone. Especially for apps installed via the F-Droid catalogue this can be very useful and they recently wrote a nice explanation about it on their blog. Apps using UP While UnifiedPush is a relatively new technology, there has been already quite some up-take especially with Fediverse (ActivityPub) apps and a a few Matrix clients. The UnifiedPush website lists a few here. Contrary to these apps that use UP to send notifications, XMPP apps are more useful as so called "UP distributors" that act as the primary receivers of UP notifications. This is because XMPP is designed exactly for such type of purposes and even the Google FCM notification service uses XMPP under the hood.

JoinJabber

We will have a combined #XMPP and #UnifiedPush stand at #CLT2026 on March 28th and 29th. Come talk to us if you are curious about either! We will have merch for both, test devices, lots of advice, and I've even heard rumors about free Haribo.

XMPP Standards Foundation: https://chemnitzer.linux-tage.de/2026/en/programm/beitrag/204

UnifiedPush: https://chemnitzer.linux-tage.de/2026/en/programm/beitrag/411