From: Jan T. <jan...@gm...> - 2007-11-18 22:37:16
|
Hello. Im hungry about making ADC good chatting proto, because LAN users wont install jabber or IRC server just for conversations, but will install DC Hub because of sharing capabilities. So what about adding "typeing notification"? Like Jabber/ICQ/etc. "Typeing" and "Stoped typeing" are rather userful in day to day conversations. And userfull (for example) for special nicklist sorting when you see who is alive right now. Now about implementation. I thought about the way how to send it... and my idea is: 1. adding new type of message, for example "TPN" (like an extention, or in BASE...) for sending this notifications. All of them should pass through the hub, because of DDOS capability. INF messages are not very good because of their context, and MSG will make parceing more complicated, when typeing notification are banned, so new type imho is better. 2. adding a switcher into cleint. (OFF/ON) so. i see it like this: 4.3.16. TPN TPN code Contexts: F, T Typeing notification. Codes: 00 - Stoped typeing 01 - Typeing... 10 - Closed tab, minimised window, etc... 11 - Now in this tab, reading message 12 - Changed tab or window bacame unfocused, but not closed/minimised all codes are sent when event occurs. if user sends TPN to hub there it is not allowed - it got STA 25 Now some notes. TPN should be send to Reply-To user (for chatroom orgainzation and etc) (PM flag in MSG if any). In that case chatrooms bot can normally broadcast this messages to "joined" users. Thats all. I suppose. B R, Jan |
From: Fredrik U. <ul...@gm...> - 2007-11-19 14:12:04
|
For one, I'm not sure that such capability would even be appreciated by users. I mean, do anyone really care if I have minimized the window, and should they *really* need that information? Why can't you just send messages via the ME capability in MSG ("* user is writing")? I mean, you still need to modify the client to listen for input/window manipulation. If you want to display the text in a particular way, why not just add a parameter to MSG and use that in combination? -- Fredrik Ullner |
From: Jan T. <jan...@gm...> - 2007-11-19 16:24:40
|
> For one, I'm not sure that such capability would even be appreciated > by users. I mean, do anyone really care if I have minimized the > window, and should they *really* need that information? If you use jabber/gtalk/gizmo (if not - install psi or gajim or gtalk and add my google-email to the roster) than you can see that this information really userful. For example you wrote something, if user in this tab - he/she thinking about answering. Typeing - he/she typeing. Closed tab/window or moved to the other stuff - you can not wait for the answer. This notifications really save time whan your every day chattings are rather active. > Why can't you just send messages via the ME capability in MSG ("* user > is writing")? I mean, you still need to modify the client to listen > for input/window manipulation. If you want to display the text in a > particular way, why not just add a parameter to MSG and use that in > combination? I thougth about it. IMHO its a little stupid. First or all you need to add special parser into the server for the case whan this message types are restricted. In "TPN" case you can just drop it after reading the header. Also if client-side dosent support this type of messages (MSG with ME flag and special text) - all the window/console (for console clients like microdc) will be filled with spam messages, but in TPN case this messages are just ignored. B R, Jan |
From: Jacek S. <arn...@gm...> - 2007-11-22 21:45:11
|
> I thougth about it. IMHO its a little stupid. First or all you need to add special parser into the server for the case > whan this message types are restricted. In "TPN" case you can just drop it after reading the header. > > Also if client-side dosent support this type of messages (MSG with ME flag and special text) - all the window/console > (for console clients like microdc) will be filled with spam messages, but in TPN case this messages are just ignored. I generally agree that this should go as a separate message - MSG is for sending text to the user, no use sending this kind of stuff as text (it would get logged, it couldn't be detected automagically etc etc)... Intuitively I'm not convinced about the code set of what the user is doing - I'd say that would need some review and maybe a reference implementation to see it in action... Also, this should clearly go as an extension, not part of BASE. It wouldn't even have to be present in the SUP since it doesn't require anything as far as hub-client comms go... /J |
From: Jan T. <jan...@gm...> - 2007-11-24 14:00:09
|
> I generally agree that this should go as a separate message - MSG is for sending text to the user, > no use sending this kind of stuff as text (it would get logged, it couldn't be detected > automagically etc etc)... > > Intuitively I'm not convinced about the code set of what the user is doing - I'd say that would need > some review and maybe a reference implementation to see it in action... Well i got this types not from the ceiling. http://www.xmpp.org/extensions/xep-0085.html#bizrules This works in jabber for years and IMHO it's nice as it already is. Maybe code shouldnt be a number, maybe it should be a string like "gone". > Also, this should clearly go as an extension, not part of BASE. It wouldn't even have to be present > in the SUP since it doesn't require anything as far as hub-client comms go... Well... may be if it (well be) put in SUP than client may make feature broadcast. This will generate less traffic. |
From: Jacek S. <arn...@gm...> - 2008-01-01 15:58:33
|
I've added the extension to the adc wiki (http://adc.sourceforge.net/wiki/index.php/Extensions#TYPE_-_Typing_notification) - I'll have a few more comments to add there... /J Jan Trofimov wrote: >> I generally agree that this should go as a separate message - MSG is for sending text to the user, >> no use sending this kind of stuff as text (it would get logged, it couldn't be detected >> automagically etc etc)... >> >> Intuitively I'm not convinced about the code set of what the user is doing - I'd say that would need >> some review and maybe a reference implementation to see it in action... > Well i got this types not from the ceiling. > http://www.xmpp.org/extensions/xep-0085.html#bizrules > > This works in jabber for years and IMHO it's nice as it already is. > > Maybe code shouldnt be a number, maybe it should be a string like "gone". > >> Also, this should clearly go as an extension, not part of BASE. It wouldn't even have to be present >> in the SUP since it doesn't require anything as far as hub-client comms go... > Well... may be if it (well be) put in SUP than client may make feature broadcast. This will generate less traffic. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > dcplusplus-devel mailing list > dcp...@li... > https://lists.sourceforge.net/lists/listinfo/dcplusplus-devel > |