Last week I finished my fake/example/reference linux #UnifiedPush distributor written in rust.
This week I started at looking into implementing a distributor with ntfy.sh, I am currently unsure about integrating into an existing app like Notify or building a separate application.
You can find my progress here: https://gitlab.com/j0dev/rust/up_ntfy_distributor
I am also looking into a DBus api to manage/configure a distributor for integration into desktop environments like #Gnome / #Phosh.
@redstone #UnifiedPush specifies how a client application and application server communicate to find, register and communicate with a 'Distributor' which receives the notifications and transports them, how that side happens is up to the Distributor, so if those get transported trough ntfy, nextcloud, gotify or something else is not specified, but there need to be apps client-side to handle the protocol.
see: https://unifiedpush.org for everything
@topjor this looks dope, definitely something very needed...especially given recent news.
is UnifiedPush standardized on the client and server side or just the client side? Like Nextcloud has an app for UnifiedPush, would it be interoperable with a desktop client built for ntfy.shV