Apologies to those that mailed me – I logged off the remote server and it seemed to close down the service. Ok now.
Thinking about it, I like the idea of an xrds giving you a pointer to the “IM” user service, just not convinced (in simpler cases such as openmicroblogging) it should always be a jabber id. steven http://livz.org From: Steven Livingstone-Perez [mailto:[EMAIL PROTECTED] Sent: 19 June 2008 17:25 To: '[EMAIL PROTECTED]'; 'XMPP and Social Networking, Two Great Tastes That Taste Great Together!' Subject: RE: [diso-project] Re: [Social] [diso-project] Re: OpenMicroBlogging For what it’s worth – if you wish to hack a demo I have set up an XMPP Openfire server. It was really to investigate where things are since my last look. To develop a server – or even a client - there is still a lot of work in XMPP (open source *servers other than Openfire were hard to find) which is my only worry. However, as a packaged solution it was pretty easy. My ISP doesn’t support the default port so I had to use an alternative but managed to connect via Exodus ok and send some messages. I found you can create a new user directly through most clients which is neat. 1. Just enter your desired jabber id in the format [EMAIL PROTECTED] … I am [EMAIL PROTECTED] 2. Choose a password 3. In the connection, enter the host as “openid.org” 4. Change the default port to 5901 5. That’s it. In view of how easy this was and the number of open source clients available, I can only imagine that this kinds of infrastructure to be a great building block. My *only* concern is that if you want to run your own server there are a lot of commercial clauses I saw and writing your own is certainly not trivial (unlike writing some simple sender/listener as defined in the openmicroblogging.org contract). If someone wishes to use this to hack some xrds and do some testing I’d be glad to help out (other than tomorrow morn when I am at a funeral). Regards, Steven http://livz.org From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Messina Sent: 19 June 2008 14:21 To: XMPP and Social Networking, Two Great Tastes That Taste Great Together!; [EMAIL PROTECTED] Subject: [diso-project] Re: [Social] [diso-project] Re: OpenMicroBlogging Perhaps we just need to code up a demo using this approach and probe the challenge moot: I'd be thrilled if the building blocks we already have solve this problem and be put in place immediately! Chris Sent by 1G iPhone. On Jun 18, 2008, at 15:29, "Bob Wyman" <[EMAIL PROTECTED]> wrote: Chris, I can't see any reason why an XRDS file with a link to the appropriate JID would NOT be the correct way to implement this. Is there something I'm missing? bob wyman On Wed, Jun 18, 2008 at 2:58 PM, Chris Messina <[EMAIL PROTECTED]> wrote: Let me frame the challenge/opportunity this way: Presume that I have a URL of my own, given a recipient URL, I want to be able to send a message "at it" and have it be received on the other end, and be routed properly, based on the recipient's rules. As the sender, I just want to be able to send a message and know that the recipient should receive it. This parallels having a "from" email address and sending it "to" a recipient email address. But in this case we're replacing email as the identifier with a URL. So if I self-identify as http://twitter.com/factoryjoe and I want to send a message to http://twitter.com/redmonk, if on that endpoint is a discovery document that suggests where to send messages and how to sign them so that the messages will be received and not rejected outright, I think we're getting somewhere. I see no reason not to use ATOM or XMPP for this, except that XMPP doesn't work well with today's shared hosting environments. Perhaps we use XRDS discovery to point to an XMPP endpoint and then offer a fallback ATOM endpoint in the case that XMPP would fail? You know that I'm against inventing unnecessarily -- which is why I pointed out this microblogging effort. It might not be the way to do it, but it gives us an example of someone's thinking that's actually been implemented and gives us something to build against. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DiSo Project" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/diso-project?hl=en -~----------~----~----~----~------~----~------~--~---
