We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have 2 requests:
The first feature would be an automatic timer that reactivates RYS after a certain period of time once you have deactivated it.
The second feature would be an option to automatically deactivate reactive RYS after watching a certain number of videos.
Sometimes, I need to deactivate the extension, but I forget to reactivate it when I no longer need it.
The text was updated successfully, but these errors were encountered:
I believe the first feature exists already, screenshot attached
The second feature sounds like a decent idea, I'll add to my list.
Sorry, something went wrong.
Ok, thanks a lot 👍
I've just seen that the first feature is available
I have 2 requests: The first feature would be an automatic timer that reactivates RYS after a certain period of time once you have deactivated it. The second feature would be an option to automatically deactivate RYS after watching a certain number of videos. Sometimes, I need to deactivate the extension, but I forget to reactivate it when I no longer need it.
The second feature would be an option to automatically deactivate RYS after watching a certain number of videos.
Hi, I made a mistake
deactivate reactivate
No branches or pull requests
I have 2 requests:
The first feature would be an automatic timer that reactivates RYS after a certain period of time once you have deactivated it.
The second feature would be an option to automatically
deactivatereactive RYS after watching a certain number of videos.Sometimes, I need to deactivate the extension, but I forget to reactivate it when I no longer need it.
The text was updated successfully, but these errors were encountered: