Hi,
Making it use Nicknames instead of usernames is trivial but usernames were selected because of their uniqueness. Nicknames aren’t unique so it might happen that two users share same chat name and Quick Chat would treat them the same. We should think of some clever way to give initial chat names without doing any extra checks for uniqueness because that would make impact on performance. If you have any ideas feel free to say 🙂
Thanks for the nice words about my work I appreciate it 😉
I see, it’s just I’ve always used those kind of shoutboxes for registered members only with Avatar and Nicknames, but none existent for WordPress today pleases me, except for yours. :]
Couldn’t you hook by the username but only display the Nickname? At least you have the avatar to help identify each user if by any chance two or more people have the same nick.
Since I can only speak for myself, let me explain how I would use the plugin and why I prefer nicknames, maybe that will help you. I have a shoutbox on a gaming community, with people having different characters that most of the time doesn’t reflect their account names, so the nicks help us identify each other.
And since we are not a huge community, I’m sure we won’t have people sharing nicknames, neither people trying to impersonate others, as we would shortly caught and ban them.
Thanks for the time. ^^
It’s just a line or two change so here you go my friend, nickname version of Quick Chat 2.33:
Quick Chat 2.33 nickname
Just make sure people have unique nicknames. Enjoy!
Wow, thanks a lot! *-*
I will start using it right away.
And I just noticed how you posted this 8 minutes ago. I swear I didn’t check this page once since my last post. xD
Cya! o/
Edit: Just tested and it still shows usernames. Also the smilies are not working, when I click any of them, it just writes “undefined” non-stop into the text area.
But thanks for the effort! ^^
The thing I forgot to write is that you need to clear your browser history to flush old history/cookies and reload page a few times. The undefined problem might be this but if normal Quick Chat v2.33 worked with smilies then I believe it’s all about history/cookies and it’ll work with this “nickname” v2.33version. The smilies part of code is is identical to the “regular” v2.33, I haven’t touched that. Good luck!
Everything worked like a charm after clearing the cache and doing those modifications. ^^
Thanks a lot!
And just to be sure so I don’t do anything stupid, I won’t be able to update the plugin if you release new versions, is that right?
No worries your mod is trivial. You just need to open quick-chat.php from any future QC version and replace all instances of $current_user->user_login with $current_user->nickname. And clear your browser cache of course 🙂
I don´t wanna be that annoying guy, but could I ask you a for few features? If you like them and have the time to implement, would be great.
– Option to enable/disable the date & time output. So if disabled, posts won´t have the time shown and it will one less line to make the chat more compact.
– If option to choose your own nickname is disabled, remove the “Nickname” textfield from the chat, again to make it compact.
– Option to use avatars from WordPress profile too, instead of just Gravatars. Although I use Gravatars and like it, I hate making people have to edit the WordPress profile AND the Gravatars too. Many people just don´t use it.
Would be great to see those changes in the future, but if not, that’s Ok anyway.
Thanks a lot for the quick replies, support and everything.
All this can be hidden with few lines of code using CSS, but I guess not everyone is comfortable with editing plugin files so I might put some checkboxes when I find time. Thanks for your ideas 😉
No problem at all. ^^
Also, one more thing you could take a look at:
Last wednesday afternoon my website went extreme slow, with each page taking 20~40 seconds to respond, then my host took my website and said something was slowing the whole server, probably some ajax script.
Only a few hours ago my website was put back online, and after a lot of search I realized the only major change I did on the blog was installing your plugin and then I saw the “Refresh every 1 second”, so I changed to 60 seconds (although it would be awesome to have something faster as I´ve had with other plugins) and I´m now waiting for my host to respond if that resolved the problem.
I´ve never had any problem with other ajax plugins, even with shoutboxes that refreshed via ajax. Don´t know if other people have had that same problem or its just me, but maybe its something worth checking.
Thanks for your patience and care to respond all my messages.
Cya o/
Thanks for the report, no it isn’t just your host. If you have a lot of visitors, shared hosting and keep QC inside sidebar your server might get into problems. The problem is that chat applications are very resource intensive because of their real time nature and because of that it isn’t easy to make one using only Ajax and PHP/html.
In the next version I will double the default user and message refresh times and I’m working on compatibility with WordPress caching plugins. That should make Quick Chat much lighter on the server. Unfortunately even then server demand would keep increasing with the number of concurrent users, that can’t be avoided.
It is a securiy issue that the admin username is shown when admin chats. It would hav been better to use the public name that is used as author in posts.
True, there are some security implications but that was the only way to ensure uniqueness of chat user names when users first come to the chat page. Any other means like checking is there any user with that user name while page is loading would have significant performance implications and chat applications are already very resource intensive. This way I’m giving login names (unique by definition) to subscribers and don’t need to worry about uniqueness. One way to triage this problem is to use public names only for admin users and let them ensure their public name is unique?
Do the chat user names need to be unique? Not registered users can choose any name anyway. If they need to be unique, your propsal to use public names for admins only is OK.
Yes the whole system assumes that chat user names are unique and when you change your username ajax request goes back to server to check is it unique (already taken or reserved for any of the registered users). The idea is that when you see user Marko on my site you know you are talking to me because no one else can take this name no mater am I currently on the chat or not. This is ensured in a way that registered users login names are reserved so when someone registers to your site automatically he gets unique chat identity trough login name. This way allowing admins to use their nicknames makes sense cause system can assume that admins won’t do funny things with chat user names.
