{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Brad Watson <[EMAIL PROTECTED]>
If anyone is looking for more info on jabber's ins & outs from a
programming perspective, I happened upon this
( http://www.amazon.com/exec/obidos/ASIN/0596002025/qid=1014878530/sr=8-1/
ref=sr_8_129_1/002-9614268-6496820 ) O'reilly book while shopping over
the holidays. Slashdot & many others seem to favor this series highly &,
from what I could tell, seems very extensive. I love the idea of
jabber & what it could potentially mean for the future of text
messaging, however there is currently, as Derek pointed out, no good
client for OSX. JabberFOX ("Jabber-For-OSX", clever name & icon) seems
to be making some headway, but leaves a lot to be desired in the
features/user interface department, which as we all know are among
Fire's strongest areas.
Brad
"Wont that be grand? The computers & the programs will start thinking &
the people will stop."
On Wednesday, February 27, 2002, at 01:04 PM, Derek J. Balling wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to "Derek J. Balling"
> <[EMAIL PROTECTED]>
>
>>> a.) Is there any way to set the Resource for the Jabber signon (e.g.
>>> "Work", "Home", "Laptop")?
>> Nope.
>
> Interestingly, from looking at the code, I thought I could set my
> server name to "jabberserver/resource", and from what I saw in
> libEBjabber.c, it would "figure out" that it didn't need to set the
> "/everybuddy" bit.
>
> Except that it made me sign in as "users@server/Work/everybuddy"
> instead of just "user@server/Work".
>
>>> b.) If I get a message from "user@jabberserver/Home", I'm being told
>>> that I'm replying to simply "user@jabberserver", which may (or may
>>> not) get to the user (depending on their client-resource/priority
>>> settings). Is this a known bug? Basically every time my boss sends me
>>> a message I end up replying to his home machine, because it has the
>>> higher priority value[1].
>>> Any thoughts on this?
>> The jabber client I did was pretty bare bones. I am still not sold on
>> the whole jabber scheme (especially their "resources") and as such
>> never even thought about tackling it a year or more ago when I did it.
>> Jabber is by far the least used Fire service (with IRC bringing up a
>> close 2nd) and as such it gets almost no attention.
>
> Any chance of you (or someone) taking a better look at the Jabber
> stuff? I've got zero C-programming skill, but I can certainly provide
> an ample test environment, and there's really no GOOD jabber client for
> OSX, so Fire is the best thing Jabber users have going for them. (and
> since my company is about to lock down AOL/Yahoo out of the office, and
> settle on an internal Jabber server, I'm motivated to "make my Mac work
> like the rest of them" because I don't want to get saddled with a
> windows machine).
>
> D
>
>
> -- +---------------------+-----------------------------------------+
> | [EMAIL PROTECTED] | "Thou art the ruins of the noblest man |
> | Derek J. Balling | That ever lived in the tide of times. |
> | | Woe to the hand that shed this costly |
> | | blood" - Julius Caesar Act 3, Scene 1 |
> +---------------------+-----------------------------------------+
>
> {#} ----------------------------------------------------+[ fire ]+---
>
>
{#} ----------------------------------------------------+[ fire ]+---
