[JDEV] My evil plans for a client. (please stop the madness)
patrick at kia.net
Fri Aug 6 17:07:04 CDT 1999
Maybe I'm just a little sensitive to this, because I try to follow a lot of
mailing lists, but Jabber is important to me, and I want to read every JDEV
message. Honestly, it is getting difficult.
Could we make some concessions to topic to keep the volume down? Because if
we're going to haggle the features or non-features or configurability or
automatic-recompiling of every Jabber client in the world, we're all going
to get 50000 messages a day and subsequently the list will be worthless.
I strongly suggest that those interested in discussing TCharon's or anyone
else's Win32 client or the meta-features of meta-clients form a list and go
there. Granted, messages from those threads occassionally cross back into
JDEV server, protocol, and transport topics, such as capping packet size, or
MIME. But these messages can always be sent to the appropriate list. It
seems to me that there's enough traffic to warrant two lists. Discussions of
client [GUI] features seem high volume and easily seperable.
I'm not saying I dislike the chitchat. But the list is getting big and the
volume is going through the roof.
To help this along I created a JabberBeans group on egroups. You can get
there at http://www.egroups.com/list/jabberbeans-dev/. Honestly, there has
been very little interest expressed to me about JabberBeans, and it isn't
exactly all over the JDEV list, so I don't think it will help the traffic
here, but it might, who knows.
BTW, if you feel the need to flame me about this, please consider doing so
in private at patrick at kia.net.
> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> Vivre Draco
> Sent: Friday, August 06, 1999 5:01 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] My evil plans for a client.
> On 6 Aug 99,, Scott Robinson sounded off on [JDEV] My evil plans
> for a client.:
> > But back into reality, I'd love to make another suggestion for
> > client fun. MIME support! Messages encoded in MIME (and the clients
> > have a rudimentery (sp?) mailcap) could allow for a whole new world
> > of kick-ass messenging. Why send text when I can send an encoded
> > mp3? (ed. Let's hope we're all on cable modems or better.) I want
> > to send my breakup message with a little "I will survive" MIDI
> > attached. You can see where I'm going with this...
> Oh... Gods... No.
> If you do this, their damned better be an option so not only do I
> not have to listen to all the shit ppl attach, I don't even have to
> waste time downloading it.
> Ugh... If Jabber messages get turned into webpages, with all the
> crap lamers put on their pages -- useless midis, animated gifs, etc --
> I'll stick with ICQ.
> "I am not an idealist, nor a cynic,
> but merely unafraid of contradictions."
> --Donald Hogan
> Copyright 1999 Vivre Draco (cfc at paganpaths.org)
> excelsior ad infinitum -- http://www.paganpaths.org/~cfc/
> jdev mailing list
> jdev at jabber.org
More information about the JDev