Shoutbox

quote:

---

Originally posted by MattyRid
Still won't work...because the user ID is YOUR user ID for stuffplug settings. So as I said...not possible from a protocol point of view

---

Which is the property Messenger.MyUserId .  As I said this is perfectly possible for even some semi-good scripter to do (as in they have written a script over 20 lines).

Prove them wrong by making it

quote:

---

Originally posted by markee

quote:

---

Originally posted by MattyRid
Still won't work...because the user ID is YOUR user ID for stuffplug settings. So as I said...not possible from a protocol point of view

---

Which is the property Messenger.MyUserId .  As I said this is perfectly possible for even some semi-good scripter to do (as in they have written a script over 20 lines).

---

Hate to break news to you but...this is from the documentation itself

quote:

---

MyUserId - Messenger User ID of the current user.

and it also says "A string specifying the Messenger User ID of the current user."

---

Now tell me if I understand this wrongly but doesn't that refer to your personal ID, not your contacts ID? so how in the world is that going to work?

Here is the script you were after.  I just wanted to prove that it could be done.  The script doesn't have any interfaces, you jut have to use the /chatonly command when in a chat with that person.  The contact specific Chat-Only name can only be set and used when there is only one other contact in the conversation with you.  I hope you enjoy it and that other people realize it wasn't impossible after all.

quote:

---

Originally posted by MattyRid
Can't be done on a per contact basis as I said on the stuffplug forums....protocol does not allow a per contact setup, just like you can't have a dp for one contact.

---

The existance of the ChatOnly Name feature is exactly because the protocol does allow you to send specific stuff to a specific chat*. Otherwise there wasn't a chatonly nickname feature to begin with.

Aka: when Messenger sends a line to a chat session*, the name of the sender is included. And it is exactly this name which is changed to have the ChatOnly Nickname feature.

quote:

---

Originally posted by MattyRid
Still won't work...because the user ID is YOUR user ID for stuffplug settings. So as I said...not possible from a protocol point of view

---

The ID hasn't got anything todo with the protocol...

PS: Code to calculate the ID of contact emails (or text for that matter) is well known (thanks to wtbw): CookieRevised's reply to MSN ID calculator

--------

The POC (proof of concept) script of markee, shows it is very well possible. But it has also some implications: eg: if you have automated messages reacting on something a contact says, the script does not change the nickname again to the contact specific one.

As such... such a request and addition to this feature is best to be implemented in StuffPlug itself (although it will always be limited to single contact conversations*).


* It will never ever be a contact specific nickname, but a chat specific nickname... Stuff is send to sessions, which can contain several contacts... hence ChatOnly nickname and not ContactOnly nickname.

I tell you what you deserve credit markee...although I will say (and not many know this apart from my closefamily members) when I tried ages ago I kept failing miserably, and just forgot about doing it, hence why I thought it was a protocol thing preventing it.

But you have definately proved otherwise...oh and by the way, just as an idea for the interface, when I was doing my one (and kept failing) I was doing it so it was like a table showing the Nickname of the contact, their email address and the chat-only name that was going to be set. Perhaps an idea to have in your mind maybe?

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by MattyRid
Can't be done on a per contact basis as I said on the stuffplug forums....protocol does not allow a per contact setup, just like you can't have a dp for one contact.

---

The existance of the ChatOnly Name feature is exactly because the protocol does allow you to send specific stuff to a contact. Otherwise there wasn't a chatonly nickname feature to begin with.

Aka: when Messenger sends a line to another contact, the name of the sender is included. And it is exactly this name which is changed to have the ChatOnly Nickname feature.

---

Fair enough, as I said I kept trying and fail each time...if only I kept it and didn't trash it when I formatted...oh well such is life I suppose.

Now to run along and watch Australia win

quote:

---

Originally posted by MattyRid
But you have definately proved otherwise...oh and by the way, just as an idea for the interface, when I was doing my one (and kept failing) I was doing it so it was like a table showing the Nickname of the contact, their email address and the chat-only name that was going to be set. Perhaps an idea to have in your mind maybe?

---

i think i will be doing an interface for it... it will be very simple... a list on the left with emails and default on to then a edit box on the right

Remember that this will NOT be a contact specific nickname! Calling it that will be wrong (just as saying "open window notifiers" to "opened session notifiers").

The ChatOnly nickname is chat specific, not contact specific.

Keep this in mind when making an interface (or whatever else).

In fact it is contact specific...I checked before I posted back...markee has used the registry to store each one

See the attachment

quote:

---

Originally posted by MattyRid
In fact it is contact specific...I checked before I posted back...markee has used the registry to store each one

---

nope it isn't... this reply is exactly why I explicitly repeated again:

quote:

---

Originally posted by CookieRevised
Remember that this will NOT be a contact specific nickname! Calling it that will be wrong (just as saying "open window notifiers" to "opened session notifiers").

The ChatOnly nickname is chat specific, not contact specific.

Keep this in mind when making an interface (or whatever else).

---

Thus it is not because this POC script stores it contact specific that the ChatOnly Nickname feature is contact specific.

The ChatOnly Nickname is chat specific....

--------------

On the matter of how to store its settings: markee, try to use the user ID to store stuff. Putting plain emails in the registry is not recommended...(and take in account yahoo contact emails which have a prefix, in case you use the sEmail parameter of events)

--------------

To others: all this is again to say that markee's script is just a POC (proof of concept) to simply show it is possible and should not be used as a "final" script because as a "final" script it doesn't work without glitches and issues.