MantisBT - Doomseeker
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001356Doomseeker[All Projects] Suggestionpublic2013-06-05 04:592018-09-29 14:43
Reporteramiga600 
Assigned ToZalewa 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version0.11 Beta 
Target VersionFixed in Version1.0 
Summary0001356: Ideas for DoomSeeker IRC
DescriptionI'd like to see the Connection Dialog made simpler, and have all the relevant options there, in a similar fashion to ZRC, example:'http://puu.sh/38EAu.png [^]'

Subtask 1740:
Please also support Numeric 005 (Server Support) and read the PREFIX= line and support all modes given, for example PREFIX=~&@%+(qaohv) - note there are some weird IRC networks which have weird modes, for example PREFIX=(yxqaohv)~&*!@%+ on irc.ntalk.de - Generally, If you support anything the server throws at you in PREFIX= this will make your IRC Client future proof, as almost all IRC servers throw PREFIX= support out in Numeric 005, If PREFIX= is not recieved, I'd assume PREFIX=@%+(ohv) as you are more than likely safe with that.

The following IRC Numerics should be forwarded to the channel window, as opposed to being shown in Status tab, as they give out vital information:
"{482} [Nick] [#Test] [You're not channel operator]" and so on.

332: Channel Topic should be output into the Channel as opposed to Status.
333: Topic Setby/Time, Example: "channelname > Set By [user] on $asctime($4) 

Whois data:
Numerics 311,379,378,307,319,312,320,317,318 could be forwarded to current channel window.
Numeric 317 is idle time/connection date

The rightclick menus could have a Whois option (/whois) and based on the PREFIX= have levels of operator, eg "Owner/Protect/Op/HalfOp/Voice" and the unset equivalents.

An Ignore option on the rightclick menus, possibly even a popup box where you can add users either via "nick!*@*" or "*!*@host" and so on.

If you are not a channel operator, rather than fading out "OP/Halfop/Voice etc", if self-op does not work (/mode [chan] +o [nick]), then attempt to use services, for example: /ChanServ OP [chan] [selected-nick]

Subtask 1738: At the moment CTCP commands do not work, if they are not going to be added, possibly a way to stop them opening a message window up with the command inside, eg currently it opens up a PM window.

Userlist issue, when clicking a name it turns orange, when you click off the userlist, the orange highlight does not disappear, would be good if that could be removed.

Option to color users in list/channel by Operator Symbol, eg ~Purple &Yellow @Red %Green +Blue [modeless]Grey and possibly an Idler option?

