That's great news! We plan to implement this in DAVx⁵, too: github.com/bitfireAT/davx5-ose…

Do I understand correctly that the approach for FCM w/o hosted gateway "only" works if there's only one VAPID key?

In case of multiple WebDAV-Push servers, they'd have different VAPID keys. In this case we could still provide a DAVx⁵ gateway or suggest another distributor, right?

But getting Push over FCM for the big fraction of users who only need Push for one account would absolutely be awesome!

[Push] Add Google FCM backend · Issue #1321 · bitfireAT/davx5-ose

Scope I'm sure that this feature request belongs here and not into Discussions. Description Since UnifiedPush 3 now supports VAPID and doesn't need a rewrite proxy anymore when VAPID is used, we ha...

^GitHub

@davx5app You have a VAPID keypair per server and on the Android side, you register to the distributor after fetching the server public key. In other words, there isn't only one VAPID key

I can update the blog post, if you have a suggestion to make it clearer

Even better! Do multiple VAPID keys work with "instance" in UnifiedPush.register? Is there a limit of max VAPID keys? Do we need to renew the registration?

Sorry if these things are already covered by the docs. I haven't read everything in detail yet, but trying to get an overview.

@davx5app You can use a VAPID key per instance/registration.

Some distributor may limit the number of registration per application, but the known distributors don't have that kind of limit at this moment, and the limit should be high enough to not be reached (>1000)

And we recommend to register again every time the application starts