GNOME Bugzilla – Bug 768341
Clarify difference between temporary nick change and persistent nick change
Last modified: 2021-06-10 11:04:32 UTC
Created attachment 330813 [details] clarification of nick popover which promotes status indication (rev5) We have bugs such as Bug 755809 and Bug 722506 filed which indicate that it is not very clear that changing the nickname from the current nick popover is a temporary change (while changing it from the network properties is permanent). The reason for having the nick popover and having temporary changes possible in the first place is for those who use the nickname to indicate status[1] (nick-away, nick|lunch etc)[1]. Changing the full nickname temporarily doesn't have much use beyond fraud, so I'm attaching a proposal to make the nickPopover treat status-indication as first-class use case. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=709952#c1
Not sure about this - traditionally, changing nicks temporarily is also used for jokes. For example, this is from last weeks #gtk+ logs: Company: yay, my xchat doesn't render underscores anymore since I updated it *Company goes blaming TingPing [halfline is now known as underline] underline: am i invisible now ? [underline is now known as halfline]
Created attachment 330814 [details] clarification of nick popover which promotes status indication (rev5b) (In reply to Florian Müllner from comment #1) > Not sure about this - traditionally, changing nicks temporarily is also used > for jokes. For example, this is from last weeks #gtk+ logs: > > Company: yay, my xchat doesn't render underscores anymore since I updated it > *Company goes blaming TingPing > [halfline is now known as underline] > underline: am i invisible now ? > [underline is now known as halfline] Mmm, we do still support '/nick foo' to facilitate stuff like that. :) if you're still unsure about it though, what about this attachment then? let me know which you prefer.
Frankly I find the distinction of channel-specific (I didn't even know that was possible) and network-global nicknames unhelpful. For example just now I started polari on a fresh computer and asked to connect to Freenode without connecting to a room, and it silently (and counterproductively) picked my system's username as my nickname, which is problematic for a bunch of reasons. But then when I went to change the IRC network's properties to set my nick to something better (like "demo-unit-L15"), when I asked to join my first room afterwards it *still* picked my system username instead of the one I had set in the IRC network properties. I would vote for the "just give me *one* global nick per network at most" approach. Or if you really want to keep the flexibility, then add a checkbox "[x] Apply nick change to all channels on [network_name]" in the nick changes dialogs.
(In reply to Jean-François Fortin Tam from comment #3) > Frankly I find the distinction of channel-specific (I didn't even know that > was possible) and network-global nicknames unhelpful. There's no such thing as channel-specific nicks, nicks are always global to the network. However with telepathy, it turns out we have three of them (in contrast to the two in the IRC spec): 1. the 'account' property (passed to the NICK command at connection time) 2. the 'username' property (passed to the USER command at connection time) 3. the 'nickname' property (used for changing the nick at runtime, again via the NICK command) The spec doesn't have the difference between 1. and 3., while we tie 1. and 2. together. I think it makes sense to always reset 3. to the username on startup, so that we always start with everything consistent, then allow users to change 3. temporarily to nick-afk etc (via the popover, not the properties dialog)
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of Polari, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/polari/-/issues/ Thank you for your understanding and your help.