Possibly Away checking on channels with less than 200 users in (this is done via /WHO #channel, and 7th row on is modes, G=Away H=Here)
Steps To ReproduceN/A
Additional InformationN/A
TagsNo tags attached.
Relationships
parent of 0001740closed Zalewa Support PREFIXES provided by IRC networks. 
parent of 0001738closed Zalewa Support for /me command 
Attached Filespng ss (2013-07-27 at 10.23.00).png (19,122) 2013-07-27 12:48
https://zandronum.com/tracker/file_download.php?file_id=1030&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2013-06-05 04:59amiga600New Issue
2013-06-20 21:12ZalewaNote Added: 0006472
2013-06-20 22:07amiga600Note Added: 0006474
2013-06-21 09:58amiga600Note Edited: 0006474bug_revision_view_page.php?bugnote_id=6474#r3560
2013-07-26 18:39ZalewaNote Added: 0006817
2013-07-27 09:23amiga600Note Added: 0006821
2013-07-27 09:23amiga600Note Deleted: 0006821
2013-07-27 09:24amiga600Note Added: 0006822
2013-07-27 12:48ZalewaFile Added: ss (2013-07-27 at 10.23.00).png
2013-11-15 23:24ZalewaAssigned To => Zalewa
2013-11-15 23:24ZalewaStatusnew => assigned
2014-03-09 18:56ZalewaDescription Updatedbug_revision_view_page.php?rev_id=4563#r4563
2014-03-09 18:56ZalewaDescription Updatedbug_revision_view_page.php?rev_id=4564#r4564
2014-03-09 18:57ZalewaNote Added: 0008370
2014-03-09 21:16Blzut3Relationship addedparent of 0001740
2014-03-09 21:17Blzut3Relationship addedrelated to 0001738
2014-03-09 22:58ZalewaDescription Updatedbug_revision_view_page.php?rev_id=4567#r4567
2014-03-11 22:20ZalewaDescription Updatedbug_revision_view_page.php?rev_id=4571#r4571
2014-03-21 16:32ZalewaRelationship replacedparent of 0001738
2014-03-22 12:27ZalewaDescription Updatedbug_revision_view_page.php?rev_id=4587#r4587
2014-03-22 12:28ZalewaNote Added: 0008439
2014-11-23 18:51ZalewaNote Added: 0010943
2014-11-23 18:52ZalewaDescription Updatedbug_revision_view_page.php?rev_id=6011#r6011
2014-11-23 19:27ZalewaNote Added: 0010945
2014-11-23 19:28ZalewaDescription Updatedbug_revision_view_page.php?rev_id=6012#r6012
2014-11-23 19:39ZalewaDescription Updatedbug_revision_view_page.php?rev_id=6013#r6013
2014-11-24 19:18ZalewaNote Added: 0010957
2014-11-24 19:18ZalewaDescription Updatedbug_revision_view_page.php?rev_id=6018#r6018
2014-11-24 23:16ZalewaNote Added: 0010967
2014-11-26 19:45ZalewaDescription Updatedbug_revision_view_page.php?rev_id=6032#r6032
2014-11-26 21:44ZalewaNote Added: 0010978
2014-11-26 21:45ZalewaDescription Updatedbug_revision_view_page.php?rev_id=6033#r6033
2014-11-26 22:06ZalewaNote Added: 0010979
2014-11-26 22:06ZalewaStatusassigned => needs review
2014-11-26 22:07ZalewaNote Edited: 0010979bug_revision_view_page.php?bugnote_id=10979#r6035
2014-12-01 17:53ZalewaNote Added: 0011020
2014-12-01 17:53ZalewaStatusneeds review => needs testing
2015-03-22 20:06ZalewaStatusneeds testing => resolved
2015-03-22 20:06ZalewaFixed in Version => 1.0
2015-03-22 20:06ZalewaResolutionopen => fixed
2018-09-29 14:43WubTheCaptainStatusresolved => closed

Notes
(0006472)
Zalewa   
2013-06-20 21:12   
Explain how is this PREFIX thing useful. Also, explain why Doomseeker should assume any kind of information when that information is not given. From my perspective it looks like a nice and quiet way to horribly break something.
(0006474)
amiga600   
2013-06-20 22:07   
(edited on: 2013-06-21 09:58)
The PREFIX support would be a useful addition, for servers which support more than the standard @%+ prefixes.

It is considered safe to always assume @%+ for servers which do not relay PREFIX= information, as most of the servers which do not relay PREFIX only support the basic prefixes eg. @%+ so to assume that would not break anything on those servers.

I have never come across any problems by assuming those 3 modes in all the time I have been around IRC Networks, Generally though, the PREFIX= is always sent in the 005 numeric of the most popular IRCd's such as UnrealIRCd (which supports PREFIX=(qaohv)~&@%+ out of the box) and InspIRCd (which can support PREFIX=(yqaohv)!~&@%+ if specific modules were enabled), also try irc.ntalk.de which supports rather a strange set of prefixes, namely PREFIX=(yxqaohv)~&*!@%+

By reading and parsing PREFIX= your built in client, will in effect, support any modes the IRC server will specify there, This will also make your client future proof, and allow support for modes which are not directly handled by doomseeker irc.
(0006817)
Zalewa   
2013-07-26 18:39   
Okay, so some of these got implemented recently.
Can you please reupload the screenshot as attachment? The original link is dead.
(0006822)
amiga600   
2013-07-27 09:24   
yes of course'http://puu.sh/3MT5k.png [^]'
(0008370)
Zalewa   
2014-03-09 18:57   
I've moved support for "PREFIXES" to a sub-task ticket:
'http://zandronum.com/tracker/view.php?id=1740 [^]'
(0008439)
Zalewa   
2014-03-22 12:28   
CTCP support added:
'http://zandronum.com/tracker/view.php?id=1738 [^]'
(0010943)
Zalewa   
2014-11-23 18:51   
Support for various WHOIS codes added. All parsed WHOIS codes are now forwarded to network's active chat box, or to the status box if no chat box is active:
'https://bitbucket.org/Blzut3/doomseeker/commits/fd7a2067cb75caab608229fd392b19687b598674 [^]'
(0010945)
Zalewa   
2014-11-23 19:27   
WHOIS command has been added to the context menu:
'https://bitbucket.org/Blzut3/doomseeker/commits/50f1ebf7f9eb9c2e701d09959781cd3e54428b28 [^]'
(0010957)
Zalewa   
2014-11-24 19:18   
Focusing outside user list will clear the selection and the nickname highlight:
'https://bitbucket.org/Blzut3/doomseeker/commits/6e0a43b3d77f1735f60137a86f48b07df46d0682 [^]'
(0010967)
Zalewa   
2014-11-24 23:16   
This change adds 'Ignore user' option to user list and priv box context menu:
'https://bitbucket.org/Blzut3/doomseeker/commits/298b3fd83991c9c9156be61ea69449cf6df21eec [^]'

Ignore is indiscriminate. All communication from given user is blocked, which also includes private messages and CTCP.

There's no box to manage ignores on given network but I'll add that soon.
(0010978)
Zalewa   
2014-11-26 21:44   
List of ignored users can now be managed from chat box context menu:
'https://bitbucket.org/Blzut3/doomseeker/commits/b764b45ebea0a3b0ad91b7a351c3ea7445515737 [^]'
(0010979)
Zalewa   
2014-11-26 22:06   
(edited on: 2014-11-26 22:07)
All grayed out ideas were implemented and need to be tested. If there's anything that needs to be fixed or improved, the next beta build will be ideal to test and adjust.

Now, regarding unimplemented ideas:

Quote
I'd like to see the Connection Dialog made simpler, and have all the relevant options there, in a similar fashion to ZRC.


I've added an "Edit" button and simplified how last used network is selected. Beyond that, I like the connection dialog as it is and it'll remain like that for foreseeable future.

Quote
If you are not a channel operator, rather than fading out "OP/Halfop/Voice etc", if self-op does not work (/mode [chan] +o [nick]), then attempt to use services, for example: /ChanServ OP [chan] [selected-nick]


I'm reluctant when adding anything that's outside RFC 1459 and CTCP standards. I've already added several things that might cause conflicts depending on the used IRC daemon. Having such fallback is just too much in this regard.

Quote
Option to color users in list/channel by Operator Symbol, eg ~Purple &Yellow @Red %Green +Blue [modeless]Grey and possibly an Idler option?


I never liked this feature in IRC clients.

Quote
Possibly Away checking on channels with less than 200 users in (this is done via /WHO #channel, and 7th row on is modes, G=Away H=Here)


This would cause similar noise as the user list coloring. Moreover, it would also require Doomseeker to ping channels in regular fashion, and to hide /WHO responses to avoid generating spam in network status box. On the other hand, responses to /WHO that were explicitly sent by the user would need to be displayed anyway. Having the same response squelched or not basing on some temporary state stored only in the client memory is walking on thin ice. It can introduce bugs. For the same reason of avoiding such bugs I don't block /WHOIS replies on ban or ignore that are called from the context menu.

There are still some issues with the IRC client that I wrote down in a personal file. I plan to resolve them for the next build (or for the one that will come after that one). Still, I consider all requests from this ticket resolved.
(0011020)
Zalewa   
2014-12-01 17:53   
Update available on beta build channel and on DRD Team page. Please test.