Re: [Standards] XEP-0816 (Invisible Command) mandates ridiculous UI
Only my two cents... You should not forget the other side and for e.g. the popular protocols ICQ and MSN. In a nutshell both protocols support the Invisible mode (in MSN it's named "appear off-line") and this is only annoying in both protocols. Take a look at the other side, you have a list full of off-line contacts, but many contacts write you messages. What's the sense of it? It's annoying! "... that's my choice", sorry, but I am not agree, stay off-line if you don't want to chat or keep the possibility that the user from the other side can see you and make sure "Invisible" is not a "normal" mode. Therefore, in my opinion, 3.1.2. makes sense. Peter -- Lastwebpage Lastwebpage's Profile: http://www.jabberforum.org/member.php?userid=41 View this thread: http://www.jabberforum.org/showthread.php?t=1903
Re: [Standards] Call for Experience: XEP-0085 (Chat StateNotifications)
one more... (I see the "Call for experience" today, but it's for developers, not for "foolish end user" like myself, therefore I post it here... ) some comments: 1) Time Values in the XEP I see, "e.g. 5sec, e.g. 30sec, e.g. 2 minutes." What means this *e.g.*? A client side adjustable setting? Imagine I am an slow typer and setup 20sec, 30sec,... in this case the other side would see many changes between paused an inactive. And the other side don't know if the state is really X or Y, why this phrase is not "Should be 5 sec","Should be 30 sec", or however ? sorry, this e.g. confuse me a little bit. 2)2 min and gone I really don't know if it is a good idea to put both condition in one state. 2 min=> The other side search in wikipedia, translate a text, user ask back to another user, or whatever, but it's possible that this 2 minutes elapse in a "normal" chat. closing the chat window=> The other side have better things to do than chat with me any longer sorry, but this is not the same, in my opinion. Peter -- Lastwebpage Lastwebpage's Profile: http://www.jabberforum.org/member.php?userid=41 View this thread: http://www.jabberforum.org/showthread.php?t=925
Re: [Standards] Call for Experience: XEP-0085 (Chat StateNotifications)
"Idle has nothing to do with XEP-0085 " yes , I found it in XEP-12 (Last Activity) in the meantime. "it should just change its status then, it can leave as your tab might still be open and the active tab." I am a little bit more confused now... For me it should works like: User type something in the chat window =>active and composing User wait for an answer or look in a dictionary =>active and paused If the user not write something within the next 30 seconds, it make no difference if the chat window is active or not. =>inactive When nothing happens within the next 2 minutes OR the user close the chat window =>Gone AND the client CAN support: -a)If someone ask for it the user can send back the info about time difference between now and the last action in the client (type something, click around somewhere, whatever), it's also possible that the user send back the time difference between now and any action on the PC. (XEP-12) -b)If the user do nothing (System or client) for a user defined time period, the client can change the status to something. E.G. Away or "Not Available" (NA). And a) and b) works completely different from XEP-85? Is this correct? Peter -- Lastwebpage Lastwebpage's Profile: http://www.jabberforum.org/member.php?userid=41 View this thread: http://www.jabberforum.org/showthread.php?t=925
Re: [Standards] Call for Experience: XEP-0085 (Chat StateNotifications)
Hello, I fear something is not really clear enough in the XEP-85: "User has effectively ended their participation in the chat session. User has not interacted with the chat interface, system, or device for a relatively long period of time (e.g., 2 minutes), or has terminated the chat interface (e.g., by closing the chat window)." But I have the following setting dialogs in miranda ([.]=check box): (It's designed for other protocols like ICQ too) === options page A: (in the general option page) Become idle if the following is left unattended: [.]Windows [.]Miranda for [...] minute(s) [.] Do not let protocols report any idle information -- options page B: (in the jabber options) in the jabber option page: [.] Send chatstate changes if chat window closed === Option page 2 is clear, user close the chat window, jabber plugin send But the orange part? What should miranda send when I setup in this dialog for e.g. 30 minutes? (And if the chat window is still open!) If miranda should send not the orange part should removed from the XEP, this 2 minutes example AND "if the windows closed" is a little bit confusing. Peter (Today was a feature request in the miranda bugtracker, and I became confused about it, therefore this posting. ;) ) -- Lastwebpage Lastwebpage's Profile: http://www.jabberforum.org/member.php?userid=41 View this thread: http://www.jabberforum.org/showthread.php?t=925
