|
|
| Author |
Message |
| 25 new of 58 responses total. |
jmsaul
|
|
response 10 of 58:
| 
May 11 17:45 UTC 2002 |
WebYAPP is hideous, I agree. If you have a lot of people who use your web
interface, you probably shouldn't switch for that reason alone.
I'm curious, though... can YAPP and Picospan read each other's conference
files transparently? If so, would it be possible to make both available for
telnet users?
|
remmers
|
|
response 11 of 58:
|
May 11 18:05 UTC 2002 |
This response has been erased.
|
remmers
|
|
response 12 of 58:
|
May 11 18:27 UTC 2002 |
No. Some data is kept in different places and in different
formats (e.g. user participation files). There are concurrency
issues as well -- they probably using different file locking
schemes, so that for example in two people are responding to
the same item at the same time, one using Picospan and the
other using Yapp, the responses might get intermingled and
system files might not get updated correctly.
|
jp2
|
|
response 13 of 58:
|
May 11 20:37 UTC 2002 |
This response has been erased.
|
jep
|
|
response 14 of 58:
|
May 11 21:14 UTC 2002 |
Hahaha. Marcus is here, and has the source; if he wants to compile
Picospan for the new system, he can do so.
M-Net switched to YAPP because we were unable to get a copy of Picospan
for our system after the Altos died. Dave Thaler wrote YAPP in
response to our need, and we were very lucky he could do a competent
job at duplicating Picospan. He did more than a competent job, he did
a marvelous job.
WebYAPP, though, has never been ready for prime time. Backtalk is way,
way better. I use both daily. I yearn for the day M-Net gets Backtalk
set up.
|
jp2
|
|
response 15 of 58:
|
May 11 21:58 UTC 2002 |
This response has been erased.
|
jmsaul
|
|
response 16 of 58:
|
May 11 22:42 UTC 2002 |
Re #12: Thanks for clearing that up. I've wondered for years, but hadn't
thought to ask.
Re #13: If that's true, than why the hell are we bothering with WebYAPP
on M-Net?
|
styles
|
|
response 17 of 58:
|
May 12 00:32 UTC 2002 |
picospan chokes on my yapp .cfonce.
big, FAT, core dump.
on the floor.
|
jep
|
|
response 18 of 58:
|
May 12 01:24 UTC 2002 |
I think janc said Backtalk will work with one of the earlier versions
of YAPP. I've been hoping/waiting for years that someone would bring
it to M-Net.
|
cross
|
|
response 19 of 58:
|
May 12 01:37 UTC 2002 |
Isn't YAPP rather expensive if you use it for more than a few months?
|
jmsaul
|
|
response 20 of 58:
|
May 12 04:16 UTC 2002 |
They've been known to donate it to non-profits.
|
jp2
|
|
response 21 of 58:
|
May 12 04:20 UTC 2002 |
This response has been erased.
|
jp2
|
|
response 22 of 58:
|
May 12 04:41 UTC 2002 |
This response has been erased.
|
cross
|
|
response 23 of 58:
|
May 12 20:47 UTC 2002 |
I compiled YAPP under Solaris last night, and wasn't too impressed
with the number of errors that came up. At one point, the compile
stopped due to something not being properly defined in the Makefile
(well, that's slightly unfair; there was no Makefile support for
Solaris).
|
jp2
|
|
response 24 of 58:
|
May 12 21:11 UTC 2002 |
This response has been erased.
|
cross
|
|
response 25 of 58:
|
May 12 21:49 UTC 2002 |
Err, didn't you just say it failed to compile under FreeBSD?
Remeber: Solaris != SunOS.
|
jp2
|
|
response 26 of 58:
|
May 12 22:32 UTC 2002 |
This response has been erased.
|
cross
|
|
response 27 of 58:
|
May 12 22:49 UTC 2002 |
Oh. My bad.
|
janc
|
|
response 28 of 58:
|
May 19 15:57 UTC 2002 |
Backtalk has been tested against Yapp 2.3, but not, so far as I know in
a production system. I don't think M-Net runs Yapp 2.3, but some later
version that moves a lot of files around to different places. Probably
it isn't too hard to fix whatever problems still exist.
The backtalk bug in #22 is probably easy to fix. The showopt.c module
is just code to what options backtalk was built with. It's a new hunk
of code and I've hit a couple minor configuration dependant bugs
before, and it looks like this is another. Knowing the options you
used to build Backtalk would help.
It looks like you've defined Yapp compatibility, but not --auth=shadow.
Yapp compatibility isn't really going to work if you are authenticating
out of anything other than the shadow password database. Or something
even stranger is wrong. I'd really need your configuration options to
debug this.
|
janc
|
|
response 29 of 58:
|
May 19 16:01 UTC 2002 |
I don't see any reason to switch between Picospan and Yapp. I'm
actually more interested in something like Fronttalk that would move us
more toward a distributed architecture. Though Fronttalk would need
quite a bit of work before it was ready for production use.
|
jmsaul
|
|
response 30 of 58:
|
May 19 16:05 UTC 2002 |
What is Fronttalk?
|
remmers
|
|
response 31 of 58:
|
May 19 19:07 UTC 2002 |
It's a Backtalk client with a Picospan-like text interface.
Very cool, but still in the experimental stage. You can
run it on Grex via the "ft" command. (Warning: It's slow.)
Or, if you have Perl on your local machine, you can probably
download it and access Grex conferences by running your local
copy, which will probably be much faster than running it on
Grex. It takes some configuration to get that to work, but
I succeeded in doing it once.
There's a fronttalk item in the Garage conferece; see that
for more details.
I share Jan's lack of enthusiasm for switching from Picospan
to Yapp. Or, from the M-Net perspective, switching from Yapp
to Picospan. They're so alike, and architecturally they're
both dinosaurs. Useful dinosaurs, and one can still learn
from them, but dinosaurs.
|
jmsaul
|
|
response 32 of 58:
|
May 21 05:04 UTC 2002 |
Interesting:
FrontTalk 0.2.4
Copyright 2001, Jan Wolter
Connected to server
(null): Permission denied, bozo
;-)
I agree about there being no real reason to switch between Picospan and YAPP.
I'm not sure what the purpose of FrontTalk is, though.
|
jp2
|
|
response 33 of 58:
|
May 21 05:20 UTC 2002 |
This response has been erased.
|
remmers
|
|
response 34 of 58:
|
May 21 11:00 UTC 2002 |
Re #32: Hm. I don't know why you would get that error.
The nifty thing about FrontTalk is that it supports distributed
conferencing. When you're running FrontTalk -- on Grex, on your
home machine, whatever -- you can in principle access any
conference on any machine running BackTalk.
|