How will these changes affect RClone?
Wow, that is a rabbit hole!
Rclone users using the default rclone key may be affected. Rclone users who have been making their own keys won't be affected, though they may have to mark their apps as internal.
I'm going to wait until I'm emailled before attempting to get rclone verified as I'm not sure all the wrinkles are out of the process yet!
In the next few months, we will start to notify impacted developers of the policy changes and will provide additional guidance on how to meet the updated policy requirements.
I just spent a couple of hours trying to figure out whether I should do anything. I'm assuming that without verification there will be limits placed on file creation?
I think the limits are on token refresh rates actually. You can mark your app as internal (follow the Learn More link) and the warning will go away.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.