View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000768 | unreal | ircd | public | 2003-03-04 22:37 | 2003-11-20 19:46 |
| Reporter | jollino | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Summary | 0000768: (idea) second parameter for /nick | ||||
| Description | I just had an idea (probably lame?) about the nick command. How about using a second parameter to be forwarded to the services for identify? That is, using /nick foo bar would be like doing: /nick foo /msg [email protected] identify bar Is this totally unfeasible? | ||||
| Additional Information | Still on b14, need to find the time to upgrade to b15 :P | ||||
| 3rd party modules | |||||
|
|
I don't understand why not to use two commands instead of one, but I think it would be better to have an ability to make aliases so it will send the given parameters to different targets... |
|
|
what do you mean? the second parameter would of course be sent to [email protected], since most of the time nickserv is just called nickserv. or maybe this could be configurable in the network file.. it would be quicker to let users change their nicks and identify with a single command. |
|
|
Well I don't totally think it is a bad idea, but it really can't work. Problem is, mIRC. If I remember, mIRC has /nick with the format: /nick newnick [altnick] where altnick is a nick to use if newnick is already in use. I can definately see this causing problems when users try this... "I type /nick mynick mypass and it doesn't identify me!" |
|
|
Currently there is no way to use real commands in aliases, but if it was coded, I would be happier to even specify what parameters goes to what targets, for example, the following command /nsid <nick> <password> would first do a /nick <nick> and second /msg nickserv identify <password>. But... I think we shouldn't think about suggesting more and more features for making aliases, because it would result something like an alias scripting feature for UnrealIRCd, but notice, that too much features make the program slower and buggier. |
|
|
codemastr: well, that'd be a client bug :P the NICK command should take a single argument, as per-rfc... angrywolf: originally, this was not an alias idea... it was adding a functionality to a command that's already there :) |
|
|
jollino: Yes, but I like thinking about alternative/other ideas. :)) |
|
|
don't be always so revolutionary ;) lol |
|
|
Bad idea IMO, I thought at the same issue as codemastr. You can easily accidently set your alternate nick to your password if you are not connected (yet)... ouch. Btw, how a client threats commands like (/bla or /nick, or whatever) is totally up to the client, RFC1459 is about the client<->server _protocol_. edited on: 03-05 23:10 |
|
|
And my idea? :) |
|
|
Are you so lazy to ask for such a lame command ? Are you assisted people so that you need things to do everything for you ? What is the next request now ? The IRCd chatting for you ? erf... On many irc network, where nick service is available, an alias exists as '/IDENTIFY pass' so /NICK LazyLamer & /IDENTIFY SoHardToType is working perfectly... and as AngryWolf stated, adding too many features will result in bugs and slower soft and I really think this is completely client side feature |
|
|
dear Goddess, mine was just a suggestion, an idea, a request for comment. i never said "go and do it, coders". consider having some valerian. |
|
|
lol don't worry, I'm not dangerous, I don't bite :P ok let explain my POV: 1st: this thing is lame, you said it yourself ;) 2nd: most people don't even know how to use the /NICK command, so you and others people who like to help will have to explain these users that they can use this command... and so for most of them, to explain why... to explain there is a service called nickserv, to guard their nick, and so this command helps them with nickserv system... etc etc... put your brain on a plate, take a gun, shoot as will... 3rd: this kind of think can be done so easily in a script or by the client directly... take any script kiddie and he will do an alias allowing you to do that, in mIRC, xchat (perl script), bitchx, even kvirc... btw this is not the discussion 4th: NickServ, ChanServ, OperServ, HelpServ, BotServ, StatServ, LoveServ, SuckMyDickServ and so on are SERVERS, meaning Unreal runs well with or without them... with this solution, the ircservices should also be modified, to not send the nickserv notices if it receive the password in, let's say a short time after the nick change... 4th1/2: "why only for nickserv ?" ... I let you imagine what will happen for other services... edited on: 03-06 15:38 |
|
|
I think they rather called Services :)) Using one server for each Service is a bad idea. But your poins are good! |
|
|
Well no one really ever provided a sane way to implement this, so what I'd just say is, if you want it, script it into your client. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-04-11 02:35 |
|
Status | new => resolved |
| 2003-04-11 02:35 |
|
Resolution | open => no change required |
| 2003-04-11 02:35 |
|
Assigned To | => codemastr |
| 2003-04-11 02:35 |
|
Note Added: 0002239 | |
| 2003-11-20 19:46 | syzop | Status | resolved => closed |
