View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001562 | Anope Development (1.9.x series) | Chanserv | public | 2014-01-18 00:16 | 2014-02-08 03:32 |
| Reporter | Techman | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | Ubuntu Server | ||
| Summary | 0001562: Add numeric 328 (RPL_CHANNEL_URL) support to ChanServ | ||||
| Description | Numeric 328, channel URLs, have been sent via Atheme for a long time now, and I'd like to see Anope send channel URLs as well. The way numeric 328 in relation to services is pretty simple. If a channel has a URL set via ChanServ, when a user joins, send the numeric to the client. On InspIRCd, you must PUSH the numeric. Some optional configuration/defaults/wanted extras for this module is this: 1) Do not send channel urls to all clients on netbursts (ircd_chanurl does this and it is very annoying) 2) Do not send channel urls to all clients when the module is (re)loaded. 3) Perhaps have a way to track netsplits or something? If a user has joined the channel already and then a netsplit occurs, keep track of that so when the servers re-link, do not push the numeric to those clients. I don't know how to make this work, but if you can do so, I would at least add some kind of setting for it. 4) (if anyone has other suggestions on features put them in the comments) | ||||
| Steps To Reproduce | N/A | ||||
| Additional Information | This is a feature I want in Anope 2.0 because of the ircd_chanurl module: https://modules.anope.org/index.php?page=view&id=125 I run a patched version for use on InspIRCd-2.0 | ||||
| Tags | No tags attached. | ||||
|
|
No longer needed for 2.0 b/c of this: https://modules.anope.org/index.php?page=view&id=263 If such a module would ever make it to the set of bundled in modules, that would be nice. For now, I'll just close this. |
|
|
Thanks Adam. When is the next RC coming out btw? |
|
|
This could be in 2.0.1. No new features are going into 2.0.0 as we are in the RC stages. |
