##gsoc-india's log is at ?q=bot/log/%2523gsoc-india
Gurpartap Singh - August 5, 2008 - 11:41
| Project: | Bot |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
Description
#punjabi's log is at ?q=bot/log/punjabi
##gsoc-india's log is at ?q=bot/log/%2523gsoc-indiaWe could trim those twin hashes; the channel names are unique in a network/freenode, regardless of this double hash thing.
#1
#2
Hrm. This is actually a bit tougher to handle than I thought - SOMETHING would have to show up in the URL to handle, say, #test and ##test as two unique channels at the same time. Otherwise, there'd be no way of determining which log you were actually looking at. I agree that this is probably pretty rare but, then, so is the notion that an IRC channel would have two hashes for its name ;)
Possibilities are:
* Force the # for all URLs (making them all really ugly)
* Do nothing; the above is as right as it's gonna be.
At the moment, I'm leaning toward doing nothing - the fact that it "works" already, but creates, certainly, an ugly URL, is probably something that Freenode people should put up with. I suppose I could add some case-scenario code - "if we're not also in #gsoc-india, then strip all hashes from ##gsoc-india" - but I'm not a huge, huge fan of that (or the infinite recursion of ###gsoc-india, etc.).
Thoughts?
#3
Talked it over in IRC; gonna leave as is.