29-Mar-2024 10:17 GMT.
UNDER CONSTRUCTION
Anonymous, there are 16 items in your selection
[Files] Another version of Jabberwocky releasedANN.lu
Posted on 28-Aug-2003 22:17 GMT by Raffaele16 comments
View flat
View list
Released on Jabberwocky site the new version (Jabberwocky030828.lha) of this good program, an Amiga Jabber client (and I wish to remember, for the benefit of you all, that Jabber is an universal messaging system, which supports ICQ, IRC, MSN, AIM, etc.).
Another version of Jabberwocky released : Comment 1 of 16ANN.lu
Posted by Raffaele on 28-Aug-2003 20:23 GMT
Oh, and I forgot to mention that it works fine on '040, '060, PPC and MorphOS based systems...

Enjoy it...

Ciao,

Raffaele
Another version of Jabberwocky released : Comment 2 of 16ANN.lu
Posted by corpse on 29-Aug-2003 04:50 GMT
"MSN, AIM, etc.)."

I wonder if the MSN transports will still work after Microsoft kicks unlicensed clients off of the network.. and if anyone will bother to create a work-around if the transports fail.

The GAIM guys sound ready to just drop MSN support if it becomes a problem :\ which is a bad for those of us with a lot of MSN contacts ;).
Another version of Jabberwocky released : Comment 3 of 16ANN.lu
Posted by Anonymous on 29-Aug-2003 05:56 GMT
Go, Jabberwocky!
Another version of Jabberwocky released : Comment 4 of 16ANN.lu
Posted by Peter Gordon on 29-Aug-2003 06:20 GMT
In reply to Comment 2 (corpse):
Considering the transport is server-side, and there is an active community of open source programmers for Jabber, I would be surprised if they didn't rise to the challenge of fixing any blockout. Time will tell, of course.
Another version of Jabberwocky released : Comment 5 of 16ANN.lu
Posted by corpse on 29-Aug-2003 08:48 GMT
In reply to Comment 4 (Peter Gordon):
"Considering the transport is server-side,"

True. :)

"and there is an active community of open source programmers for Jabber, I would be surprised if they didn't rise to the challenge of fixing any blockout. Time will tell, of course."

I just hope the changes find their way back to libmsn (or whatever it is now) as I prefer local clients :).
Another version of Jabberwocky released : Comment 6 of 16ANN.lu
Posted by Peter Gordon on 29-Aug-2003 09:58 GMT
In reply to Comment 5 (corpse):
"I prefer local clients"

What difference does that make to the end user?

Server side transports, pros:

+ Updates are made on the server, ALL clients benefit
+ Minority platforms don't suffer because there are less people working on the clients; the server gets updated often
+ Clients are simpler to develop, simpler to port, take up less hard disk space

Cons:

- Errr... are there any?
Another version of Jabberwocky released : Comment 7 of 16ANN.lu
Posted by Peter Gordon on 29-Aug-2003 10:01 GMT
In reply to Comment 6 (Peter Gordon):
More pros:

+ Client only has to connect to one server, to talk to many networks
+ NAT users only have to forward the ports for the native protocol
+ You are immune to any exploits of the protocols of other services, since you only use one protocol on your system
Another version of Jabberwocky released : Comment 8 of 16ANN.lu
Posted by StAn on 29-Aug-2003 12:37 GMT
Speaking of NAT, is there a port to be redirected for Jabberwocky ?
It seems to work quite badly here... ICQ users can't msg me or put me in their contact list...
Another version of Jabberwocky released : Comment 9 of 16ANN.lu
Posted by Peter Gordon on 29-Aug-2003 13:35 GMT
In reply to Comment 8 (StAn):
I'm using Jabberwocky with NAT, and i didn't need to forward any ports. You would only need it if you use direct connections for files and stuff, but i don't know if Jabber has that, or even if Jabberwocky supports it.

It just works, here.
Another version of Jabberwocky released : Comment 10 of 16ANN.lu
Posted by corpse on 29-Aug-2003 18:31 GMT
In reply to Comment 6 (Peter Gordon):
" + Updates are made on the server, ALL clients benefit"
And if the transport becomes broken all clients loose out...

"+ Minority platforms don't suffer because there are less people working on the clients; the server gets updated often"

