| 98 |
|
No. When there is a valid reason for this, then possibly, but I honestly |
| 99 |
|
don't see why anyone needs it. |
| 100 |
|
|
| 101 |
– |
- Can I resv a local channel? |
| 102 |
– |
|
| 103 |
– |
Yes. It takes the same format as creating a resv on a normal channel: |
| 104 |
– |
/resv &clones :no clonebots! |
| 105 |
– |
|
| 101 |
|
- Do you support wildcard channel resv's? |
| 102 |
|
|
| 103 |
< |
No. This is mainly for speed reasons. When we are searching nicks, we |
| 104 |
< |
cannot just check if the nick, and the item in the list of resv'd nicks |
| 110 |
< |
are string equal, we have to check if they match, so we have to search a |
| 111 |
< |
full list. With channels however, we can search a hash table to see if an |
| 112 |
< |
entry exists, if it doesn't, then the channel isn't resv'd. We don't have |
| 113 |
< |
to search through all the channels. |
| 114 |
< |
|
| 115 |
< |
Besides.. it's legal for a channel to be called #*warez* anyway ;) |
| 103 |
> |
Yes. For an exact match, wildcard characters can be escaped with a |
| 104 |
> |
backslash. |
