-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Will Kamishlian wrote:
My inability to document the Jabberd 2 code base has been an continual
frustration for me. When I started jabberdoc, I intended for it to be
half admin guide and half developer guide. Thus, after the work I've put
in, I
On Thu, Sep 02, 2004 at 12:48:39AM -0500, Nolan Eakins [EMAIL PROTECTED] wrote:
Lucas Nussbaum wrote:
1) Jabber is a difficult technology. It is very difficult for end users
to understand what it's all about. I think we lack a good documentation
for end users, covering stuff like what is a
On Thu, Sep 02, 2004 at 01:03:27AM -0500, Nolan Eakins [EMAIL PROTECTED] wrote:
Will Kamishlian wrote:
My inability to document the Jabberd 2 code base has been an continual
frustration for me. When I started jabberdoc, I intended for it to be
half admin guide and half developer guide.
Here is a proposal for some of the problems that were discussed here.
*** Create a community site ***
Create a website targeted at end users with :
- Client reviews :
Review the 2 or 3 major clients on each platform, compare them, etc.
- Documentations :
- Introduction
On Thu, Sep 02, 2004 at 12:48:39AM -0500, Nolan Eakins wrote:
So why aren't ISPs giving out Jabber accounts yet? That's gotta do with the
state of our code-bases. An ISP isn't going to setup a buggy, incomplete,
and hard to manage server. They need the equivalent of an Apache, something
they
Lucas Nussbaum wrote:
I know some people already did parts of this. It would be great if all
their work could be put together on the same website.
I've been planning this for, eehm, ages now :) The main problem has been
time and having too many other fun projects. That has improved a
(little)
Great idea!
Maybe we can call it JabberCentral or something like that? ;)
Not to be a cynic, but did anyone notice this whole discussion about
community sites and jabber complexity takes place every year? And every
year the outcome is the same, everyone agrees we need to make something
to aid
I gmane.network.jabber.devel, skrev Bart van Bragt:
Lucas Nussbaum wrote:
I know some people already did parts of this. It would be great if all
their work could be put together on the same website.
I've been planning this for, eehm, ages now :) The main problem has been
time and
Hello,
Am Do, den 02.09.2004 schrieb Lucas Nussbaum um 9:22:
Here is a proposal for some of the problems that were discussed here.
*** Create a community site ***
Create a website targeted at end users with :
[ ... ]
I did think about such a community site a lot these
Jesper Krogh wrote:
Could it be possible to localize it? Something like the
Debian.org-pages. If you're building it from ground, is it probably
easier to do now that as an addon later.
We could but I don't know if we want to. It's hard enough to find people
that want to help with creating the
Stefan Strigler wrote:
* a personal account of course (which is a jabber account
simultaneously)
* a searchable profile (which merges with the user's vcard of course)
* a blog which can be edited from within jabber (just like the one at
amessage.info). the blog also offers an rss-feed for each
On Thu, 2 Sep 2004 15:48, Nolan Eakins wrote:
Does email have good documentation? If you're online, you know what email
is. Why? Because any ISP will give you at least one email address to use,
and then name off a couple of email programs to use and how to set them up.
If an ISP gave you a
On Thu, 2 Sep 2004 17:03, Lucas Nussbaum wrote:
For a 10 lines advanced hello world, maybe. For a 5 lines project,
good code is often more difficult to understand than bad code, because
it is much more structured.
But wait. What if you were the sort of person who wrote good, structured
Jacek Konieczny wrote:
On Thu, Sep 02, 2004 at 12:48:39AM -0500, Nolan Eakins wrote:
So why aren't ISPs giving out Jabber accounts yet? That's gotta do with the
state of our code-bases. An ISP isn't going to setup a buggy, incomplete,
and hard to manage server. They need the equivalent of an
In Sendmail's defence, I suppose there are tons and tons of books on
the
subject, which simply isn't the case for Jabberd. However, how much
longer
has Sendmail had to accumulate these books? Did it have this many
books in
its opening years?
Likely not, but one could also make the argument
On Thu, Sep 02, 2004 at 07:51:48PM +1000, Trejkaz Xaoza [EMAIL PROTECTED] wrote:
On Thu, 2 Sep 2004 17:03, Lucas Nussbaum wrote:
For a 10 lines advanced hello world, maybe. For a 5 lines project,
good code is often more difficult to understand than bad code, because
it is much more
Hello!
What's about Odigo transport for jabber ?
--
Regards, Oleg
xmpp: [EMAIL PROTECTED]
___
jdev mailing list
[EMAIL PROTECTED]
https://jabberstudio.org/mailman/listinfo/jdev
On Thu, 2 Sep 2004 20:12, you wrote:
By contrast, Jabber is not 'the only game in town' when it comes to
instant messaging. In fact, if it's trying to become a popular
end-user IM solution, instead of just a corporate solution (where, yes,
it is in a much smaller playing field), then it is
Trejkaz Xaoza [EMAIL PROTECTED] writes:
So why don't we direct the attention _there_? If all Jabber
packages on all distros worked out of the box, would there still be
a good excuse not to run it?
Which leads to the question: is anyone at all building RPMs for
jabberd2? If so, I haven't
A second ago we were talking about one implementation of a protocol,
but now
we're talking about a protocol in a sea of closed protocols. I'm sure
there
were plenty of closed electronic mail implementations when Sendmail
reared
its head too, and their existence is largely irrelevant here.
I
Congrats for the release :)
I am on the process to install pymsnt on a jabberd2 server and it seems
the transport uses legacy xdb/.xml files to register itself.
Is there some obscure config option I missed or should I develop a patch
for this ;)
--cedricv
On 2 Sep 2004 at 21:35, Trejkaz Xaoza wrote:
That there is still so much criticism directed at Jabberd for its
difficulty to get working, reflects not only on Jabberd itself, but on the
people who created packages for their distros, which were supposed to work
out of the box.
So why don't
On Thu, Sep 02, 2004 at 01:37:04PM +0200, Cedric Vivier [EMAIL PROTECTED] wrote:
Congrats for the release :)
I am on the process to install pymsnt on a jabberd2 server and it seems
the transport uses legacy xdb/.xml files to register itself.
Is there some obscure config option I missed or
A quote from Rachel which nicely sums up most of it:
Rachel Blackman wrote:
In order to overtake the existing networks in terms of end-user usage,
Jabber needs something to 'win out' over them which the target audience
-- IM end-users -- will understand. Pubsub, for instance, is a really
cool
Chalk this up to old fashioned email usage, but why do people keep
forking threads? First it was the XHTML-IM thread, now it's the State
of our Code-bases -- can't we all just talk on one topic under the
same name?
D.
On Thu, 02 Sep 2004 17:41:36 +0200, Bart van Bragt [EMAIL PROTECTED] wrote:
On Thu, 2 Sep 2004, Jacek Konieczny wrote:
So why aren't ISPs giving out Jabber accounts yet? That's gotta do with the
state of our code-bases. An ISP isn't going to setup a buggy, incomplete,
and hard to manage server. They need the equivalent of an Apache, something
they do setup and use.
And preferably Python (C is ok to)...
A while back I was looking at XMPP for use in a custom non-IM
application - well, computer agents talking to each other instead of
people. Using an existing server (jabberd, etc) was not really an
option as we didn't really need a lot of what was in there,
I would suggest to build a community site whereas community means for me
that it offers users a wide range of services (certainly all built upon
jabber if possible) additionally to those end-user informations. Users
would a have:
SNIP
Nearly every point you listed has, at one point or
On Thu, 2 Sep 2004 [EMAIL PROTECTED] wrote:
What about setting up a Server FAQ or adding info to the jadmin FAQ?
I added some info on server software to
http://www.jabber.org/wiki/index.php/FAQ-JADMIN
- just go ahead and add content.
Regards
___
jdev
On Thu, Sep 02, 2004 at 09:35:32PM +1000, Trejkaz Xaoza wrote:
Jabberd is less than ideal, but only because whatever distributions
are shipping it, must be shipping it with a configuration which simply
doesn't work. If it worked, there wouldn't be so much criticism
around here.
I'm the
On Thu, Sep 02, 2004 at 02:42:06PM +0200, Magnus Henoch wrote:
Trejkaz Xaoza [EMAIL PROTECTED] writes:
So why don't we direct the attention _there_? If all Jabber
packages on all distros worked out of the box, would there still be
a good excuse not to run it?
Which leads to the
I gmane.network.jabber.devel, skrev Jamin W. Collins:
On Thu, Sep 02, 2004 at 09:35:32PM +1000, Trejkaz Xaoza wrote:
Jabberd is less than ideal, but only because whatever distributions
are shipping it, must be shipping it with a configuration which simply
doesn't work. If it worked, there
On Thu, 2 Sep 2004 12:59:10 -0500 (CDT)
Thomas Charron [EMAIL PROTECTED] wrote:
I would suggest to build a community site whereas community means for
me that it offers users a wide range of services (certainly all built
upon jabber if possible) additionally to those end-user informations.
There is a fair amount of functionality in the last stable release of
Twisted that should help you with the socket management, XML parsing
and xpathish sort of operations.
It's not a full server, but it may be a useful start.
D.
On Thu, 2 Sep 2004 11:49:20 -0600, Jason Ish [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
One of the few things that I can think of (and that I have been
evangelising (sp?) quite a few times now :D) is web/email-integration.
IMO it would be great if I could see if someone that just sent me a
mail is still online so I can quickly ask a question related to
On Thu, 2 Sep 2004, Will Kamishlian wrote:
- Build internationalization support in
- Do not use a wiki
- Make it look as professional as possible
- Include discussion forums
- Use a well-known application server
Internationalization support needs to be built in because it will be much
too
On Thu, 2 Sep 2004 21:59:22 +0200 (CEST)
[EMAIL PROTECTED] wrote:
On Thu, 2 Sep 2004, Will Kamishlian wrote:
- Build internationalization support in
- Do not use a wiki
- Make it look as professional as possible
- Include discussion forums
- Use a well-known application server
On Thu, 2 Sep 2004 07:49:22 +1000, James Bunton [EMAIL PROTECTED] wrote:
* If a contact changes their nick you'll see it
This COULD be the cause of the serious performance problems we're
seeing on jabber.org. I'm wondering what the motivation is behind this
change was? Jabber has ALWAYS valued
On Thu, Sep 02, 2004 at 09:35:32PM +1000, Trejkaz Xaoza wrote:
The competitors in the space I was really talking about are Ejabberd and
Jabberd. Ejabberd is probably far better on the usability side... I wouldn't
know, as it still can't do virtual hosting, which would be the top priority
Will Kamishlian wrote:
Maybe it's a question of the intended goal? My goal would be to create a
community of Jabber end-users. That's a different goal from providing
quick start information for end-users. If my goal were the latter, I
would *recommend* a wiki. On the other hand, I'll admit
On Thu, 2 Sep 2004, Will Kamishlian wrote:
however, making a wiki look professional does require a lot of work out
of the box, and then maintaining/changing that presentation requires
contributors who are familiar with the wiki application base.
Typically, changing some CSS file or template
On Fri, 3 Sep 2004 07:04, you wrote:
I guess it is possible to start multiple ejabberd instances on one
machine. Different ports, of course, but this is not problem as SRV
record should be used to find the right port. So the
virtual-hosts-problem is solveable.
True. I just have to wait until
[EMAIL PROTECTED] wrote:
A nice thing would
certainly be something like a Jabber-powered forum which integrates
chatrooms and a WWW-based forum, also emphasizing Jabber's strengths and
flexibility this way. Unfortunately there doesn't seem to be any software
around that implements this.
Can't
Bart van Bragt wrote:
So what do we need to win 'Joe Average' over (if we want to do this)?
Joe Average definitely doesn't want to run and manage his own server. That's
why I talked about ISPs running Jabber servers.
It would be great if I could send a message to someone that just posted
on
44 matches
Mail list logo
