Hello all,
I just found this page,
http://oid.jabber.org/?oid=1102
It talks of a Web Client for Jabber by Jeremie. Looks
like this project has been left at alpha stage only.
Are any updates expected for this. I think a Web client
for Jabber has enormous value and am looking for the same.
Jer
Actually I was just about to ask someone for a JEP on that -- we need a
real solution to the software update problem, not the current hacks.
Peter
--
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.php
On Thu, 3 Oct 2002 [EMAIL PROTECTED] wrote:
> > And no - w
> And no - we have no way to make the fix a mandatory release. Are you
> offering to fix update.yabber.org so that it actually works?
Opps, make that update.jabber.org that is broken...
Michael.
___
jdev mailing list
[EMAIL PROTECTED]
http://mailman
Settle down. It's just a bug (albeit a very very annoying one) with the
Auto-away code. It's only been reported once (by you) and no one has
given us any ideas how to recreate it (it doesn't seem to happen on all
machines)
Unfortunately we were only notified of it shortly after Marc left Brazil
>> My own, I havent released it im letting my friends test it at the
>> moment,
>> yup its a Windows one and the lookups work fine in 98 SE/NT4/2000/XP,
>> but
>> not in 98 or 95 yet since I havent found any way in those operating
>> systems
>> to determine the current DNS server the system is
On Thursday, October 3, 2002, at 08:22 pm, Ben Schumacher wrote:
> Ralph Siemsen wrote:
>>> I just dont see the point, why not just leave that as it is and wait
>>> for the
>>> XMPP workgroup to sort out proper entries, e.g.
>>>
>>> _xmpp-server._tcp
>>> _xmpp-client._tcp
>> Ah, didn't see the
Grettings Jabber Developers,
This morning we announced the availability of a beta version of our .NET Jabber SDK.
Since I hate long emails, I'll just link you over to the site:
http://www.winfessor.com/press.asp. Over the next few months we will be adding many
new and exciting features to th
So sitting behind a NAT box doesn't sound like it should affect
things.
Just to be sure I hadn't done something wrong I extracted to
another directory, rebuilt, and started from the stock
configuration file. All I changed in it were the admin addresses
and the and contents so they matched my F
It has come to my attention that Everybuddy is doing the same thing Yabber
is: sending one presence packet a second if your status is auto-away. So
now Linux users too can flood the Jabber network with redundant
presence packets.
If you are a developer on Everybuddy or Yabber, please fix your cod
Ralph Siemsen wrote:
>> I just dont see the point, why not just leave that as it is and wait
>> for the
>> XMPP workgroup to sort out proper entries, e.g.
>>
>> _xmpp-server._tcp
>> _xmpp-client._tcp
>
> Ah, didn't see these anywhere. Is it in any of the working drafts?
Nope. Keep in mind that
I'm happy to announce the JabberManual project. The intent of this project
is to create a complete set of documentation related to Jabber, including
guides for end users, server admins, and developers as well as complete
protocol documentation. All of the documentation currently hosted on the
new
Quoting "matthew c. mead" <[EMAIL PROTECTED]>:
> Testing that the NAT is working:
> bash-2.05$ telnet goof.com 5269
> bash-2.05$ telnet goof.com 5223
> bash-2.05$ telnet goof.com 5222
> 20021002T22:33:47: [notice] (update.jabber.org): failed to establish
> connection
> 20021002T22:39:22: [notice]
For some reason IE is saving the file with the wrong name. It should be called
xdb_perl.tar.gz.
I forgot to mention in the initial email: to read the docs type "perldoc xdb_perl.pl"
Joe
> -Original Message-
> From: Bruce Heller [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 03,
Richard Dobson wrote:
> I just dont see the point, why not just leave that as it is and wait for the
> XMPP workgroup to sort out proper entries, e.g.
>
> _xmpp-server._tcp
> _xmpp-client._tcp
Ah, didn't see these anywhere. Is it in any of the working drafts?
Well what I really wanted to get
It is gzip'd. Try this commaned to untar:
tar xzvf xdb_perl.tar.gz
That works for me. If it matters, I made it on a RedHat 7 system.
> -Original Message-
> From: Bruce Heller [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 03, 2002 11:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [J
Reply throughout...
On Thu, Oct 03, 2002 at 12:59:17PM -0500, [EMAIL PROTECTED] wrote:
> Sorry to repost this, but now that someone brought up AIM I feel compelled to ask:
>
> 1) Is your AIM transport using OSCAR or TOC?
>
OSCAR, TOC is a sham to me
> 2) have you been limited by AOL as to the
Sorry to repost this, but now that someone brought up AIM I feel compelled to ask:
1) Is your AIM transport using OSCAR or TOC?
2) have you been limited by AOL as to the number of AOL users that can concurrently be
connected to AOL?
3) If (2) is true, how have you avoided it?
4) How many use
This is a public shaming for the Yabber client:
20021003T16:57:54>>> xaI am
available
20021003T16:57:54>>> xaI am
available
20021003T16:57:55>>> xaI am
available
20021003T16:57:56>>> xaI am
available
20021003T16:57:57>>> xaI am
available
20021003T16:57:58>>> xaI am
available
20021003T16:58:02>>>
Hi,
I have registered Yahoo & MSN, running fine.
I have registered with AIM transport through WinJab client.
But on populating
buddy list in Jabber client (WinJab / webclient),
I'm getting following
error in AIM gateway console.
Thu Oct 3 10:34:39 2002 deliver.c:678 delivering to i
Sorry but the tar file seems to be corrupted... :(
Bruce Heller
Ligne Directe: 01.47.66.55.64
Fax: 01.47.66.55.54
Standard: 01.47.66.55.50
TERRA VIRTUAL
73, rue de Saussure
75017 PARIS
---
- Original
> If my understanding is correct, the IEFT or IANA has specified
> _jabber-sever, so I suspect that we'll have to support that sooner or
> later. It adds a bit of complexity, but not too bad:
> 1) try qtype=SRV for _jabber-server._tcp.domain.com
> 2) try qtype=SRV for _jabber._tcp.domain.com
> 3)
I have put the pre-pre-pre-alpha release of what I am calling xdb_perl on my site
http://howtos.eoutfitters.net/xdb_perl until someone at JabberStudio.org creates me a
project. Anyone who wants can download it and give it the once over. It doesn't
support all of the roster stuff, vcard, or filt
matthew c. mead wrote:
> So for my (and hopefully the list's) benefit, can you provide a
> description of all the SRV record data supported by jabber
> servers and clients? I don't quite understand what all the
> numerical data included means.
You mean the numbers that come back in the SRV look
Richard Dobson wrote:
>
> I think its best to leave _jabber._tcp as it is and not add
> _jabber-server._tcp because that unneccessaryly complicates things (you
> shouldnt change what is already the standard because it complicates things
> for all the existing implementations, and all the thousand
On Thu, Oct 03, 2002 at 08:22:39AM -0400, Ralph Siemsen wrote:
> So best idea would be to have _jabber._tcp and _jabber-server._tcp
> records for the server, and _jabber-client._tcp for port 5222. Sound
> reasonable?
So for my (and hopefully the list's) benefit, can you provide a
description
Martin Lesser wrote:
> Why not use multilog from http://cr.yp.to/daemontools.html in
> combination with the other utitlities provided by this great piece of
> software?
Interesting stuff, thanks for pointing it out. Looks useful for taming
ill-behaved daemons, particularly those whose source y
> So best idea would be to have _jabber._tcp and _jabber-server._tcp
> records for the server, and _jabber-client._tcp for port 5222. Sound
> reasonable?
I think its best to leave _jabber._tcp as it is and not add
_jabber-server._tcp because that unneccessaryly complicates things (you
shouldnt
Ben Schumacher wrote:
> Ralph-
>
> That would be the most appropriate way, but currently only S2S
> components use the SRV records, and they are still using _jabber._tcp,
> instead of _jabber-server._tcp.
So best idea would be to have _jabber._tcp and _jabber-server._tcp
records for the serve
28 matches
Mail list logo
