9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] AIM software
Date: Wed, 13 Nov 2002 17:06:55 -0500	[thread overview]
Message-ID: <Pine.LNX.4.30.0211131650160.7785-100000@athena> (raw)
In-Reply-To: <de55ba61fbbca2bdd706f83312449d11@plan9.bell-labs.com>

> especially if you use toc, an aim file server should be trivial.

Last I checked the protocol hadn't been *officially* released
by anyone under AOL-TW's umbrella and had been pieced together
by (perhaps) clever hackers.  That being said, what I saw of the protocol
looked messy enough to inhibit me from writing a client.  AIM
also uses minimal html syntax to mark up the text (fonts, backgrounds,
and the like), which I feel should be parsed out and trashed.

>
> i'd like to see an aim client.
>

Me too, if it's minimalistic.  Something running in an acme win would
be schweet.  I don't want to discourage your genuine interest in the
project, but it's quite likely you won't be a total 9 shop in the
near future; the lack of a decent web browser is enough to necessitate
a linux box to vnc opera from.  You could similarly use gaim at the
same time and let *those* fools chase down the protocol problems every
time AOL-TW decides to break TOC/OSCAR.

Cheers,

Sam



  reply	other threads:[~2002-11-13 22:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 21:42 Russ Cox
2002-11-13 22:06 ` Sam [this message]
2002-11-13 22:39 ` Dan Cross
2002-11-13 22:55   ` matt
  -- strict thread matches above, loose matches on Subject: below --
2002-11-14  6:49 Russ Cox
2002-11-13 22:42 Russ Cox
2002-11-13 23:37 ` Dan Cross
2002-11-13 22:17 rog
2002-11-13 22:09 Russ Cox
2002-11-13 16:46 Null
2002-11-13 17:22 ` matt
2002-11-13 14:26 Skip Tavakkolian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.30.0211131650160.7785-100000@athena \
    --to=sah@softcardsystems.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).