What’s the “unsupported community build of Nextcloud”?
What are these “push notifications” (web, mobile, both - NC Talk also affected)?
What means “limited”? Is there kind of a rate limit
with delayed delivery?
“hard” rate limit
no notifications at all?
What’s that “free service”? Can this be self hosted not to “overload the free service”?
I wasn’t able to find any official statement/documentation on this.
I mean, that looks fishy, just like NC is trying to force bigger instances into a subscription: “If you have no subscription, we reduce the features”. With NC 25 it’s some kind of “free push notification service”, but what comes next? Some apps are only available for subscribers?
If I remember correctly, this was exactly the reason for the fork from ownCloud years ago…
So, a lot of questions, hope that these can be clarified by an official satement.
I feel like I read at some point they were using google’s Firebase for cloud push but can’t find confirmation for that, if so it’s usually non-trivial to swap that out due to how clients interact with it. I do know that if you use the F-droid built Nextcloud applications on Android Push notifications are disabled. You still end up with polled notifications which isn’t that bad (except with NC Talk, it’s unusable).
I feel that’s it’s fair that they rate-limit free push notifications for larger user-bases, after all it’s costing them money, I’ll note RocketChat does the same thing so you could see this as a “standard” way of encouraging community use while avoiding burdensome costs.
Afaik this has been discussed before (not sure whether I saw that discussion on GitHub or on the forums) Anyways, @dugite-code has summed up the problem well as far as I can tell with my limited knowledge. Also, as far as I understand it, in Nextcloud 25 only the message about the “Rate Limit” is new, whereas before it just didn’t always work reliably. Now the users at least know what to expect.
Yep, afaik pretty much all bigger opensource projects that are using Google’s Firebase for cloud push notifications are facing this issue…
Thank you for Nextcloud 25. Even though many are happy about the new features of Nextcloud 25. Those who work productively with their Nextcloud should perhaps wait a little longer. I always do that - not only with Nextcloud.
You do not have to use the release on the first day of the new release. Most Windows users don’t do that either on Windows 10/11 You wait until the software has aged a little.
Ok. Of course, I’ve had it on my test system for a few weeks now. I was so curious
Thanks a lot for NC25. Upgrading from 24.0.6 to 25.0.0 based on the official docker images works smooth. Most of as incompatible marked apps - important for me is fulltext-search with elastic - works also atm. Great work!
That’s the problem: I wasn’t able to find any official documentation. Just stumbled upon the message from the screenshot in a test instance and took a look at the source code to find out what’s going on.
I’m just curious: Today NC disables or limits access to the notification service, but what comes next? Subscriber-only apps? Max. number of users without subscription? This could lead into the wrong direction imho.
You are grossly overreacting. They are offering push notifications when before they offered none. Limiting it to 500 whatever per Nextcloud server seems more than reasonable, because they don’t have to offer anything.
I agree that I’d like to see some clear documentation on it.
With no official information, we can only guess what’s going on.
But when there are no notifications at all in some circumstances, this would be a pretty hard cut.
Notifications is not a new feature, this was part of the very first version of NC (and OC before).
I don’t want be be gross here, I’m really sorry if it came across that way.
But providing no information at all about such a change is not the best way. Imho this should be openly communicated before putting it into a release.