Definitely best to be in sync with core, but will you consider implementing both types if both remain in core?
Currently there is the
&username=user&api_key=key approach that is implemented and working, and if I understood Falco correctly he will also add support for the user_api_key?
Either works for me, as long as at least one of them work for private forums ).
Let’see how Falco approches this one, if I understand correctly this key will still be available only once, when first generated.
Which means that the user will have to succesfuly copy the webcal link the first time they open the Subscribe button? And then save it somewhere, if they want to use it again later in another calendar app (I can predict most won’t remember to save it, or if they do it will definitely NOT be in a secure way). Unless one key is only redeemable once.
And what will happen, if they click the Subscribe button again? Old key is revoked? New one generated? Another key generated?
This is much more work and more confusing for the end user then a single link. But let’s see how it will be imemented in core first