On Thu, Apr 10, 2008 at 12:54 AM, Sander Devrieze [EMAIL PROTECTED]
wrote:
This is not bad. For the Aunt Tilly user using the XMPP client it
should just work.
Agreed, this is better for the Aunt Tilly scenario, but far worse for the
early XMPP adopter that can't receive files from his MSN
2008/4/10, Richard Dobson [EMAIL PROTECTED]:
Norman Rasmussen wrote:
On Thu, Apr 10, 2008 at 12:54 AM, Sander Devrieze [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
This is not bad. For the Aunt Tilly user using the XMPP client it
should just work.
Agreed, this is better
2008/4/10, Richard Dobson [EMAIL PROTECTED]:
Who said targeting tech people is a good idea? Did tech people were
the ones that choose which closed IM system they use? Compare
targeting tech people with Mozilla or Linux distributions before
Ubuntu appeared and targeting Aunt Tillies with
Norman Rasmussen wrote:
On Thu, Apr 10, 2008 at 12:54 AM, Sander Devrieze
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
This is not bad. For the Aunt Tilly user using the XMPP client it
should just work.
Agreed, this is better for the Aunt Tilly scenario, but far worse for
the
I was talking about webdav file transfers which will not need reverse
engineering of the closed network file transfer protocol as the
transport can simply send the webdav uri as a plain text message to
the contact on the closed IM system. This file transfer method will be
safe for protocol
It was an *example*...
2008/4/10, Richard Dobson [EMAIL PROTECTED]:
I was talking about webdav file transfers which will not need reverse
engineering of the closed network file transfer protocol as the
transport can simply send the webdav uri as a plain text message to
the contact on
2008/4/9, Peter Saint-Andre [EMAIL PROTECTED]:
Daniel Henninger wrote:
I don't disagree from the client perspective. But my philosophy has
always been to make XMPP as great as it can be, then everyone else will
eventually decide that they need to use XMPP and not some proprietary
software development list
Subject: Re: [jdev] My GSoC project : to continue the PyMSNt development.
2008/4/9, Peter Saint-Andre [EMAIL PROTECTED]:
Daniel Henninger wrote:
I don't disagree from the client perspective. But my philosophy has
always been to make XMPP as great as it can
Jonathan Dickinson wrote:
One of the things that makes my life easier /is/ the gateways. I work
at a pro M$ company so they are Live Messenger through and through:
despite my VERY BEST efforts to convert the entire company. Being
able to use MSN via Jabber has been a huge help for me, but
TANSTAAFL = Taking Another Step Toward An Awesome Full Life?
On Wed, Apr 9, 2008 at 10:25 AM, Peter Saint-Andre [EMAIL PROTECTED] wrote:
Jonathan Dickinson wrote:
One of the things that makes my life easier /is/ the gateways. I work
at a pro M$ company so they are Live Messenger through
On Wed, Apr 9, 2008 at 4:25 PM, Peter Saint-Andre [EMAIL PROTECTED]
wrote:
Understood. But what features do most people really use? Is it just
presence and IM (and possibly groupchat), or do most people also require
the ability for file transfers, voice calls, emoticons (etc.) to go
across
On Wed, Apr 9, 2008 at 7:10 PM, Sander Devrieze [EMAIL PROTECTED]
wrote:
4) When closed network contacts try to send you a file they can get an
unfriendly technical error message like Your client does not support
webdav file transfers. Contact owner of the network for more
information.
This
2008/4/9, Norman Rasmussen [EMAIL PROTECTED]:
On Wed, Apr 9, 2008 at 7:10 PM, Sander Devrieze [EMAIL PROTECTED]
wrote:
4) When closed network contacts try to send you a file they can get an
unfriendly technical error message like Your client does not support
webdav file transfers. Contact
Florent wrote:
Hi all,
I have seen this week only that James Bunton no longer wanted to continue
developing the MSN transport, since all his friends are now using Jabber.
Perhaps that's a sign of the times. :)
I'm also applying for two other GSoC projects, but this one is the most
2008/4/8, Peter Saint-Andre [EMAIL PROTECTED]:
I am not convinced that working on transports is an
appropriate topic for the Google Summer of Code. I plan to give my votes
to projects that improve or extend XMPP itself, not provide bridges to
closed technologies.
I do not agree on this.
Sander Devrieze wrote:
2008/4/8, Peter Saint-Andre [EMAIL PROTECTED]:
I am not convinced that working on transports is an
appropriate topic for the Google Summer of Code. I plan to give my votes
to projects that improve or extend XMPP itself, not provide bridges to
closed technologies.
I don't disagree from the client perspective. But my philosophy has
always been to make XMPP as great as it can be, then everyone else will
eventually decide that they need to use XMPP and not some proprietary
garbage.
I won't get into my diatribe about why I think that will never happen.
Dnia 2008-04-08, wto o godzinie 18:08 +, Daniel Henninger pisze:
I won't get into my diatribe about why I think that will never happen.
People were saying the same about SMTP.
You know - this marginal protocol used to bridge proprietary Electronic
Mail systems...
--
/\_./o__ Tomasz
Ok, I’ll believe it when I see it.
Daniel
On 4/8/08 5:48 PM, Tomasz Sterna [EMAIL PROTECTED] wrote:
Dnia 2008-04-08, wto o godzinie 18:08 +, Daniel Henninger pisze:
I won't get into my diatribe about why I think that will never happen.
People were saying the same about SMTP.
You know -
Daniel Henninger wrote:
I don't disagree from the client perspective. But my philosophy has
always been to make XMPP as great as it can be, then everyone else will
eventually decide that they need to use XMPP and not some proprietary
garbage.
I won't get into my diatribe about why I think
Hi Florent,
After a discussion, James told me : Your primary goal should be to update
PyMSNt to support the latest Jabber standards. This means XEP-0144 for
exchanging contacts, 172 for nicknames and
85 for chat state notification.
Well, xep-85 has been done for ages
2008/4/6, Remko Tronçon [EMAIL PROTECTED]:
As far as I know, all the functionality that maps onto
jabber (avatars, chat, groupchat, chat states) is already present in
pymsn-t.
Missing features:
* VoIP/video: for this it is probably the best to forward to another
service similar to TokBox
I just sent my application, I can edit it until tomorrow, and after with
mentors' authorizations.
I think the real remaining work would be to move PyMSN-t to use PEP
for its extended presence (avatars etc.), but I'm not sure how
interesting that is as a project.
It is interesting for me :-),
Hi all,
I have seen this week only that James Bunton no longer wanted to continue
developing the MSN transport, since all his friends are now using Jabber.
I'm also applying for two other GSoC projects, but this one is the most
motivating for me.
I have not his chance : I still have a lot of
On Sat, Apr 5, 2008 at 4:28 PM, Florent [EMAIL PROTECTED] wrote:
I know I come a bit late to propose this Summer of Code subject, but trust
me I dream to do it, I have a real interest in it other than earning money
from Google.
Applications close this Monday (7th) so you've still got plenty of
2008/4/5, Norman Rasmussen [EMAIL PROTECTED]:
Applications close this Monday (7th) so you've still got plenty of time
:-P
Yes, I'm doing it ;-)
you're more than welcome to post on the py-transports list for help, and
I'll try and answer as best I can. I'd also like to see the MSN transport
26 matches
Mail list logo
