This would prevent unnecessary cycling since if you don't have access in a registered channel, cycling isn't gonna do anything.
The problem is determining if a channel is registered or not. Some networks' services set a channel mode on registered channels, while some have no clear indication.
This would prevent unnecessary cycling since if you don't have access in a registered channel, cycling isn't gonna do anything.
The problem is determining if a channel is registered or not. Some networks' services set a channel mode on registered channels, while some have no clear indication.
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1411670-autocycle-shouldn-t-cycle-registered-channels?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:27581096 -->
This would require a lot of special-case code and may well be impossible if you can't detect the IRCD + Services used.
This would require a lot of special-case code and may well be impossible if you can't detect the IRCD + Services used.
<!-- github-comment-id:35071685 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This would prevent unnecessary cycling since if you don't have access in a registered channel, cycling isn't gonna do anything.
The problem is determining if a channel is registered or not. Some networks' services set a channel mode on registered channels, while some have no clear indication.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
You could use
/msg *autocycle add !#registeredchannelThis would require a lot of special-case code and may well be impossible if you can't detect the IRCD + Services used.