Hello there! I have configured instance of Nextcloud Hub 26 Winter (33.0.2) with configured local push server. Mobile apps both on IOS and Android work fine and get push notifications without any problem, but desktop apps Windows and MacOS show âpush not availableâ in about screen. Is there any workaround on this? Both mobile and desktop apps work on same network.
Are you referring to the notify_push app or one of the third-party apps?
The notify_push app is not used for âpush notificationsâ on mobile platforms.
Correct, but indeed for the desktop client 
But for File push/sync, not for Talk
This app attempts to solve the issue where Nextcloud clients have to periodically check the server if any files have been changed.
Oh yes it is
Oh, thatâs a TIL for me. Thatâs not mentioned in the Readme. But the Nextcloud Snap wiki mentions using notify_push for Nextcloud Talk. So youâre right!
Not directly, but it says
Update notifications for nextcloud clients
It is used to not have to poll for new notifications and that is then also used in the talk desktop client to reduce delays for notification.
@mritzmann thanks for mentioning the snap wiki. are you referring to this:
[!TIP]
Set Nextcloud Talk push notification in config.php to enable notification
Setting Talk push notification
edit config.php and add/edit line in config.php
'has_internet_connection' => 'true',
or issue command on host:
occ config:system:set has_internet_connection --value="true"
I mentioned this as a Tip! and TBH Iâm not even sure if notify_push is actually necessary if you run the OCC command! maybe @SysKeeper can shed some light on this?
personally I never miss any Talk messages having both âclient pushâ, âtalk-push-notificationâ active. that includes local and federated chats â Requires âAndroid Nextcloud Services appâ on devices, so there are obviously a range of dependencies, but it works like a charm.
Yes. But to be honest, I find all these âhigh-performance backendsâ* a little bit confusing. And probably wonât be that interesting for me either, as I rarely use Nextcloud Talk 
@Vasilij_Lebedinskij But I hope you find a solution 
*personally I only use notify_push so that changes are synchronised more quickly. This works great!
does this mean, youâre not using a public certificate? if so, thatâs where you can turn the knob first.
I am shocked.
;-).
Let me try.
-
Mobile apps (Android, iOS), receive their notification through the corresponding vendor push system (FCM for Android, APNS for iOS) via our push proxy, therefore external requests from the instance are required. When you set
has_internet_connectiontofalse(!), the instance knows external requests are not possible and will not even try to send push notifications. Since the default ofhas_internet_connectionis alreadytrue, it does not change anything if you explicitly set it totruein the config. Only setting it tofalsewould be âproblematicâ.
That all being said, mobile clients do not care at all aboutnotify_push, it doesnât matter if itâs there or not. -
Talk Desktop/Web are different, thereâs no push system here (as of now, Iâll not go into WebPush). So to show the user if there are notifications or not, these clientâs will periodically poll an endpoint to tell them if there are new notifications or not. This is where
notify_pushcomes into play, which offers a websocket connection which allows the server to notify these clients about new notifications. So the periodic polling can be skipped or the interval can be increased. Since this all works without any external interaction,has_internet_connectionshould not have an effect there. (Should as I did not check the relevant code path, but I donât see why it would).
As per above has_internet_connection and notify_push are totally different things.
That is how it works âby design/per defaultâ. There are other ways, eg. thereâs some UnifiedPush implementation IIRC, but I cannot tell you more about these.
Hope that helps.
me too 
I hardly ever use it either.
First, because I canât realistically set up accounts for everyone I occasionally communicate with on my Nextcloud and expect them to use Nextcloud Talk, and for my closest contacts, I use a self-hosted Prosody XMPP server with Conversations as the client.
Why XMPP?
XMPP with Conversations behaves more like a classic instant messenger (like WhatsApp), which is typically what you want as a home user, rather than something like Slack (which Nextcloud Talk is more comparable to).
Instant notifications also work reliably, without Play Services or additional services like NextPush that drain the phoneâs battery. 
Oh, and by the way, video calls work well too with this setup, using a simple Coturn server and without the need for a high-performance backend.
Iâm absolutely shattered!! 
Federated Talk is the best thing since sliced bread 
Letâs move slowly back to the topic of that thread again and discuss the pros and cons of talk in a different one
@Vasilij_Lebedinskij Did that answer your question?
XMPP is federated by design, as it works more like email. However, I donât use server-to-server federation on my instance. In theory, though, anyone with an XMPP account can message anyone else with an XMPP account/address, provided their servers their on allow it.
That said, Iâm not trying to discourage anyone from using Nextcloud Talk, itâs a good solution. But for my personal needs as a home user, XMPP just fits a little better, and I quite like it.
ahhh⌠that could be misleading in the snap-wiki!
Iâm quite chuffed that folks like @mritzmann actually read the snap-wiki â thanks 
Itâs probably the talk desktop client without notify_push. Seems my explanation wasnât that good after all..
So there is push functionality in desktop app but no backend service on server for desktop apps, right?