|
|
| Author |
Message |
| 22 new of 109 responses total. |
nikm
|
|
response 88 of 109:
|
Sep 16 06:00 UTC 2008 |
Can I read ft code? Where can I find it?
|
cross
|
|
response 89 of 109:
|
Sep 16 14:06 UTC 2008 |
resp:87 Hmm, interesting idea. We've been thinking about "fishbowl"
conferences for some time now; YAPP had the ability to have
finer-grained access controls for conferences which would, I think,
provide a starting point for the sort of things you are talking about
(accessible from the command line, not accessible from the web; up to
the conference's administration to decide which way to go). The
problem with enabling that sort of support in backtalk was, of course,
legacy support for Picospan. Since we're moving away from Picospan,
however, we might be able to rethink these sorts of things (fronttalk,
the "new" terminal-based interface for BBS, is just a frontend to
backtalk). Anyway, the point is that it's technically possible,
provided it's something that the community wants to do.
With respect to the web site, I think the thing to do is keep most of it
static, with some cron scripts and
resp:88 Certainly! Read /usr/local/bin/fronttalk, and the libraries are
in /usr/local/lib/fronttalk-0.9.2. Feel free to read whatever you
like; if you see bugs, or want to make a change, just send email or
post here, or (for changes) copy the files in question to your home
directory, make a change, and email or post a patch (diff -u format
works best). Provided the changes are reasonable, I've got no problems
incorporating them into the running version here on Grex and sending an
email to Jan.
For that matter, there are a number of things that need to be
incorporated into the current code to make it compatible with Picospan.
|
nikm
|
|
response 90 of 109:
|
Sep 18 11:55 UTC 2008 |
|
nikm
|
|
response 91 of 109:
|
Sep 18 12:05 UTC 2008 |
I thought of making some changes to web pages.
1. Creating common header html which can be included in all the html files.
2. Creating common footer
3. Creating common sidebar html file
In order to do this I tried copying all the files from /var/www/htdocs to my
home directory. But it looks like I dont have enough disk quota. Is there any
way I can copy this entire folder to my local machine?
|
keesan
|
|
response 92 of 109:
|
Sep 18 15:09 UTC 2008 |
Do you have wget? Can you work in /tmp at grex?
|
madmike
|
|
response 93 of 109:
|
Sep 18 15:23 UTC 2008 |
To download the htdocs folder is to attempt to get way more files than
you need or would even want. There are subfolders to htdocs that are
actually links to folders elswhere in the system and those probably
contain symbolic links to other folders as well. It is entirely
possible you are meeting yourself coming and going - downloading files
more than once in some cases. Some folders and contents are permission
based and cannot be accessed. Much of what you can download is no-doubt
irrelevent to your project but may shed some light on the structure of
the grex website.
I have downloaded what I could. I have ommitted the GREX minutes
documents but admit they would probably be in interesting (& dry) read.
I've also pruned the stats folder (almost 50MB in itself.) I have made
these files available for downloading in a compressed ZIP file at the
following link.
check here http://www.cyberspace.org/~madmike/GREX/
I was hoping this might ease bandwith demands on grex in case anyone
else was curious as to these files and their contents. I havent yet
checked what all is included but I'm sure you will find what you are
looking for.
When I get the time I'll prune this down to the bare essentials. But
for now I think I'll have a look myself.
STAFF: If you would rather I did not do this let me know.
|
nikm
|
|
response 94 of 109:
|
Sep 18 16:54 UTC 2008 |
resp: 92 Even if I work in /tmp it wont help because I should be able to see
the result in a browser.
resp: 93 I am on a very narrow bandwidth. It looks like the size of the zip
file is 3.2 MB.
|
nikm
|
|
response 95 of 109:
|
Sep 18 16:55 UTC 2008 |
Oops I tried downloading. But I am not able to do the same.
|
madmike
|
|
response 96 of 109:
|
Sep 18 22:05 UTC 2008 |
perhaps this will get it...
http://infinitelyremote.dyndns.org/members/madmike/GREX/htdocs.zip
It is possible that the firewall may be blocking you. I do have several
large IP blocks filtered. sorry, but if you email me your IP address I
will be happy to poke a hole in the wall for ya.
|
cross
|
|
response 97 of 109:
|
Sep 19 01:03 UTC 2008 |
resp:93 I don't have a problem with it; the stuff can be easily retrieved
by a web browser; I'm sure lots of it is already stored in various archives and
caches automatically (like most of the web's content).
The Grex web pages (the ones that we actually edit, anyway; not the meeting
minutes, Apache manual, stats, etc) are now in CVS: /var/ncvs/grex/web is the
location of the repository.
|
hera
|
|
response 98 of 109:
|
Sep 19 05:17 UTC 2008 |
madmike is a madasswipe!!! nyah! nyah! HE can't hear me!!! I'll bet he has
sex with geese and wipes his ass with his finger and then sticks it in
cyklown's mouth.
|
madmike
|
|
response 99 of 109:
|
Sep 19 10:44 UTC 2008 |
Twit Filters are a beautiful thing!
|
mary
|
|
response 100 of 109:
|
Sep 19 11:51 UTC 2008 |
(Mary gives madmike the secret handshake.) ;-)
|
madmike
|
|
response 101 of 109:
|
Sep 19 12:34 UTC 2008 |
Okay then... I have moved the file to a bigtime server for hosting.
Should be World accessable now. See this page for the updated link.
==== http://www.grex.org/~madmike/GREX/ ====
I've included most of the following folder /var/ncvs/grex/web/htdocs in
the htdocsII.zip file
the /var/www/htdocs is still available in the htdocs.zip file
re# 100 ;o)
|
cross
|
|
response 102 of 109:
|
Sep 19 17:45 UTC 2008 |
It stikes me that we do allow people to mirror the Grex CVS repositories using
cvsync; it might be easier to just suck those down than getting the RCS file
from the CVSROOT subtree (those don't give you much, really).
|
madmike
|
|
response 103 of 109:
|
Sep 19 19:50 UTC 2008 |
Sounded like a good idea...
Am I doing something wrong?
=================================
[root@myserver grex]# cvsync cvsync://grex.org:80
Connecting to grex.org port 80
Connected to 216.86.77.194 port 80
Socket Error: recv: 2 residue 2
Recv: protocol version length
=================================
(takes about 5 minutes to do above cycle)
|
madmike
|
|
response 104 of 109:
|
Sep 19 21:05 UTC 2008 |
I know what I'm doing wrong...
Trying to do something I have no idea what I am doing. I'll read the
docs and get edgamacated. (this'll be fun) thanx cross
|
hera
|
|
response 105 of 109:
|
Sep 20 00:36 UTC 2008 |
Idiot. I'm losing nothing by him filtering me. hah!
|
madmike
|
|
response 106 of 109:
|
Sep 22 15:07 UTC 2008 |
cvsync -v cvsync://grex.org/grexcvs/rcs/?prefix=/grex
*******************************
Done (collection grexcvs/rcs)
Finished successfully
Total time: 465.256 sec
now to figure out what to do with these ;)
|
nikm
|
|
response 107 of 109:
|
Sep 28 03:26 UTC 2008 |
I have found two things that is different from picospan.
1) Initially when we get into front-talk it displays help messages which says
that typing "help conf" will display the available conferences. But this
command is not working. I think it should be "help conference".
2) I tried "help conference" and it worked. But there is no pagination for
this command so the list runs out of the screen.
Don't you think changing the initial message and adding pagination will help?
|
cross
|
|
response 108 of 109:
|
Oct 21 02:11 UTC 2008 |
I do; remind me to put it on my list of things to do!
|
politoto
|
|
response 109 of 109:
|
Dec 18 10:26 UTC 2015 |
Today I can see
(type "help conf" for a list of conferences)
above the Ok: prompt. :)
And "help confe" works and "help conf" doesn't. And there is no pagination.
|