Recently the feature "Personal Message" was added to MSN, which meant
they finally supported status messages.

The problem was, were to put the nickname then?

Currently the nickname is put in vCard-temp, an unofficial JEP, not part
of XMPP. But the bigger problem is, most clients ignore the nickname
part of vCard-temp completely (and I agree with them).

So my proposal:

hack the msn status message to have both nickname and personal messages:

"Foo
 Personal Message: Bar"

So first the nickname, cause that one is most widely used and could be
displayed on one line, then on the second line the much less used
personal message.

I could implement this easily, I suppose, since I know some python. But
I can implement 301 features and have them on unstable.nl, I'd like some
feedback and assurance that such a feature would get universal
acceptance.

Background:
The original Jabber philosophy was to make clients as simple as
possibel, and put complexity in servers. Our current situation is that
we have many many Jabber clients, that by now in 2005 all support Status
Messages. BUT I can't think of 1 that will automatically display
nickname... So PyMSNt can find it handy to put it in the nickname field,
but let's design PyMSNt to work with the maximum amount of clients in
mind ;)

-- 
        Andreas        [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
                       [  callto:ils.seconix.com/[EMAIL PROTECTED]   ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 
http://modevia.com/pipermail/py-transports/attachments/20051008/616ca1a6/attachment.pgp
From [EMAIL PROTECTED]  Sat Oct  8 07:47:02 2005
From: [EMAIL PROTECTED] (Trejkaz)
Date: Sat Oct  8 07:47:11 2005
Subject: [py-transports] about MSN nicknames
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Sat, 8 Oct 2005 12:31, Andreas van Cranenburgh wrote:
> So my proposal:
>
> hack the msn status message to have both nickname and personal messages:
>
> "Foo
>  Personal Message: Bar"
>
> So first the nickname, cause that one is most widely used and could be
> displayed on one line, then on the second line the much less used
> personal message.

I'm not completely adverse to putting the nickname in a status message, but 
IMO it would work better like this:

    Does the user have a personal message?
      If so, set the personal message into the status.
      If not, set the nickname into the status.

This way is slightly better because people who have the newer client and thus 
set the status message, don't have their nickname showing up as a status 
message in various places.

TX

-- 
             Email: Trejkaz Xaoza <[EMAIL PROTECTED]>
          Web site: http://trypticon.org/
         Jabber ID: [EMAIL PROTECTED]
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://modevia.com/pipermail/py-transports/attachments/20051008/e871ff59/attachment-0001.pgp
From [EMAIL PROTECTED]  Sat Oct  8 10:15:28 2005
From: [EMAIL PROTECTED] (Nikos Kouremenos)
Date: Sat Oct  8 10:15:30 2005
Subject: [py-transports] about MSN nicknames
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On 10/8/05, Trejkaz <[EMAIL PROTECTED]> wrote:
>
> On Sat, 8 Oct 2005 12:31, Andreas van Cranenburgh wrote:
> > So my proposal:
> >
> > hack the msn status message to have both nickname and personal messages:
> >
> > "Foo
> > Personal Message: Bar"
> >
> > So first the nickname, cause that one is most widely used and could be
> > displayed on one line, then on the second line the much less used
> > personal message.
>
> I'm not completely adverse to putting the nickname in a status message,
> but
> IMO it would work better like this:
>
> Does the user have a personal message?
> If so, set the personal message into the status.
> If not, set the nickname into the status.
>

first of all the problme is not only with MSN. but generally. second of all
I like how it's done now, than have such babel as client dev. I'ts not good
to put the nickname to status, leave out the fact that since recently you
were the only transport to do that so babel :)

the desired nickname atm is put only in vcard-temp (which is OFFICIAL jep
but it's everyday said that it should be replaced.. :P) I think the right
place to discuss that is JIGs-list (as the problem is more general) and
there discuss alternatives for when vcard-temp is rm'ed

--
Nikos Kouremenos | Jabber ID: [EMAIL PROTECTED] |
http://members.hellug.gr/nkour
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://modevia.com/pipermail/py-transports/attachments/20051008/0c4f9f73/attachment.html
From [EMAIL PROTECTED]  Sat Oct  8 11:13:01 2005
From: [EMAIL PROTECTED] (Lars T. Mikkelsen)
Date: Sat Oct  8 11:13:04 2005
Subject: [py-transports] PyMSNt Questions
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On Fri, Oct 07, 2005 at 03:43:40PM -0700, Steve Ramage wrote:
> 2) I had a problem with an 'older' version of .10-cvs, where all of a
> sudden it would go ape and start signing in again and again and again
> and again (once a minute). I have the log, and I'm wondering if anyone
> else has expeiranced this problem (James I'll send you the log directly).

This could be the PingService that is unable to ping the main Jabber
server and thus reconnects. Please check that mainServerJID in
config.xml is correct and reachable for PyMSNt. You could also try to
comment out mainServerJID - this will disable the PingService.

> 3) The latest version of cvs (I assume I can grab it with cvs update
> from the directory) pukes when I try and run it with:
> 
> [15:34:51] [EMAIL PROTECTED]:/usr/local/bin/jabberd2/PyMSNt-0.10-cvs$./PyMSNt
[snip]
>   File "/usr/local/bin/jabberd2/PyMSNt-0.10-cvs/src/legacy/glue.py", line 25
>     <<<<<<< glue.py
>      ^
> SyntaxError: invalid syntax

This looks like a CVS conflict. If you haven't made any important
changes to src/legacy/glue.py, simply remove the file and run cvs up to
restore it. If you have made important changes, you need to manually
merge those.

Best regards,
Lars
From [EMAIL PROTECTED]  Sat Oct  8 13:08:01 2005
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Sat Oct  8 13:08:03 2005
Subject: [py-transports] directed presence
Message-ID: <[EMAIL PROTECTED]>

Hey there,

Is there any chance that when a second (or third, etc) resource log
into PyMSNt that the existing resources don't get the presence
messages.  (I believe this is directed presence).

At the moment when I login with an extra resource, all of my exisiting
resources get the 'presence storm', it would be much better if only
the connecting client got the storm.

Cheers

Norman

--
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Sat Oct  8 14:27:15 2005
From: [EMAIL PROTECTED] (Andreas van Cranenburgh)
Date: Sat Oct  8 14:27:18 2005
Subject: [py-transports] about MSN nicknames
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Ok whatever. Everyone disagrees. Let's simply make everything
configurable down to the bone. Then I'll have my nicknames in status
message on my server, and everyone else can do whatever they want.

-- 
        Andreas        [ http://unstable.nl | xmpp:[EMAIL PROTECTED] ]
                       [  callto:ils.seconix.com/[EMAIL PROTECTED]   ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 
http://modevia.com/pipermail/py-transports/attachments/20051008/12c9f357/attachment.pgp
From [EMAIL PROTECTED]  Sat Oct  8 15:11:03 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Sat Oct  8 15:17:32 2005
Subject: [py-transports] Psi nickname patch
Message-ID: <[EMAIL PROTECTED]>

I've made a few patches that make Psi broadcast understand nicknames in 
the presence packet, alongside the photo hash.

These patches apply to Remko's psi-avatar branch.

You will now see nicknames of PyMSNt users in the status tooltip.

Have a look at http://delx.cjb.net/psi

There's an OSX build there you can try out.

Any chance of this getting into Psi mainline for 0.10 or 0.11?

---

James

Reply via email to