|
|
| Author |
Message |
| 25 new of 73 responses total. |
jep
|
|
response 37 of 73:
| 
Jan 9 05:18 UTC 2004 |
I believe my suggestion of making a separate filesystem for the blog
conferences, and having separate conferences for each blog, is
workable on Grex using Picospan. There are no obvious technical
obstacles to it.
A conference on Grex is a subdirectory of /bbs, and also a line
in /bbs/conflist. For example:
ag_ora:%agora48
The line in /bbs/conflist can point to directories which are not
subdirectories of /bbs. I don't recall the exact syntax, but I
imagine it would look like this:
jep:/blog/jep
The biggest obstacles are not the space or separate directory required
for the conference itself, it would be the participation files. A
different participation file is needed for each conference you read.
If blogs, using my proposed format, become common, then some users
might have thousands of participation files for them, with each
consuming 1 block of disk space and 1 inode. I speculate a block on
the home filesystem for NextGrex will be 1K, so 1000 participation
files would occupy 1 MB.
There's nothing preposterous so far. Disk space is really, really
cheap these days.
If blogs using this system become really popular, it might be well to
automate the creation of the blog conference directory and entry
in /bbs/conflist.
Now for the advantages. The powers suggested for the blog conference
are the same powers a fw already has. A fw of his own blog conference
can make use of the rc, login, logout, index and bulletin files to
customize his conference. He can remove -- but not edit -- responses
or items. It would be possible, if the cfadm set it up that way, to
have lists to permit or restrict individual loginids access, or write
access, to the conference.
As I said previously, I am not familiar with blogs, but it seems to me
this ought to add up to a pretty reasonable capability for producing a
blog.
|
davel
|
|
response 38 of 73:
|
Jan 9 13:33 UTC 2004 |
Just as a technical matter, for that to work you'd need a separate FS for each
blog conference. Otherwise, anyone could link someone else's blog into his
conference & refuse to delete it. I don't think it'll work, John.
|
jep
|
|
response 39 of 73:
|
Jan 9 15:10 UTC 2004 |
Is there no way to disable the link capability for the fairwitness of a
conference?
|
other
|
|
response 40 of 73:
|
Jan 9 16:25 UTC 2004 |
If I were to guess, I'd say that linking is just another way of
saying "creating a symlink" and as far as I know, there is no way to
prevent anyone with write access to a directory from creating a
symlink to any other file on the filesystem to which that user has
read access.
Am I wrong on this?
|
jp2
|
|
response 41 of 73:
|
Jan 9 16:28 UTC 2004 |
This response has been erased.
|
other
|
|
response 42 of 73:
|
Jan 9 16:33 UTC 2004 |
Ok, correction noted, but in what way does that alter my conclusion
(that there's really no way to prevent item linking by anyone with
fw access to the conference directory without significantly
rewriting picospan to redefine the functions of or create a whole
new class of fw)?
|
jp2
|
|
response 43 of 73:
|
Jan 9 17:05 UTC 2004 |
This response has been erased.
|
other
|
|
response 44 of 73:
|
Jan 9 17:15 UTC 2004 |
or #0, since #1 is rather short on verbage of any useful sort.
|
jp2
|
|
response 45 of 73:
|
Jan 9 17:43 UTC 2004 |
This response has been erased.
|
bhelliom
|
|
response 46 of 73:
|
Jan 9 17:58 UTC 2004 |
Yeah but what's that in binary, huh? :p
|
jp2
|
|
response 47 of 73:
|
Jan 9 18:01 UTC 2004 |
This response has been erased.
|
mynxcat
|
|
response 48 of 73:
|
Jan 9 19:49 UTC 2004 |
You've been reading too much Doug Adams.
|
mary
|
|
response 49 of 73:
|
Jan 9 21:29 UTC 2004 |
You folks are setting yourself up for disappointment
here. If you enter text in a blog conference, with all
kinds of special rules about how you'll be in control
of your own text, etc., etc., you be begging folks to
save copies of your items just because they can.
Doubt it? Check out M-net about a day after you
start feeling comfortable with your new control.
Grex is public. You shouldn't enter anything here
you don't want public. If you do, the system is
gracious enough to allow you to remove your words.
But we can't go any further and it's unrealistic to
expect we can make your mistakes go away.
|
willcome
|
|
response 50 of 73:
|
Jan 9 21:32 UTC 2004 |
doesn't mean Grex shouldn't try. As a nurse who has performed thousands of
abortions, you should know pretty well the reasons why it's heartless to not
help people clean up their mistakes.
|
jp2
|
|
response 51 of 73:
|
Jan 9 21:34 UTC 2004 |
This response has been erased.
|
other
|
|
response 52 of 73:
|
Jan 9 21:37 UTC 2004 |
51: <chuckle> Yup. Sure did.
|
jep
|
|
response 53 of 73:
|
Jan 9 21:44 UTC 2004 |
Mary's got a good point about control of text. On Grex or on any other
system, there is no way for information to be both public and
controlled.
I don't think that means a blog conference or system can't be part of
Grex. I think people just need to be aware that that's the way it is.
|
naftee
|
|
response 54 of 73:
|
Jan 9 23:48 UTC 2004 |
re 48 He makes for good reads.
re 50 YEAH< BEING MARY< SHE SHOULD"VE MARRIED THE PEOPLE < RATHER THAN
ABORT THEM< AGHAHAHA
|
happyboy
|
|
response 55 of 73:
|
Jan 10 01:07 UTC 2004 |
re50:
/shoots fresca out of nose!
|
scott
|
|
response 56 of 73:
|
Jan 10 02:16 UTC 2004 |
Ya know, this is a golden opportunity for us Grexers to FORCE righteous
M-Netters to archive ludicrous amounts of essentially useless text.
|
cmcgee
|
|
response 57 of 73:
|
Jan 10 02:25 UTC 2004 |
OOOh, what a Great Idea!
|
jmsaul
|
|
response 58 of 73:
|
Jan 10 04:50 UTC 2004 |
M-Net's got plenty of disk space.
|
happyboy
|
|
response 59 of 73:
|
Jan 10 11:39 UTC 2004 |
and it is FASTER.
|
jaklumen
|
|
response 60 of 73:
|
Jan 10 12:22 UTC 2004 |
ya know ya make me hot when ya talk dirty like that.
|
jmsaul
|
|
response 61 of 73:
|
Jan 10 14:09 UTC 2004 |
I don't want to make you hot. I've seen what you post about in the sex.cf.
|