-------------what I already sent you-----------

Here are the ideas for the wiki system:

Allow for a diversity of syntax of paging systems (and possibly convert
from one to another ?)
The diversity need not be done to start with (one wiki formatting may be
enough in a first step), but it is at least a goal for further releases.
I mean that there is for example the wikimedia syntax
http://en.wikipedia.org/wiki/Wikipedia:Tutorial_%28Formatting%29
http://en.wikipedia.org/wiki/Wikipedia:Tutorial_%28Wikipedia_links%29
but different wikis may have a different syntax (I don't know precisely)
Also there is the TEX syntax for mathematical texts, that may be processed
by tth or I don't know what. I'm not sure whether tth is the right way to make web pages with
mathematics but it's just to give you a general idea of the goal.

That hyperlinks be GLS+bookmarks active : if you follow a link you go
through a redirection through home host to be identified; probably the
best option is to use a throwable pseudo. A throwable pseudo is a pseudo
that only exists during session, to browse read-only host B, anonymously
except for the data of what is the home host A. This way host B does not know who
is the user but can interact with A who knows who he is. This opens the
possibility of the following functions:
- To add a page or a link to bookmarks (stored in the user's account in A)
- To swich to an authentication under a true pseudo (replacing the
throwable pseudo by a true one) by a pop-up in home host that displays the
pseudos list of the user, for choosing one.

To have a rights system for every wiki page or set of wiki pages, similar
to what is presently implemented in forum:
nothing - read - write - admin
becomes
nothing - see - see history - edit - admin
BUT allows for a diversity of rights systems (just like in forums)
The common point of rights systems is : when a user comes to somewhere
with a rights system, an internal function is called to determine the
user's right there and store it to session variables. From a rights system
to another, the computation may be different. For example, in the future,
some rights will be calculated out of the trust system.

Problem: the same web page may contain different parts with different
rights systems. For example, in a forum, there are different messages with
each different rights below the whole forum's rights.

History : take the same principle as the save-preview-post now implemented
in the forum, that is, valid/invalid status of new entries. A user that
edits a page may store it as a draft that only he can see and edit. So in
history there will be drafts (also called "hidden" or "invalid") that are
only visible by their authors, and can be deleted or modified without
trace (except that the date updates to last modification date). And the
idea that something validated can be invalidated again as long as it was
not seen by anyone else. But will the date of a version be the one of last
editing or last validation ?

A new feature for wikis: a quotations system.

To let a wiki page integrate another wiki page (or an excerpt, but it
would be more difficult to implement).

How it would work:
A user requests a wiki page A. The server, before sending it, observes that 
page A contains a quotation of page B. So it connects to B's host
(if it does not have a recent cache copy) to request B. If B contains a
quote, it will not be operated by B's host but by A. If there is a loophole or if
there are more than 4 levels of quotation (for example), it gives up and
displays a not-operated quotation sign that can be done if user requests
it.

Usefulness:
Different authors can make redundant lists of links to other sites (with
each his appreciation for selection). But if someone referenced at
different places wants to update the title or description, or even the
entry address or host, how can he do without contacting all list authors ?
The solution is that the author of a site offers some shorter or longer
models of links to his site with descriptions. Then a links page will be
made of a list of quotations.

Other usefulness: Instead of being integrated to a wiki page, quotations
could be used by other programs, like user board, news systems, calendar
system...

----------
> About GLS:
> 1. Is it finished? As far as I cansee, in the demo app I only could create
> a
> pseudo, but I couldn't connect to another server using that pseudo.

A version has been done but I don't know how satisfactory it is.
From trust-forum.php.by you cannot connect to any peer site because it is
installed with zero known peer site.
From tforum1.php.by/gls it had been possible to connect to a peer site
(namely tforum2.php.by/gls) but unfortunately as I'm trying again now I
see it does not work anymore.
So I don't know what happened. I'm forwarding this reply to the person who
maintains this: a.yaroshevich@php.by. I hope he will answer.


> 3. About Bookmark concept... is a URL of a server name? please, explain me
> more about this concept

I don't know what you already read about it so I don't know what I should
exactly explain.

Roughly, each user has a fixed home site that is his account containing
his bookmarks list (instead of having them on his browser : this way he
will keep his personal bookmarks when going to an internet cafe).
Bookmarks are GLS active, that is, it is a request to the home site that
redirects to the intended site together with a pseudonymous authentication
of his choice: the peer site will know a pseudo and the home site of the
user. Or instead of a pseudo it maybe a throwable pseudo. This choice is
stored together with bookmark.
When browsing other site with such authentication he can bookmark other
pages as well, that will be added to his bookmarks list.

We can develop new addressing conventions inside the network: give hosts
other names than the domain name...
I'm not sure if it is very useful. So to start with, we can simply keep
the normal URL.

What are your questions ?

> 4. The "throwable pseudo"... you have to configured it in the session? I
> understand that is a pseudo with only read rights in the forum, but, only
> in
> the forum??

Yes in the session variables there must be mention of whether it is a
throwable pseudo or not (the concept of throwable pseudo has not been
implemented yet)
No, it will be a general feature that throwable pseudos can only visit and
never make operations that affect other users.

>
> About Wiki:
> I don't completely understand what you mean when you talk about wiki. Is
> is
> like wikipedia, where you can write you own articles and other member can
> update or modify your article... is it the same idea??

Well it aims to contain the main features of wikis like wikipedia, except
what is specifical for encyclopedia, because it aims to be a totally
generalist system also good to serve for personal web pages; and have some
more features to fit with the rest of the project.
For example with wikipedia each article is given by a name, but since it
is public pages there must be only one page with a given name. On the
contrary, as I want to develop rights system (so, other than "everybody
can edit"), this provides another division of pages. This can be made in
the form of folders, with urls like
http://myserver.com/Peterscommunity/ourconceptionoflife




------------the second part I had not sent you------------


There must be sets of Web pages, where in each set, all pages refer to a common calculation of rights. Either that pages are explicitly affiliated, or whether membership will be implemented through instruction in the procedure for calculating rights on a given page. Or maybe a mix of 2. See what you think is the most relevant.
In any case, the program should let the owner of a set of wiki pages select which one(s) among the 3 following options will be available to the visitors looking for contacts:

- To an address (author)

- A public forum. In wikimedia is a wiki page for discussion.
Why not, a forum for discussion instead of a wiki discussion page? Indeed, a forum associated with a web page is precisely what is happening in blogs! (One detail:  a wiki page will have public discussion forum whose messages are themselves encapsulated wikis, with strictly private rights and personal contact).

- Another idea, that would be complicated but perhaps interesting : a collective (or personal) nickname, that would be (for the purpose of the trust system) internally associated to the owner of this set of wiki pages; on the other hand, would let the visitors of this page create a thread in a private forum in the following way: the visitor creating the thread would have supplementary right of access to this thread only, while a set of registered users in the forum rights table will have access to all threads. It would bring together in one forum, to the team of publishers of the original wiki page, the various private discussions with visitors.

The important thing is obviously integration GLS + bookmark finally giving those functions their fullest use.
(In the very beginning of the discussion with programmers I think I mentioned a few things in relation to it (for the discussion of GLS), well it does not matter): 

In the headers of each page, should be the following (here is a list in disorder, maybe not comprehensive ?): "quit", "home", possibly "discussion" and/or "author", possibly"history"; "bookmarks list" (=pop-up to home site), "add to bookmarks"  (to be replaced by "remove from bookmarks" if the page is one of the bookmarks from the user).

With each link in the page there would be the function to add the link to bookmarks. A pop-up will appear with the title to be edited for display in the list of bookmarks. The question remains as to whether it will be pre-filled and how... by the way we should think of the addressing system of pages: I consider to do in the whole project an internal addressing system built over, which would replace the traditional URLs, especially with the advantage of allowing special characters: spaces and accents...) , we might add the option for hurrying visitors, to switch to a fast method of bookmarking which would accumulate rapidly bookmarks without question.
But the implementation of such an option may not be necessary ...


Re-reading a message of Thursday, January 6, 2005 16:59 to fteam@mail.ru I draw the following idea:
There is a need to find a way to cut and paste links or bookmarks to the content of a wiki page (particularly to a message forum, where they will be rebuilt from the wikis).

-------------
To know the list of all existing wiki systems you can follow these links:

http://usemod.com/cgi-bin/mb.pl
http://c2.com/cgi-bin/wiki
http://c2.com/cgi/wiki?RunningYourOwnWikiFaq
http://dmoz.org/Computers/Software/Groupware/Wiki/Wiki_Engines/
http://ikiwiki.info/
http://www.weblogkitchen.com/

http://en.wikipedia.org/wiki/Wiki
and all connected articles, particularly
http://en.wikipedia.org/wiki/List_of_wiki_software
http://en.wikipedia.org/wiki/Comparison_of_wiki_software
http://en.wikipedia.org/wiki/Wikitext
http://en.wikipedia.org/wiki/Bliki