My thinking is that if we make a bug in the plugin's update logic, we'll have to make a new release to fix it while we can update the server's code any time without any release and it also offers more flexibility in case we need to change something in the future.
This is a good point.
Still, I think it would be best to let the plugin decide whether to update or not.
But we can definetely improve the server response and provide more information, e.g. like suggested in #1314 (comment) but as response instead of request.
Having the logic in the plugin would not require to send any information to the server and so be more privacy friendly.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.