eh, um .. most clients use standard libs to do the grunt work, even jabberwocky. If the client developers post their improvements back I can't see any problem.

LibMSN etc work on amigaOs with a little work ...
Another version of Jabberwocky released : Comment 11 of 16ANN.lu
Posted by corpse on 29-Aug-2003 18:35 GMT
In reply to Comment 7 (Peter Gordon):
"+ NAT users only have to forward the ports for the native protocol'

I'm a NAT user.. Local clients work fine for me ;)

"+ You are immune to any exploits of the protocols of other services, since you only use one protocol on your system"

But if the main server goes down you loose contact to all of the networks you use.

There are advantages either way... Boils down to what you find works for you.
Another version of Jabberwocky released : Comment 12 of 16ANN.lu
Posted by SWAUG info on 30-Aug-2003 06:03 GMT
If you want to learn a bit more about setting up Jabberwocky on the Amiga we have a full tutorial on our website.

http://www.swaug.org.uk/support
Another version of Jabberwocky released : Comment 13 of 16ANN.lu
Posted by Peter Gordon on 30-Aug-2003 17:40 GMT
In reply to Comment 11 (corpse):
" + Updates are made on the server, ALL clients benefit"
"And if the transport becomes broken all clients loose out... "

If the transport becomes broken it is because the network owners have changed the protocol in an update, usually. Then ALL clients lose out, server side transports or no. The difference is, the server guy upgrades the transport, and EVERY client suddenly works again with no user interaction.


"+ Minority platforms don't suffer because there are less people working on the clients; the server gets updated often"
"eh, um .. most clients use standard libs to do the grunt work, even jabberwocky. If the client developers post their improvements back I can't see any problem."

The onus is on the user to update. Also, libraries have to be ported to each platform. ALL clients for ALL platforms INSTANTLY benefit with the server-side transport, without any effort on the part of the user.


"LibMSN etc work on amigaOs with a little work ..."

MSN transport works, and is updated without any work at all on the part of the user.

"+ NAT users only have to forward the ports for the native protocol'
"I'm a NAT user.. Local clients work fine for me ;)"

Yes. As I explained, NAT only needs setting up for direct traffic (file transfers etc.), not the basic IM functionality.

"+ You are immune to any exploits of the protocols of other services, since you only use one protocol on your system"
"But if the main server goes down you loose contact to all of the networks you use."

Pick a stable server, then. There are plenty of stable Jabber servers with proven records.


"There are advantages either way... Boils down to what you find works for you."

If you say so. Personally I just can't see any real significant advantage to the local client methods, but lots of disadvantages.
Another version of Jabberwocky released : Comment 14 of 16ANN.lu
Posted by Kulwant on 31-Aug-2003 18:41 GMT
In reply to Comment 1 (Raffaele):
I recently got Jabberwocky working on my Amiga and am glad to be able to chat to my friends using my Amiga - some are amazed that I can do all this stuff with my Amiga - especially when they have just spent £100's on new PCs. Thank-you for Jabberwocky - it is great. Keep up the excellent work.

Is there any chance of features like seeing when the other person is typing (as in MSN Instant Messenger) and the ability to send and receive files?

And it would be neat to assign a different font and/or colour for outgoing text to make it easier to see what I have written.

Regards,

Kulwant
Another version of Jabberwocky released : Comment 15 of 16ANN.lu
Posted by Raffaele on 01-Sep-2003 06:24 GMT
In reply to Comment 14 (Kulwant):
Mr. Kulwant wrote:

>Is there any chance of features like seeing
>when the other person is typing (as in MSN Instant Messenger)
>and the ability to send and receive files?

I think you must ask it to the programmers themselves...

...and regarding file transfer, it seems to e that Jabberwocky performs the task...

...but only for Amiga files...

(can someone say more about it?)

>And it would be neat to assign a different font and/or colour
>for outgoing text to make it easier to see what I have written.

Same suggest as above... :-)

Ciao,

Raffaele
Another version of Jabberwocky released : Comment 16 of 16ANN.lu
Posted by Kulwant Bhogal on 01-Sep-2003 19:27 GMT
In reply to Comment 15 (Raffaele):
Sorry, from your style of writing I assumed that you were the programmer....

I will make the suggestions to the programmer(s).

K
Anonymous, there are 16 items in your selection
Back to Top