| Dates white ==> Nov2005 Pink ==> discussion1 Blue ==> discussion3 purple ==> discussion4 green ==> versions purpledar1==> mail1 yellow ==> downloaded files brown1=>mail3 |
Discussions
==> Specifications |
Was
this implemented? Yes or NO Date of Implementation |
What
was implemented : exactly same or different from specifications |
What
do the testing show? |
| 2004 |
Electrified Forum |
|||
| PB: page d'envoi d'un message a
un email ==> list des contacts ---> envoi |
marche |
|||
| webmail a integrer |
Marche pas car ne peut lier a
l'imap |
|||
| 12
july 2004 |
* forums software:start from the present code or from other existing ones ? ------------ * user choose his own syntax system in forums, bold and italic, his own system of smileys. * forum with # syntaxes systems in the same thread (a different one for each message) * wiki ~ system of forums: invitations systemfor rights to write and rights to read for all pages of a given folder ( ~ for my forums system there is an invitations system for each forum) * ~ personal pages (like wiki but the right to right is reserved for one person) * attach to each page author pseudo identification --> multi-site login system ---> system where each user identified while visiting other site --> When they visit remote web pages: links for - "Bookmark this page" - "Navigation board" - "logout from this site" option for contact info to the author of the page. * how to generate the web pages. * let users make their own web pages easily. * components based methodology |
|||
| 13
july 2004 |
* In a host --> thousand of users (logins) each user --> many pseudos. * 2 functions: - each pseudo: find its login. ~~~~> database of all pseudos with their logins - given a user logged in, find his pseudos ===> user choose pseudo in a menu for given ~~~~~> same table OR table for each login giving the list of its pseudos OR store the list of pseudos in session variables |
|||
| 13
july 2004 |
* # users can have the same pseudos. ==> forbid users to take a pseudo that is already taken. |
|||
| 13
july 2004 |
* host ==> thousand of users (logins) each user ==> several pseudos. * 2 functions -1. each pseudo ---> its login ? # users can have the same pseudos. database of all pseudos with logins -2. user logged in --> list of his pseudos ? ~~~> menu : user choose his pseudos same table / one more table /pseudos in session variables ? |
|||
| 16
july 2004 |
* private forums between remote users : - inter site login system - structure database for forums |
|||
| 19
july 2004 |
* "Tables of invitations into forums, boxes and associated pseudos" * "Display of boxes" * "Form for forum creation and message creation": writing to a new person simpler * multi-language --> dating parameters,etc. * -"webmail and simple invitation system" - contact lists : ~~ invitation relation between users ~~ admin can display invitations towards an existing user (not their pseudos but their autoincremental numbers of invitations) - system of private forums between remote users (where the boxes listing forumst to include the features of the "bookmarks page" ) - system of invitation between servers ( user of an existing server can invite another server). * procedure for invitation between servers : A can open "write someone" B by opening a new private forum in A's site and inviting B there, so a user A of the new server will open a private forum and invite a user B of the existing network, but the networks do not know each other yet, just that A's server knows the pgp public key of B's server (because this key came together with the installation). So A's server will send to B's server (before or while adding A's message to B's list of forums)a pack of A's public key and a symmetric key, crypted with B's pgp key. ==> By this symmetric key, B can click for his board (authentifying himself to A's server) and read the message. ==> Then B can continue the conversation on A's server, then , he can validate A's server into the network, by clicking on a button thatappears in front of the forum's name. ==> Then B's server sends the coordinates (URL and public key) of A's server to the whole network, that takes note of which server (B's) invited the new one (A's). |
|||
| 16
july 2006 |
* systems using Java. * PHP/MySQL. * private forums between remote users thanks to the inter site login system * way to structure database for forums as I described in the todo list for this purpose |
|||
| 27
july 2004 |
* pseudos system * GLS |
|||
| 27
july 2004 |
http://spoirier.lautre.net/work/
|
|||
| 31
july 2004 |
* my own hosting / only do PHP/mysql, no java no https; http://forum.spoirier.lautre.net |
|||
| 3
august 2004 |
ElectrifiedForum. |
|||
| 3
august 2004 |
http://www.electrifiedpenguin.com/ |
|||
| 3
august 2004 |
ElectrifiedForum ( protection part) (EFF)> InvisionBoard (security) http://www.eff.org/ |
|||
| 6
august 2004 |
* EFF * security : access to the database or another information. * InvisionBoard, but EFF kernel better security. |
|||
| 8
august 2004 |
* hosting installation problems |
|||
| 8
august 2004 |
http://annuaire.lautre.net/phpinfo.php |
|||
| 8
august 2004 |
http://annuaire.lautre.net/wiki/ScriptsPhpbut http://annuaire.lautre.net/phpinfo.php |
|||
| 14
august 2004 |
* private forums * multi-site mode |
|||
| 17
august 2004 |
* JSP * forum system already work with remote users through multi-site login system or to be included? ? |
|||
| 17
august 2004 |
http://sylvain.belprog.com/efforum/ * JSP |
|||
| 17
august 2004 |
( user4, pass4) |
|||
| 18
august 2004 |
http://sylvain.belprog.com/efforum/ * Start by a login form * have a list of boxes * Main box opens immediately once logged in * box = list of forums (private, public). * info about users : separate page = link on username. * system of pseudos installed on forum. * in the forum "user4" ( login name) --> The login names should not appear in forums, --> only pseudos should appear. |
|||
| 24
august 2004 |
* Forum,Message forum =list of messages messages belong to forums * have a tree structure between messages in a forum * "All keys are now ID int auto_increment" * "4. Reconfiguring the system. There is already separate class that reads config from file or from DataBase(possible)." user can configure his own display ? Or do you mean a general thing for the administrator ? configuration parameters? "5. The hole in the safety of forum is closed. All dependencies from Registered_Globals = On deleted." "6. Admin part is in another directory now and it's widening is in plans (1-2 days)." |
|||
| 24
august 2004 |
* forum = list of messages * messages belong to forums - Forums are not necessarily big. forum with one message but no answer: ==> -- Topic selection (like Windows Schemes) ----- CSS ----- pictures *templates |
|||
| 24
august 2004 |
1. Form validation 2. Error messages added to the lang. file; badwords moved from Lang to Realm 3. Working with look and feel (boxes). * menu with links that were in the one of my program * "my pseudos", "configuration" + user language choice |
|||
| 24
august 2004 |
===Forums, Pseudos, User Configuration========= 1. Base Forum - EFForum with full refactoring. 2. Logic will be separately from reflection (Code separately from design) 2.1 Developing Business-objects (Forum,Message,User etc) 2.2 Using templates system (i choosed Smarty as most powerful and flexible for Programmer-Designer command + caching ability) T 3. The database optimized and unified already for the next integration and development. All keys are now ID int auto_increment. 4. Reconfiguring the system. There is already separate class that reads config from file or from DataBase(possible). 5. The hole in the safety of forum is closed. All dependencies from Registered_Globals = On deleted. 6. Admin part is in another directory n |
|||
| 24
august 2004 |
1. Form validation 2. Error messages added to the lang. file; badwords moved from Lang to Realm 3. Working with look and feel (boxes). 4. Authentication (cookie-based). |
|||
| 24
august 2004 |
* forum = list of messages * messages belong to forums * tree structure between messages in a forum * "All keys are now ID int auto_increment" in all tables * "4. Reconfiguring the system. There is already separate class that reads config from file or from DataBase(possible)." ==> General options for administrating. * It will contains: -- Topic selection (like Windows Schemes) ----- CSS ----- pictures * parameters of the configuration to include ? Table colors etc * "5. Registered_Globals = On deleted." Registered_Globals = On. ( php internal hole) * "6. Admin part is in another directory n Editing possibilities for any thing (user, message(?), forum, etc.) * templates? |
|||
| 24
august 2004 |
* -- Topic selection (like Windows Schemes) ----- CSS ----- pictures * user can choose his own color scheme for the forums. * parameters of the configuration to include ? * templates separate code and html and to make more clean HTML |
|||
| 24
august 2004 |
What do you do with badwords
==> filter? |
|||
| 25
august 2004 |
* bad words filtration? ("fuck", "shit", etc) ==> don't care ==> no filtration |
|||
| 25
august 2004 |
* user can sort forums ( = choose in what box goes each forum according to whether there are new messages or not, choose the order between forums in each box) * To visit a box: - click on its name - "to column them on boxes" a box appears as a column listing forums. * "To create forums (_on the one server_)" "and to create Read/Write access" "+ subscribe other users (from any server from the servers) "which is the same, isn't it ? ==> First by the creator of the forum (who is the first user and admin of the forum if you includeadmin functions), and anyone with a right can share it with someone else with this event recorded ( see description of mysql table) - "+ editing of blacklist" = forbid to invite a given person ? * "The question: "inter-site login system". - When the user entered to the system ==> it needs to request all other servers to know if there any unread messages. ==> NO. - when someone sends a message to a forum, the sql table of this forum knows who is "subscribed to this forum" with "marked read", and sends to their respective servers the info to mark this forum unread in the user's table of forums. --> So, all the info about which forums have unread messages is already at home when the user logs in to his home site. ---> tables organization ---> "The problem is that user id must be unique between all servers." % forum : visitors and authors= (pseudo, home host)= ( pseudo@homehost) This is # to login. * Each user is on his home server - authentified as login and therefore carries all his pseudos (whose list may be in session variables for example) and when he visits a forum on the same server, by the one of this pseudos by which he subscribed to this forum. But when he visits the forum of another server he is only known as one pseudo (by which he subscribed to this forum) with id of home host where this pseudo is from. (you can define an id of pseudo, and carry both the pseudo and its id which is completely redundant as the correspondance is bijective in each home host) * personal web pages |
|||
| 25
august 2004 |
*Forums. *User configuration. *Systems of Pseudos. * Agrees with Multi-language system. * EFforum for future work. * New database structure > 1. The Forums * "Relations between users and private forums" System of display for the user, possibility to sort forums, to column them on boxes, to group the boxes (folders). To create forums (_on the one server_) and to create Read/Write access + subscribe other users (from any server from the servers) + editing of blacklist *"inter-site login system". - user enter system ==> request all other servers to know if there any unread messages. ==> The problem is that user id must be unique between all servers. * "Presentation of Forums" "Display of the tree of messages in forums" 2. User Configuration, personal web page. Personal page, where the user can write all he wants User's info display configuration (First Name, Last Name, icq, ip, signature, etc) 3. The system of Pseudos. Every user can to create any number of pseudos and manage them on the separate page, add comments.( limit with a constant maximum number of pseudos) 4. Multi-language system. From the full spec.: - Possibility to edit language files through web-interface, storing the version an author, version comparing. Regarding the numeration I would like to use english constants (fr,en,ru) against figures for text identification. * How common user chooses the language he wants to see the forum? (I mean if there is some lang-version of different authors for his language. Then whose version the user will use? ) |
|||
| 26
august 2004 |
* "Presentation of Forums" * "Display of the tree of messages in forums" 2. User Configuration, personal web page. * Personal page ( user can write all he wants) * User's info display configuration (First Name, Last Name, icq, ip, signature, etc) * names and ICQ. Users can put them in "Comments" - entries specified are to be optional. 3. The system of Pseudos. -Every user can to create any number of pseudos (one at a time) -manage them on the separate page, add comments. -limit with a constant maximum number of pseudos 4. Multi-language system. - can edit language files through web-interface, storing the version an author, version comparing. - Regarding the numeration use english constants (fr,en,ru) against figures for text identification. * numbers in chronological order ? -include pseudo of the author -author of a version can delete it if nobody uses it. * How common user chooses the language he wants to see the forum? (I mean if there is some lang-version of different authors for his language. Then whose version the user will use? ) * can list languages two ways -1. with all versions to choose one of them -2. only one version per language The first time (for default) --> the version used by the majority of users of this language or last version if no user uses it Then the version last selected by the user. 1) (multi-language) 2) invitations system 3) calendar |
|||
| 26
august 2004 |
* a forum =list of messages and
conversely messages belong to forums * Message belongs to the forum???? * dependencies between forums and messages: 1. Yes, one to many. - list of messages in each forum -several threads per forum - where there is only one thread it displays directly ~~~ "1) user's side - main menu (left side) - forum displayed by categories " - main menu, left ==> list of boxes, not forums - logs in: list of forums ( from main box) are on the right. - Another box = list of public forums shown by category. - Private forums:user puts his forums in the box he wants. ------------------------------------------------------------------- À: webdevs@tut.by "1) All forums are displayed by categories at user's side This is main menu (left side)" - main menu,left, list of boxes, NO FORUMS. - logs in ==> list of forums ( contained in the main box) on the right (~ had clicked on it; the same way when one clicks on a box, the list of forums of this box appears on the right). - clicks on a forum, list of messages in a new window (so when it is hosted elsewhere, its address is seen) - Another box ("Tous les forums publics" (="All public forums")is the list of all public forums, and display by category, NOT by default, NOT in the left column. YES on the right, listing at the same time categories and the forums they contain, ---> categories can be like titles or folders to open or close. - Private forums : user puts his forums in the box he wants. user can add a public forum to one of his boxes (==> copy of the link. ---Add, delete, move (forums), create/delete/rename folder buttons displayed on the separate page of profile How do you mean on a separate page ? * add forum to folder? link in "UserInterface" or choose at configuration page from list? ==> A forum, in a folder, in 3 possible ways: 1) user creates a new forum 2) user copies the link of a public forum or moves the link from a box to another 3) user invited to the forum by another existing user of the forum * For cases 1) and 2): --> managed by a page of "user configuration for this forum" (reached by clicking on "edit subscription" aside the name of forum), which offers the following possibilities: - Subscribe? (yes/no) ~~~~ If yes: -in which box to appear if unread (menu) -in which box to appear if read (menu, including "none" if a public forum) ~~~~ If no: -in which box to appear (menu, including "none" if a public forum, or "Resign my invitation" if private). (Or did you already program to have folders and subfolders in boxes ? Well, then I don't know...) For case 3) --> default choices of the above values decided by the general user configuration. OR put it all to the main box. Then the user will have the time to change these values for each different forum he receives. 4) Authentication(cookie based) * Sessions with URL-rerecording --> Safety is important * maximum number of pseudos limit set by admin |
|||
| 26
august 2004 |
* System classes coding * Debuging and bugfixing. * forum columns. |
|||
| 26
august 2004 |
limit with a constant
maximum number of pseudos |
|||
| 26
august 2004 |
* forum list of messages * messages belong to forums Forum only contain the message list. ~~~~~~~~~~~~~~~~ * menus ( former program) + "my pseudos", "configuration" (user specific language choice) ~~~ 1) All forums are displayed by categories at user's side This is main menu (left side) ---Add, delete, move (forums), create/delete/rename folder (Possible the buttons will be displayed on the separate page of profile) * add the forum to the folder - link in "UserInterface" -OR choose at the configuration page from list 2) Pseudos, Profile(configuration), Language, Open Forums, Closed Forums, Contacts(this functional have dependencies from Inter-Site system). Invitation. 4) Authentication(cookie based) Sessions with URL-rerecording less safe / more universal. |
|||
| 27
august 2004 |
* left menu. * Every user has 2 folders (Main - it is empty All - all Public Forums) * User can create/delete any number of folders/subfolders and place forums into them. * All and Main can't be deleted. * The names of forums contained in the folder are appeared after the user clicks on folder. |
|||
| 28
august 2004 |
- Main box - Other boxes (listed) - Public forums - Email ( includes invitations to become members to this site) - My pseudos - My contacts (includes invitations of new people by this session without email) - Configuration (includes: language - create box - rename boxes) * network members invitations (contacts or other) to a forum is done : -in the forum or in the "edit subcription to this forum" * inter-site aspect |
|||
| 28
august 2004 |
* "Presentation of forums" * "display of boxes". - forums / tree order of messages - "Bookmarks" |
|||
| 28
august 2004 |
============================================================================= #000001: System objects and operations with them (for forums). ================ Objects list we have at this time see below: - Message (author, text, etc) - Forum (Header, message quantity, type[Public|Private] etc id_box_read, id_box_new) - Folder (Name, All Forums quantity, Quantity of Forums with new messages ) Forums are groupped by folders. Folders can have subfolders. At first time there is 2 standart folders - "Main box" and "Public Forums" Main Box can not be deleted. 1)Operations with folders. - Delete. All forums in folder moves to "Main Box" (if checked "with forums" then forums are deleted too) - Create (with parent reference) - Rename - Move to another folder - Pointing the ordinal number (operations Up and Down) 2)Operations with forums - Delete - Create - Editing Subscription - User invitation 3)Operations with folders and forums - Place to folders(it means to point 2 folders (read, unread)) - Change Folders 4)Operations with Messages - The user added the message. The message can not be changed. ============================================================================= ============================================================================= #000002: Not essential objects. ================================ - Thread (Header, forum IDзаголовок) - Category (Name) Forum is able to have some threads. If one then all messages display directly. Forum can to belong to one(for simplicity) category (ex. sport, hobby, cars, etc) ============================================================================= ============================================================================= #000003: Forum/Folders Display . ================ There is 2 columns on the page. Frames are disabled (will be troubles with new windows, 3 connections with server agains 1, hard way to reach good display). ____ __________ | 2 | |_____________| | | | | 1 | 3 | |___|_________| 1) Sorted list of folders (see №000001 "Operations with folders") 1.1) At first time we can to make just spaces, then will use dhtml-tree for display 2) User's Menu (see №000004 ) 3) Forums list in current folder. (At this time will make without sorting, in the future will follow your choice - or by categories either by User's order. 3.1) There is a link to forum's editing configuration beside the forum header in the right window (3). - delete forum (similar to "Resign My Invitaion), (physically the forum can be deleted by the admin only, the user just stops to see deleted forum, other users can to continue posting to this forum) - To Subscribe somebody to this forum - Own subsrcibe editing - change folders (read, unread) Must to choose the folder.( "none". There is no differences between "Public forums" and other folders) ============================================================================= ============================================================================= #000004: User's menu (repeating for any case) ================ Pseudos, Profile(configuration), Language(see #000006). ============================================================================= ============================================================================= #000005: User types ================ 1) Guest. This users haven't left menu. They can just view open forums. 2) User (Member). 3) Admin. (How much admins the host will have? Should we create log of their actions? The easiest choice - we are to create password for /admin/ folder and tell the password to admin. Admin is able not to be a member of the system. I would like to choose this variant at this time.) ============================================================================= ============================================================================= #000006: Language ================ Every user can choose preferred language.(The design will be defined in the future, just select-box above at this time). The user can to choose "Languages" in menu and will be forwarded to the page of "Managing Languages". The list of translates will be displayed on the page in the next format( Language{link, becomes current after click}, pseudo of translator, version( what format do you need?), creation date, comment(i think this fiel is necessary), "compare" link. "edit" link ( this link appears just for the author of translation. This task is not over the coding at this time, there is some nuances) "delete" link (this link appears just for the author. Do we need this link in the project?) ) There is possible filtration by language, date, etc. 1) Translate creation (The scenario I propose.) - The user goes to the page of Language Creation - Downloads (clicks on link "download pattern" cvs file in format "id";"value in his language";"?" ) - Fills all fields "?" - Fills on the same page pseudo (from pseudos list), version, comment. Chooses the language from the list (There will be some predefined languages for the first time, in the future I'll find out how to add new language. The best way to add new language - admin do this. And the user just press "Request for new language" to avoid adding non existing languages) Uploading filled file. (The error is returned if there is some fields are missed in the file.) 2) Comparing example see "http://orbitel.by/shop/compare/_bin/add.php?productID=61". ============================================================================= ============================================================================= #000007: Pseudos ( repeat ) ================ The separate page, create (without delete and edit! to keep the DataBase structure and wholeness ) Edit Pseudo comments The maximum number of pseudos is limited with a constant number. The pseudo is unique within one server ============================================================================= ============================================================================= #000008: Invitation ( repeat ) ================ The user created the forum at the page "Forum Configuration". After this he can to invite users. 1) Pseudo input (input type=text) 2) Host input (input type=text, default=current host) 3) 2 checkboxes for Read & Write rights. ============================================================================= ============================================================================= #000009: Administrating (revised) ================ 1) Users (delete/edit/create) 2) Forums (delete/edit) 3) Languages (add new language after user request). What more do we need to add into the admin's part ? ============================================================================= ============================================================================= #000010: Pages of User interface. ================ 1) login ( Entering the system with Forgot password) 2) registration 3) profile (Change registration data) 3.1) pseudos 4) index 5) forum ( view messages, some messages per page (ex 10,20,50 message per page), Add new message form) 6) forum_config ( Signature setup, invitation) 7) forum_create ( Create new forum) 8) box ( Managing folders - create, delete, rename. I think it would be better to make it on the separate page to avoid left menu loading.) 9) lang ( The page where user can choose version of translation) 10) lang_create (Uploading new translation) |
|||
| 30
august 2004 |
====== #01 ====== - Private Forums: list of invited people + rights (admin, read/write or read only) - public forums: admin rights + blacklist managed by admin of the forum - Folder: unique owner identified by login, who can access it (except folders of public forums that are accessible by everyone) - "3) operations with folders and forums - place to folders - change folders" 4)user's message: can validate it directly when sending it or later. Once validated other users can see it. As soon as another user saw it, the message cannot be changed anymore. === #03 === -calendar events - below list of forums of the main box (in your space 3). - The entry "Calendar" added to your menu 2. forum appear in "read" folder even if it's unread. ==> unsubscribing: put "none" as "unread folder". 3.1. includes: - under which pseudo one appears in the forum. (- forum's original name / personal display name that one can change) ====== #04 ===== - Pseudos - Contacts (=list of friends) - profile and preferences (including language - Logout and later: - Bookmarks - Calendar .... ==== #05 ==== 1) Guests. A login form in above menu. ==== #06 ==== * List of translates: ordered by language + creation date version format * "compare" link: A comparison between at least 2 versions * "delete": except if already used. * link "Publish": before published, only exists for its creator. Translate creation: NO download/upload. ~~~> edit as a form in a table : with as many entries (lines) as there are items to translate, with possibly other versions displayed in other columns. The same kind of table can be used for "compare". *link "Comparing example". === #O7 === * webmail * pseudo usable as email address or not. === #08 === 3) Invitation ==> reading right * Admin can invite (admin right/writing right/read-only) * User writing right :(writing right/read only) * User with only reading right invite only read-only. |
|||
| 7 October 2004 |
"Mark Invalid" means: I've created the message but nobody have seen this. SO, I still can Unvalidate it and edit/delete/.. "Create forum" contacts list invitations of another user to a forum, with rights to read, write and admin - Pseudos in forum should be clickable to get to an info page on that user Now that info page will only consist in displaying a longer comment associated to the pseudo (so there should be 2 comments for a pseudo, a short one for display in messages and a long one for display on info |
|||
| 9 oct 2004 |
* register as a new user - private forums in my main box - click it This is private forums created by the other people. They didn't invite you so you haven't access to that forums. * can create a new public forum No!!!==> need create first pseudo * create pseudo. Comment field * add someone to this list. --> button "Edit Forum Rights" --> add #(pseudos, rights) * New user: I had private forums in my main box - click="not allowed to access" - click to create a new public forum --> no sense as no pseudos created yet-->forum does not appear. - create a pseudo --> does not work - field to create comment. - list of contacts : add someone to this list |
|||
| 10 oct 2004 |
* http://forum.belprog.com User: user200 Pass: pass200 * create a new account. |
|||
| 10 oct 2004 |
* dating part * translations page * - Add new translation, based on selected one (1) - Edit selected(1) translation ==> only one, named: - Edit selected(2) while viewing (1) * Editing : -> # version, in # language * Compare 2 selections: one table with 2 columns --> every entry in one language <-->other language entry. |
|||
| 10 oct 2004 |
* Editing can make # version, in
# language than the one (2) it is made from. (1) and (2) can be identical (2) can be empty |
|||
| 13 oct 2004 |
* dating part * release: host how 2 make an installation * people use it, with SSL access, with admins that we trust. |
|||
| 18 oct 2004 |
* forum + subscribe/unsubscribe
option. |
|||
| 18 Oct 2004 |
* statistics page accessible by
members - total numbers of users , pseudos, disk space |
|||
| 19 Oct 2004 |
* rights to write (not admin) this forum. * read public forum: MaxAccess=w; My pseudos: sylvain=w; |
|||
| 19 oct 2004 |
1. Forum. 2. Uniting. 3. testing in multiple hosts. * »» ''bopub1'' Folder »» ''FFOORRUUMMM'' Forum MaxAccess=w; My pseudos: sylvain=w; 123123456 2004-10-09 00:00:00 user1 {Aio oaeay aio inaaaa} TestMessage * (between {} latin characters, not russian )~~> characters |
|||
| 20 oct 2004 |
* character sets is * Frozen Team for their webmail ? * top bar --> new entry called "help" * "documentation"--> new users understand features ( "mark valid","mark invalid") * multi-language |
|||
| 20 oct 2004 |
* user's display --> guests'messages are --> display & database |
|||
| 22 oct 2004 |
* technical documentation |
|||
| 25 oct 2004 |
*dating system specification. *dating description |
|||
| 26 oct 2004 |
============================================================================= Making a statistics page accessible by members, --> number users and pseudos, total disk space used. ~~~~~~~~~~~~~~~~~~~ #001: Where does it have to be placed? ============================================================================= ============================================================================= * for every pseudo,choose box forums newly received by invitation to that pseudo will be put if we don't move it somewhere else. ~~~~~~~~~~~~~~~~~~~ #002: Where (in what page) is it to be managed? ============================================================================= ============================================================================= * top bar "help" "documentation": features of this program ("mark valid","mark invalid" functions). * help : multi-language also. ~~~~~~~~~~~~~~~~~~~ #003: * pop-up window? *let a user view help in languages, different from his current translation? * one page / structure ? ============================================================================= ============================================================================= * admin chooses whether the people with writing right in forum can view the invitations table. ~~~~~~~~~~~~~~~~~~~ #004: can admin decide if a specific pseudo can view this table? ============================================================================= ============================================================================= * user info page: display ( same style as a folder) list of all forums where he wrote a valid message and that oneself can read. * messages in public forums of remote servers * limits of the system ~~~~~~~~~~~~~~~~~~~ #005: * page look # % (# users)? -I view someone's details: do I see only those forums where this pseudo has posted essage and where I have at least reading right? ============================================================================= ============================================================================= * language list: expressions ( "such forum already exists!" * creation of forums with the same name - public forums only or for all type of forums ? - no for 2 public forums - ok for 2 private forums can distinguis by other parameters (list of members...) (while the computer distinguishes them by forum id). ~~~~~~~~~~~~~~~~~~~ #006: * users can create the same named private forums? ============================================================================= |
|||
| 27 oct 2004 |
1. user posts a reply
after the session has expried, the message is not lost. It is accepted but kept invalid, and the user is shown a corresponding alert. He can login again and mark the posted message valid or delete it. 2. The messages posted by guests are now seen by registered users. 3. When you view messages of some thread of a multi-thread forum, you can see the name of the thread. 4. Forum information page: the list of pseudos who have posted messages (admins in bold) and list of invitations sent by the user's pseudos and to the user's pseudos. 5. "public forums" added to the language file. 6. The user cannot add its own pseudos into his contact list so now he has to enter them by hand to invite them. ============================================================================= * public forums Admins of public forums --> "not allowed" list : list apply on all corresponding pseudos! ~~~~~~~~~~~~~~~~~~~ #001: forbidden user can not use pseudo to try again ============================================================================= |
|||
| 28 oct 2004 |
1. Statistics page . It
contains the total number of pseudos, users, and the total disk space used by DB; 2. The "configuration" link . It contains "Pseudos settings", "Translations" and "Statistics"; 3. For every pseudo, the usercan decide, to which forum the newly received forums will be placed. 4. admins of private forums can decide whether the pseudos not having admins rights have or have not access to view (not modify) * invitations table. - when somebody having invitations ~~~> viewing access invites somebody else he can allow/disallow the pseudo he invites to view invitations table. 5. info page of a pseudo the list of forums accessible by the viewer he wrote valid messages in is displayed. 6. help page in "Configuration" menu. |
|||
| 28 oct 2004 |
* delete accounts --> person register again --> check folders S |
|||
| Mar 2
novembre 2004 |
* Dating * Personal WebPages |
|||
| Mar 2
novembre 2004 |
hosting issues |
|||
| Sam 6
novembre 2004 |
- The forum was updated. http://forum.belprog.com http://forum.belprog.com/admin/ |
|||
| Sam 6
novembre 2004 |
============================================================================= #001: uploaded photos are suitable or not (like: size, resolution, etc). ============================================================================= ============================================================================= #002: pages should the system contain? - Is it to have any kind of the main page? - items in the user menu? - links to start a dating account to be placed? ==> index.php or an inclusion (like dating_login.inc)? ============================================================================= ============================================================================= > The helping comments for each item (profile or photo) forms a public > forum attached to it. ============================================================================= ============================================================================= > personal web page, first choose an existing pseudo of yours, or create a new one just for this purpose. ==> Then you will make a web page attached to this pseudo. ~~~~~~~~~~~~~~~~~~~ #004: So, how many diffirent independent dating accounts and web pages can have a single user and a single pseudo? ============================================================================= ============================================================================= #005: As I see, the first web page should contain all the information about a person which was entered at the 1st step and nothing more, and the second (optional) web page should contain any additional information the user wants to be read by the selected (or S+) by him people. Am I right? ============================================================================= ============================================================================= - reviewing of your matches, you have the option to let them appear on two windows alternatively, so that every one is being loaded during the time when you are reviewing the other: after you reviewed one page and click to validate your selection, this page goes to the background for loading the next matches while you can review the other page that has already been loaded. ~~~~~~~~~~~~~~~~~~~ #006: And is there to exist a third (actually, first) page with the list of viewed users? ============================================================================= ============================================================================= > From 4) or 4bis), those you select receive from you the status S > (while U/N of T/N becomes S/U so your profile appears to them), so > that they go to 4ter) or 5). ~~~~~~~~~~~~~~~~~~~ #007: As I understand, people have "unlisted" (N) status for me, if they do not match to my search criteria. But if some user that is "unlisted" for me selects me, he anyway becomes shown in my lists. Is it right? ============================================================================= ============================================================================= #008: How, more concretely, the user is to be able to connect his dating profile(s) with his pseudos? ============================================================================= |
|||
| Sam 6 novembre 2004 |
try the hosting http://www.webhost4life.com/ : Windows servers. |
|||
| Dim 7 novembre 2004 |
======================================================================== #001: Are there any criteria according to which the system would decide whether the recently uploaded photos are suitable or not (like: size, resolution, etc). In what way (where) can they be set? ======================================================================= Why do you speak about "recently uploaded photos" ? If user is uploading a photo specially for this, yes it would be good to check limits in size: that width and height are inside a range of values, and that the size in kb is no heigher than a given value. So, display these values of the uploaded photo together with the ranges of acceptable values. This range of acceptable value would be universal constants, so they cannot be set to different values. But since with the personal web pages part that Frozen Team is doing, user can also upload photos there, it would be good to "unify" these upload possibilities, so that user can for dating, instead of uploading a photo once more, select one of his existing photos. Or maybe give another URL somewhere else so that a photo can be displayed without upload. Anyway, I think of giving the possibility to other users to say if they think a photo is not suitable. ======================================================================= #002: Would you please describe more definite, what pages should the system contain? Is it to have any kind of the main page? What items are there to be in the user menu? Where are the links to start a dating account to be placed? I mean, should I create an index.php or an inclusion (like dating_login.inc) first? ======================================================================= With the user documentation there would be a part of doc about dating. In the user configuration page there would be a link: "Open a dating account". This would add a new link "Dating" at the top menu. Clicking on this link would access a dating menu following more or less the list of points I described in my text of dating user documentation, something like : -create/edit profile - creat/set personal web page - activate profile (reception of matches):yes/no - send profile! - review new matches (how many are there) - reviewing old matches and their personal pages (now many, how many new)... I don't understand your question " should I create an index.php or an inclusion (like dating_login.inc) first" ======================================================================= > The helping comments for each item (profile or photo) forms a public > forum attached to it. ~~~~~~~~~~~~~~~~~~~ #003: Please, describe it more definitely. ======================================================================= Finally, don't do this part as I got another idea to solve the problem more simply: let the possibility to activate profile before sending it, and the possibility to warn another user that the photo has a problem wy a simple click. ======================================================================= > As for any other personal web page, you must first choose an > existing pseudo of yours, or create a new one just for this purpose. > Then you will make a web page attached to this pseudo. ~~~~~~~~~~~~~~~~~~~ #004: So, how many diffirent independent dating accounts and web pages can have a single user and a single pseudo? ======================================================================= A single user can have only one dating account, linking to one or two web pages. But he can have different web pages for each pseudo. ======================================================================= #005: As I see, the first web page should contain all the information about a person which was entered at the 1st step and nothing more, and the second (optional) web page should contain any additional information the user wants to be read by the selected (or S+) by him people. Am I right? ======================================================================== No. Both web pages are like any personal web pages, freely composed by the user.I think one's parameters could be accessed from the matches list; it is not a personal web page, just an info on profile that need not access the other's site but is just extracted from the info that was received for matching computation.One's search criteria, though first received together with parameters for matching computation, should never be accessible by the other user (so, be deleted from the receiver's site just after this computation ?). ============================================================================= > To spead up the reviewing of your matches, you have the option to > let them appear on two windows alternatively, so that every one is > being loaded during the time when you are reviewing the other: after > you reviewed one page and click to validate your selection, this > page goes to the background for loading the next matches while you > can review the other page that has already been loaded. ~~~~~~~~~~~~~~~~~~~ #006: And is there to exist a third (actually, first) page with the list of viewed users? ======================================================================== No. What viewed users ? I was speaking about the two pages to be displayed simultaneously. Once a screen was viewed and eventually some matches were selected, after click all matches from that screen change statuses and therefore go to different lists.Of course, if one wants after that to view again matches seen just before, one can click elsewhere to review the trash or other lists of selected matches. ======================================================================== > From 4) or 4bis), those you select receive from you the status S > (while U/N of T/N becomes S/U so your profile appears to them), so > that they go to 4ter) or 5). ~~~~~~~~~~~~~~~~~~~ #007: As I understand, people have "unlisted" (N) status for me, if they do not match to my search criteria. But if some user that is "unlisted" for me selects me, he anyway becomes shown in my lists. Is it right? ======================================================================= Yes: unlisted is a very abstract status that concretely means: not received in the database of your server (but your profile is in the database of his server). Then, this has the effect of him sending his profile to you. ======================================================================= #008: How, more concretely, the user is to be able to connect his dating profile(s) with his pseudos? ======================================================================= He does not connect his dating profile with his pseudos. Only his web page is connected to his pseudos (each page has an author). And the profile is connected to the web page as a link in the old matches list after both users have selected each other. |
|||
| 7 nov 2004 |
=============================================================================> #008: How, more concretely, the user is to be able to connect his > dating profile(s) with his pseudos? > =============================================================================> More precisely: of course at the home site the profile is connected to the user. Then what is sent with the profile to other site is the profile id. I wondered about the possibility to have a specifically dating pseudo that would accept invitation to forums only by old matches. Not sure it is really needed (instead, user can blacklist by hand).Also, to decide about web pages whether the reading rights would be automatically reserved to matches with the corresponding status (but anyway user can choose to use for dating a pseudo that allows invitation by anybody, and web pages that anybody can access). |
|||
| Dim 7 novembre 2004 |
- list of private forums
of a given pseudo : "The user took part in the following private forums" --> make these active links ! The aim of telling in what private forums we discussed with a user is to give a shortcut to continue corresponding with that user in an existing forum instead of creating a new forum. We may have forgotten in what folder the forum is so unless this is an active link it does not help finding the forum. It would be good also to display the folder name aside the name of forum. The best would be if in the contact list we also had direct access to the corresponding forums if there are not too many, with a priority given to the forums with only two members (onself and this person), in the same way as I said it would be best if in folders we had direct view of the list of members (other than oneself) of those forums (with priority to admins). |
|||
| Lun 8 novembre 2004 |
We should distinguish between two things: A) functionalities necessary ==> the visitors trying the beta bersion of the software, and to make it usable B) long term, in particular to support in practice the large-scale extension of the network, but that are more "hidden" functionalities What you did with adding new languages is of type B). But there are still things of type A) that I told you and you did not do though they do not depend on the unification with GLS. - Correcting admin rights: let admins edit a set of limitations of rights instead of making unappropriate invitations. (For denial of admin right, let us to simplify limit it to resign, and disable this resign when there is no other admin) - presentation of folders = ugly with its repetition of the big button "Move to folder" at every line, and instead include there (for private forums) the list of participants other than oneself - oneself (what pseudo) can also be included but in another column (as : under what pseudo we connect to the site hosting that forum). - In contacts page and info page on a pseudo, make active links of the private forums we had with this person. |
|||
| Lun 8 novembre 2004 |
"- The user cannot subscribe to public forums" Why ? I did not ask you this. On the contrary I would think that the possibility to subscribe to public forums can be interesting. Or maybe, subscribe to appear when new to another box dedicated to the subscriptions to public forums, different from the main box. (Or it could also be the main box that would list first the private forums with new messages, then below the public ones)Or did you have any reason to do this ? "-The Info page of the forum has been updated: editable custom title, two comments, and subscribe/unsubscribe option have been added. Link to the info page has been added to the forum page (where we view messages/existing threads). " All right. how this will be managed for forums hosted on a server different from the user's home server ? - new host ? |
|||
| Lun 8 novembre 2004 |
-aesthetic reasons one should not multiply the number of links or big buttons for modifying parameters on each line in the table of forums in a folder. --> The link for modifying the custom name of a forum is one of them. this link should simply disappear so the costum name can only be modified from the info page of the forum.But I'm not sure, neither for other modifications. I think we should consider the following idea, think how to use it precisely. Instead of putting a link on a word ("subscribe", "unsubscribe", "move to folder", "info", "(change)", we could put there a small icon to click on. Icons take less room on the screen. An icon could already inform us on whether we are subscribed or not, and clicking on it would modify it...For modifying the custom name of a forum, if we do it directly at the folder page the icon could be a pencil. What do you think of this ? Of course we need not often modify custom names of forums, so doing it only from info page would be OK. |
|||
| Lun 8
novembre 2004 |
-MainBox item has been added to the language file. -The user cannot subscribe to public forums. -There are no categories anymore; the table 'categories' has been dropped from the database. -Every forum now have two comments. The first (short) is shown when we view threads or messages of a forum (if it is not null). Admins can change forums' comments on their info pages. -Every user can set a custom name of each forum he is in invited to (and each public forum he is not blacklisted to). -The Info page of the forum has been updated: editable custom title, two comments, and subscribe/unsubscribe option have been added. Link to the info page has been added to the forum page (where we view messages/existing threads). |
|||
| Mar 9
novembre 2004 |
- dating system. ============================================================================= #001: More definitely, what search criteria will there be? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - kinds of criteria: - criteria which have a constant set of possible values (answers); - criteria which values (answers) can be any text information. ============================================================================= |
|||
| Mar 9 novembre 2004 |
=============================================================================> #001: More definitely, what search criteria will there be? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ two (or more?) kinds of criteria: - criteria which have a constant set of possible values (answers); - criteria which values (answers) can be any text information. ============================================================================ - description of the search criteria ? in part 1) of http://spoirier.lautre.net/forum/dating.htm - more complicated than in traditional dating systems, ==> for every member there will be only one search to produce a completely satisfying list of matches that will represent the best of what computers can do, so, much less human waste of time. - hosting ? |
|||
| Sam 13 novembre 2004 |
000001: Registration ================================ Actions: 1.The user enters his common parameters only once to create the dating account. 2.The user chooses criteria to search for other users.3.The user enters any other information describing him. 4.Upload a photo. 5.Ask for advice. 6.Help advising others. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1,2. There is some set of searching criteria. The user is first asked to enter his corresponding parameters (1) and then asked to choose criteria by which the system should search for matches (2). User’s parameters (common trades of character, weight/height, date of birth, some personal preferences and so on) cannot be changed later. Criteria of search can be changed at any time. ===========-> Of course the birth date should not change but there are some parameters that may honestly change, like wheight, hobbies... It would be recommanded to the user that he changes nothing but it's not an obligation. Changing search criteria is no less problematic than changing parameters, from a technical viewpoint (both are parts of the same file, and modifications rises the question of whether the matching with past profiles should be recomputed or not. ========== 4. There can be some constant limitations (file size, dimensions). The system should check them before accepting the picture. 5.A. Is the user is not sure whether the picture is suitable, he may check “ask for advices” so that others would see click links “I think the picture is not suitable” and “I think the picture is suitable” and leave messages. Then the statistics of opinions is displayed to the user and he is notified when too many people think the picture is bad. Incoming messages are also shown. ===== -> Ok. I suggested that we would drop this part as another solution would be to allow for profile activation before sending, then including the possibility to do warnings in this real context, but the best may be to implement both ideas at the same time. ===== 5.B. If the user is not sure whether the information he entered (3) is suitable, he can also turn on the option “ask for advices”. Everything is the same. 6. The user can also give advices to others if he wants. There should be an item “Help advising others” where the user would be able to choose to view either men’s or women’s photos or men’s or women’s profiles. It can also help to decide if his profile is well done and to study the usual mistakes. ===== -> OK. ============================================================================= #000002: Creating a personal Web page.================================ Actions: 1.Create a new Web page and associate with to some pseudo. 1.1.Choose whether it will be a public or a private page. 1.2.Upload more pictures/videos. 1.3.Edit text information. 2.Edit existing Web pages. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -> That is Frozen Team's part ===== For the dating account to start functioning, the user is to have at least one public page. Every pseudo must have a public page to have a private page. ====== -> No. Having one page is sufficient. One can have a private page without having a public page. Then one would select in dating which page to use. If it is a public page, then it will stay so. If it is a private page, then the reading rights will be automatically modified by the dating program depending on status of matches. ===== Pages can contain any pictures/videos (no limitations) and any other text information the user wants to make known. Public pages can be viewed by everybody. Private ones can be viewed only by those people who have corresponding rights (see below). This step can be passed and done after the 3rd step is done, but this step is necessary for the dating account to be activated. =========================================================================== -> I would say: this step is necessary for the dating system to run until the end. But I call "activating the dating account" the fact of receiving new matches, which is what the 3rd step is handling. ============================================================================= #000003: Review and select new matches (“U” folder).================================ 1.Choose parameters to display in the list of matches. 2.View the list of matches. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Here the user chooses the columns of the table of matches to be displayed. There must be some constant initial settings. 2. The list of matches the system found suitable for you. The user chooses (checks) the people who he thinks would maybe be interesting for him. There are following statuses of matches:unlisted (N) unreviewed (U) trashed (T) selected (S) selected+ (S+) ========== -> I said the real status of a match is not one such symbol but a pair of such symbols: (status A gives to B, status B gives to A). ====== Unlisted: those matches which do not correspond to the search criteria. ==== -> I called this way the situation of being possibly oneself on the other's server but not having the other's file in one's server because he did not select us. OK, another situation is when the computation gives a negative result. I think, keeping them would be interesting only in the case one modifies his profile and wants to review matches agreeing with the new profile without disturbing anybody else. But it forces the system to keeping a copy of all profiles received. Is it heavy if there are millions ? ====== All other matches have an “U” status from the very beginning. After this step, the user checks matches he thinks he might be interested in page by page, so that the listed matches become either trashed (“T”) or selected (“S”). The user views each of the listed matches in the following way: two pop-ups are shown. One of them displays information about the currently viewed match (the user views it and decides whether to select or not), the he finally clicks “next”. Then another pop-up becomes active. The idea is to save time: the first pop-up is loaded while the second one is viewed and vise versa. When the user clicks next, another pop-up containing already loaded information about the next match becomes active. ============================================================================ -> Yes, but with a difference: each pop-up displays information not about one match but about 10 or more matches, one per line (the exact number can be chosen in the configuration together with the list of parameters to show). To select a profile, check the box on the left. Next answers in the next message. What about the hosting? |
|||
| Sam 13 novembre 2004 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - user can change matches’ statuses everywhere they appear ============================================================================= Yes between T, S and S+ |
|||
| Sam 13
novembre 2004 |
http://shost1.frozenteam.sobig.biz http://shost2.frozenteam.sobig.biz - communicating with GLS and WebMail systems. |
|||
| Dim 14 novembre 2004 |
http://shost1.frozenteam.sobig.biz http://shost2.frozenteam.sobig.biz - GLS . - syntax for full pseudo names. - public forums are inter-site or not. ~~~> creates a public forum: listed from all sites or only for users of this site. * 2 main folders of public forums: one for public forums reserved for users of this site, one shared with all other sites. * create nicknames for hosts: easier to remember than full URL. This would serve as a replacement for domain names inside our network. So user would see those names of hosts, and there would be a table inside each server that would transform this into an URL. The interest of this is to make easier identifications of peudos or web page addresses. |
|||
| Dim 14 novembre 2004 |
- relation between dating files and pseudos. - link to first web page goes the pseudo author of this page. In order to let this work together with the possibility to activate file before sending it, let us do according to the following procedure: While A's file is active, let B send his file, to be received by A. Without link nor pseudo, just dating id. Suppose the matching computation gives positive result. Status U/N A reviews B. If A selects B, then A's file is sent to B. Still without link nor pseudo. Status S/U. B can review and select A. But as long as B's web page is not active, the status change is kept in B's server and does not come to A's server. As soon as B selected A and B's web page is active, the status change is sent to A together with B's pseudo and link. But if A's web page is not active, A can only see how many results he gets in the S/S list but cannot display the list. As soon as A's web page is activated, A's server pings back B's server together with A's pseudo and web page link. (in the next steps, you can exchange A and B). A can display the list and visit B's web page. He does it using the GLS with his pseudo. With the authentification info is the mention of the fact that it is for dating. Then, if A clicks on the "Write to this user" link at the top of B's web page, the forum created in A's server would contain in its header (or: see below) for B's display the mention it is for dating and the link to A's web page, and for A's display, the mention it is for dating with the link to B's web page. Then, the pages of S/S and more matches will contain direct links to these forums. Or, I'm just thinking: why not make still another list of matches called (S/S or more with forum started) that will combine the functionnalities of: (S/S or more) matches list, and of a folder of forums. This folder would also appear as a subfolder of the main box.In fact, this simple fact of what folder it is in would suffice to stand for the mention of the fact it is for dating. I tried to think about the problem of the behaviour of the U/U status. I's a subtle problem I did not finish specifying. |
|||
| Dim 14 novembre 2004 |
============================================================================= #000005: Select more closely.================================ In this folder are listed the matches with statuses S/U and S+/U. It means that the user has already chosen these people with S or S+, but they haven’t yet. Well, the user may either move someone to trash or update S status for S+ to possibly help starting contacting this match a bit earlier. ============================================================================ This list can also display the matches blocked by the absence of personal web page. ============================================================================= #000006: List of twofold selected matches.================================ In this folder are listed the matches which have been chosen as S or S+ by the user and have also chose the user as S or S+. =========================================================================== Yes, and every match there also links (aside the web page(s)) to the creation or viewing of a forum if it is not done; and I am not sure whether to list to the same screen those where a forum has started or not. ============================================================================= #000007: Viewing the info pages of matches.================================ I meant "First web page" (without excluding of course the possibility to view the set of parameters like in every list), which can be also private.Then, optional second web page. ------ - forums system - dating. |
|||
| Mar 16 novembre 2004 |
-a beta testing - demo site for the public - release of a version directly stable. - dating part - web pages work - The money system |
|||
| Jeu 18 novembre 2004 |
=========================================================== > Unlisted: those matches which do not correspond to the search criteria. > ==== >> I called this way the situation of being possibly oneself on the other's >> server but not having the other's file in one's server because he did not >> select us. > ====== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #000001: =========================================================== The sending of the profile by new member B to old member A is one-way information flow B ->A . The"answer" sending back A profile to B's server happen by the selection of B by A, N/U -> U/S. =========================================================== > #000006: List of twofold selected matches.================================ > In this folder are listed the matches which have been hosen as S or S+ by > the user and have also chose the user as S or S+. > ===== >> Yes, and every match there also links (aside the web page(s)) to the >> creation or viewing of a forum if it is not done; and I am not sure >> whether to list to the same screen those where a forum has started or not. > ===== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #000002: What forum are you talking about? =========================================================== The private forum for the 2 people to correspond together of course. |
|||
| Jeu 18 novembre 2004 |
=============================================================================> #000001: Registration ================================ Actions: 1. The user enters his common parameters only once to reate the dating account. 2. The user chooses criteria to search for other users. 3. The user enters any other information describing him. 4. Upload a photo. 5. Ask for advice. 6. Help advising others. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> 1,2. There is some set of searching criteria. The user is first asked to enter his corresponding parameters (1) and then asked to choose criteria by which the system should search for matches (2). The user has an ability to change his parameters, but he is recommended not to do it. He can also change his search criteria. From a technical point of view, changing either personal parameters or criteria of search is rather problematic as these actions cause all matches to be checked once more and each time it takes a lot of time for the system to re-check the matches. Unless one decides to not do this re-checking and only apply the new data to the newly received files; this should be the default way of doing things. So the user must be reminded to be very accurate while filling the fields. More precisely, to take one's time to do it, check it and check it again (re-edit it) before activating the file, and even more before sending it. |
|||
| Jeu 18
novembre 2004 |
=========================================================== > Unlisted: those matches which do not correspond to the search criteria. > ==== >> I called this way the situation of being possibly oneself on the other's >> server but not having the other's file in one's server because he did not >> select us. > ====== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ =========================================================== > #000006: List of twofold selected matches.================================ > In this folder are listed the matches which have been chosen as S or S+ by > the user and have also chose the user as S or S+. > ===== >> Yes, and every match there also links (aside the web page(s)) to the >> creation or viewing of a forum if it is not done; and I am not sure >> whether to list to the same screen those where a forum has started or not. > ===== ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #000002: What forum are you talking about? =========================================================== |
|||
|
Jeu 18 novembre 2004 |
============================================================================= #000001: Registration ================================ Actions: 1. The user enters his common parameters only once to create the dating account. 2. The user chooses criteria to search for other users. 3. The user enters any other information describing him. 4. Upload a photo. 5. Ask for advice. 6. Help advising others. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1,2. There is some set of searching criteria. The user is first asked to enter his corresponding parameters (1) and then asked to choose criteria by which the system should search for matches (2). The user has an ability to change his parameters, but he is recommended not to do it. He can also change his search criteria. From a technical point of view, changing either personal parameters or criteria of search is rather problematic as these actions cause all matches to be checked once more and each time it takes a lot of time for the system to re-check the matches. So the user must be reminded to be very accurate while filling the fields. 4. There can be some constant limitations (file size, dimensions). The system should check them before accepting the picture. 5.A. If the user is not sure whether the picture is suitable, he may check "ask for advices" option and let others to advise him. In this case, others see links "I think the picture is/isn't ok" and click on them and leave messages explaining why, if they wish. Then the user sees the statistics and sent messages. So before activating the account, the user waits for others' opinions. But if he doesn't want to wait but regrets, he may upload a photo and check "allow to do warnings" option. It allows him to end the registration and activate an account. In this case, everybody viewing his photo sees the link "I think it's bad" and, clicking on it, can also send a message explaining why. In this case the user can change a photo but everybody who has already viewed it and moved the user to trash do not view it again after the photo changes. The plus point of this case is in saving the time but on the other hand, the user looses some matches. By the way, the user can choose the system to activate his account automatically and stop asking for advice if enough people think that the picture is good (in the 1st case). In the 2nd case, the user can also choose the system to stop allowing people to do warnings when many people do not click the link "I think the picture's bad", and to make a reminding alert when too many people do. 5.B. Everything is the same with the description the user entered. 6. The user can also give advices to others if he wants. There should be an item "Help advising others" where the user would be able to choose to view either men's or women's photos or men's or women's profiles. It can also help to decide if his profile is well done and to study the usual mistakes. ============================================================================= ============================================================================= #000002: Creating a personal Web page. ================================ Actions: 1. Changing the statuses of the pages. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Web pages can be public or private. Every pseudo can have no pages. In doesn't forbid the account to be activated but it forbids the user to contact with his matches. His account is blocked until the personal page is created. Pseudos can also have one public page. It can be viewed by everybody. The pseudo can have as many private pages as he wants. They can be viewed only by those people who have received the "S" or "S+" status from the user (read below about the statuses). The user can also edit permissions by hand. For example, he can disallow somebody selected by him to view some of his private pages or otherwise allow some not already selected people to view ones. ============================================================================= ============================================================================= #000003: Review and select new matches ("U" folder). ================================ 1. Choose parameters to display in the list of matches. 2. View the list of matches. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Here the user chooses the columns of the table of matches to be displayed. There must be some constant initial settings. 2. The list of matches the system found suitable for you. The user chooses (checks) the people who he thinks would maybe be interesting for him. Technically, in each pair of people {x,y} that the automatic selection had found as a possible match, there are two parameters: the status of x for y (that y chose to give to x), and the status of y for x. The following statuses exist: - unlisted (N) - unreviewed (U) - trashed (T) - selected (S) - selected+ (S+) Unlisted: those matches which do not correspond to the search criteria. All other matches have an "U" status from the very beginning. After this step, the user checks matches he thinks he might be interested in page by page, so that the listed matches become either trashed ("T") or selected ("S"). The user views each of the listed matches in the following way: two pop-ups are shown. One of them displays information about some number of the currently viewed matches (the user views them and decides whether to select or not), the he finally clicks "next". Then another pop-up becomes active. The idea is to save time: the first pop-up is loaded while the second one is viewed and vise versa. When the user clicks next, another pop-up containing already loaded information about the next matches becomes active. The number of shown matches can be changed together with selecting the parameters to show. The default value is 10. ============================================================================= ============================================================================= #000004: Statuses of matches. ================================ When the user first sends his profile, he doesn't access yet to the others' profiles so they are unlisted (N) for him, but he becomes unreviewed (U) for all those the computers find he matches with. New matches, contains without visible distinction, except that in fact, it is displayed in the following order of priority: U/S+; U/S; U/N; U/U* For every page of the list of the new matches the user views, they will all change their status for either S or T according to whether the user selects them or not, when he clicks to review his next page of matches. * We will implement the U/U status later. ============================================================================= ============================================================================= #000005: Select more closely. ================================ In this folder are listed the matches with statuses S/U and S+/U. It means that the user has already chosen these people with S or S+, but they haven't yet. Well, the user may either move someone to trash or update S status for S+ to possibly help starting contacting this match a bit earlier. This list can also display the matches which are blocked because of not having the personal web page. ============================================================================= ============================================================================= #000006: List of twofold selected matches. ================================ In this folder are listed the matches which have been chosen as S or S+ by the user and have also chose the user as S or S+. ============================================================================= ============================================================================= #000007: Viewing the info pages of matches. ================================ The user must be able to do the following actions: 1. View the public web page. 2. Invite the match to the own private web pages. 3. View the user's second (private) page, if he is invited to. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By the way, the user is to be able to change matches' statuses everywhere they appear between T, S, and S+. ============================================================================= |
|||
| Ven 19 novembre 2004 |
=============================================================================> #000001: Registration ================================ Actions: 1. The user enters his common parameters only once to create the dating account. 2. The user chooses criteria to search for other users. 3. The user enters any other information describing him. 4. Upload a photo. 5. Ask for advice. 6. Help advising others. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> 1,2. There is some set of searching criteria. The user is first asked to enter his corresponding parameters (1) and then asked to choose criteria by which the system should search for matches (2). The user has an ability to change his parameters, but he is recommended not to do it. He can also change his search criteria. From a technical point of view, changing either personal parameters or criteria of search is rather problematic as these actions cause all matches to be checked once more and each time it takes a lot of time for the system to re-check the matches. So the user must be reminded to be very accurate while filling the fields. 4. There can be some constant limitations (file size, dimensions). The system should check them before accepting the picture. 5.A. If the user is not sure whether the picture is suitable, he may check "ask for advices" option and let others to advise him. In this case, others see links "I think the picture is/isn't ok" and click on them and leave messages explaining why, if they wish. Then the user sees the statistics and sent messages. So before activating the account, the user waits for others' opinions. But if he doesn't want to wait but regrets, he may upload a photo and check "allow to do warnings" option. It allows him to end the registration and activate an account. In this case, everybody viewing his photo sees the link "I think it's bad" and, clicking on it, can also send a message explaining why. In this case the user can change a photo but everybody who has already viewed it and moved the user to trash do not view it again after the photo changes. The plus point of this case is in saving the time but on the other hand, the user looses some matches. By the way, the user can choose the system to activate his account automatically and stop asking for advice if enough people think that the picture is good (in the 1st case). I would think it is better to never let the activation of account be automatic. In the 2nd case, the user can also choose the system to stop allowing people to do warnings when many people do not click the link "I think the picture's bad" Why not *always* allow people to do warnings ? Just to avoid spam ? Well, it's like any spam: informing the root about it will put spammers in trouble.As I said, the warnings should form a public forum associated to the profile because it is not for private correspondance, and if someone makes a remark, the next one can say: " I agree with x's remark and would add that...". The link to this public forum appears only in the new matches list and (cf below) whereas the list of selected matches links only to the private forum of the match. I think more and more of the necessity to have a special folder for matches in intermediate statuses:- In question because one hesitates or because the photo is not clear - Selected but yet unreviewed by the other - Selected but blocked by the absence of web page of one or the other. |
|||
| Ven 19 novembre 2004 |
=============================================================================> #000002: Creating a personal Web page. > ================================ > Actions: > 1. Changing the statuses of the pages. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> Web pages can be public or private. Every pseudo can have no pages. In > doesn't forbid the account to be activated but it forbids the user to > contact with his matches. His account is blocked until the personal > page is created. Pseudos can also have one public page. It can be > viewed by everybody. The pseudo can have as many private pages as he > wants. They can be viewed only by those people who have received the > "S" or "S+" status from the user (read below about the statuses). The > user can also edit permissions by hand. For example, he can disallow > somebody selected by him to view some of his private pages or otherwise > allow some not already selected people to view ones. > ============================================================================= Don't forget it should be included in the context of Frozen Team's work of personal web pages whose use is general and not specifically for dating. By the way, I don't understand why they still sent me no news of their work though I recalled them that I was expecting news. Pseudos can have as many public pages as they want. In general, there is a system to handle rights to view private pages by editing rights by the author and by invitation except the invitations will be disabled in the case of dating, and the modification by status of matches will run instead. ============================================================================= > #000003: Review and select new matches ("U" folder). > ================================ > 1. Choose parameters to display in the list of matches. > 2. View the list of matches. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> 1. Here the user chooses the columns of the table of matches to be > displayed. There must be some constant initial settings. 2. The list of > matches the system found suitable for you. The user chooses (checks) > the people who he thinks would maybe be interesting for him. > Technically, in each pair of people {x,y} that the automatic selection > had found as a possible match, there are two parameters: the status of > x for y (that y chose to give to x), and the status of y for x. The > following statuses exist: > - unlisted (N) > - unreviewed (U) > - trashed (T) > - selected (S) > - selected+ (S+) > Unlisted: those matches which do not correspond to the search criteria. So I told you in a recent message what I meant, different from this, but I wonder: as there are many people per server, among 2 users x and x' of a server considering match with user y of another server, one can have y "unlisted" for x but unreviewed or selected for older user x'. Until eventually y selects x. In this case I wonder: should y's server send again y's profile for x although it is already stored for x' ?Anyway, before y selected x, though y's profile was in x's server it was not handled in relation with the account of x, more precisely the computation of possible match between x and y did not happen in x's server because it is done by y's server. |
|||
| Sam 20 novembre 2004 |
-dating: parameters and search criteria independently. - the money system - webmail but it should have been a webmail integrated with the forums. - "webmail and invitations system" (to invite people to open an account to the system) - GLS is working |
|||
| Mar 23 novembre 2004 |
-personal web pages - PWP |
|||
| Mer 24 novembre 2004 |
=============================================================================> #000001: Registration > ================================ > - Place of living (some constant cases are given; only one can be > chosen, of course) > - Purpose of meeting (some constant cases are given; any number > is possible to be chosen) It looks like you still did not read the web page I told you describing the parameters & criteria !!!The place of living is not a good parameter as it can change it time. > 4. There can be some constant limitations (file size, dimensions). The > system should check them before accepting the picture. > 5.A. If the user is not sure whether the picture is suitable, he may > check “ask for advices” option and let others to advise him. In this > case, a new public forum is created. Others see links “I want to give > an advice” and click on them and leave messages explaining why, if they > wish. Then the user sees sent messages. Others can leave messages because they have access to this public forum. > So before activating the account, the user waits for others’ opinions. > But if he doesn’t want to wait but regrets, he may upload a photo and > check “allow to do warnings” option. It allows him to end the > registration and activate an account. In this case, everybody viewing > his photo sees the link “I think it’s bad” I would put the expression "Do warning" instead. > and, clicking on it, can access the attached public forum, therefore > also send a message explaining why. In this case the user can change a > photo but everybody who has already viewed it and moved the user to > trash do not view it again after the photo changes. The plus point of > this case is in saving the time but on the other hand, the user looses > some matches. > By the way, the user can choose the system to turn off the “allow to do > warnings” option when many people pass (do not click) the link “I think > the picture’s bad”, and to make a reminding alert when too many people > do. > 5.B. Everything is the same with the description the user entered. Well, I did not react to this yet but I'm not sure that doing warnings for parameters can make any sense. Parameters are something personal. The only people that can eventually detect something wrong in parameters are people that personnally know this person. I suggest to not develop anything for this in the short term.Or if you have a different view on this problem, ============================================================================= > #000002: Creating a personal Web page. > ================================ > Actions: > 1. Changing the statuses of the pages. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> Web pages can be public or private. Every pseudo can have no pages. In > doesn’t forbid the account to be activated but it forbids the user to > contact with his matches. His account is blocked until the personal > page is created. I would not say "his account" but only "the next steps of the dating operations" are blocked |
|||
| Mer 24 novembre 2004 |
=============================================================================> #000001: Registration > ================================ > Actions: > 1. The user enters his common parameters only once to create the > dating account. > 2. The user chooses criteria to search for other users. > 3. The user enters any other information describing him. > 4. Upload a photo. > 5. Ask for advice. > 6. Help advising others. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> 1,2. There is some set of searching criteria. The user is first asked > to enter his corresponding parameters (1) and then asked to choose > criteria by which the system should search for matches (2). The user > has an ability to change his parameters, but he is recommended not to > do it. He can also change his search criteria. From a technical point > of view, changing either personal parameters or criteria of search is > rather problematic as these actions cause all matches to be checked > once more and each time it takes a lot of time for the system to > re-check the matches. But the user can choose not to do the > re-checking but to apply the new data to the newly received files > only. Anyway, the user must be reminded to be very accurate while > filling the fields. More precisely, to take one's time to do it, check > it and check it again (re-edit it) before activating the file, and even > more before sending it. > There should be next necessary fields: > - Date of birth (three integer values) > - Sex (M/F) > - Place of living (some constant cases are given; only one can be > chosen, of course) > - Purpose of meeting (some constant cases are given; any number > is possible to be chosen) > 4. There can be some constant limitations (file size, dimensions). The > system should check them before accepting the picture. > 5.A. If the user is not sure whether the picture is suitable, he may > check “ask for advices” option and let others to advise him. In this > case, a new public forum is created. Others see links “I want to give > an advice” and click on them and leave messages explaining why, if they > wish. Then the user sees sent messages. > So before activating the account, the user waits for others’ opinions. > But if he doesn’t want to wait but regrets, he may upload a photo and > check “allow to do warnings” option. It allows him to end the > registration and activate an account. In this case, everybody viewing > his photo sees the link “I think it’s bad” and, clicking on it, can > also send a message explaining why. In this case the user can change a > photo but everybody who has already viewed it and moved the user to > trash do not view it again after the photo changes. The plus point of > this case is in saving the time but on the other hand, the user looses > some matches. > By the way, the user can choose the system to turn off the “allow to do > warnings” option when many people pass (do not click) the link “I think > the picture’s bad”, and to make a reminding alert when too many people > do. > 5.B. Everything is the same with the description the user entered. 6. > The user can also give advices to others if he wants. There should be > an item “Help advising others” where the user would be able to > choose to view either men’s or women’s photos or men’s or women’s > profiles. It can also help to decide if his profile is well done and to > study the usual mistakes. > =============================================================================> > =============================================================================> #000002: Creating a personal Web page. > ================================ > Actions: > 1. Changing the statuses of the pages. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> Web pages can be public or private. Every pseudo can have no pages. In > doesn’t forbid the account to be activated but it forbids the user to > contact with his matches. His account is blocked until the personal > page is created. Pseudos can also have as many public pages as they > want. They can be viewed by everybody. Rights for private pages can be > edited, but it is the other programmer’s work. > =============================================================================> > =============================================================================> #000003: Review and select new matches (“U” folder). > ================================ > 1. Choose parameters to display in the list of matches. > 2. View the list of matches. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> 1. Here the user chooses the columns of the table of matches to be > displayed. There must be some constant initial settings. > 2. The list of matches the system found suitable for you. The user > chooses (checks) the people who he thinks would maybe be interesting > for him. > Technically, in each pair of people {x,y} that the automatic selection > had found as a possible match, there are two parameters: the status of > x for y (that y chose to give to x), and the status of y for x. > The following statuses exist: > - unlisted (N) > - unreviewed (U) > - trashed (T) > - selected (S) > - selected+ (S+) > Unlisted: those matches which do not correspond to the search criteria. > All other matches have an “U” status from the very beginning. > After this step, the user checks matches he thinks he might be > interested in page by page, so that the listed matches become either > trashed (“T”) or selected (“S”). > The user views each of the listed matches in the following way: two > pop-ups are shown. One of them displays information about some number > of the currently viewed matches (the user views them and decides > whether to select or not), the he finally clicks “next”. Then another > pop-up becomes active. The idea is to save time: the first pop-up is > loaded while the second one is viewed and vise versa. When the user > clicks next, another pop-up containing already loaded information > about the next matches becomes active. The number of shown matches can > be changed together with selecting the parameters to show. The default > value is 10. > ============================================================================ One detail: in each pop-up, the number of (u) remaining matches is displayed. In case the user is planning to stop reviewing before all U matches are viewed, he can click a checkbox saying "Stop displaying new matches now" before clicking on the "Next" button. So the other pop-up appears for its last review but this one is closed after sending selection data, and then the other pop-up closes also after its selection. =============================================================================> #000006: List of twofold selected matches. > ================================ > In this folder are listed the matches which have been chosen as S or S+ > by the user and have also chose the user as S or S+. Every twofold > selected match, when appears, causes a new private forum to be created. > > ============================================================================ Yes, or more precisely: first, a link to a private forum that need not "exist" as long as it has never been used, but that will be created at first click (or by the validation of the first message ?). If simultaneously both people have this link to create a private forum, one clicks to create the forum at his home server, which sends the signal to the other's server so that when the other clicks to create the forum he does not create another one but is redirected to the forum just created. > =============================================================================> #000007: Viewing the info pages of matches. > ================================ > The user must be able to do the following actions: > 1. View the public web page. > 2. Invite the match to the own private web pages. > 3. View the user’s second (private) page, if he is invited to. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Oh yes but this is concerns the personal web pages part and info page on pseudo independently of dating, and since Frozen Team is working on it let's wait and see the result of their work. |
|||
| Mer 24
novembre 2004 |
============================================================================= #000001: Registration ================================ Actions: 1. The user enters his common parameters only once to create the dating account. 2. The user chooses criteria to search for other users. 3. The user enters any other information describing him. 4. Upload a photo. 5. Ask for advice. 6. Help advising others. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1,2. There is some set of searching criteria. The user is first asked to enter his corresponding parameters (1) and then asked to choose criteria by which the system should search for matches (2). The user has an ability to change his parameters, but he is recommended not to do it. He can also change his search criteria. From a technical point of view, changing either personal parameters or criteria of search is rather problematic as these actions cause all matches to be checked once more and each time it takes a lot of time for the system to re-check the matches. But the user can choose not to do the re-checking but to apply the new data to the newly received files only. Anyway, the user must be reminded to be very accurate while filling the fields. More precisely, to take one's time to do it, check it and check it again (re-edit it) before activating the file, and even more before sending it. There should be next necessary fields: - Date of birth (three integer values) - Sex (M/F) - Place of living (some constant cases are given; only one can be chosen, of course) - Purpose of meeting (some constant cases are given; any number is possible to be chosen) 4. There can be some constant limitations (file size, dimensions). The system should check them before accepting the picture. 5.A. If the user is not sure whether the picture is suitable, he may check “ask for advices” option and let others to advise him. In this case, a new public forum is created. Others see links “I want to give an advice” and click on them and leave messages explaining why, if they wish. Then the user sees sent messages. So before activating the account, the user waits for others’ opinions. But if he doesn’t want to wait but regrets, he may upload a photo and check “allow to do warnings” option. It allows him to end the registration and activate an account. In this case, everybody viewing his photo sees the link “I think it’s bad” and, clicking on it, can also send a message explaining why. In this case the user can change a photo but everybody who has already viewed it and moved the user to trash do not view it again after the photo changes. The plus point of this case is in saving the time but on the other hand, the user looses some matches. By the way, the user can choose the system to turn off the “allow to do warnings” option when many people pass (do not click) the link “I think the picture’s bad”, and to make a reminding alert when too many people do. 5.B. Everything is the same with the description the user entered. 6. The user can also give advices to others if he wants. There should be an item “Help advising others” where the user would be able to choose to view either men’s or women’s photos or men’s or women’s profiles. It can also help to decide if his profile is well done and to study the usual mistakes. ============================================================================= ============================================================================= #000002: Creating a personal Web page. ================================ Actions: 1. Changing the statuses of the pages. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Web pages can be public or private. Every pseudo can have no pages. In doesn’t forbid the account to be activated but it forbids the user to contact with his matches. His account is blocked until the personal page is created. Pseudos can also have as many public pages as they want. They can be viewed by everybody. Rights for private pages can be edited, but it is the other programmer’s work. ============================================================================= ============================================================================= #000003: Review and select new matches (“U” folder). ================================ 1. Choose parameters to display in the list of matches. 2. View the list of matches. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Here the user chooses the columns of the table of matches to be displayed. There must be some constant initial settings. 2. The list of matches the system found suitable for you. The user chooses (checks) the people who he thinks would maybe be interesting for him. Technically, in each pair of people {x,y} that the automatic selection had found as a possible match, there are two parameters: the status of x for y (that y chose to give to x), and the status of y for x. The following statuses exist: - unlisted (N) - unreviewed (U) - trashed (T) - selected (S) - selected+ (S+) Unlisted: those matches which do not correspond to the search criteria. All other matches have an “U” status from the very beginning. After this step, the user checks matches he thinks he might be interested in page by page, so that the listed matches become either trashed (“T”) or selected (“S”). The user views each of the listed matches in the following way: two pop-ups are shown. One of them displays information about some number of the currently viewed matches (the user views them and decides whether to select or not), the he finally clicks “next”. Then another pop-up becomes active. The idea is to save time: the first pop-up is loaded while the second one is viewed and vise versa. When the user clicks next, another pop-up containing already loaded information about the next matches becomes active. The number of shown matches can be changed together with selecting the parameters to show. The default value is 10. ============================================================================= ============================================================================= #000004: Statuses of matches. ================================ When the user first sends his profile, he doesn’t access yet to the others' profiles so they are unlisted (N) for him, but he becomes unreviewed (U) for all those the computers find he matches with. New matches, contains without visible distinction, except that in fact, it is displayed in the following order of priority: U/S+; U/S; U/N; U/U* For every page of the list of the new matches the user views, they will all change their status for either S or T according to whether the user selects them or not, when he clicks to review his next page of matches. * We will implement the U/U status later. ============================================================================= ============================================================================= #000005: Select more closely. ================================ In this folder are listed the matches with statuses S/U and S+/U. It means that the user has already chosen these people with S or S+, but they haven’t yet. Well, the user may either move someone to trash or update S status for S+ to possibly help starting contacting this match a bit earlier. This list can also display the matches which are blocked because of not having the personal web page. ============================================================================= ============================================================================= #000006: List of twofold selected matches. ================================ In this folder are listed the matches which have been chosen as S or S+ by the user and have also chose the user as S or S+. Every twofold selected match, when appears, causes a new private forum to be created. ============================================================================= ============================================================================= #000007: Viewing the info pages of matches. ================================ The user must be able to do the following actions: 1. View the public web page. 2. Invite the match to the own private web pages. 3. View the user’s second (private) page, if he is invited to. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By the way, the user is to be able to change matches’ statuses everywhere they appear between T, S, and S+. ============================================================================= |
|||
|
Mer 24 novembre 2004 |
- how GLS works. - dating system - uniting forum, GLS and webmail . |
|||
| Mar 30
novembre 2004 |
1. All systems can work independently at one host. 2. We will provide separate modules (for forums and for Dating) that will use GLS and make requests to other hosts. |
|||
| Sam 4 décembre 2004 |
- translations system Add new translation, based on selected one (left) Compare (view) selected translations (left & right) Use selected (left) translation Edit selected (left) translation I suggest to unite first and last functions into one (but before doing it, please tell me is there now any other difference between them, than the fact "version" and "description" fields are filled with old values, and the "edit" function is reserved for the author of that translation ?): Edit from left translation while seeing right translation. Left translation can be empty, letting blank spaces to fill. If right translation is not selected, a copy of the left one will be displayed instead. I don't understand why now the version can stay the same after edit. Finally, I think there should be an option to publish or not publish a version to let the others see and use it.For example it can be an irreversible "Publish" function that will fix what a given version number from a given user can mean. Until published, the user can re-edit the version keeping the same number. - money system. But anyway I want to have it done, beta tested, revised and completed even if it stays unused and unpublished.It will be "released" late, at the right time when the rest of the project will be successful and the governments cannot anymore stop it. The money system is illegal ? No problem, we can first release the - political system instead. Indeed, whereas the concept of money system is an "existing concept" subject of regulations by governments (only the particular specifications mine will have is "new"), on the other hand my political system is so new that it will have the chance to enter none of the existing categories, and therefore cannot be prohibitted. |
|||
| Sam 4 décembre 2004 |
- money system: - system of trust declarations. - dating systems : problem of trust: on Internet, people do not say the truth about who they are. - trust declarations between users, complaints, and profiles certifications. There would be basic trust on the one hand, special trusts for other purposes on the other hand.When seeing a user's info page one would see if he is trusted or not, or whether there is a trusted complaint against him. - trustedforum.html |
|||
| Jeu 9 décembre 2004 |
- For the case when the dating web page of A is public, there should be a way for someone B visiting it to directly make a match with status S/U from his dating account (while for example the profile of one has not been sent or the criteria do not match: First, see what the status is, and how much are the penalties of each other. From it, if A did not already trash B during review, possibility to reach S/U status. - Have a parameter "apparent age" (how old do people say I am). - If photo too heavy, possibility to select online a part of the photo using the mouse - The functionality to say a photo is not visible should always exist at first, before possibly be disabled by others (now I'm using a web site and I'm upset to see less than half of the photos are visible, as was already the case at other sites). |
|||
| Dim 12 décembre 2004 |
- conversation starts in
the private forum of a match, then one trashes the other, then it is an unsubscription from the forum; the other can still access the forum in one of his folder but, I don't know how exactly it should be: cannot write anymore in the forum ? - one's parameters can be known by the other but not one's criteria, so what to do with parts of the file that are neither parameters nor criteria, like the part : "looking for" (giving numbers of penalties for each possibility) : I think the computer should compute for each possibility the sum of both numbers of penalties, then select the possibilities where this number is no more than 10 plus the minimum over all possibilities, and display for each user the penalty numbers for each of these possibilities. |
|||
| Jeu 16 décembre 2004 |
- GLS Documentation. - Using GLS: To make GLS work correctly programmers must include a ‘gls/index.php?function=checkLocalLogin’ URL in every page which is accessed directly by links navigation. I.e. in WebDev’s forums everything is accessed through index.php with some parameters, so GLS must be included only in index.php. - Bookmarks: To access bookmarks page programmers must give a link to a ‘gls/pages/bookmarks.php’. That’s it :-). This is a latest addition I’ve made. This page will bring user to a bookmarks page from where he can navigate any where using his bookmarks, or add/delete bookmarks. I’ve fixed trouble in addition of doubled bookmark when clicking ‘Back’ button after addition. - Functions and stuff: You said that there is a need to make some additional functions (in future) for maybe later use. To add a new function programmer must do the following:Add a file named <function_name>.func.php into a ‘gls/libs’ folder. Write some code there Access to this function is made by: a. Direct access to a ‘gls/index.php?function=<function_name>&[some_parameters]’.b. Inclusion of link specified above using include or include_once PHP statements.c. Getting the contents of the function using file_get_contents(link_to_a_function) or using curl module. What do we need: GLS MUST be in the folder called ‘gls’ in the rood folder of every host which is using gls.Smarty template engine must be in the root folder of the host. m_crypt library must exist on the host; MySQL must be accessible. MySQL access must be configured in ‘gls/libs/dbconfig.php’ file. When logging in a user programmer must: put a uid parameter into a session which is a userId from the database put a pseudo parameter into a session which is a name of the user put a homesite parameter into a session which is a home site of the user (the site where user was registered and where he is logged in) |
|||
| Dim 26 décembre 2004 |
- personal web pages |
|||
| Mar 28 décembre 2004 |
- GLS+forum - dating system. 2) What is the unlisted status? I meant that it did not enter yet one's database (whereas the inverse match can be present in the other's database, that one's database knows this absence from the first one). 4) There was a preposition to create public forum instead of messages about bad foto/details. Will this forums have a direct connection with forum system (or will be separate?). Also where this forum will be displayed?(Among other forums???) Who will be owner(1st admin) of that forum? - possibility of public forums that do not appear in the global list of public forums, but that people can however subscribe to and add to a folder.The owner will be the author of the profile. He will be automatically subscribed to this forum, so it will appear in his main box when there are new messages (uh, did you make the possibility to subscribe to public forums ?). For others (until they subscribe), they can find it only by following the link "comment others'photos" in the dating system, aside the photo (or clicking on the photo). 5) The same questions like in the 4), but about Private forum for messaging of 2 people that selected one another. Where this private forum will be displayed(what box?) For first admin, you can let the first one who writes a message as first admin and let this forum be hosted at his site.I think it would be good to add a folder specific for dating that will automatically contain these private forums once created (and one's public forum above for his profile).Also in the dating part, the list of S/S and more matches should display the photos together with the links to the private forums or creation of these forums (so that you must first go there for starting conversation, then you continue it either by this list or by the dating folder) 6) Common question. One person is registered in the system and has many pseudos. He creates "Dating Account". Is it possible to create just One dating account? Or some dating accounts? (I think this string is not correct) Yes, only one. How we should connect Dating with Accounts and Pseudos? (You know that Personal Web Pages and forums have an attachment with pseudos ) I said that dating is connected with the pseudo author of the dating Personal Web Page but this pseudo is not sent together with profile (only an abstract dating id (with host of course) is sent with profile), but pseudo is sent only by the S status. Uh, for the public forum of the photo I wonder. Maybe use another pseudo ? or let the dating id play the role of pseudo ? 7) What about administrating of the rights for the "private web pages". 8) Will be "trashed" users have an access to the "public web pages" Trashed users have not the link (they have no more the match in their lists), except if they had the chance to bookmark it by other means of course... 9) Some letters ago you said about "files", "activating the files". Activating the file means that the "new matches" list is created and one starts receiving matches there. In other words, that when it is active, any time a profile will be received from the outside (from others that "send" it) it will be compared to this file to possibly enter this matches list. Previously received profiles B will not be compared to this newly active one A, because they will wait for A to be sent to B to be reviewed by B first. 10) >> Why not *always* allow people to do warnings ? Just to avoid spam ? >> Well, it's like any spam: informing the root about it will put >> spammers in trouble...... > We think that if the user is sure that all information is correct then > why we should clutter up with a code. > Probably, he will not look at > it. So we need to inform the user that there is new > messages. This forum to his main box ! 11) What is the sense of creating some "public pages" per pseudo? I don't remember to have asked such a thing: no obligation to create public pages for every pseudo, but every page created must have an author (a pseudo).Or do you ask about the "info page" on a pseudo, with the comment : when there will be the trust system, info on the level of trust to this pseudo or complaints will appear. 12) > handling web pages is other programmers' part. > What features they will handle? Will they create "rights editing" ? > Would be nice to see Personal Web Pages' DataBase structure. I saw their demo (it is at forum.frozenteam.sobig.biz) - system of rights editing > One part from the messaging: >> So I told you in a recent message what I meant, different from this, >> but I wonder: as there are many people per server, among 2 users x and >> x' of a server considering match with user y of another server, one >> can have y "unlisted" for x but unreviewed or selected for older user >> x'. Until eventually y selects x. In this case I wonder: should y's >> server send again y's profile for x although it is already stored for >> x' >> ?Anyway, before y selected x, though y's profile was in x's server it >> was not handled in relation with the account of x, more precisely the >> computation of possible match between x and y did not happen in x's >> server because it is done by y's server. - specialists in the field of DataBase planning, cross-platform systems etc: the traffic between servers. - centralise the distribution of sent profiles to reduce traffic, so that those who send, send only once, and those who receive, receive many at the same time from different hosts. But if they receive several, they will be busy testing their matches at once, which may make the server busy for some seconds, unless of course this process is affected a low priority... |
|||
| Mar 28 décembre 2004 |
-errors in uniting GLS+forum - dating system. 2) What is the unlisted status? 4) There was a preposition to create public forum instead of messages about bad foto/details. Will this forums have a direct connection with forum system (or will be separate?). Also where this forum will be displayed?(Among other forums???) Who will be owner(1st admin) of that forum? 5) The same questions like in the 4), but about Private forum for messaging of 2 people that selected one another. Where this private forum will be displayed(what box?) 6) Common question. One person is registered in the system and has many pseudos. He creates "Dating Account". Is it possible to create just One dating account? Or some dating accounts? (I think this string is not correct) How we should connect Dating with Accounts and Pseudos? (You know that Personal Web Pages and forums have an attachment with pseudos ) 7) What about administrating of the rights for the "private web pages". 8) Will be "trashed" users have an access to the "public web pages" 9) Some letters ago you said about "files", "activating the files". Please explain more precisely. 10) > Why not *always* allow people to do warnings ? Just to avoid spam ? Well, > it's like any spam: informing the root about it will put spammers in > trouble...... - need to inform the user that there is new messages. 11) What is the sense of creating some "public pages" per pseudo? 12) handling web pages is other programmers' part. What features they will handle? Will they create "rights editing" ? Would be nice to see Personal Web Pages' DataBase structure. One part from the messaging: - there are many people per server, among 2 users x and x' of a > server considering match with user y of another server, one can have y > "unlisted" for x but unreviewed or selected for older user x'. Until > eventually y selects x. In this case I wonder: should y's server send > again y's profile for x although it is already stored for x' > ?Anyway, before y selected x, though y's profile was in x's server it was > not handled in relation with the account of x, more precisely the > computation of possible match between x and y did not happen in x's server > because it is done by y's server. - cross-platform systems etc. -traffic between servers. - multihost testing. |
|||
| Ven 7
janvier 2005 |
- forum system (http://forum.belprog.com). - unite the GLS with Forum system. |
|||
| Ven 7 janvier 2005 |
- http://forum.belprog.com - unite the GLS with Forum system. - GLS : ? bookmark to a particular page of a site (a personal web page, a forum...) and not just the root page. |
|||
| Ven 7 janvier 2005 |
- http://forum.belprog.com - absurd "edit forum rights". |
|||
| Ven 7 janvier 2005 |
- forum unified with GLS ? - forum.belprog.com |
|||
| Ven 7 janvier 2005 | - database structure and the code. - optimizations ? - remove "edit forum rights". |
|||
| Sam 8 janvier 2005 |
- forums system: - About Edit forum rights: the invitation table should not be editable, even by admins.There should be * permissions by invitation, that can only increase; someone's inviter is the last one who increased the right* limitations, that can be edited by admin; no limitation can be put to an admin.The status of admin can be lost only by resign and if there exists another admin. The right that one can really use and invite other people to have, is defined to be the smaller between permission and limitation. Well, all this scheme may not be always perfect but it is already good and we will be satisfied with it in the short term. - About folders: I already wrote you at least twice (please find the messages) that the presentation should be revised, to not fill the screen with "move to folder" buttons: have checkboxes to select forums, then specify which operation to do with them at the bottom of the list. Do not display the name of creator there but the name of members (whose who wrote or may write) except oneself if there are not too many, else only amins. - About languages: I told you to revise the list of possible operations on language files. - GLS is now but it should contain in its database the list of peer servers that you will use in your dating system. |
|||
| Sam 8 janvier 2005 |
- having folders contain forums hosted at different places through GLS: it is required for the dating system to work. - dating system - private forum between 2 people, I think letting both be admins is the right way. |
|||
| Mar 11 janvier 2005 |
- integrate webmail and invitations, PWP |
|||
| Mer 12 janvier 2005 |
=============================================================================> #000001: Registration ================================ Actions: 1. The user enters his common parameters only once to create the dating account. 2. The user chooses criteria to search for other users. 3. The user enters any other information describing him. 4. Upload a photo. 5. Advices. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> 1,2. There is some set of searching criteria. The user is first asked to enter his corresponding parameters (1) and then asked to choose criteria by which the system should search for matches (2). The user has an ability to change his parameters, but he is recommended not to do it. He can also change his search criteria. From a technical point of view, changing either personal parameters or criteria of search is rather problematic as these actions cause all matches to be checked once more and each time it takes a lot of time for the system to re-check the matches. But the user can choose not to do the re-checking but to apply the new data to the newly received files only. Anyway, the user must be reminded to be very accurate while filling the fields. More precisely, to take one's time to do it, check it and check it again (re-edit it) before activating the file, and even more before sending it. There should be next necessary fields: - Date of birth (three integer values) - Sex (M/F) Ok for this, but: - Place of living (some constant cases are given; only one can be chosen, of course) NO!!!!!! HOW MANY TIMES SHOULD I REPEAT YOU THE SPECIFICATIONS FOR PARAMETERS AND SEARCH CRITERIA ARE THOSE DESCRIBED ON PART 1 OF http://spoirier.lautre.net/forum/dating.htm!!!!!! - Purpose of meeting (some constant cases are given; any number is possible to be chosen) NO AGAIN: SEE THE ABOVE LINK !!!!!! 4. There can be some constant limitations (file size, dimensions). The system should check them before accepting the picture. 5.A. When an account is created, a new forum "Photo advices" is automatically created and placed into "Dating forums" folder (a child of "Public forums") No because unlike usual folders, this shows photos; and this "folder" should not be accessed from the list of public forums but from the list of dating operations.And the "dating forums" folder is normally a list of private forums, plus only oneself's photo's public forum. (more later) |
|||
| Mer 12
janvier 2005 |
In this case the user can
change a photo but everybody who has already viewed it and moved the user to trash do not view it again after the photo changes. The plus point of this case is in saving the time but on the other hand, the user looses some matches. Now I think there should be another status "don't know" where it is not selected but not trashed either and it can be reviewed again in the special folder for blocked matches and S/U status. > 5.B. Everything is the > same with the description the user entered. A public forum called > "Common advices" is created. I told you I'm not sure this has a point. Can you see it ? > Actions: > 1. Changing the statuses of the pages. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> Web pages can be public or private. Every pseudo can have no pages. In > doesn't forbid the account to be activated but it forbids the user to > contact with his matches. The next steps of the dating operations are > blocked until the personal page is created. Pseudos can also have as > many public pages as they want. They can be viewed by everybody. Rights > for private pages can be edited, but it is the other programmer's work. > It has to be said that the dating account is strongly connected with > the pseudo. So the user can have no more dating accounts than the > number of pseudos he has. No, the user has only one dating account, related to one pseudo. |
|||
| Mer 12 janvier 2005 |
> 1. Common things: > a. Integration to forums > b. Developing DB > 2. Registration: > a. Entering account information page > b. Managing photos page The upload of photos PWP part. Here you just need to include one URL of the photo in the file and this URL will be entered as such in the "img src" of the matches lists.> c. Creating special public forums page > 3. Integrating Personal Web Pages. This step can be passed if > necessary. 4. DB developing: > a. Creating dating folders tables > b. Creating matches statuses tables (a. and b. repeat the same information ? in different tables) > c. Developing search system Yes it's a big part, computation of totals of penalties for each of both people and common penalties. > 5. "U" folder page > 6. "T", "S", "S+" folders pages No: one folder "T", one folder "special or blocked or waiting (S/U) ", one folder "S or S+" > 7. Twofold selected matches: > a. Managing matches page > b. Creating private forums > 8. Solving some security problems > 9. Testing, fixing bugs > 10. Integrating with GLS, solving multi-host problems ok ------- |
|||
| Mer 12
janvier 2005 |
============================================================================= #000001: Registration ================================ Actions: 1. The user enters his common parameters only once to create the dating account. 2. The user chooses criteria to search for other users. 3. The user enters any other information describing him. 4. Upload a photo. 5. Advices. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1,2. There is some set of searching criteria. The user is first asked to enter his corresponding parameters (1) and then asked to choose criteria by which the system should search for matches (2). The user has an ability to change his parameters, but he is recommended not to do it. He can also change his search criteria. From a technical point of view, changing either personal parameters or criteria of search is rather problematic as these actions cause all matches to be checked once more and each time it takes a lot of time for the system to re-check the matches. But the user can choose not to do the re-checking but to apply the new data to the newly received files only. Anyway, the user must be reminded to be very accurate while filling the fields. More precisely, to take one's time to do it, check it and check it again (re-edit it) before activating the file, and even more before sending it. There should be next necessary fields: - Date of birth (three integer values) - Sex (M/F) - Place of living (some constant cases are given; only one can be chosen, of course) - Purpose of meeting (some constant cases are given; any number is possible to be chosen) 4. There can be some constant limitations (file size, dimensions). The system should check them before accepting the picture. 5.A. When an account is created, a new forum "Photo advices" is automatically created and placed into "Dating forums" folder (a child of "Public forums"). Others start to see the link "Give an advice" and click on them and leave messages explaining why, if they wish. The only admin of this forum will be The User. It should be said that this forum is some kind of "private" in the sense that it is stored only in the user's "Dating forums" folder, noone else sees it in his folders. If many people think the photo is bad, they can leave advices. In this case the user can change a photo but everybody who has already viewed it and moved the user to trash do not view it again after the photo changes. The plus point of this case is in saving the time but on the other hand, the user looses some matches. 5.B. Everything is the same with the description the user entered. A public forum called "Common advices" is created. ============================================================================= ============================================================================= #000002: Creating a personal Web page. ================================ Actions: 1. Changing the statuses of the pages. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Web pages can be public or private. Every pseudo can have no pages. In doesn't forbid the account to be activated but it forbids the user to contact with his matches. The next steps of the dating operations are blocked until the personal page is created. Pseudos can also have as many public pages as they want. They can be viewed by everybody. Rights for private pages can be edited, but it is the other programmer's work. It has to be said that the dating account is strongly connected with the pseudo. So the user can have no more dating accounts than the number of pseudos he has. ============================================================================= ============================================================================= #000003: Review and select new matches ("U" folder). ================================ 1. Choose parameters to display in the list of matches. 2. View the list of matches. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Here the user chooses the columns of the table of matches to be displayed. There must be some constant initial settings. 2. The list of matches the system found suitable for you. The user chooses (checks) the people who he thinks would maybe be interesting for him. Technically, in each pair of people {x,y} that the automatic selection had found as a possible match, there are two parameters: the status of x for y (that y chose to give to x), and the status of y for x. The following statuses exist: - unlisted (N) - unreviewed (U) - trashed (T) - selected (S) - selected+ (S+) Unlisted: those matches which do not correspond to the search criteria. All other matches have an "U" status from the very beginning. After this step, the user checks matches he thinks he might be interested in page by page, so that the listed matches become either trashed ("T") or selected ("S"). The user views each of the listed matches in the following way: two pop-ups are shown. One of them displays information about some number of the currently viewed matches (the user views them and decides whether to select or not), the he finally clicks "next". Then another pop-up becomes active. The idea is to save time: the first pop-up is loaded while the second one is viewed and vise versa. When the user clicks next, another pop-up containing already loaded information about the next matches becomes active. The number of shown matches can be changed together with selecting the parameters to show. The default value is 10. ============================================================================= ============================================================================= #000004: Statuses of matches. ================================ When the user first sends his profile, he doesn't access yet to the others' profiles so they are unlisted (N) for him, but he becomes unreviewed (U) for all those the computers find he matches with. New matches, contains without visible distinction, except that in fact, it is displayed in the following order of priority: U/S+; U/S; U/N; U/U* For every page of the list of the new matches the user views, they will all change their status for either S or T according to whether the user selects them or not, when he clicks to review his next page of matches. * We will implement the U/U status later. ============================================================================= ============================================================================= #000005: Select more closely. ================================ In this folder are listed the matches with statuses S/U and S+/U. It means that the user has already chosen these people with S or S+, but they haven't yet. Well, the user may either move someone to trash or update S status for S+ to possibly help starting contacting this match a bit earlier. This list can also display the matches which are blocked because of not having the personal web page. ============================================================================= ============================================================================= #000006: List of twofold selected matches. ================================ In this folder are listed the matches which have been chosen as S or S+ by the user and have also chose the user as S or S+. Every twofold selected match, when appears, causes a new private forum to be created. ============================================================================= ============================================================================= #000007: Viewing the info pages of matches. ================================ The user must be able to do the following actions: 1. View the public web page. 2. Invite the match to the own private web pages. 3. View the user's second (private) page, if he is invited to. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By the way, the user is to be able to change matches' statuses everywhere they appear between T, S, and S+. ============================================================================= ------- Time Shedule.doc Work scheduling. 1. Common things: a. Integration to forums b. Developing DB 2. Registration: a. Entering account information page b. Managing photos page c. Creating special public forums page 3. Integrating Personal Web Pages. This step can be passed if necessary. 4. DB developing: a. Creating dating folders tables b. Creating matches statuses tables c. Developing search system 5. "U" folder page 6. "T", "S", "S+" folders pages 7. Twofold selected matches: a. Managing matches page b. Creating private forums 8. Solving some security problems 9. Testing, fixing bugs 10. Integrating with GLS, solving multi-host problems |
|||
| Jeu 13 janvier 2005 |
=============================================================================> #000001: Registration > ================================ > Actions: > 1. The user enters his common parameters only once to create the > dating account. 2. The user chooses criteria to search for other > users. > 3. The user enters any other information describing him. > 4. Upload a photo. > 5. Advices. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > 1,2. There is some set of searching criteria. The user is first asked > to enter his corresponding parameters (1) and then asked to choose > criteria by which the system should search for matches (2). The user > has an ability to change his parameters, but he is recommended not to > do it. He can also change his search criteria. From a technical point > of view, changing either personal parameters or criteria of search is > rather problematic as these actions cause all matches to be checked > once more and each time it takes a lot of time for the system to > re-check the matches. But the user can choose not to do the re-checking > but to apply the new data to the newly received files only. Anyway, the > user must be reminded to be very accurate while filling the fields. > More precisely, to take one's time to do it, check it and check it > again (re-edit it) before activating the file, and even more before > sending it. There should be next necessary fields: > - Date of birth (three integer values) > - Sex (M/F) > - Place of living (some constant cases are given; only one can be > chosen, of course) - Purpose of meeting (some constant cases are > given; any number is possible to be chosen) 4. There can be some > constant limitations (file size, dimensions). The system should check > them before accepting the picture. 5.A. When an account is created, a > new forum "Photo advices" is automatically created and placed into > "Dating forums" folder (a child of "Public forums"). Others start to > see the link "Give an advice" and click on them and leave messages > explaining why, if they wish. The only admin of this forum will be The > User. It should be said that this forum is some kind of "private" in > the sense that it is stored only in the user's "Dating forums" folder, > noone else sees it in his folders. If many people think the photo is > bad, they can leave advices. > In this case the user can change a photo but everybody who has already > viewed it and moved the user to trash do not view it again after the > photo changes. The plus point of this case is in saving the time but on > the other hand, the user looses some matches. 5.B. Everything is the > same with the description the user entered. A public forum called > "Common advices" is created. > =============================================================================> > =============================================================================> #000002: Creating a personal Web page. > ================================ > Actions: > 1. Changing the statuses of the pages. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Web pages can be public or private. Every pseudo can have no pages. In > doesn't forbid the account to be activated but it forbids the user to > contact with his matches. The next steps of the dating operations are > blocked until the personal page is created. Pseudos can also have as > many public pages as they want. They can be viewed by everybody. Rights > for private pages can be edited, but it is the other programmer's work. > It has to be said that the dating account is strongly connected with > the pseudo. So the user can have no more dating accounts than the > number of pseudos he has. > =============================================================================> > =============================================================================> #000003: Review and select new matches ("U" folder). > ================================ > 1. Choose parameters to display in the list of matches. > 2. View the list of matches. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> 1. Here the user chooses the columns of the table of matches to be > displayed. There must be some constant initial settings. 2. The list of > matches the system found suitable for you. The user chooses (checks) > the people who he thinks would maybe be interesting for him. > Technically, in each pair of people {x,y} that the automatic selection > had found as a possible match, there are two parameters: the status of > x for y (that y chose to give to x), and the status of y for x. The > following statuses exist: > - unlisted (N) > - unreviewed (U) > - trashed (T) > - selected (S) > - selected+ (S+) And as I said, another status "special" between "unreviewed" and "selected", for the case when the photo is not clear and one wants to wait for it to become clear, for example. Passing from "unreviewed" to "special" makes no effect to the other user. It is just a way of delaying the decision to select or trash. So let us call it D for "delayed". > Unlisted: those matches which do not correspond to the search criteria. No: when it does not correspond, there is no status in my sense. Just nonexistence in the matches table (after checking the match, and seeing that it does not correspond, the server does not include it in the user's table).Status "unlisted" is only half a status: If "B's status for A is N", it is no status for A as it means A sent file to B but A's server does not know of the existence of B, it is only a status registered in B's server that knows that B is not known to A. > All other matches have an "U" status from the very beginning. > After this step, the user checks matches he thinks he might be > interested in page by page, so that the listed matches become either > trashed ("T") or selected ("S"). or delayed. > The user views each of the listed > matches in the following way: No, only the unreviewed list, to be quick. The other lists (trash, delayed, selected) are not meant to be reviewed so quickly, so the trick of 2 popups is not useful. > two pop-ups are shown. One of them > displays information about some number of the currently viewed matches > (the user views them and decides whether to select or not), the he > finally clicks "next". Then another pop-up becomes active. The idea is > to save time: the first pop-up is loaded while the second one is viewed > and vise versa. When the user clicks next, another pop-up containing > already loaded information about the next matches becomes active. The > number of shown matches can be changed together with selecting the > parameters to show. The default value is 10. > =============================================================================> > =============================================================================> #000004: Statuses of matches. > ================================ > When the user first sends his profile, he doesn't access yet to the > others' profiles so they are unlisted (N) for him, but he becomes > unreviewed (U) for all those the computers find he matches with. New > matches, contains without visible distinction, except that in fact, it > is displayed in the following order of priority: U/S+; U/S; U/N; U/U* > For every page of the list of the new matches the user views, they will > all change their status for either S or T or D > according to whether the user > selects them or not, when he clicks to review his next page of matches. > * We will implement the U/U status later. > =============================================================================> > =============================================================================> #000005: Select more closely. > ================================ > In this folder are listed the matches with statuses S/U and S+/U. and D/anything and those blocked by absence of PWP. > It > means that the user has already chosen these people with S or S+, but > they haven't yet. Well, the user may either move someone to trash or > update S status for S+ to possibly help starting contacting this match > a bit earlier. This list can also display the matches which are blocked > because of not having the personal web page. > =============================================================================> > =============================================================================> #000006: List of twofold selected matches. > ================================ > In this folder are listed the matches which have been chosen as S or S+ > by the user and have also chose the user as S or S+. Every twofold > selected match, when appears, causes a new private forum to be created. > =============================================================================> > =============================================================================> #000007: Viewing the info pages of matches. > ================================ > The user must be able to do the following actions: > 1. View the public web page. Only from the list of twofold selected matches > 2. Invite the match to the own private web pages. You mean the second one ? This is no explicit operation. The only thing is to choose between S and S+. The status S+ means to give access to the second PWP if exists, else it just means "I love you". > 3. View the user's second (private) page, if he is invited to. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > By the way, the user is to be able to change matches' statuses > everywhere they appear between T, S, and S+. > ============================================================================= - forums to arrange access rights, presentations of folders and folders of forums hosted elsewhere through GLS (the trick of function for translations is less urgent). |
|||
| Jeu 13 janvier 2005 |
Hi. Here is the schedule I want: 1) Correct the forum (presentation of folders, forum rights) and make it work with GLS with folders of forums hosted elsewhere 2) Debug and release your forum 3) Work on parameters and search criteria for dating according to the description on my web page !!! 4) Start implement dating as you said in your schedule, but without connection to GLS nor PWP 5) get back from Frozen Team the forum unified with PWP so that you can make the rest of dating 6) Debug 7) make networking aspect of dating |
|||
| Dim 16 janvier 2005 |
============================================================= #000001: A> Are you ready to learn the other's language (check: 0 or 1 or 2)? A> This would add this quantity to the quality of conversation in a A> language where the other's skill is better than yours, but not A> exceeding the other's skill. A> Example: if two people A and B have respective skills 2 and 3 for a A> given language, and both put "2" for "ready to learn the other's A> language", then their quality of conversation in this language is 3 A> because B cannot teach A to get a better skill than the level 3 he A> already has. What if the user puts "1" for "ready to learn other's language"? How should the system work in this case? ============================================================= ============================================================= #000002: A> Smoker: s= A> 1) No A> 2) A little but I can stop A> 3) A little A> 4) Yes A> Requirement: how many points of penalties for possible values of A> the of the other's s'>s (while zero for the lower s') What if a persons wants to find definitely a smoker? ============================================================= ============================================================= #000003: A> 1) Geographical criteria: make a table with columns: A> Region | badness as a place for first meeting | would have an A> income there if a long-term living (yes/ a little or perhaps /no) | A> badness if other has | a little | won't have an income What if a person considers the place is OK for first meeting but is bad for long-term living? ============================================================= ============================================================= #000004: A> If the person A registered before the person B, then we have the A> following history of matchings between A and B: A> B's status in A's list / A's status in B's list A> A> New1 ...... Not listed Why "Not listed" except for "New1"? When B registers, why doesn't he see A as a match? What's the difference between "old1" and "old2" ("new1" and "new2")? ============================================================= |
|||
| Dim 16 janvier 2005 |
- modifications of the forum that I requested ? - dating sites, for girls : pb many men there are already married and just want to have fun a little. - people mention their situation, but also that parameters are certified by other people, with these certifications based on a trust system according to the logic of trust declaration I had imagined - and the people who make false declaration take the risk, like spammers, to have their account deleted. - dating system - trust system. - complaints system based on forums. |
|||
| Lun 17
janvier 2005 |
=========================================================================================== #000001: One more question about GLS: there is a problem. Every time a logged in user loads a page (goes to some link or refreshes, no matter) except for only the first time he just is logged in, I get a notice: >Notice: A session had already been started - ignoring session_start() >in d:\program files\apache >group\apache\htdocs\smartytry\www.domain2\gls\libs\checkLocalLogin.func.php on line 5 =========================================================================================== =========================================================================================== #000002: Forums: > - About Edit forum rights: the invitation table should not be editable, > even by admins. Please, explain more definitely. > There should be > * permissions by invitation, that can only increase; > someone's inviter is > the last one who increased the right* limitations, that can be > edited by admin; no limitation can be put to an > admin.The status of admin can be lost only by resign and if there exists another > admin. As far as I see, it's ok now. Permissions can be increased only by other invitations (to the higher access level) or eliminated by admins only. No limitations > The right that one can really use and invite other people to have, is > defined to be the smaller between permission and limitation. I can't understand what do you mean saying "limitation". Do you mean blacklisting? Well, concerning public forums: there are no permissions table, blacklisting only. As for private forums, there are no blacklist table, there is a table of permissions (invitations) only. Their functions are in fact similar, but public forums can have only one admin. And the users are by default allowed viewing public forums and disallowed viewing private ones. > Well, all this scheme may not be always perfect but it is already good and > we will be satisfied with it in the short term. =========================================================================================== - updates (availible at http://forum.belprog.com ). In the last version I received from you I notices an extra unneeded folder "templates". This folder had been used by the forum before I added an admin page and renamed it to "templates_root" (and added "templates_admin"), it looks like you just unpacked an archive I sent to the root not having cleaned the root directory. So now I'm sendnig forum with all needed directories and GLS connected. By the way, I also noticed, "smarty" directory repeats twice (for forums and GLS). Updates made to forums: - checkboxes in the left of folders list appeared except for "subscribe/unsubscribe" links and "move to folder..." buttons; - Now in the list of forums we see the list of admins in bold, then - the members (max. 5 pseudos) except for the pseudo of the creator. - In contacts page and info page on a pseudo, links of the private forums we had with this person are now active. |
|||
| Lun 17 janvier 2005 |
============================================================= #000001: A> Are you ready to learn the other's language (check: 0 or 1 or 2)? A> This would add this quantity to the quality of conversation in a A> language where the other's skill is better than yours, but not A> exceeding the other's skill. > A> Example: if two people A and B have respective skills 2 and 3 for a > A> given language, and both put "2" for "ready to learn the other's A> > language", then their quality of conversation in this language is 3 A> > because B cannot teach A to get a better skill than the level 3 he A> > already has. > What if the user puts "1" for "ready to learn other's language"? How > should the system work in this case? > ============================================================= If A puts 1 and B puts 0 then the result is 3. If A puts 0 and B puts 1 then the result is 2. In general the formula is min(max(A's skill,min(B's skill,A's skill+A's readiness)),same exchanging A and B). > > ============================================================= > #000002: > A> Smoker: s= > A> 1) No > A> 2) A little but I can stop > A> 3) A little > A> 4) Yes > A> Requirement: how many points of penalties for possible values of A> > the of the other's s'>s (while zero for the lower s') > What if a persons wants to find definitely a smoker? > ============================================================= Makes no sense as such. Nobody is bothered by someome not smoking. But if someone is smoking, he may be outselected by someone not smoking.However I'm not sure that this formula I wrote is the best one. I'll tell you next time. Or do you have another suggestion on this point ?I have the example of a man who does not like smoke but his wife smokes but she only smokes outside so he is not bothered.We could consider putting penalties to people who do not tolerate smoke. > ============================================================= > #000003: > A> 1) Geographical criteria: make a table with columns: > A> Region | badness as a place for first meeting | would have an > A> income there if a long-term living (yes/ a little or perhaps /no) | > A> badness if other has | a little | won't have an income > What if a person considers the place is OK for first meeting but is bad > for long-term living? > ============================================================= These questions are independent. A common number of penalties is computed for first meeting, minimum over all places; another one is computed for long term living, minimum over all places, that can be at a different place. > ============================================================= > #000004: > A> If the person A registered before the person B, then we have the A> > following history of matchings between A and B: > A> B's status in A's list / A's status in B's list > A> > A> New1 ...... Not listed > > Why "Not listed" except for "New1"? When B registers, why doesn't he > see A as a match? When B sends his file, A can receive it in his matches, and unless he selects it, B never sees it. > What's the difference between "old1" and "old2" ("new1" and "new2")?\ |
|||
| Lun 17 janvier 2005 |
===========================================================================================> #000001: One more question about GLS: > there is a problem. Every time a logged > in user loads a page (goes to some link or refreshes, no matter) > except for only the first time he just is logged in, I get a notice: > >>Notice: A session had already been started - ignoring session_start() >>in d:\program files\apache >>group\apache\htdocs\smartytry\www.domain2\gls\libs\checkLocalLogin.func.php >>on line 5 > =========================================================================================== ===========================================================================================> #000002: Forums: >> - About Edit forum rights: the invitation table should not be >> editable, even by admins. > Please, explain more definitely. The invitations table can be viewed, but it is modified only when someone with a right invites another person up to this right, and it is not reversible. >> There should be >> * permissions by invitation, that can only increase; >> someone's inviter is >> the last one who increased the right* limitations, that can be >> edited by admin; no limitation can be put to an >> admin.The status of admin can be lost only by resign and if there >> exists another admin. > As far as I see, it's ok now. Permissions can be increased only by > other invitations (to the higher access level) or eliminated by admins > only. No limitations How is the elimination by admin ? Just deleting the entry from the table ? I mean it would be interesting to add a kind of blacklisting so that the person cannot be invited anymore unless admin agrees to. >> The right that one can really use and invite other people to have, is >> defined to be the smaller between permission and limitation. > I can't understand what do you mean saying "limitation". Do you mean > blacklisting? Yes. Forbidding to write, or even forbidding to read. > Well, concerning public forums: there are no permissions > table, blacklisting only. As for private forums, there are no > blacklist table, there is a table of permissions (invitations) only. > Their functions are in fact similar, but public forums can have only > one admin. Why ? Well, modifying this is not urgent. > Updates made to forums: > - checkboxes in the left of folders list appeared except for > "subscribe/unsubscribe" links and "move to folder..." buttons; > - Now in the list of forums we see the list of admins in bold, then - > the members (max. 5 pseudos) except for the pseudo of the creator. Why do you make a special case for the creator ???? The only pseudo you should exclude is oneself: because one already knows that one can access the forums that appears in one's folders. > - In > contacts page and info page on a pseudo, links of the private forums we > had with this person are now active. |
|||
| Lun 17 janvier 2005 |
- have folders containing forums hosted elsewhere ?t important use of GLS in the forums system. What has now been made is another way: having access to the full functionality of an account at the remote host. It can be interesting as a way to create pseudos at another host, but it is not fundamental.So we can keep it as an option, but not as a general way of working. What is really needed is give an access to a private forum at a remote host without any other special functionality (not another contacts list,...) I'm wondering about what host should display the info page of a user. I think it is the home site of oneself, to keep the possibility to display the list of forums we have with that remote pseudo, with any of one's pseudos.This obliges the comments to be sent between hosts (the home site requests the comments, gets them and displays them). I don't need you code until all that will be done. Thank you. |
|||
| Mer 19
janvier 2005 |
>> ============================================================= >> #000004: >> A> If the person A registered before the person B, then we have the A> >> following history of matchings between A and B: >> A> B's status in A's list / A's status in B's list >> A> >> A> New1 ...... Not listed >> >> Why "Not listed" except for "New1"? When B registers, why doesn't he >> see A as a match? A> When B sends his file, A can receive it in his matches, and unless he A> selects it, B never sees it. So, when the user B registers he receives no files immediately but starts receiving files of those who registers after him. Meanwhile, when his account activates all the existing users matching him receive his file. If somebody of them (like A) selects B, B also receives his (A's) file. Is that right? >> What's the difference between "old1" and "old2" ("new1" and "new2")?\ A> Forget about this part. It was the first draft before I developed all what A> we already discussed (status...). Thus, we leave all we already discussed (status...) adding calculating badnesses. Performing search, do we need to store values of badnesses in the DB for, for example, showing lists of matches already sorted to users in future or can we forget this value? |
|||
| Mer 19 janvier 2005 |
============================================================= >>> #000004: >>> A> If the person A registered before the person B, then we have the >>> A> following history of matchings between A and B: >>> A> B's status in A's list / A's status in B's list >>> A> >>> A> New1 ...... Not listed >>> >>> Why "Not listed" except for "New1"? When B registers, why doesn't he >>> see A as a match? > > A> When B sends his file, A can receive it in his matches, and unless > he A> selects it, B never sees it. > > So, when the user B registers he receives no files immediately but > starts receiving files of those who registers after him. More precisely, those who send it. > Meanwhile, > when his account IS SENT all the existing users matching him receive > his file. ^^^^^^^ (the file is first activated, then sent if the quantity of matches received per day is reasonable) > If somebody of them (like A) selects B, B also receives > his (A's) file. Is that right? Yes, as already explained in terms of status. > Thus, we leave all we already discussed (status...) adding calculating > badnesses. Performing search, do we need to store values of badnesses > in the DB for, for example, showing lists of matches already sorted to > users in future or can we forget this value? As you guess: we can keep it, for sorting new matches inside each list of those with a given status (U/S+,U/S or U/N). More precisely, in A's list of new matches, I think the order should be the growing order of the sum (B's penalties according to A's criteria + common penalties). |
|||
| Mer 19 janvier 2005 |
- "Edit forum rights" part: is it reserved for the admin ? Is it the same as the invitations table that some can view even if they are not admin except that they cannot change it ? - In public forums, there should be the possibility for an admin to invite another admin to have admin right.And as I said, you should take the system of "edit forum rights" from public forums to apply to private forums, to deny rights to which someone was invited, so that for every user there will be both an invitation by someone, and a possible deniance. - have folders contain forums hosted elsewhere ? - webmail and PWP. |
|||
| Jeu 20
janvier 2005 |
A> Can you explain me how
works your "Edit forum rights" part: is it reserved A> for the admin ? Is it the same as the invitations table that some can view A> even if they are not admin except that they cannot change it ? "Edit forum rights" is a part where admin can view and manage invitations to the forum. He can invite somebody, or delete the invitation, or change the access level, or manage visibility of this table to invited users. He can also invite more admins. Admins can disable other admins to access forum. The creator of the forum is an admin forever. A> In public forums, there should be the possibility for an admin to invite A> another admin to have admin right.And as I said, you should A> take the system of "edit forum rights" from A> public forums to apply to private forums, to deny rights to which someone A> was invited, so that for every user there will be both an invitation by A> someone, and a possible deniance. OK. A> Do you think you can soon manage to have folders containing forums hosted A> elsewhere ? It is what I consider as the most important use of GLS in the A> forums system. To let the system access forums hosted elsewhere I need to have libraries which would perform sending/receiving custom queries between different hosts of the system. As I understand, this part belongs to development of GLS. A> What has now been made is another way: having access to the full A> functionality of an account at the remote host. Do you mean that GLS doesn't support contacting remote hosts? A> It can be interesting as a A> way to create pseudos at another host, but it is not fundamental. A> So we can keep it as an option, but not as a general way A> of working. - blacklisting in private forums -multi-host forums. |
|||
| Ven 21 janvier 2005 |
In public forums, there should be the possibility for an admin to invite another admin to have admin right. And as I said, you should take the system of "edit forum rights" from public forums to apply to private forums, to deny rights to which someone was invited, so that for every user there will be both an invitation by someone, and a possible deniance. > > OK. > > A> Do you think you can soon manage to have folders containing forums > hosted A> elsewhere ? It is what I consider as the most important use > of GLS in the A> forums system. > > To let the system access forums hosted elsewhere I need to have > libraries which would perform sending/receiving custom queries between > different hosts of the system. As I understand, this part belongs to > development of GLS. Is that right? > A> What has now been made is another way: having access to the full A> > functionality of an account at the remote host. > > Do you mean that GLS doesn't support contacting remote hosts? unification of GLS+forum : bookmark goes to a forums site it makes a whole account there. What I had in mind is to lead only to a particular forum, without any registration in a users' database except the invitations table of the forum. - It can be interesting as a way to create pseudos at another host, but it is not fundamental. |
|||
| Mer 26 janvier 2005 |
H forum.frozenteam.sobig.biz forum2.frozenteam.sobig.biz = PWP |
|||
| Mer 26 janvier 2005 |
webmail.frozenteam.sobig.biz |
|||
| Lun 31
janvier 2005 |
This is an updated TZ for the dating system. We've got one more question: >>============================================================================= >>#000006: Viewing the info pages of matches. >>================================ >>The user must be able to do the following actions: >>1. View the public web pages of twofold selected matches, >>2. Invite the match to the own private web pages. > You mean the second one ? This is no explicit operation. The only > thing is to choose between S and S+. The status S+ means to give > access to the second PWP if exists, else it just means "I love you". Q: What if the user has several private web pages and wants some ppl to access not all of them but only some? Q: Can the user invite somebody selected (but not selected+) to his private page? |
|||
| Lun 31
janvier 2005 |
============================================================================= #000001: Registration ================================ Actions: 1. Choose a pseudo. 2. The user enters his parameters and search criteria (badnesses). 3. The user enters any other information describing him. 4. Upload a photo. 5. Advices. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. The user chooses a pseudo under which to create a dating account. The user can have an only dating account. In future he won't have possibility to change this pseudo. Either, he won't have possibility to remove this pseudo unless the dating account is removed. 2. The selection of possible partner will happen by a system of negative points, called penalties. For each possible situation concerning the parameters of the other person, the user will affect a number of penalties from 0 to 40. The computer will consider a person as a possible match so that each can review the other's profile, if the following three conditions are satisfied: - His/her total number of penalties in the user's criteria is lower than 40, - The user's total number of penalties in his/her criteria is lower than 40, - The sum of these two numbers and of the common badness penalties is lower than 70. Therefore, for each question, the user gives the number 0 to the best possibility in his view, and 40 to what he wants to exclude. First, here are the criteria of selection of one by the other that should not exceed 40. - Languages: for each possible language the user is asked to enter the skill in the language: 0: not speaking 1: something 2: a little 3: manage well 4: good 5: very good/native The user defines the badness to each possible quality of conversation (gives a number of penalties for each of the six possible qualities of conversation). This must be a decreasing series of numbers, as a poor quality of conversation (0) has a bigger badness than a good one (5). The common badness for languages is defined as the sum of badnesses that each puts on the quality of conversation for the language where this quality is maximum. The quality of conversation in a language is defined to be the minimum of the skills of both people in this language. - Are you ready to learn the other's language (check: 0 or 1 or 2) ? This would add this quantity to the quality of conversation in a language where the other's skill is better than yours, but not exceeding the other's skill. For each of the following, the user tells which is his situation, and how many penalties for every possible situation of the other: - (Nationality: not sure it is useful) - Smoker: s= 1) No 2) A little but I can stop 3) A little 4) Yes Requirement: how many points of penalties for possible values of the of the other's s'>s (while zero for the lower s') - Gender : M/F/other - drinking habits - Birth year - Marital status - Children already in charge (0,1,several) - Height - Weight - Eyes color (colors should be displayed) - Hair color (idem) - Hair style - Ethnicity - Religion or creed - Education - Income (range) - Handicap : no - a little - yes For each possible hobby or interest, same question: do you like (yes - a little - no) Badness if the other likes - if a little - if no Then, here are common badness criteria: - Geographical criteria: make a table with columns: Region | badness as a place for first meeting | would have an income there if a long-term living (yes/ a little or perhaps /no) | badness if other has | a little | won't have an income - Checkboxes (or active links) in front of divisible regions -> replaces in the table, the line of this region by as many lines as there are subsets of this region. When not divided, it means the same answer for all regions First are displayed the continents: North America - South america - Europa - other western-style regions or islands - Africa - Middle-East - East (ex- soviet union) - China - India Explanation: There are here two different criteria: First, the common badness for first place meeting is defined as the minimum over all geographical areas, of the sum for both people of the badnessed they put for this area. Second, the common badness for long-term living place is defined as the minimum over all geographical areas, of the sum of both badnesses for each other on this area, where the badness of a person A for the other B in an area is the one affected by B to the situation regarding income that A declared in this area. - Type of relationship: for each type of relationship, put the badness: - Holidays: - Correspondence: - Short relationship: - Long relationship : - Marriage: - Want children (zero for your choice, badness for the other) ? - Yes: - No: About changing parameters/criteria: The user is warned to be very careful while filling the fields as when he first sends his information, all the existing users of the system receive his file and won't re-receive it if he performs any changes. So changes will apply only to users who will register after him. (Is this right?) 3. The user enters any other text information describing him. Does he? 4. Upload a photo. There can be some constant limitations (file size, dimensions). The system should check them before accepting the picture. 5. When an account is created, a new forum "Photo & private info advices" is automatically created. Unlike usual ones, this forum shows photos of ppl who post messages. It can be accessed from the list of dating operations and from nowhere else. Others start to see the link "Give an advice" and click on them and leave messages explaining why, if they wish. The only admin of this forum will be The User. ============================================================================= ============================================================================= #000002: Creating a personal Web page. ================================ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Personal Web Pages can be public or private. The page is connected to one of user's pseudos. A pseudo can have any number of personal pages. Public can be viewed by everybody. Rights for private pages are editable. It is a part of the PWP's development. The user can pass the step of creating a page but in this case he won't be able to contact with his matches. ============================================================================= ============================================================================= #000003: Review and select new matches ("U" folder). ================================ 1. Choose parameters to display in the list of matches. 2. View the list of matches. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Here the user chooses the columns of the table of matches to be displayed. There must be some constant initial settings. 2. The list of matches the system found suitable for you. The user chooses (checks) the people who he thinks would maybe be interesting for him. Technically, in each pair of people {x,y} that the automatic selection had found as a possible match, there are two parameters: the status of x for y (that y chose to give to x), and the status of y for x. The following statuses exist: - unlisted (N) - unreviewed (U) - trashed (T) - delayed (D) - selected (S) - selected+ (S+) When one's account is created, his file is sent to other existing users matching one. So one becomes unreviewed ("U") for others. But one doesn't yet receive others' files (unless they select him). Thus, from the very beginning the user receives no files. But one's status for others (those who match him) is unlisted "N". When the user receives some new file, he checks matches he thinks he might be interested in page by page, so that the listed matches become trashed ("T"), selected ("S") or delayed ("D"). The user views the unreviewed list ("U" list) in the following way: two pop-ups are shown. One of them displays information about some number of the currently being viewed matches (the user views them and decides whether to select or not), the he finally clicks "next". Then another pop-up becomes active. The idea is to save time: the first pop-up is loaded while the second one is viewed and vise versa. When the user clicks next, another pop-up containing already loaded information about the next matches becomes active. The number of shown matches can be changed together with selecting the parameters to show. The default value is 10. The matches are displayed in the following order of priority: U/S+; U/S; U/N; U/U*. Matches with the same statuses are showed in the increasing order of the sum (B's penalties according to A's criteria + common penalties). U/S+ and U/S are matches which happen between the users and those who registered before the user, received user's file, reviewed, and selected the user causing their files to be sent to the user; U/N is when the user receives files of recently registered users. * We will implement the U/U status later. ============================================================================= ============================================================================= #000004: Select more closely. ================================ In this folder are listed the matches with statuses S/U and S+/U. (Notice: and D/anything and those blocked by absence of PWP.) It means that the user has already chosen these people with S or S+, but they haven't yet. Well, the user may either move someone to trash or update S status for S+ to possibly help starting contacting this match a bit earlier. This list can also display the matches which are blocked because of not having the personal web page. ============================================================================= ============================================================================= #000005: List of twofold selected matches. ================================ In this folder are listed the matches which have been chosen as S or S+ by the user and have also chose the user as S or S+. Every twofold selected match, when appears, causes a new private forum to be created and placed into "Dating forums" folder (child of "Private forums"). Near and in each forum is shown a photo of a user. In each forum are placed links to user's PWPs. ============================================================================= ============================================================================= #000006: Viewing the info pages of matches. ================================ The user must be able to do the following actions: 1. View the public web pages of twofold selected matches, 2. Invite the match to the own private web pages. >> You mean the second one ? This is no explicit operation. The only thing is to choose between S and S+. The status S+ means to give access to the second PWP if exists, else it just means "I love you". What if the user has several private web pages and wants some ppl to access not all of them but only some? Can the user invite somebody selected (but not selected+) to his private page? 3. View the user's second (private) page, if he is invited to. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ By the way, the user is to be able to change matches' statuses everywhere they appear between T, S, and S+. ============================================================================= |
|||
| Lun 31
janvier 2005 |
Q: Please make more detailed
explanation: >> Others start to see the link "Give an advice" A> which is like two folders (one of men, one of women) Do you mean that two seperated forums are created and when smb clicks the link, he traps into either forum for men or forum for women so that men can't see women's advices and vice versa? A> containing all the A> photos with links to corresponing advice forum, containing all the photos of one person? A> only of people who asked A> for advice (until they deselect this request). So where does the link "Give an advice" lead? Q: During the registration, is the person asked whether he wants advices conserning his picture? Q: As I understand, the person can remove the forum of advices in future if he doesn't need them anymore (deselect this request), is that right? ----- > When sending profile it is tested with and received if > positive by all except those already received and found positive by > criteria (because they are already handled - those received and found > negative can be retested in case the parameters and criteria were > modified). Q: Will matches which were once found negative during the search be recalculated in future in the case of changing parameters or criteria? So when one changes his info/criteria, does this mean re-testing his profile with all already existing matches and sending it to those ones which became positive after (during) re-calculating? ----- |
|||
| Lun 31 janvier 2005 |
- the dating system. =============================================================================>>>#000006: Viewing the info pages of matches. ================================ >>>The user must be able to do the following actions: >>>1. View the public web pages of twofold selected matches, >>>2. Invite the match to the own private web pages. >> You mean the second one ? This is no explicit operation. The only >> thing is to choose between S and S+. The status S+ means to give >> access to the second PWP if exists, else it just means "I love you". > Q: What if the user has several private web pages and wants some ppl to > access not all of them but only some? Then it should be possible but it is not specific to the dating system, but it is a general functionality to the PWP system, that remains to be done. > Q: Can the user invite somebody selected (but not selected+) to his > private page? Well, anyway, all people selected access the first page; and if there is a second one, the way to give access it is normally to make select+ : this status S+ has no other functionality than this possible access to the second page, and the fact of being displayed (once the other selected also), so why not use it ? |
|||
| Lun 31 janvier 2005 |
> Hello, Sylvain. > > =============================================================================> #000001: Registration > ================================ > Actions: > > 1. Choose a pseudo. > 2. The user enters his parameters and search criteria (badnesses). > 3. The user enters any other information describing him. > 4. Upload a photo. > 5. Advices. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> > 1. The user chooses a pseudo under which to create a dating account. > The user can have an only dating account. In future he won't have > possibility to change this pseudo. Either, he won't have possibility to > remove this pseudo unless the dating account is removed. > > 2. The selection of possible partner will happen by a system of > negative points, called penalties. For each possible situation > concerning the parameters of the other person, the user will affect a > number of penalties from 0 to 40. The computer will consider a person > as a possible match so that each can review the other's profile, if the > following three conditions are satisfied: - His/her total number of > penalties in the user's criteria is lower than 40, - The user's total > number of penalties in his/her criteria is lower than 40, - The sum of > these two numbers and of the common badness penalties is lower than 70. > > Therefore, for each question, the user gives the number 0 to the best > possibility in his view, and 40 to what he wants to exclude. > > First, here are the criteria of selection of one by the other that > should not exceed 40. > > - Languages: for each possible language the user is asked to > enter the skill in the language: 0: not speaking > 1: something > 2: a little > 3: manage well > 4: good > 5: very good/native > > The user defines the badness to each possible quality of conversation > (gives a number of penalties for each of the six possible qualities of > conversation). This must be a decreasing series of numbers, as a poor > quality of conversation (0) has a bigger badness than a good one (5). > The common badness for languages is defined as the sum of badnesses > that each puts on the quality of conversation for the language where > this quality is maximum. Well, I'm seeing that I wrote this but in fact there is no need here to have the output to common badness, since the quality of conversation is uniquely defined, as the maximum of the quality of conversation over all languages, and each person attributes a given badness to this quality. Let's not do the smoking now, we'll add it later when we will decide how to do. I had the following idea: Smoking ? yes/no. If yes, what badness if the other dislikes smoke, for: - only smoking little inside - not smoking inside - only smoking little even outside - Stop smoking completely If no, what badness if the other smokes, for him/her: - smoking a little outside - smoking outside - smoking also a little inside - smoking inside The problem is that some people are "trying to quit", which complicates things ! Also, it is not obvious what output to make from computation: common badness or individual badness ? or a mix of both ? next questions later... |
|||
| Lun 31 janvier 2005 |
> About changing parameters/criteria: > The user is warned to be very careful while filling the fields as when > he first sends his information, all the existing users of the system > receive his file and won't re-receive it if he performs any changes. So > changes will apply only to users who will register after him. (Is this > right?) Yes. > 3. The user enters any other text information describing him. Does he? No, that's the role of PWP. > 4. Upload a photo. > There can be some constant limitations (file size, dimensions). The > system should check them before accepting the picture. Yes. > 5. When an account is created, a new forum "Photo & private info > advices" is automatically created. Unlike usual ones, this forum shows > photos of ppl who post messages. ??? No. This shows only the photo of the involved dating account. And it is only to discuss photo. > It can be accessed from the list of > dating operations and from nowhere else. Others start to see the link > "Give an advice" which is like two folders (one of men, one of women) containing all the photos with links to corresponing advice forum, only of people who asked for advice (until they deselect this request). > and click on them and leave messages explaining why, > if they wish. The only admin of this forum will be The User. > > =============================================================================> > =============================================================================> #000002: Creating a personal Web page. > ================================ > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~> Personal Web Pages can be public or private. The page is connected to > one of user's pseudos. A pseudo can have any number of personal pages. > Public can be viewed by everybody. Rights for private pages are > editable. It is a part of the PWP's development. The user can pass the > step of creating a page but in this case he won't be able to contact > with his matches. > ============================================================================= I mean, something where pages only have the functions of: - Module for uploading photos, which gives their URL For edition of the web page: like in a wiki, only the "content" is editable whereas the header remains fixed, which contains the author's pseudo linked to his info page... and other things we will discuss later, and which will be related to GLS. So, the editing of content gives the possibilities of: - having titles (one style is enough) and paragraphs - putting links - including photos (where one types the URL of photo) |
|||
| Lun 31 janvier 2005 |
> When one's account is created, his file is sent to other existing users > matching one. Not immediately. First the dating account is created to start filling and editing parameters... Then when it is ready, one can activate the account (to receive profiles), then send profile. When sending profile it is tested with and received if positive by all except those already received and found positive by criteria (because they are already handled - those received and found negative can be retested in case the parameters and criteria were modified). > So one becomes unreviewed ("U") for others. But one > doesn't yet receive others' files (unless they select him). Thus, from > the very beginning the user receives no files. more precisely, he starts receiving the files that will be sent, when they will, not those which were sent before activation. > But one's status for > others (those who match him) is unlisted "N". ? Unlisted is what the others'servers "think" that their status is for him. |
|||
| Mar 1 février 2005 | > Check the attached .doc-file. > Sorry for the doc but please review that. It has more explained > structure than plain text. If you can't view docs anyway we will > resend plaintext to you. > |
|||
| Mar 1 février 2005 | So: yes, qualities of conversation in languages shouldn’t affect the common badness since there is a way to split it into each one's badnesses (the notion of common badness is just the way not too wrong I found to express problems where I cannot define separately one's badness for the other since it depends on what people choose, so they must find a compromise). But quality of conversation is a common parameter, defined by the complex formula depending on willingness to learn (there is no such thing as "A’s quality of conversation in a language"), and each of both badnesses is defined using it. You should have stricked the "smoking"... -GLS and webmail ? |
|||
| Mar 1 février 2005 |
The last idea of making global public forums including particular photos asking for advice as threads makes "The only admin of this forum will be The User." obsolete. Don't care about admin right, let it be the superuser of the system for example but it is not a significant question in the project. "By the way, what if we’ll separate it into two or three sub-lists: a) S/U, S+/U; b) D/*; c) temporary blocked?" Yes. "The only difference of S+/U status comparing to S/U is in allowing selected+ matches to view private web pages by default." No: it is the difference between (S+/S or S+/S+) and (S/S or S/S+) to view the second web page by default if it exists (while the first is always visible), whereas the difference between and S+/U and S/U is in the priority of display for review (while the web page is not visible). |
|||
| Mar 1 février 2005 |
> Q: Please make more detailed explanation: >>> Others start to see the link "Give an advice" > A> which is like two folders (one of men, one of women) > Do you mean that two seperated forums are created and when smb clicks > the link, he traps into either forum for men or forum for women so that > men can't see women's advices and vice versa? ok so to make a more specific description: Let there be only two such public forums, once and for all (as long as the dating system only works inside one site without GLS).One for photos of men where women post advices, and one conversely. In this forum, there is one thread per profile who asked for advice, and with it only one photo, the main photo of the profile (i.e. not the PWP). In the forum of men's photos, women access by their link "Give an advice", men access by a link aside their option "Ask for advice" which leads them directly to their personal thread.And vice versa. > A> containing all the > A> photos with links to corresponing advice forum, > containing all the photos of one person? I meant the photos of all the people, one per person - now I say: link to the corresponding thread. > Q: During the registration, is the person asked whether he wants > advices conserning his picture? Yes. > Q: As I understand, the person can remove the forum of advices in > future if he doesn't need them anymore (deselect this request), is that > right? Yes. >> When sending profile it is tested with and received if >> positive by all except those already received and found positive by >> criteria (because they are already handled - those received and found >> negative can be retested in case the parameters and criteria were >> modified). > Q: Will matches which were once found negative during the search be > recalculated in future in the case of changing parameters or criteria? Well ok we can consider this, but with a limit in frequency: no more than twice in 4 months for example. I considered doing this exception above because it happens that one may not have put the perfect data at the first try, and the fact of activating profile before sending it is just here to give one a chance to make a last correction before the important action of sending profile. > So when one changes his info/criteria, does this mean re-testing his > profile with all already existing matches and sending it to those ones > which became positive after (during) re-calculating? Yes, one can give the option after modifications (which can be done at any time) to re-send modified profile, but, as I said, with a limited frequency.You need not implement this at first. |
|||
| Mer 2 février 2005 |
- There is work to do for GLS (you know well you need what to send requests between hosts) and bookmarks (to link not only to the root of sites but also to PWP, and relate closely bookmarks with links in PWP) - I also asked about how is the database and way of working of GLS and got no answer. - The webmail should be integrated to the forum and be a webmail and invitations system (to send by email invitation to join the system) - Have groups of PWP with for each group some handling of rights to read and write Moreover I even don't have the code for their PWP editor, |
|||
| Jeu 3
février 2005 |
Q: Will matches which were once
found negative during the search be recalculated in future in the case of changing parameters or criteria? So when one changes his info/criteria, does this mean re-testing his profile with all already existing matches and sending it to those ones which became positive after (during) re-calculating? Q: So, we decided to make a global public forum containing photos of asking for advice people as threads, didn't we? And to put a link to an apprpriate thread near each one's photo on an info page, right? Q: Is there an option "ask for advices" while registration? I mean, has the user a possibility to reject asking for advices frmo the very beginning? The user can uncheck this option in future, can't he? |
|||
| Jeu 3 février 2005 |
Q: Will matches which were once found negative during the search be recalculated in future in the case of changing parameters or criteria? So when one changes his info/criteria, does this mean re-testing his profile with all already existing matches and sending it to those ones which became positive after (during) re-calculating? It should not be automatic, so re-testing can be an available function after modification, but limited in frequency. Q: So, we decided to make a global public forum containing photos of asking for advice people as threads, didn't we? Yes, two forums, one for men's photos, one for women's photos. > And to put a link to an > apprpriate thread near each one's photo on an info page, right? Yes... what info page are you speaking about ? Well, reading again your document I see you make a difference between #000005: List of twofold selected matches. and #000006: Viewing the info pages of matches. I did not pay attention to that. I meant that the links to PWP of each match were present inside the list of twofold selected matches itself. Ok, let there be also all links in the info page of match which is the page displaying all parameters of that profile (whereas the search criteria remain invisible). The link to thread of photo can be on one's own dating account, and in each matches list for each match. But in fact, the only matches list where it is necessary to have this link is the list of delayed matches. > Q: Is there an option "ask for advices" while registration? I mean, has > the user a possibility to reject asking for advices frmo the very > beginning? > The user can uncheck this option in future, can't he? Yes. I'm thinking of one detail: in the decision to ask for advice or not, in fact it is in the absolute not one possibility among 2 but among 3:The thread may exist but not appearing when one looks a the forum (the list threads). So I wonder if we should keep all three possibilities or only 2 and which ones: should the threads of those who don't ask for advice exist while being invisible in the forum, but be only accessible from the delayed matches list ? ---------------------------------------------------------------------------------------------- |
|||
| 7 feb 2005 |
techdesc2.doc | |||
| 7 feb 2005 |
- PWP, GLS and webmail. -Dating System Some notes from programmers: ========================================================================== -What concerns webmail: I wasn't able to start the system yet I pressed "submit" at login.php, I got a lot of notices (see webmail.txt attached) and nothing more. Then I started to receive "No input file specified." message in my browser window (as I remember, it's a message of GLS). Sometimes I just get HTTP 404 error. Possibly, I was mistaken somewhere while importing and setting the DB. - tables (gls_users,users,gls_bookmarks,gls_code_keys,wm_users) which have duplicate fields (with equal names) I can't understand the exact difference between. ==> describe these tables and their fields to help me install the system correctly? - What concerns GLS: in 'gls/libs' folder I see classes which implement (I suppose) the functionality of GLS, but I see only ones which perform logging in, some crypting ones and nothing more. - dating system and finish forums, I need libraries which would implement queries between registered servers and as - Bookmarks didn't work. ========================================================================== -for every set of pages there must be a different set of permissions (a different list of users that can see it, or see and edit it).Also, set allow for invitations or not (one that can see can give right tosee to someone else). - dating system to work, the following features of PWP will be necessary: ---> groups of personal web pages (for example, a group of pages is identifies by the fact it is the pages inside a given folder). ---> For each group, a different set of rights (viewing public / private for a given list of people attached to this group) (writing personal/public/reserved for a set of people). ---> The dating program will handle the list of people that may view the page. --> create editing functions that can be called by other programs. --> The home site will produce (in dating matches lists) direct links to PWP of other sites that make the GLS authentication.So, this is more general than bookmarks to the root of another site: it is bookmark to a PWP; and those bookmarks will be integrated as links in pages from home site that run in their own ways. - Integrate the webmail, making it a "webmail and invitations" system by which email correspondents can register and: * be added to the contacts of the inviter * be recorded as having been invited by that person, so that the site's admin can see it, and see the chain of invitations that leads to anyone - Integrate the PWP with a system of groups of web pages with their rights, and ways to directly link to a page by GLS as I said. - GLS 1) In each server, a list of peer servers with their respective domain names (or URL) and public keys, and as I recently suggested, the nickname of each server, in order to not be slaves of the long domain names that could be found for their DNS. - any user to invite a new server to be a peer server of the network. Until then, to be simple we can just let the admin of each server enter by hand this list of servers with their public keys 2) From this, automatically generate a symmetric key with each peer server to add to the above table 3) Let each user of the server have his own bookmarks list. A first kind of bookmark will be simply to the root of another server of the network. Therefore it makes no sense for the user to enter the URL by hand. He need just select it inside the list of known peer servers, the 1) above.( the pseudo should be selected from the list of existing user's pseudos, and not mascarade as someone else).A second kind of bookmark will be to particularthings in other servers; so there should be a way to identify web pages, forums and threads, where:- Anywhereyou are, you can "copy the address of this page to clipboard", "add this page to bookmarks list" or simply view its address/identity on the top of the window- You can paste the link into a web page, a message of forum, yourbookmarks list. I know forums is not your work but this problem must find a solution one day anyway. - every link from a PWP to a PWP be a link to go anonymously;but on the right of the link, have an icon like a little book to bookmark the link (add to the user's home site bookmarks).When editing a PWP, give the possibility to paste a link from bookmarks, or more precisely (preselecting among bookmarks) the last bookmarked page. - more about GLS In the bookmark list there should be the possibility to modify the pseudo used for every bookmark, inside the list of one's pseudos plus "Anonymous" (to visit publically visible pages).I also think one should include in the transfered info, together with the pseudo, the choice of prefered language for the interface: on top of the PWP one visits there are links to Author - bookmark/unbookmark this page - see my bookmarks - logout and so on as I said (do you remember when I described what I wanted long ago): unless you replace them all by pictures you need to choose the language - anyway it will have other uses, in particular in the future when one makes versions of one's page in different languages. |
|||
| Lun 7 février 2005 |
-GLS - webmail: integrate in your forum; - some panel for creating email accounts ==> independent system that creates itself its email addresses. |
|||
| Lun 7 février 2005 |
Hi. (PWP, GLS and webmail) (system of rigths of PWP): In particular, for every set of pages there must be a different set of permissions (a different list of users that can see it, or see and edit it).Also, set allow for invitations or not (one that can see can give right tosee to someone else). - dating system to work, the following features of PWP will be necessary: Make groups of personal web pages (for example, a group of pages is identifies by the fact it is the pages inside a given folder).For each group, adifferent set of rights (viewing public / private for a given list of people attached to this group) (writing personal/public/reserved for a set of people). Having only the personal writing is OK for now. The dating program will handle the list of people that may view the page. So, create editing functions that can be called by other programs. The home site will produce (in dating matches lists) direct links to PWP of other sites that make the GLS authentication.So, this is more general than bookmarks to the root of another site: it is bookmark to a PWP; and those bookmarks will be integrated as links in pages from home site that run in their own ways. - new version of the forum. - Integrate the webmail, making it a "webmail and invitations" system by which email correspondents can register and: * be added to the contacts of the inviter * be recorded as having been invited by that person, so that the site's admin can see it, and see the chain of invitations that leads to anyone - Integrate the PWP with a system of groups of web pages with their rights, and ways to directly link to a page by GLS as I said. Thank you very much. I will probably come in February (I can't be sure of the exact time now). Subject: What I want with GLS 1) In each server, a list of peer servers with their respective domain names (or URL) and public keys, and as I recently suggested, the nickname of each server, in order to not be slaves of the long domain names that could be found for their DNS. Another time we can develop a way for any user to invite a new server to be a peer server of the network. Until then, to be simple we can just let the admin of each server enter by hand this list of servers with their public keys 2) From this, automatically generate a symmetric key with each peer server to add to the above table 3) Let each user of the server have his own bookmarks list. A first kind of bookmark will be simply to the root of another server of the network. Therefore it makes no sense for the user to enter the URL by hand. He need just select it inside the list of known peer servers, the 1) above.(I also noticedsomething wrong with the user's pseudo used in bookmark: the pseudo should be selected from the list of existing user's pseudos, and not mascarade as someone else).A second kind of bookmark will be to particularthings in other servers; so there should be a way to identify web pages, forums and threads, where:- Anywhereyou are, you can "copy the address of this page to clipboard", "add this page to bookmarks list" or simply view its address/identity on the top of the window- You can paste the link into a web page, a message of forum, yourbookmarks list. I know forums is not your work but this problem must find a solution one day anyway. Hi. To be more specific, I just thought about how for example to do with links in your PWP:Have every link from a PWP to a PWP be a link to go anonymously;but on the right of the link, have an icon like a little book to bookmark the link (add to the user's home site bookmarks).When editing a PWP, give the possibility to paste a link from bookmarks, or more precisely (preselecting among bookmarks) the last bookmarked page. more about GLS In the bookmark list there should be the possibility to modify the pseudo used for every bookmark, inside the list of one's pseudos plus "Anonymous" (to visit publically visible pages).I also think one should include in the transfered info, together with the pseudo, the choice of prefered language for the interface: on top of the PWP one visits there are links to Author - bookmark/unbookmark this page - see my bookmarks - logout and so on as I said (do you remember when I described what I wanted long ago): unless you replace them all by pictures you need to choose the language - anyway it will have other uses, in particular in the future when one makes versions of one's page in different languages. |
|||
| Mar 8 février 2005 |
For each parameter, will be a number of penalties, or of common penalties. Then will be computed the sums of the numbers of penalties over all parameters/criteria, giving 3 total numbers: the total number of A's penalties for B, of B's penalties for A, and of other common penalties. The "ask for advice" is only for photo, so the thread is created when "ask for advice" is chosen, and this question can be set only after photo has been uploaded (or photo URL has been given). The computation of badness of type of relationship and want children is similar as geographical criteria (minimum over all possibilities of the sum of badnesses). "** - I think it would be right because maybe somebody would like to leave a message (advice) having decided to trash the match anyway." Good remark. I read down to #2 included. Please tell me if you made any further correction after those ones, that I should read again. |
|||
| Jeu 10 février 2005 | > #000001. I updated this part according to what you said about > badnesses of relaitionships, about threads of asking for advice forum, > and about penalties and common penalties. > > A> I read down to #2 included. Please tell me if you made any further > A> correction after those ones, that I should read again. > > #000003. > One can change his parameters or search criteria. It doesn’t > automatically cause re-searching new matches among all the existing > users of the system; it only touches detecting whether one matches > users who register after. But one has an option “re-send my profile” to > launch the re-testing his profile and sending it to suitable > matches. This function must be limited in frequency. > > Q: Ask for advice: So, we decided to let three choices exist: > - Ask for advices about his photo, > - Don’t ask for advices but let the users leave corresponding messages > if they wish, - Decline to receive such messages, > Didn't we? OK > Q: In the third case, can such user be set a "D" status? Yes. So, that's OK and you can start implementation. Thank you. Now the next things to discuss will be GLS, (webmail and invitations) and PWP. ---------------------------------------------------------------------------------------------- |
|||
| Jeu 10 février 2005 |
I think we can start with GLS for the first time. Step-by-step Preposition from our side: 1) Discussing every module (ex. GLS, WebMail, Invitaion, PWP etc). 2) Description preparation (like Dating-system spec at this time). 3) Project specification approvement. 4) Object description preparation (for programming). 5) Database planning and normalization. 6) Coding. 7) Testing stage. 8) MileStone. |
|||
| Jeu 10 février 2005 |
http://freelancewebprogramming.com/projectdetails.php?id=13528 [voir copie de cette page tout en bas] (...) Do you mean to let the user browse the page anonymously ? Well, it may depend on the cases: some pages can be public thus browsed anonymously, some other may require authentication. I wonder if it's possible to automatically redirect to the home server to make the authentication but maybe not. Anyway we can do without. For private pages the answer will just be "Error: you are not authentified", and eventually display again what request to type inside the home account to come back to this page. > And this list will be different depending on what site user visits Not sure what you mean. Each user has his own list of bookmarks. Eventually they may be organised in folders (for example displayed like in bookmarks.html) according to the host or not. Propose an example of solution, even if not sophisticated. Let's not too much focus on this question now. > What is the main language for your whole project in global? Is it php or > Java? For now it's php. I heard that in general, different langages can interface well with each other. So it is better to make things so that it can be easily called from other languages. Is it a problem ? Sorry I don't know enough about languages to figure out the problem. I think you understood. > Using this key we can gather information about login, > password, host from which user came, etc In the version to do now, these information will be just those sent by the home site.So your task is to make a program accessible as a kind of function at thehome server that can receive any number of parameters that are all info it wants to send, without any request initiative from the visited site.Later new features could be developed for requests of info but not for the present work. More precisely I spoke about having a list of bookmarks with the said functionalities. In fact, what I expect from you more precisely is not to make the display of that bookmark page but to make a set of elementary functions of authentication and info exchange between sites, not including any particular display, letting open the list of parameters to be transmitted, such that it would be easy to make the said bookmarks pages in php or any language using a call to these functions. You see that in my project there will be a use of these functions in a context of other kinds of displays than the simple list of bookmarks. That is, the display of all forums contained in a "box". For this and for other future contexts of uses, I need to have available the function "Make a link on this piece of text to that page of that site in an authentified way, and transmitting those values for those variables" (although the info of "that page" to go to may be as well included in the parameters transmited to that site). Effectively programming a bookmarks page can be interesting, maybe for being used as such, but also more interestingly as a simple example of a demo of how these functions can be called.So, don't bother to organize the bookmarksinto folders. Just make a very simple program (for example in php) that takes the list of links from a table and displays it simply one above the other using your functions in java or not, but links to request your java program that will do the work. But I wonder how future uses can stay free to program the decision of what info to send, without passing this info in clear in the request from the bookmarks page to the call to one's home page for authentfiied redirection: even if it goes through SSL it is insecure in the sense that the user himself if he is malicious, might trick the data. The data to transmit should never be modifiable directly by the user.Do you have a solution forthis ? An idea would be to have (for each user ??) a mysql table of all links and of the parameters to include, so that a link on the bookmarks page can just keep the incremental number refering the link so the redirection program will just take the data from the database, crypt it if not already done and send it.The two advantages compared to the idea of having crypted requestto other server already included in the bookmarks page are that it makes a less heavy html page and that it keeps track of sessions to make possible the general logout. -- |
|||
| Jeu 10
février 2005 |
#000001. I updated this part according to what you said about badnesses of relaitionships, about threads of asking for advice forum, and about penalties and common penalties. A> I read down to #2 included. Please tell me if you made any further A> correction after those ones, that I should read again. #000003. One can change his parameters or search criteria. It doesn’t automatically cause re-searching new matches among all the existing users of the system; it only touches detecting whether one matches users who register after. But one has an option “re-send my profile” to launch the re-testing his profile and sending it to suitable matches. This function must be limited in frequency. Q: Ask for advice: So, we decided to let three choices exist: - Ask for advices about his photo, - Don’t ask for advices but let the users leave corresponding messages if they wish, - Decline to receive such messages, Didn't we? Q: In the third case, can such user be set a "D" status? |
|||
| Ven 11 février 2005 |
- display of new matches in the new matches folder, how to either select, trash or delay. Trash will be by not doing anything. I think that Select will be by cheching box while Delay will be by clicking on a "?". I'm only wondering what should happen on the display once the "?" has been clicked, and whether it sends a request to the site immediately or only as an info among others in the form. I'm also wondering whether profiles should appear as lines or columns. Appearing by columns would allow for more information to be displayed in the same screen without using the lift. Unless, of course, we have a presentation with 2 columns (2 columns * 5 lines = 10 matches) as ______ | |info1 o |photo|info2 (other photo, other info) ? |_____|info3 (other photos, other info) (other photos, other info) .... (where "o" is the checkbox) |
|||
| Sam 12 février 2005 | [what I suggested before he insisted to make "checklogin" function instead:] > e. find out, is such user logged in or not? we can do this by accessing > to a> database of the reffering host and seing the list of active users. In my idea, this info comes from the fact that the request being first processed by the home server of the user where he is logged in, it checks the loginis still on and includes the date and time of request in the coded info, and theother host decrypting the info checks that the date and time are the present ones. (...) > user login, user password No. The user password must not be known by any other host than the home site of the user, for obvious security reasons: I want a general internet, not the service of a central organisation.There should not be any possibility formalicious sites receiving the visit of a user, to take the control of the account of this user.Moreover, in myproject the chosen pseudo of user is transmitted, not the login. Anyway this can just be part of general parameters. [the symmetric keys] > Soone or later > (better later) they WILL get in ot wrong hands How (sorry I'm not expert in cryptography) ? I would think that each key being between two sites only, they should not be known by other machine.Do you meanthere is a way to analyse the crypted info exchanged to deduce which key is used ?I suppose the answer is no, else, if it is just a matter of timeto find the key, no crypting can resist long enough attacks for decryption (as I heard that pgp encryption is the encryption of a symmetric key plus message crypted using this symmetric key. Do you mean using the same key 1000 times gives the possibility to find the key easier by analysing those crypted data than if is is used only once ? Do you mean decrypting one key is possible but decrypting all 365 keys generated every day of a given year multiplies the calculation time by 365 and thus makes it unreasonable while only decrypting the one day requests is not interesting enough (or cannot be done inside the day so that key broken cannot be used to create fake info ? but if hackers parallelise the work enough I'm afraid this makes not much difference) ?In my idea there is a network of 10,000 independent sites where each user of each site visits different other sites, so every key for a pair of hosts is not so much used and there are many enough such key (about 50,000,000) to make it too difficult for hackers to have a significant impact if they break only a few of those keys. So maybe regularly changing the keys is good but probably not as often as once a day (only before or after use for example). From any centralised idea to its decentralised version there is a simple way : let the home site of each given user serve as his own data center for all his requests. Hello. I think that among the next tasks I have proposed you to do (in parallel or after the present one), the one that would be more logicalfor you to doas it has more connection with the problem you are working on will be the personal web pages. For now, I expect you to undertake the task I gave you, for example in the way I proposed last time,unless you find a better idea but at least you shouldconsider this as a good example ofa flexible solution expressing the way I need things to work from theoutside:Having the list of links (with corresponding info to be sent) in a database table so that any furtherdevelopment of the project can be made by storingin this table for every link the desired parameterstogether with the link, then when the link is clicked,the java program, after checking the session fromcookie, takes the parameter from the database, includes the date and time of request,crypts this and sends the crypted version with the redirection. The other site target of the redirection can be also a java program that takes noticeof which host this redirection comes from, decrypts the request, checksthe date (and maybe user IP ? is it useful ?)and opens a session giving obtainedparameters (including host name) for other programs to process (for example in session variables). Though as I said I don't know much of programming, I suppose this explanation does not leave atoo big mystery of how all the thing can ever be done. Thank you. Hello. Finally I think I would be also interested to find someone more to do the webmail and invitations part in parallel, in order to ensure a quicker release of my project. Would you be interested to do it soon or would you know any other team that may be interested (you can forward to them this description - propose a price and I will see) ? Precisely (the description is on my project page, here is maybe a few more details): - Concerning the webmail fonctionalities itself I'm not looking for anything sophisticated. Just a simple way of working, in a multi-language environment, with sent mails stored. Since my project is under GPL, if I understand well the GPL license, it is acceptable to use for start, a copy of any existing GPL webmail or component of webmail provided that you mention the source. - What is important is to share the login system with the one of my project, and that the webmail function appears as one of the things to access from the menu. - Possibility of several email addresses per user, more precisely addresses given by some of their pseudos - Possibility to send invitation to the system, that is, an URL with randomly generated identifyer where the receiver of the message can register (the registration form already exists). In the description on my site I told about adding a standard invitation message in a desired language. If this trick is not quick to implement, it need not be made in a first version, but just add a bare URL with parameter at the bottom, and rely on the sender to add the useful explanations. - Adding automatically the pseudo of the new user in the list of contacts of the user that invited him (in my project there already is a list of contacts; the problem is to make things work together, mixing emails for the outside and contacts internal to the system). Let the invitations tree between users be recorded in a database. Thank you. From Frozen Team: Hello, Here is what we have discussed about our Global Login System. First I will give you common functions, then - execution logic, then some questions. 1. COMMON PROTOCOL FOR ELEMENTARY FUNCTIONS: 1.1.Function name: authotentificate (not sure if my spelling is right :\) Description: authotentificates user on remote host which is specified in bookmark link. Function is sent to remote host when user clicks bookmark. Params: HomeUserID - identification parameter on home site (can be login or ID in database) TargetLogin - login on remote system where we try to authotentificate (optional) HomeLoginSystemURL - parameter needed for function checkLogin (see checkLogin). 1.2.Function name: logout Description: performs logout on home site. Function is sent to home site. Params: HomeUserID - identification parameter on home site (can be login or ID in database) 1.3.Function name: checkLogin Description: checks if user is logged in at the home site. Function is sent to home site using HomeLoginSystemURL passed with "authotentificate" function. This function refreshes time of user's last activity if this time is less than session's expiration time otherwise it will redirect user to home site login page. Function is sent to home site. Params: HomeUserID - identification parameter on home site (can be login or ID in database) 1.4.Function name: getBookmarkList Description: gets bookmark list from home site in plain html format. Function is sent to home site. Params: HomeUserID - identification parameter on home site (can be login or ID in database) 1.5.Function name: addBookmark Description: Adds bookmark to home site bookmark list. Function is sent to home site. Params: HomeUserID - identification parameter on home site (can be login or ID in database) BookmarkLink - link to the page to bookmark TargetLogin - login to use at site specified in the link of the bookmark(optional) 1.6.Function name: removeBookmark Description: Removes bookmark to home site bookmark list. Function is sent to home site. Params: HomeUserID - identification parameter on home site (can be login or ID in database) BookmarkID - identificator of bookmark (i.e. in database) 1.7.Function name: editBookmark Description: Edits bookmark in home site bookmark list. Function is sent to home site. Params: HomeUserID - identification parameter on home site (can be login or ID in database) BookmarkID - identificator of bookmark (i.e. in database) TargetLogin - login to use at site specified in the link of the bookmark(optional) 2. ACTIVITY LOGICS: Here we will track user from the beginning. Step by step. 2.1.User first came to the network. This is the first time users is in our network. He registers at one of the sites ofour system. He gets access to: first of all - bookmark page, later - webmail, invitation systems, etc. We think that we should have access basic bookmarks list (list of sites of oursystem) that will be accessible for every new user. 2.2.Sooner or later user clicks bookmark. User is redirected to the site bookmark of which he just clicked. Additional information of bookmark link contains only the information of user's home site. Atfirst user is not registered (user has not login) at the site he/she has entered. 2.3.user enters bookmarked site. Our global login system processes this user. It checks the following: IF there is a key specified. If yes than system tries to decode coded informationand sets user's login flags (i.e. flag LOGGED_IN=true in session). If No key isspecified user is passed to local login system which desides what pages to show tounauthorized user. 2.4.User registers at new site. User clicks "Register" links ont this site, local login system registers him/her.That it checks the following: if there exists information sbout user and his/herhome site in, for example, session, than local login system sends EditBookmartcommand to home site with the foolowing params: HomeUserID, BookmarkID, TargetLogin(this is the logn we have entered during registration at the bookmarked host. If wemodify bookmark with this login (as you call it - pseudo) to automatically login wheyou click this bookmark next time). 2.5.Users is browsing through sites using bookmarks. see p. 2.3. 3. QUESTIONS: 3.1. What should we do with not valid request (i.e. if invalid key is specified, ifno key is specified)? 3.2. Is there is a bookmark list associated with some host? Some host we think canhave a little different bookmarks than other. (For example site dedicated to WWIIshould have bookmarks to other sites concerning this thematics, but not gardenerssite). Thank you for specifications. Here are my comments: For each function, you should tell not only "sent to" (i.e. where it is executed) but also "sent by", that is, where does the request come from: is it another program on the same server, or is it a function directly requestedby the user or by another server. 1.1.Function name: authenticate (if I don't mistake) Maybe I should have more insisted: my login system is already a bit more complex thanthe usual ones, in that every user can have several pseudos, and only thehome site of the user should know what pseudos belong to the same login. So, insteadof HomeUserID or TargetLogin it will be pseudo or maybe pseudoID (do you think it is usefulfor the servers to associate to every pseudo a pseudoID that is anumber, to make things run faster ?). In a sense we could say that the home server manages TargetLogins itself, except that it is pseudos that are of universal possible use and recognised by the home server, not only at a fixed remote server. In the user's table of links, the user can configure the data: for each link, under whichof his pseudos he will be authenticated. Something more: in fact I will need not only one list of bookmarks per user but several kinds of links. Well, all could be kept in the same mysql table for each userwith a parameter "type of link" so that each development of the bigproject can choose to handleonly the type of links it is concerned with, while itcould remain possible to display the whole list. (I hesitate between this and having a separate table for each type of link)So, for each user there would be a mysql table of linkswith parameters including"chosen pseudo", "type of link", and for sometimes possibly "title oflink" (text to display under the link)- possibly also one more field to identifythis link in the context of applicationExample: some links would be of type "link to a private forum" (this willbe my firstmain application of this system). See list of table fields for the user'stable offorums in my todo file. Entries (lines) in this table would correspond tobookmarks in the bookmarks list.Or could these two tables be made into one (andseparate from tables of other types of bookmarks) ? HomeLoginSystemURL: maybe you are right, I don't know. My first idea was to suppose that this thing was fixed and stored in the table of other hosts in the database of each host, as a contact address to send any requests to other hosts. Logout: well I don't see well the point: where is this function requested from ?Do you consider that remote servers can request it as asked by users visiting them ?Does it send logout requests to all other host that user connected to ? All of this maybe ? If requested through remote hosts, then the home host must find the user from the pseudo.Or there can be partial logout, where the userlogs out from a remote host that notices the home host about it, CheckLogin: seems not all right, as the last activity of the user can have happened at a remote host. So if you want to makea timeout and let this timeout becounted from last activity of the user on any of the hosts,it maybe a bit complicated to update the last activity time fromeverywhere. An idea would be: let T be the half timeout duration, the same for all sites for a given user.Each host would have recorded its own LATU ("last activitytime update") recorded for each user, and have the following rule: For each activity request at a time t: - If t < LATU+T then the activity passes through without bothering - If LATU+T < t < LATU+2T then new LATU := t and this is new LATU is sent to home server, to let also HSLATU := t (home server LATU)- If t > LATU+2T then acheck login is requested from the home server, and - If t < HSLATU + 2T then do like the second case - If t > HSLATU + 2T then the login is no more valid and a login prompt at home server appears Unless the home server sends itself logout requests to remote hosts as time t= HSLATU+2T ? 1.4. GetBookmarkList: what is this function requested by ? Just to help us debugging the system ? There could be: DisplayBookmarks (in an active way in an html page), or: display bookmarks of a given type. 2.1. Well I would like your work to be integrated into the rest of my project, where new users could freely register(until invitation system restrictsregistration) and user already access some functions (viewing public or private forum, see contacts). Okay for basic bookmarks list, at least to test the system. In fact, public forums hosted elsewhere will be as such. 2.2. "additional information" you mean received by target site ? I said the home site can include info to send to the target site.This list of info is openbut contains at least one pseudo of his the user choosed.In the case of forum it contains also the id of the forum and the invitation id of the user in the forum.(in my todo list I did not include the pseudoin the user's table of forums but I should add this, though it is redundant). 2.3. Remote hosts takes notice what is the home host that the user is coming from (from previous URL or from host ID included in the request), then takes from the database the key associated to this hostand decrypts the information by this key. There is not such a thing as registration in the remote server. You know there exists LINUX distributions to be run based on CD that never accesses thehard drive. In a similar way, you should not be surprised by the idea thatthe remote hosts receives authentified users from elsewhere while never registeringany account for them. (Only in forums tables of users there is mentionthat so-and-sopseudo from that host is allowed to access this forum). So there will be no 2.4 step, at least for now. Later, in a future task, we can consider tolet users register a "real account" in a remote host. If ever we consider the possibility that the user chooses a new pseudo when he is in theremote server, then a request should be sent to the home server toverify that this pseudois not taken by someone else, or else this pseudo is either an existingpseudo of thatuser or it becomes so, namely, pseudo@homeserver becomes a new universalidentificationfor the user if it was not yet so. Let's not bother about it for now. In future developments we can consider the possibility for the user to register another home accountat another host, by which he can create more pseudosthere (thanks to which he isnot anymore publicly known as being from his main home server). This is not for the present work. 2.5. what do you mean ? The normal way of working will be that bookmarks for a userare centralised by the home server. If a user wants to follow a link froma remote server Ato another remote server B in an authentified way, the link on thepage of A is technicallya link to a jsp program on the user's home server (together withinformation) that will addthe bookmark in the bookmarks list of the user and redirect to the next server. So, this link is dynamically generateddepending on where the user visitingthe page is from. 3.1. Don't bother. Maybe just display "Error: user not authentified". 3.2. Not your task for the present work. From Frozen team: Hello! Soory, my fault, I wrote not all things which are needed to fully understand what weare proposing. So. >For each function, you should tell not only "sent to" >(i.e. where it is executed) but also "sent by", that >is, where does the request come from I dont think this is necessary, we can get information from where user came fromrequest itself (it contains reffering URL inside) How our system will work. It MUST be called on every page where authentication of user is needed (or even onall pages, I will explain later why). This could be just an include statement in PHPor Java, but let's leave this question for later. After it is called we check whatcommand came and process it. checkLogin function. this function will be sent to home site from every page user is visiting. We don'tcare what page is user visiting, is it page of the home site or is it page on someremote host. The point is that every time checkLogin if received by home site - lastactivity time of user is updated, so, we can track user activity from every page. logout function. It can also be sent from any page to home site to log user of _on home site_. Imagine the follwing, user clicks LogOut, logout function is sent to home site anduser is deleted from active logged in users list. Next Users tries to navigate tothe page which requires authorization. checkLogin function is sent to home site butit will fail cause user is logged off from home site, and so he appears to be loggedoff from all other sites. GetBookmarkList: It will work as your DisplayBookmarks -) Still some questions: 1. Could you please give us more details of how registration will be comleted ondifferent sites, why some sites do not have registration (if there is no registration how user will get a pseudo on this site?). 2. As I understood there will a great number of so called home servers (where userscan register and this server will become his home site). The question is: what iftoday user comes to site www.site1.com and registers there. Tomorrow he comes towww.site2.com and registers there. So he will have 2 different home sites with 2logins. Maybe it is necessary to merge this logins some how? Or we shouldn't botherabout this? Please give us as detailed info as possible, so we could continue implememtation tohave a demo application ready as soon as possible. Thank you. Best regards, Vadim " >For each function, you should tell not only "sent to" >(i.e. where it is executed) but also "sent by", that >is, where does the request come from I dont think this is necessary, we can get information from where user came fromrequest itself (it contains reffering URL inside) " Maybe I did not explain well what question I was asking :-/ I was asking a technical question, that is, is the function requested by the userdirectly accessing this server that makes the operation, or by another server and in what circumstance. "It MUST be called on every page where authentication of user is needed (or even onall pages, I will explain later why). " Very strange statement, I did not think that way. I considered that for every session in the home server, the user can use his bookmarks butfor every remote host he need to create a session there only once,then the session existsand he can use it for as many pages as he wants. I suppose that making this authentication procedure again is heavier than just using an existing session. This is why I would favor using a session. checkLogin function. "this function will be sent to home site from every page user is visiting" (So, this is a direct request from remote server I suppose ?) Interesting idea but I'm afraid it increases traffic in an unnecessary way. Anyway, for every page it is necessary to check the cookie to verify the session. My idea reduces traffic at the only cost of having a margin of indetermination from 1 to 2 in the timeout.All right, in exchange you save trafficduring the logout operation. Still globally you involve more traffic than me. And the traffic you involve is when user is waiting for access to his pagewhile during logout, homeserver could send all logout request at the same time in background even after displaying "Logout request is noted and processing". "1. Could you please give us more details of how registration will be comleted ondifferent sites, why some sites do not have registration (if there is noregistration how user will get a pseudo on this site?)." Home server of a user = server where user is registered. Remote server of a user = where user can have a session but is not registered.His pseudo there, was first communicated inside the crypted info, then iskept among session variables together with id of home server and other parameters (I know about session variables in PHP). You do not deal with registration in this task (only the webmail and invitation part deals with registration). "2. As I understood there will a great number of so called home servers " Yes, any server can be the home server of some users (for example, about thousands of users each), and there can be thousands of servers, so that there can be many millions of users in the network. No you should not bother now about the case when user is registered at several places.More work on possible further registration may come later, with furtherdevelopments of the project.Now for the present task, the user is supposed to register at only one place, as the systemwe're making is designed to try to make generally useless anyfurther registration.Being registered at one place should be sufficient for all. The rest issessions. "Please give us as detailed info as possible, so we could continue implememtation tohave a demo application ready as soon as possible." I'll try to think about this and write you later if I have more ideas. > Please give us as detailed info as possible, so we could continue > implememtation to have a demo application ready as soon as possible. > Thank you. You're right, I forgot something: There should be a function "Display sessions" at the home server, where the user can see the list of all remote servers where he has sessions open at this time. This list comes as known by the home server at this time, without requiring any further requests(I would say, in the session variablesin the home server but it can be not goodfor the case of a request that comes from a remote server and not from theuser directly.So, instead of session variables it can be in a database or I don't knowwhere). In front of each server name there is a checkbox, and below there is a button "Logout from checked servers". Then, for checked servers, a logout request is sent to those hosts, killing the user's sessions there.Conversely, every time the user is at a remoteserver and logs out from there, the info is sent to the home server to update his list of open sessions. Is all that possible ? Well, sorry, in what I wrote you there was two ideas about logout which were not consistent with each other.One was about timeout, the other was aboutglobal logout. The question is: if timeout is something globally defined and if the list of open sessions is centrally registered, then logically the timeout should be centrally measured and when reached, the logout should be centrally decided and sent towards all existing sessions to close them. For this, it is possible to measure the timeout as you said, by a checklogin request from the remote server to the home server. But this fuction should not serve to check the login but only to update the last activity date (so it can be a "post"). Therefore it can be done just after the remote server answers to the user, and not before, in order to show faster the displayto the user. Only at the time when the timeout is reached, the home server should wake up by itself and warn all the others (from the list of open sessions ofthe user) that the sessions are finished. The problem is: ifever the home server got down, the other session would stay open. So what do you think is best: like this or with some local timeout like I said, or request of answer by remote servers ? One more idea: Hello. I think about the following idea: On top of visited pages there should be a toolbar of links like: - Bookmark this page (when done this link becomes inactive or "bookmarked" or "delete bookmark" -it may have been bookmarked already but the link "bookmarkthis page" still appears becausethis fact is unknown here, it's not a problem) - Open navigation board (in new window or popup, or refresh the existing one) - Close this session In the navigation board in popup (from the home server) there would be access to the list of open sessions(that could be closed as I said), the list ofbookmarks (well I would have to think about the display details as there may be too many bookmarks),a possibilityof general logout or access the entry page of the home account Hello. I can already let you know about the next works to do after multi site login,webmail and invitations. First, there will be the personal web pages, that I already mentionned. For this I think about including in the same toolbar I told you (with "bookmark this page",navigation and logout) an "Author" link, by which it will bepossible to access information on theauthor and send him a message. Then there will be the dating part. It will make use of the personal web pages part.The main work there will be to make the registration of all personalparameters and search criteria (I wrote a listof such parameters but am open to moresuggestions). I have a contact with someone who has already an interesting piece of software that hasan admin board with possibility to create new parameters and searchcriteria in manyformats, using some metadata, without affecting the database (amodification of parameters or of their naturecan be applied over an existing userdatabase !). He is ready to sell it to me. He gave me access to a test implementation of his software (I can forward to you the address). I tried a little, but I did not very well understand this admin board. From this I would add complexity in the search criteria by including a system of points to evaluate the correspondance in a continuous way. I will tell you more specifications when you will be ready. |
|||
| Sam 12 février 2005 |
webmailspecification. Webmail-specification Only registered and authorised users can use webmail. Realization: PHP and MySQL Now we have to receive two main questions: What is webmail? Is it the interface between user and your mail-server? We right? Itincludes receiving, processing and dispatch of mail with the help of your server. Sowe have to create an interface between user and mail-server. In that case we need toknow which kind of software you are going to use, which drive protocols, and preferably your server configuration, situation of mailboxes and other informationon this topic. What is invitation sistem? Could you send us all information about it? What shouldwe add to users’ email? Write us an example of text and link, please. User abilities: - ability to look through mailboxes - ability to compose email - ability to attach file to the composed email - ability to send email to other users and to free adress - multi language interface - ability to read email inside mailboxes - ability to delete email (one or all) - ability to replace email to anoter mailbox (one or all) - ability to answer the received mail - ability to foward mail to another user - ability to use sessions while working with webmail Invitation link and text will be added automatically to all mail composed by user. ------- [my reply:] Sorry for my impatience. It's OK now. About webmail: I think you understand well, but sorry if I'm not sure. To be more sure, I'll express things in my terms. I would like to give people (anyone downloading the code of my project I will release on sourceforge)the means to install this code in relatively any (= in asignificant number of possibilities) hosting service (either shared or dedicated hosting), that offers an SSL connection a domain handling that can serve both for http and for an illimited number of email addresses. Such a person that install the code, let's call him a super-user, that is possibly a user from the viewpoint of the provider if in shared hosting, but admin from the viewpoint of users of the new network. Each such installation would handle many user accounts (so, the super-user that pays for the hosting offers himself accounts for the users of my network).The emails received and sent will be handled by the code of my project.For example, by the sendmail function of php; I don't know how php code or whatever can handle the receiving of emails.I mean that my code would give users thepossibility to send emails, and also to read emails received at pseudo@domain.com, where "pseudo" is a pseudo of the user. Thus I need an installable code by which emails received by the server would be readable by the respective users when they log in to their account.I mean, I don't want to add the constraint to oblige users to log in oncemore somewhere. They are logged in to their account, they access the different functions of the project, and among them, they can display their received mails. Probably such code already exists. I'm commonly user of squirrelmail and imp, and I know they are free softwares.I know it is allowed to take free softwareand integrate it in other free software provided you indicate the source.So the problem is to do the integrationinside a larger project. What I ask is to find one of the cheapest ways of doing this work, even if does not give all the powerful options of imp or squirrelmail.In my project, webmailwill not be the most important way of private communication. Communication between users of the network will generally not happen through webmail but through private forums.Webmail is necessary only to allow forcommunication between members and non-members. "In that case we need to know which kind of software you are going to use, which drive protocols, preferably your server configuration"I beg your pardon ? Idon't know about technical details, I'm not expert in protocols. Please explain the possibilities among which I would choose.And you,do you have an idea on the question ? What system would you want for your convenience if your internet communication was based on such an account in a network with good communication possibilities inside the network but where private communication with the outside of the network would be based on this webmail ? (let's not try to make any mailing list with the outside, but simple one-to-one communication) Your list of function looks good. So it is just as usual webmail. I hope that by being usual it makes easy the programming work of integrating this (as a "copy-paste" of existing programs or something like this). Tell me if it makes this programming really easier this way. If not (that is, if you have to re-do everything in details), then I would consider inventing something.The only thing new here is integrating the system of pseudos. That is, bythe same login one can use different pseudos that are email addresses (for each pseudo the user has the choice in his list of pseudos configuration, whether it is a valid email address or not), and therefore read and write under any of these pseudos.For example (an idea of how to handle this): for each ofhis pseudo that is an email address, it is a different inbox and a different link to the compose message page, which would carry this pseudos.Or: all messages could be mixedin the same boxes whatever the pseudo but it would be nice if the compose message page offers a menu to choose which pseudo to use as sender, while, when replying to a message, the default pseudo (the one selected if we don't modify the selection) to be sender is the one receiver of the message to which we are replying. What would be easiest to program ? I don't understand well your last point: "ability to use sessions while working with webmail"The relation with the inter-site login is this one: webmail isworking only in the home server of the user, not in any secondary session at remote hosts. (I told you: each user has an account at only one server, his home server. The webmail requires an account, so it is at the home server).The session at the home account is the same used by webmail. "Invitation link and text will be added automatically to all mail composed by user." I thought of having a checkbox while composing a message to decide whether to add an invitation or not. Invitation text has the difficulty of possibly choosing another language. Link should be with a code to be used for registration only once (possibly sending the same code for re-inviting the same user if he did not use it ?) and take record of the relation inviter-invited. Thank you. Hello. How are you with your work ? You did not answer concerning symmetric keys: should they be changed regularly and why ?Thanks. [by Frozen:] Hello! Sorry for such a delay - lots of things are going around right now -). What can I say: beta version of GLS is almost ready, but we have some issues todiscuss. Fist of all - I insist that we send "checkLogin" function from every page that needsauthorization. Why? 'Couse of the following reasons: 1. Imagine that user has performed Global log off. Than he clicks on a link in someopened window to a site where he has already been authorized. Without "checkLogin"we will not be able to track users status in that case. 2. "checkLogin" not only checks if user is logged in on home site - it also updatesuser's last active time, so that we keep track that his "global" session is notexpired (by saying "global" I mean that it is all session on all sites that users iscurrently is logged in. If all this sessions expire - global session will expire anduser will have to relogin). 3. So as you can see our "checkLogin" works as synchronization mechanism betweendifferent hosts - thats why it is so important. About traffic gain that troubles you: this function only sends login as a parameter(that is for now, maybe this functionality will be extended later is we need it).Now the cost of traffic that is this function "eats" is so minimal, I can assure you- this is not the point for nervousness. 50-100 bytes more with every request - thata fair price for functionality we are proposing. Another question. For through-site navigation we will use packets in xml format (so called SOAP technology). The reasons for this are: 1. It is easier to implement SOAP messaging with STL than standart request-responsearchitecture. 2. Packets in XML format can be easily coded using our PGP coding (which we willdiscuss a little later). 3. This is simply the only suitable solution we have found - all other technicscannot give us all developing power we require. If you have other propsitions we are looking forward to hear them. Symmetric keys. I think that yes, they should be changed regularly, simple because of the securityreasons. Per day changes - yes I agree this is a little too much - but perhaps oncea month or a week is required. As I mentioned above we will discuss PGP coding whenfirst beta will be ready. What we have for now: Almost complete really extensible login engine, that will not only support PGP, butalmost everything you would like. For now we are not using pseudos - we haventaggreed upon this question with another developers team yet - but changing few linesof code will add this functionality painlessly. As I mentioned in my first letters - we are developing GLS in Java. What languagesare other teams using? About my phone - it is hard to cath me on phone now -( I am moving to other appartment and for I'm almost like on isolated island. I hope things will settledown in a week or so, and we could discuss our problems more precisely. Thanx for your patience, Vadim [my reply:] > Fist of all - I insist that we send "checkLogin" function from every > page that needs authorization. Why? 'Couse of the following reasons: I told you the idea to have something like this, but to post to the home site AFTER replying to the user. And not to check if session is active (of course it is, else a logout request would have already been received) but just to update the last active time. > 1. Imagine that user has performed Global log off. Than he clicks on a > link in some opened window to a site where he has already been > authorized. Without "checkLogin" we will not be able to track users > status in that case. In my idea, if Global log off has been performed then the home site would have sent the request to all sites with an open session to end this session, so when the user clicks, the access is refused.However I don't know if itwould be difficult to implement. Is it ? > 2. "checkLogin" not only checks if user is logged > in on home site - it also updates user's last active time, so that we > keep track that his "global" session is not expired (by saying "global" > I mean that it is all session on all sites that users is currently is > logged in. If all this sessions expire - global session will expire and > user will have to relogin). 3. So as you can see our "checkLogin" works > as synchronization mechanism between different hosts - thats why it is > so important. About traffic gain that troubles you: this function only > sends login as a parameter (that is for now, maybe this functionality > will be extended later is we need it). Now the cost of traffic that is > this function "eats" is so minimal, I can assure you - this is not the > point for nervousness. 50-100 bytes more with every request - that a > fair price for functionality we are proposing. Yes but I'm not considering the waste of machine time, but the waste of user's time when he clicks on a links and he has to wait before display. If the signal is posted after replying to the request to the user, then it is good for the user. Moreover, a signal to post the activity notification is more economical than a request for information that requires the home site to reply. > Another question. > For through-site navigation we will use packets in xml format (so > called SOAP technology). The reasons for this are: 1. It is easier to > implement SOAP messaging with STL than standart request-response > architecture. 2. Packets in XML format can be easily coded using our > PGP coding (which we will discuss a little later). 3. This is simply > the only suitable solution we have found - all other technics cannot > give us all developing power we require. If you have other propsitions > we are looking forward to hear them. No I have not, thank you, I trust your knowledge in this regard. > What we have for now: > Almost complete really extensible login engine, that will not only > support PGP, but almost everything you would like. For now we are not > using pseudos - we havent aggreed upon this question with another > developers team yet - but changing few lines of code will add this > functionality painlessly. All right (...) Hello. Concerning the dating part of the project, I mentioned to the programmer working on profiles that they would be posted between sites. He answered the below comment. I then answered that the networking problems were not his business, I would care about that. More precisely, I think it is enough to ensure that profiles posted are authentified as coming from the network, as machines that would post parasitical profileswould be banned. -------- Hi there, > Question: I wonder if it would be better for privacy that the profiles > posted between sites be crypted usinga symmetric key that will exist in the network as the "Frozen Team" is > implementing. Is it something difficult ? You know i think it's too hard for implementation and it is not necessary. When data have to be posted from one site to another it'll work on sockets technology. And when we start to talk about remoute profiles posting to another sites: send me the list of the sites (where you need to post profiles). Each site have own security system which work to STOP posting by any BOTs (robots) it's really hard work to implement the remote profiles posting . To make it's real i have to learn security system of each site (where we have to submit profile)and implement program posting for each of the site one by one... This algorithms cost much more than $250 ... Regards, Evgeniy [my next reply to frozen:] > Hi, > I'm not quite sure what you mean. You don't want PGP coding now, > instead of it we should just check was a request sent from inside our > network? Checking this is the most important. If it is not a problem (for cpu resources...) to add encryption, then let's do it also. > I havent looked in to details bu I dont think that implementing PGP > coding is such a difficult problem, 'cause all algorithms are already > written. But if you say so... I don't say, I ask questions. Thanks. Anyway it's not any urgent question for now. Regards, Sylvain >As I metioned before GLS written in such manner to be included in ANY >other web>application. Good. >Just imagine: user logs in at home site ant wants to >check hist mail. So he clicks a Bookmark (i.e. "Check new mail") and is >automatically logged in into his Webmail account All right. I did not see this as a really useful possibility (webmail at the home site should be enough) but why not. >For GLS there is no difference at >what site to perform authorization.As far as I understand this would be more >preferred solution for us. What do you think about it? Please give me >your point of>view. You mean it is the same kind of authentication for home users and foreigh users ?Okay, provided that any application at a site has the possibility to knowwhether the user has hishome account here or is coming from elsewhere and where. >Well lets discuss this a bit later when GLS will be finally tested and >approved, ok? Okay. >1. Will there be the only mail server for the whole system or there will >be "one>host-one main server"? In out opinion one (or several, but not >one-to-one) mail>server is more prefferrable. What I want is to let each server have all functions. That is, its own set of home accounts from which users can be authentified everywhere. I told you that what I want to do is a new Internet, with globally billions of users with their home accounts distributed into many servers (thousands of users per server). >2. We would like to know more info about mail server you are using: what >protocol>(POP3, IMAP), information about port which you are using. All in >all we need>complete information about your mail server. I don't have any mail server yet. Hosting is yet to be found or created. It would be good if it was relatively easy for people to install themselves the program on hostings not hard to be found.So you have the choice. If Iunderstood well, IMAP is better as it offers richer possibilities of operations than POP3.So if it does not make things harder, Ithink that we should choose IMAP. Hello. In the connection you make between GLS and webmail, what do you do with pseudos ? The interest I saw with webmail at the home site of the user is that it could handle several pseudos, but at remote site it can handle only one pseudo. (end of relevant messages) |
|||
| Jeu 10
février 2005 |
I think we can start with GLS
for the first time. Step-by-step Preposition from our side: 1) Discussing every module (ex. GLS, WebMail, Invitaion, PWP etc). 2) Description preparation (like Dating-system spec at this time). 3) Project specification approvement. 4) Object description preparation (for programming). 5) Database planning and normalization. 6) Coding. 7) Testing stage. 8) MileStone. |
|||
| Mar 15
février 2005 |
- GLS description and technical
specification. |
|||
| Dim 20
février 2005 |
Global Login System specification #000001: Overview #000002: Data transfer between hosts #000003: Automatic logging in into all the hosts #000004: Bookmarks #000005: Security =========================================================================== #000001: Overview ======================================= Suppose we have a given list of independent web hosts located at different places, each accessible by a different domain. Each host has its own set of user accounts. Common functions of GLS are: 1. Performing data transfer between hosts 2. Providing automatic logging in into all the hosts 3. Providing bookmarks =========================================================================== =========================================================================== #000002: Data transfer between hosts ======================================= 1. Functions description 2. Requests format description ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Functions description The main feature of GLS is to allow different independent hosts connect to each other directly and transfer some data. Each host has a private and a public PGP keys and a list of other hosts' public keys. We do not consider here the problem of how these data will be entered (let us enter them by hand). So, GLS must contain a library (a PHP class) with following functions: a. Get a list of registered hosts b. Send a custom request to the remote host and get the response c. Send a custom request to all the hosts Thus, GLS must also contain the second part, a library which would: a. Receive a request from the remote host b. Perform some pre-defined actions depending on the local destination of the request (described below) c. Return some data (if necessary) 2. Requests format description Request is some data sent from one host to another; the system contains many parts which use these functions, so we should discuss the following things: a. Format We will use RPC and packets in XML format. Some list of methods names will be given later; this list must be extensible. Corresponding functions will also be given. They will get the sent data and return data to be sent back. These functions will work with ordinary PHP variables, so a task of GLS is to form XML packet from the given data and vice versa. b. Security Data will be crypted using the servers' PGP keys; maybe, we should create symmetric keys for each pair of hosts to perform encrypting and decrypting. SSL connections everywhere between hosts are required. =========================================================================== =========================================================================== #000003: Automatic logging in into all the hosts ======================================= What I need is a system by which, once logged in to his own host G, a user can visit any other host H and be authentified there as "user with name xx and parameters yy from host G" (where name and parameters are whatever the host H decides to communicate). So GLS must have a function called every time somebody logs in into the host. It will notify all the registered servers when the user logs in. When the user goes to some other host, the host checks if 1) the session is expired, 2) the user has logged out. By default, the user logs in and out at his "home" host, i.e. the host where he is registered. User's password must be known only by his home host, so he can login at the home host only. But he can logout anywhere, so if he logs out not at the home host, a corresponding request is sent to his home host. Every user's request to the foreign host causes the host to find out at the home host whether the user hasn't logged out or the session time hasn't expired. So every user's request to the foreign host will cause this GLS's function to be called; the request will be accepter depending in the result. So, the following functions must be implemented: a. Local login (sends logging in notification to all the foreign hosts) b. Local logout (called when the user logs out or the session time is expired; sends logout notification to all the foreign hosts) c. Check login (requests the user's home host whether he is still logged in) d. Foreign logout (called when the user logs out at the foreign host) Certainly, for each of these functions two sides must be implemented: sending and receiving ones. =========================================================================== =========================================================================== #000004: Bookmarks ======================================= User's home site will store some set of pages of foreign hosts to visit. The user can manage this list (add/edit/delete bookmarks' names/links). These links must be clickable. A click will open a new explorer window at a place the bookmark leads to. There must be a default set of hosts to visit for a newly registered user. Every time the user registers, this set is added to his bookmarks. Every page of the remote host contains an "Add to my bookmarks" link (visible to the logged in users, of course). When it's clicked, a corresponding request to the home host is sent. So, GLS must provide: a. Bookmarks managing page b. Adding bookmark (sends request to the home site) =========================================================================== =========================================================================== #000005: Security ======================================= For security reasons, symmetric keys must be changed from time to time. A suitable period would maybe be one or two times per month. It would be good to make this process automatic. We'll discuss it later. =========================================================================== |
|||
| Lun 21 février 2005 | You cannot send automatic logging in into all the hosts because the system must be designed to work for a network of hundreds of thousands hosts and: - It would be too much useless traffic - the information of when the user logs in should not be published everywhere this way. So logging in to the home site will not directly produce any request to other sites, but only later when needed. So the "global log in" will exist as something integrated into the bookmarks system, in the following way. In home host of the user (for example in the session variables) there is a list of all sites B where the user has an open session. The user can display this list and decide to end one of these sessions (this will send a logout request from home host to remote host - unless it is a request by the user to the remote host that will inform back the home host ?). I imagine a bookmark from a host A (user's home site) to a host B as the following. It is a link of request to the host A, that (as the user is logged in), if the user has not yet a session in B, A will compute and send back to the user a redirection to the host B containing the crypted list (xml ?) of data: - Pseudo used - Prefered language - Time of request (the present time of clicking the link and producing this data)- What page one wants to access (for example, a personal web page, a forum, a thread in a forum)- (and for later, possibly other info) So, the host B receiving the request from the user will decrypt this data (knowing from the request that it comes from A, and deducing from it what symmetric key to use for decryption) and, if the time is checked to be the present time (with no more than a few seconds difference): Open a session with session variables set: - what host A it is from - Pseudo - Prefered language Then pass the execution the PHP program that controls the page one wants to access (program of forum or PWP), passing to it the detailed id of that wanted page. If the user already has a session in B, the bookmark will only contain the info of what page to access. Concerning bookmarks: there is a "list of bookmarks", but other programs that will need to produce links to remote hosts in an authenticated way will also have their links working this way, calling the GLS system as above |
|||
| Mar 22 février 2005 |
- GLS spec. - idea of sending a signal to all peer sites saying the user has logged in ==> no sense. The problem is not to know whether a user is on the web or not but to identify securely wich data is coming from him and not from elsewhere. - improve security of the system by crypting all links internal to every site. - cannot figure out how a link from a page of the home site directly to a remote host without being first a request to the home site that redirects, would not take the risk to be intercepted by a spy and later reused after SSL decryption (that is hard but as I heard not totally impossible, at least it would take time) unless the condition to be instantly used after creation (with time included in crypted data) is put. In a link to a remote site, the link is not instantly used after it appears on the screen so this condition cannot be put. |
|||
| Ven 25 février 2005 |
- GLS understanding - trustedforum.html updated - forum ==> see the invitation line (invite someone else to the forum). ==> page of list of threads. ==> forum info page ---> add the invitation line somewhere else than inside threads, probably in the "forum info" page. - GLS |
|||
| Sam 26 février 2005 |
php 5 innovations: handling of
XML |
|||
| Dim 27
février 2005 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An updated GLS specification is attahced. q: What should happen when the user clicks "logout" somewhere at a foreign host? I see two cases: 1. Close a session to this host only 2. Close a session to this host and send a request to the user's home host to close all opened sessions. What if ask the user of it every time he clicks the link? --- Now we think of starting implementing dating system as a question of format of requests between servers is generally solved: GLS will contain a library providing functions which get ordinary PHP variables (arrays and so on), encrypt them with a public PGP key, form XML and send to the remote host, and then get an answer and analyse it and return a response. --- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An updated dating specification of Datings is attached. I've changed: #00001.4 (ask for advices) #00003.1 (choose parameters to display in the list of matches) #00005 (list of twofold selected matches). |
|||
| Lun 28
février 2005 |
- dating: the object of the info page is to display the parameters of that person (with the details for common penalties data but not other criteria). - GLS: things should be managed so that user@hostA 's request (crypted info) to access hostB should not be misused by the user as if he was user@hostB accessing remote hostA. For example, to do this, let the key be different from hostA to hostB than from hostB to hostA, or let "hostB" be among info. What do you think of the idea to name hosts by new names for use and display in our network instead of using their domain names ? ---------------------------- http://freelancewebprogramming.com/projectdetails.php?id=13528 ---------------------------- Project Description Suppose we have a given list of independent web hosts located at different places, each accessible by a different domain, and that agree for the following. Suppose each host has a pgp key, and each has the list of public keys of all other hosts. So we need a database to list those keys. We do not consider here the problem of how these data will be entered (let us enter them by hand). Suppose each host handles its own list of user accounts. What I need is a system by which, once logged in to his own host G, a user can visit any other host H and be authentified there as "user with name xx and parameters yy from host G" (where name and parameters are whatever the host H decides to communicate). More precisely, here is how things should happen: In the site H there are a number of possible pages to visit, say, URLs with parameters. Each user will have on his board at G, a list of his own bookmarks to some of these addresses in different sites (some in H, some in other H'...). The first feature I need is that this list of bookmarks can be extended, either by the user copying the address in his account, or, if the host H itself decides to send this bookmark to a given user of G. In particular, when the user of G will be already authentified this way (described below) to a given page in H, he browses H further, finds another page and wants to bookmark it, so clicks "bookmark this page" in H, so H posts to G the request to add this page to the user's bookmarks. The second feature I need is that, when the user clicks on one of these bookmarks that appears on his board at G to a page in some host H, then a new window opens that accesses to that address in H while opening there a session where the user is known by H as user of G with given parameters. Here is a suggestion of a possible procedure to make this: Before all this, at the creation or update of the network, for each pair of hosts a symmetric key is created, to be available for operations like this. The parameters to access H will be crypted by G using this symmetric key. This crypted info will be included in the link to H. I imagine two ways: either the bookmarks page is itself made of such links to other sites, so that the request will be direct; or it is made of links to G that request G to produce this crypted info for H and make the redirection. I imagine the second solution may be preferred for security reasons, to better control the set of sessions of the user at other host from his board at G, and allow for a "general logout" operation at G that requests all other hosts to cancel their sessions (unless with the first solution H posts to G the indication of session). I suppose that SSL connections everywhere are required I imagine that H will know who is G by the fact the previous address is included in the request (is it ?), else the identity of G can be included in the request. I'm not an expert in computers, so I'm not sure the proposed solution is the best. Else, please explain. I wonder if the IP can be taken as an authentication criteria (because if the user has a dynamic IP it may not work). I wonder about the possibility for third parties to spy the crypted info and use it to request authentication instead of the legitimate user. How to avoid this ? Is including the IP and/or the date and time of the request in the crypted info sufficient ? Also, by the possibility to cancel a session in H by a request to G that will forward the logout request to H ? I have wondered if a direct request from G to H can be useful but it seems not so for this authentication operation. This project can be done in any language provided that it is secure, efficient, based on free software, and interfaces well with php pages. |
|||
| Lun 28 février 2005 |
http://spoirier.lautre.net/trustedforum.html - what has been done - what is being done - next features to develop. About crypting: cryptography but I thought I heard that PGP is to handle public identity whereas the best way to communicate between two given hosts is with symmetric key; that even PGP crypting consists of crypting with a symmetric key and PGP crypting the symmetric key, in order to simplify computation. On the other hand, PGP is first necessary to communicate a symmetric key in a secure way. Then, communication by symmetric key has the effect of providing both crypting and sender authentification at the same time. So as soon as you have symmetric keys for each pair of host, isn't it enough to crypt every request with the symmetric key without using PGP anymore ? - Is SSL already working like this, first creating a symmetric key for the session ? Also, I'd like to understand the reason why symmetric keys should be changed regularly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An updated GLS specification is attahced. q: What should happen when the user clicks "logout" somewhere at a foreign host? I see two cases: 1. Close a session to this host only 2. Close a session to this host and send a request to the user's home host to close all opened sessions. What if ask the user of it every time he clicks the link? I think the best is to have not one link but two: a "local logout" link and a "global logout" link. - have icons for these links instead of text. - user documentation in the menus. This documentation would be nothing else than a personal (or collective) web page, and like every web page, it can have links with GLS effect. - The user's bookmarks is personal, therefore every user is free to put there what he likes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - Datings - #00001.4 (ask for advices) OK. This choice to ask for advice or not can be modified later by the user. - #00003.1 (choose parameters to display in the list of matches) OK - #00005 (list of twofold selected matches). OK. So for #6 you should include the links present in #5 “in the dating system”, not only the links to PWP but also to forum. |
|||
| Mer 2 mars 2005 |
- replace redirections I see the following hole, "The link leads directly to the foreign server and has some unique id attached. This id contains something like:" What do you mean by "this id" ? Do you mean it is the list of the following data ? Consider the following scenario. Some user U is logged it to his home site A. Some hacker H does not know about it but bets he may be. H wants to acces site B pretending to be U. For that, he produces the id containing A's global id in the system, id of U which is used and sends this request to B. Then, when B connects to A, then A answers that U is logged in. So this session with H is accepted.U does not pay attention to this, and lets this session at B open. So, adding a random number would be absolutely necessary to make your idea secure. I had already thought about this scenario before, but then thought that the senario I proposed to you would be more simple, not needing a random number, and avoiding the need for a direct connection between servers . (or would you add a connection between servers to make a new symmetric key ?) Your idea will force you to handle a table of random numbers in the database. I think it will not be very simple. Somehow, I tought that the crypted data plays the role of random numbers with no need to make a table of them; and every page displayed to the user would be loaded with many hidden random numbers with your proposition, not with mine. Do you mean that accessing a crypted data by a symmetric key gives a chance to find out what this symmetric key is ? "the user doesn’t access anything that depends on (computed on the base of) the server’s private (and public) keys" ? I meant it would only depend on symmetric key between servers. For the hacking problem of one server: I do not see the difference between getting the private key and controlling the server completely.If a hacker can get the private key, he can also access users'passwords, therefore log in instead of users and access remote servers in normal mode by first loggin in as user.What can he do more to remote hosts with the private key, that he cannot do by simply loggin in as user and using GLS in normal way ? ----------------------------------------------------------- |
|||
| Mer 2 mars 2005 |
a user from host A visits a page in host B and from there sees a link to host C, this link should be a redirection from A to C in order to authenticate the user from A, which B cannot do (or it would be insecure in case B behaves badly). Well, we can still adapt it to your idea by making this redirection be with a random number while other info are transmitted directly from A to C. |
|||
| Mer 2 mars 2005 |
- integration of webmail and GLS. - dating (and simple PWP) |
|||
| Jeu 3 mars 2005 |
- #6 of dating: the object of the info page is to display the parameters (from #1 2.) of that person (with the details for common penalties data but not other criteria). When A views B’s info page, do you mean that only the details which affect common penalties are shown? I wrote "WITH" which means "and also". I mean the parameters of B and also the common penalties parameters but not the details of penalties that B affected to A's parameters. > Why shouldn’t we show number of B’s > penalties for A near each field while A cannot access his number of > penalties for B? That's what I meant > > A> For GLS: things should be managed so that user@hostA 's request > (crypted A> info) to access hostB should not be misused by the user as > if he was A> user@hostB accessing remote hostA.For example, to do this, > let > A> the key be different from hostA to hostB than > A> from hostB to hostA, or let "hostB" be among info. > > What do you mean? In the description I wrote that the ID attached to > the link contains the index of the home server (or its name). How can > the request be misused? Then no problem. I mean that this id is redundant as normally the remote host should already know what is the home host in order to use the right key. I just thought that if we delete all what is redundant, an ambiguity might appear. > > A> So, adding a random number would be absolutely necessary to make > your idea A> secure. I had already thought about this scenario before, > but then thought A> that the senario I proposed to you would be more > simple, not needing a A> random number, and avoiding the need for a > direct connection between A> servers . (or would you add a connection > between servers to make a new A> symmetric key ?) > > A> Your idea will force you to handle a table of random numbers in the > A> database. I think it will not be very simple. Somehow, I tought that > the A> crypted data plays the role of random numbers with no need to > make a table A> of them; > > That’s right > > A> and every page displayed to the user would be loaded with many > A> hidden random numbers with your proposition, not with mine. > > We can use an only random number for each user. or more precisely for each triple (session,pseudo,remote host). As if a user uses a number to access host B, then B should not use it to access host C in the name of the user. > Well, I think that > 1) Redirections work longer (the user first requests A and then B) > than direct links But the direct link needs to wait for the communication between servers to be validated. 2) That’s right, we’ll need to manage one more > table containing random numbers. But I think it’s much less complex > than implementing one more encrypting algorithm especially for that > purpose (apart from SSL). I don’t think that queues (and this table of > random numbers) are difficult to be implemented at all. They require > two or three extra requests to MySQL. Let's talk about queues another time. As I wrote, I saw an info saying that php5 naturally handles xml. If you use it, I do not see why you say you would need a new encrypting algorithm. Are not the crypting functions already available separately ? Are you speaking about the fuss to explicitly handle and update a table of keys of hosts ? I think of something, maybe it is not realistic as it does not fit usual configurations, but: A way to keep the private key secure is to let another processor use it exclusively and to keep record of all communications between it and the main server. for the webmail, I don't know the price, it will depend on what others can offer. http://spoirier.lautre.net/trustedforum.html |
|||
| Sam 5 mars 2005 |
Considering a hacker enters the system. He cannot know password as it is hashed but he can change it so login as a normal user after changing password, then restore the initial value of password to not get noticed. the same for random numbers: he can produce a new random number, store its hashed value in the server to do as if it was produced normally, and also modify the queue. Can't he ? ----------------------------------------------------------- |
|||
| Mar 8 mars 2005 |
- security problems with GLS I mean that I am generally pessimistic about the possibility to protect anything concerning a server and its user accounts (and the authentication of its users to other servers) when it is hacked. So we can give up and hope that the server will not be hacked. For a long term future I had imagined a general way to protect servers from hacking: http://spoirier.lautre.net/network.htm -webmail. |
|||
| Mer 9 mars 2005 |
- general way to protect servers SP from hacking: http://spoirier.lautre.net/network.htm The one described in http://spoirier.lautre.net/network.htm -GLS, webmail and invitations, PWP and dating. |
|||
| Mer 9 mars 2005 |
-GLS, webmail and invitations, PWP and dating - trust and complaints system - calendar system, wiki - money system. - user edit their private TeX files in their accounts, and run pdftex online :-) |
|||
| Jeu 10 mars 2005 |
- webmail 1) Integrate the webmail into the forum: In one's pseudos list, one can decide for each pseudo "pseudo" whether it will play the role of an email address pseudo@server to receive and send messages (no difference between abilities to send and to receive for each pseudo: these go together). Contrary to what I described on my page trustedforum.html, I think about the following better way : having the same webmail for all pseudos of a given user, not different webmails. From the forums system there is a link to the webmail, and from the webmail a link back to the forum. In the webmail, one can send messages from any of the pseudos that can (according to the decision above). For every pseudo there is a separate "sent messages" box, and a separate "received messages" box to contain read messages; there will be an inbox to contain all new messages. (I forgot if Frozen already made automatic putting of messages into folders) 2) Add an invitations system When sending an email, one can select whether this email will be an invitation email or not. If it is, it means that the server will produce and add to the end of the message a piece of text with a link with a code, by which the receiver can register to the site. In the database, the information about who invited this user is stored. So, to do this, the form of writing a message will contain a checkbox to decide if it is an invitation (by default not), with a menu to select the language in which to make this invitation (it appears in 2 ways: to add the automatic invitation sentence in the message, and set the value of interface language for the new user) 3) Automatic adding to contact When A invites B to the system, then each will have the other in contact list.It would be good to develop the contacts system so that user A can, in his contacts list, add his own comment on each contact for his personal display of his contacts list.This way, when A invited B to the system by email, in A's contact list, he will see B's email address used for invitation at the place of his own comment on B. 4) Display invitation chain for admins The admin of the system can ask the computer the invitation chain that leads to any user or pseudo That is, he types a pseudo X and sees on the screen the list A>B>C>....>K=X where A was not invited or was invited by admin directly; A invited B, who invited C, who.... who invited the user K with pseudo X. 5) Record problems to detect bad users The admin can set "User X made a problem", with a comment on the problem. So a problem is an item with data (X,comment). It can also be deleted by admin. This affects for the admin's view all the invitation chain that leads to X, so that when the admin will see user B (for example in invitation chain), he can see how many problems passed through B. Therefore the invitation chain to a user will look like A(50)>B(24)>C(18)>D(5)>K(1)=X Then if admin clicks on C, he will see the list of all 18 problems that passed through C, with their invitation chains and comments. Admin can also ask for the list of all users by whom pass a number of problems larger than a given number, with their invitations chains. To improve this, we can also introduce a badness number associated with a problem, so that instead of the number of problems, would be the total of badnesses of problems. |
|||
| Ven 11 mars 2005 |
- the possibility to invite a new user without email, from the account of an existing user - The possiblity for users to see the problems they are concerned with: the problems affected to him personnally, and for each problem which passes through him, who is the next user un the chain (that he invited) ; with the comment. ==> for each person he invited, he can see how many corresponding problems, and by clicking, can display the list of associated comments. |
|||
| Lun 14 mars 2005 |
-forum : it works slowly. |
|||
| Jeu 17 mars 2005 |
- webmail |
|||
| Ven 18 mars 2005 |
- Datings as that spec. - GLS security issues Remark 1: Forum works slowly in a reason of a low priority of subdomains in our domain. Remark 2: We have another one programmer ready to start working with WebMail and Invitations. no webmail spec |
|||
| Dim 20 mars 2005 |
About webmail and invitations: Let the admin the possibility to forbid a user from making any more invitations of new users. |
|||
| Mer 30 mars 2005 |
http://tforum.php.by - I read "Pubilc forums_forums" More remarks about forums system: I created a forum, and in "edit forum rights" I have no link to go back to the forum, and the back button of the browser does not do the trick. The "move to folder" should keep displaying the same box and not the box the forum is moved to. When a forum is created, the creator should be subscribed to the forum, until he unsubscribes. About dating parameters: I just start looking. I see about languages the question is repeated for a given list of languages. It is not good. To explain in more details, there are 3 questions. 1) "parameter" : first, the user selects some languages from a given list of languages. Then, another display shows for each of language, what is your ability: as in your column "choice" (or any logically equivalent display). 2) other "parameter": willingness to learn the other's language": 0/1/2 3) "criteria": what badness for each quality of conversation (this question does not mention any particular language) I will review more things next. |
|||
| Mer 30 mars 2005 |
languages: - First on page is a list of languages already filled with their respective skills that are editable. At the start, it only contains the interface language with "very good". Then, one can add more languages one by one : Add langage : (menu of languages not yet filled) - with skill (menu of skills, except "not at all") - button "Add". In order to avoid problem like: "My God, I just wanted to add a language and all the fields I filled below have been forgotten !", it may be wise to divide the editing of parameters and criteria into several pages. So the "Edit parameters and criteria" would lead to a list of links to the editing of different sections. One would be language, one geography, one would be interests and so on. |
|||
| Mer 30 mars 2005 |
for nationality - European - African - ... - link "details" that will replace it by the list of all countries of that continent, ( with value for the continent). |
|||
| Mer 30 mars 2005 |
- Are you ready to learn the other's language? ==> NO badnesses associated to its values. - On the left, the "help" should go to the help of the dating, not the general help of forum. - On top bar, replace the "Dating account" by "Forums". |
|||
| Mer 30 mars 2005 |
- Weight is in kilograms, height is in cm. - American people use feet and inches - given list of intervals, each value in cm can be translated into a value "x feet y inches" by the mere trick of language files. For intervals: If there are n lines (intervals) there are (n-1) fields for the limits between them; there are no "other cases".So: From 0 to (), badness is () From it to (), badness is () ..... Above, badness is () Income: What currency (euro/dollar/...) I don't understand why you make a "low limit" and "high limit". You should just put one value, even if it is an approximative value. |
|||
| Mar 5 avril 2005 |
- Income: What currency (euro/dollar/...) We need to convert values somehow exchange rates of course ( convert these) - to simplify, let's use only euro and dollar for now. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Abour languages: make an only form containing: 1. Table to select a quality for each language (possible qualities in comboboxes, "not at all" by default" 2. Selection of willingness to learn the other's language 3. Selection of badnesses for each possible quality of conversation like: - not at all - <input value> - a little - <input value> ... 4. submit button (continue entering information) OK : But for the 1., anyway there needs to be some better display than a whole table per language which would make a too big page if there are 100 languages. If you make a table, for example you can make one language per line, and don't separate lines by too big spaces. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You told me about constant intervals for height, width, etc. 1) What do we do with the units? (cm/inches/ets...) 2) What exact intervals should I use? Well, let's stay with cm and free intervals, and we'll add a help page with conversion table with feet and inches for people who need it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ You told me to make a tree of natinalities. : it touch ethnicity, religion or handicap? - classification of world religions on some web sites. ---> divide also "catholic" into "deeply catholic" and "moderate/liberal catholic". ---> correlation between nationality and ethnicity. -----> e 2 nationalities, I wonder what we can do with them. If possible, include the 2 nationalities, then for computation, use the min of badness between them. If it's a problem, let down for now, each user will choose which nationality to put. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - make decision with the parameter of smoking habit. = interest among others, presented as you did for marital status for example. |
|||
| Mer 6 avril 2005 |
security worries |
|||
| Jeu 7 avril 2005 |
dating + GLS + simple PWP + forum running in network + webmail + invitations system. |
|||
| Sam 9 avril 2005 |
> Login: testuser01 > Passw: tu123456 - webmail Invitation tree: only admin should see the "tree" of invitations; user can only see for each of the people he directly invited, the list of problems associated:- either directly to this person - or indirectly, but without knowing the other intermediate people. Only the admin should be able to see intermediate people. - link back to the forum should read "forum" or "home", not "trusted forum". The "Options" link should not lead to the options that I see here which should be defined by (parameters given by) the forum configuration. - The only interesting thing to keep would be to add folders, which is not working. - The other thing is to manage which of one's pseudos can receive mail. I just thought about the idea to have a whitelist attached to given email addresses, so, pseudos that can receive mail but only from a restricted set of senders. Please ensure that there is a link back on every web page. - emails @php.by ? Do you also own the domain php.by ? or mail.php.by ? The email addresses of our system should not mix up with the email addresses of the host php.by itself. - I tried to send message from that account to my address spoirier@lautre.net but I only received it to the same testuser01 account. |
|||
| Sam 9 avril 2005 |
- got the message in my email spoirier@lautre.net - pseudo of inviter should not appear in clear in the URL. It is bad for security: imagine one wrote this url with another pseudo... So it should be a random number instead, stored in database with pseudo of inviter and email address of invited person (or id from address book) so that the inviter will see it in his contacts list. |
|||
| Dim 10 avril 2005 |
- how this system would be installable elsewhere if it depends on a mail server you do not have control of (for example, what if one's pseudo is identical to an email address that has already been created by someone else). - use webmail from the account I had created (login:sylvain) and I get the error message: sorry, i can't connect to IMAP. ==>I want a system that has a complete control of the list of possible email addresses of a given domain. |
|||
| Lun 11 avril 2005 |
- Dating system. - Forums for two ppl to conversate with each other (I don't know how to invite smb from a remote host to a forum on a local one) Well, just consider the case of 2 people hosted on the same server - Sending account: sending an account and checking criteria. - checking the matches parameters. - sending to all server includes sending to itself, which means checking this account with all other accounts hosted on the same server. - the "sending" will do both operations: sending to other servers and "sending to oneself", checking with other users of the same server. - Folders (U, T, S, ...) just because nothing can be placed there yet. login: pasha pass: 111 |
|||
| Lun 11 avril 2005 |
1) possibility to invite a new user without email, from account of an existing user 2) one pseudo - one webmail, no possibility to choose if each pseudo can play a role of an email address or not, every pseudo is an email address. ===> - one webmail for all pseudos, with possibly folders inside it for different pseudos after the messages are read. It will be good when one can choose if each pseudo can be an email but in a first time, "every pseudo is an email address" is ok. 3) procedure of registration by invitation. i think it have to be in the next way: a) i create an md5 form current time(or any random number), add this md5 to the letter to invitation url, and add this md5 to database in forum. b) when the user is trying to register, registration module checks if md5's are equal. if fail - user can not to be register. Is this way correct ? if not, tell me please what to do with invitation. Yes, I don't see the interest for md5, just a random number is ok. Don't you think so ? * other people to install your full software to other servers ? Will the use of subdomains different from forum to mail be necessary ? I notice that email account is not yet automatically created at registration. |
|||
| Lun 11 avril 2005 |
- criteria * "A little but I can stop" fits more for smoking than for drinking. I thought of including "trying to quit" for smoking status. * can I edit myself some file of list of parameters and their different options instead of asking you to make any modification I have in mind ? * I did not see the option to "ask for advice" or not: how to stop asking for advice ? OK, I did not think about separating the selected from the selected+. I only see display of parameters, not yet possibility to modify it. - trees (ethnicity...) - geographical criteria. |
|||
| Lun 11 avril 2005 |
- pasha account : subfolders of public forums. So I suppose they are public forums and this is why it does not appear in the list of common forums with user1. But I do not understand why the right to write is reserved for one pseudo. In the future : subscribe to public forums (i.e. have it appear in main box when there are new messages) and invite people to them, that is, subscribe them to it (while one can know who invited one to a forum). |
|||
| Lun 11
avril 2005 |
/database/gif_1.gif (0.05
MB) DB Scheme image is attached. > The "A little but I can stop" fits more for smoking than for drinking. I thought of including "trying to quit" for smoking status. Sure. > More generally, once the system released (or before), can I edit myself some file of list of parameters and their different options instead of asking you to make any modification I have in mind ? Of course you can. I think you'll be interested in the following tables of the database: dating_criteria - Questions (like: smokin habit, natinality,...) 'cases_count' field: -1 if an integer value is expected, 0 otherwise dating_cases - Answers (following choices) 'dating_criteria_id' field: I think you'll guess what it is. Be accurate inserting new criteria between the existing ones (not in the end)! All the criteria are shown sorted by their IDs. So you'll need to shift corresponding cases and all users' data! Anyway, if it's possible then it's better to append criteria to the end of the list, not to the middle. 'parent_case_id' field: this is used for tree representation. Root choices have 'parent_case_id' equal to their own 'id'; child choices have 'parent_case_id' equal to their parent's 'id'. dating_multilang_infos - Different users of different lang_zones (see 'forums_lang_zones' table) need the translations of the info parameters and choices. 'lang_zone_id': ID if the lang zone (see forums_lang_zones) 'key_id','from_which': this table contains translations of phrases if criteria and cases both. so key_id is the ID of either some case or criterium, and from_which is either 'Cr' or 'Ca' - for criterium or case. Some translations may be absent in this table. Then they simply won't be translated. dating_languages - just a list of languages dating_multilang_languages - their translations on different languages (depending on user's lang_zone_id). Not all possible translations for all the languages are needed. If some records are absent, then appropriate languages' names simply won't be translated. dating_languages_cases - levels of languages' knowledge are stored there (mroe precisely, their translations for different lang_zones). Not all possible records are needed. If some record is absent, then appropriate phrase simply won't be translated. Graphical representation of database structure is attached (MS Office Visio file). Take a look at it for more detailed information. As far as I remember, comments there are in russian. Soon i'll correct them. > I did not see the option to "ask for advice" or not: how to stop asking for advice ? Now the user chooses whether to ask for advice only when activating his account. Activating an account link is enabled (clickable) when EITHER (an account wasn't activated yet but all the info is filled (including photo and criteria)) OR (the user changed some settings - then he has to re-activate an account to apply changes). Well, I didn't think of stopping asking for advice. Ok, I'll do this very soon. > OK, I did not think about separating the selected from the selected+ but it's a good idea. > I only see display of parameters, not yet possibility to modify it. Why not? You first (for the very first time) enter the parameters so then they are stored. 'Minus' sign becomes 'Plus' near the corresponding menu point. But you still can click the link and view your parameters. All the fields are visible but disabled for editing. If you anyway want to edit them, you click the button at the bottom of the page and the fields become enabled (editable). To store changes, you click "ok". > In particular I will be interested to ckeck your trees (ethnicity...) working. Aren't my trees working? Didn't you see 'plus' signs near expandable criteria? Just click this 'plus'. > Waiting for geographical criteria. OK. |
|||
| Mar 12 avril 2005 |
- user chooses whether to ask for advice only when activating his account. Activating an account link is enabled (clickable) when EITHER (an account wasn't activated yet but all the info is filled (including photo and criteria)) OR (the user changed some settings - then he has to re-activate an account to apply changes). ==> Not good: this way, the profiles received between modifications and reactivation would be lost, which should never happen. The solution : keep both the old version still active and the new version being edited, until the activation switches to the new version. |
|||
| Mer 13 avril 2005 |
analysis of database another time. -OK: separate the selected from the selected+ - display of parameters, not yet possibility to modify it. ---> Why not? You first (for the very first time) enter the parameters so then they are stored. 'Minus' sign becomes 'Plus' near the corresponding menu point. But you still can click the link and view your parameters. All the fields are visible but disabled for editing. If you anyway want to edit them, you click the button at the bottom of the page and the fields become enabled (editable). To store changes, you click "ok". - button to enable editing. instead of a whole line for "activate account" in the menu, make a link "account status" which would give control of the following actions (because they are not often used, putting them together in the menu is ok): - Ask for advice or not - Activate account/inactivate account. - Send account - Set/modify PWP address(es) (just as an URL now, until the PWP system is made). Note: the "send account" should send with each server the list of profile id in the other server that matched with user, no matter their status, in order for the other server to not re-test the profile with those matches. It does not matter to recompute what has been computed and found negative (not a good match) because the profiles details may have changed since so the result may become positive, but it matters to not make users review profiles again uselessly (if one has been trashed, he is trashed and remains so). In trash, the display is by order of trashing date, from most recent to oldest. |
|||
| Jeu 14 avril 2005 |
- stable (= to not be deleted at every update) public forum in English for visitors to discuss the parameters of dating ? |
|||
| Jeu 14 avril 2005 |
- "dating" link should not appear on the top bar by default, but: - It can appear there if configured so. - Until then this link should instead appear in the "Configuration" page, together with the choice to display it on the top bar or not - The choice of pseudo should appear instead among the "Account status" options, so, to be possibly fixed after filling parameters. |
|||
| Sam 16 avril 2005 |
- Webmail . The one "question" is "One Pseudo-One Email". - better to have for each account only one webmail but that can handle several pseudos (which are email addresses). Or, maybe a better idea: For each pseudo, possibility to choose the following: Unless another rule is stated for a given message (depending on sender for example):- In what folder will the message go - Will it also appear or not in the inbox before it is read |
|||
| Sam 16 avril 2005 |
- The link from forum to webmail is not working with firefox: there is an antislash which is not correctly interpreted. - Waiting for the system to relate to pseudos correctly (and have the webmail automatically accessible from any user account) - When composing message, the presentation concerning the save to draft may be confusing: if I click "send" I feel like the message is sent. If I want to save to draft only and not send, I would feel things clearer if I clicked on another button aside "send", not the "send" button itself - better than adding a mere link back to the forum, Could you please include in webmail the whole top bar of forums system, replacing "webmail" by "forum": Forum - (possibly) Dating account - Contact list - Configuration - Exit so you can delete the "logout" link on the left. and this for every sort of web page that the webmail system contains. - For the "options" page I wonder why you have a Password management ??? If it is to change the pass to the whole account (I cannot see what else it can be) you should move it to the Configuration page of the forum. I also see no reason for the change of interface language as it is already handled by forum. - The link "Register new user" should also be moved to the forum's Configuration page. So now the webmail options should only contain the "manage folders". Probably in the future it will contain more things. - The link "Register new user" makes an error message with session. Then, using the back button on the browser gives more error messages. |
|||
| Dim 17 avril 2005 |
- user chooses whether to ask for advice only when activating his account. Activating an account link is enabled (clickable) when EITHER (an account wasn't activated yet but all the info is filled (including photo and criteria)) OR (the user changed some settings - then he has to re-activate an account to apply changes). --->> Not good: this way, the profiles received between modifications and reactivation would be lost, which should never happen. The solution would be to keep both the old version still active and the new version being edited, until the activation switches to the new version. Is there a reason to re-activate account at all? In fact, re-activation means not more than new chanhes will be applies. I thought it would be quite a suitable solution to disable re-activation at all, why not? As soon as the user changes his params/criteria, new incoming matches start being checked according to his changes immediately, why not? ---------> ok. - It does't touch re-sending account. The use first changes his parameters and then re-sends his accounts like if he was a new user. - not waste the time of everybody reviewing profiles (and photos) one more time, the sending account will contain the list of id of matches (whether selected or trashed) hosted on the site to which profile is sent, to omit them in the testing of matches.In the case of resend of a profile in A to host B, B will also check if this profile from A was not already trashed by B's user. - GLS |
|||
| Lun 18 avril 2005 |
- webmail: for each account only one webmail but that can handle several pseudos (which are email addresses). ~~~~> For each pseudo, possibility to choose the following: Unless another rule is stated for a given message (depending on sender for example): - In what folder will the message go - Will it also appear or not in the inbox before it is read - The link from forum to webmail is not working with firefox: there is an antislash which is not correctly interpreted. - Waiting for the system to relate to pseudos correctly (and have the webmail automatically accessible from any user account) - When composing message, the presentation concerning the save to draft may be confusing: if I click "send" I feel like the message is sent. If I want to save to draft only and not send, I would feel things clearer if I clicked on another button aside "send", not the "send" button itself - Sorry to have not thought of it earlier, but, better than adding a mere link back to the forum, Could you please include in webmail the whole top bar of forums system, replacing "webmail" by "forum": Forum - (possibly) Dating account - Contact list - Configuration - Exit - you can delete the "logout" link on the left. - this for every sort of web page that the webmail system contains. - For the "options" page I wonder why you have a Password management If it is to change the pass to the whole account (I cannot see what else it can be) you should move it to the Configuration page of the forum. - I also see no reason for the change of interface language as it is already handled by forum. - The link "Register new user" should also be moved to the forum's Configuration page. So now the webmail options should only contain the "manage folders". Probably in the future it will contain more things. - "the possibility to invite a new user without email, from the account of an existing user". "register new user" link created for invite user without email, this link renamed to 'invite user'. - The link "Register new user" makes an error message with session. Then, using the back button on the browser gives more error messages. - attitude between pseudo and mailbox. what is bad in idea of creating a new email for every pseudo? Do you mean a different interface, and in particular a different inbox ? - The problem is that if one received email to different pseudos and they arrive to different mailboxes, one must check every webmail one by one to see if there is a new message. Having a common inbox that receives messages to all of one's pseudos (making email addresses pseudo1@host, pseudo2@host...) avoids this problem and the risk to forget one. One other thing that I want is the possibility to have a pseudo that will not receive any email from outside, or at least not from unknown people (have a whitelist of senders), because else it would be an open door to spam: spambots would browse our public forums for pseudos, and send them spam. > but if > i will have one webmail for all pseudos, everybody will no that this > pseudo corresponds to this login. I can't see how |
|||
| Lun 18 avril 2005 |
- WebMail - PWP - Dating - webmail for every account |
|||
| Mon 18 April 2005 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Important tips conerning datings DB structure: in order to optimise the requests from PHP scripts to the DB I had to put the following restrictions into operation: table dating_mplaces: the records must never have their parent_id values more than their id values table dating_cases: the records must never have their parent_case_id values more than their id values please be careful with these things, they are very significant for the normalcy of the system ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Users with dating accounts: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ user1/pass1 pasha/111 eee1/eee1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ today I've done: -geographical parameters & criteria -settings page, -activating/deactivating -re-sending account -choosing pseudo every time activating the account -choosing whether to ask for advice at any time one wants -checking validness of entered data an only thing I'm still having bugs with is -quick "U" folder viewing (using pop-ups) I had problems with JavaScript coding. Everything else is done. I'll fix popups by tuesday's evening (I think I'll be sleeping on Monday) But I think, anyway the project is now quite presentable. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I thought you might be interested in the DB scheme (attached). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- |
|||
| Mar 19 avril 2005 |
- webmail of testuser01: why in the "draft" folder there is a message with From some nonsense address: Draft messages are messages one wrote planning to send it to outside, therefore the From: field should be oneself and the To: field should be anything? In the Inbox (1/17) there is a new message but why does it appear to the second page, second from the end ? - In dating, the "type of relationship" and "want children" fields are common badness fields, therefore there should not be a field "Choice" on left, but only a badness value field (the result of common badness will be the minimum of sum of both badnesses over all possible values). - the "want children" field would be ignored in computation in case other than "long relationship" or "marriage". This gives precisely: 1) Compute the common badness X for "want children", as min over children numbers of (sum of badnesses by both people for this number). This will not directly be counted in the sum of common badnesses, but: 2) Compute the common badness Y for the global question (type of relationship and want children) defined by min among types of relationships, of ((X if long relationship or marriage, 0 else)+ sum of badnesses by both people for this type). Under Firefox, I tried to edit personal info of user1. Clicking the button "Edit" has no effect. Once before it succeeded. I don't know why. Maybe because of the browser. - Trying to edit the "languages" field, the button "edit" had an effect, made a connection and gave an error message: Notice: Undefined variable: l in /h/phpby/htdocs.tforum.php.by/datingaccess.class.php on line 303 In Folders setting, you need not ask about "forum link" as it must always be there. The "folders setting" link would be better above the folders, not below. - list of dating forums as a folder in the main forums system. This should be optional, to choose in the page "Folders setting". Also, the default value (=until changed) of subscription to such forums should be set. |
|||
| Mar 19 avril 2005 |
- /en/userdoc.htm - In dating folders the profile move to: the U status should not be included. ---> link to view the parameters of that profile. ---> The username should not be displayed in the Unreviewed folder. Why are there numbers in () in geographical criteria ? -automatic webmail creation -GLS. |
|||
| Mer 20 avril 2005 |
- webmail: one user - one webmail, a new button in the menu called 'new messages', pressing this button you will see new messages from all of your pseudos, with links to their mailboxes(changing sessions to other mailbox). - Can this page be what is displayed at first when getting to webmail ? Can the webmail link appear in bold and/or with another color if there is a new message in webmail ? Why is it written: INBOX (0/22) whereas the first message in inbox has its time in bold which may mean it is a new message ? - test with user "testuser01", "tu123456", because it was created a mailbox with the same name and mailboxes for all pseudos. - Trouble is not solved - automatic creating of mailbox to new pseudo, it will be solved soon (after deciding of how the system parameters will looks like for the system developer). in options menu you can: 1) invite new user without email, from yours account, pressing this button redirect you to registration procedure. - Can this function be accessible directly from forums configuration page, without asking for webmail ? 2) manage pseudos, where you can to choose pseudo to observe its mailbox what do you mean ? and to select, is this pseudo a pseudo@host or not. this will be completed after trouble with automatic creating of mailbox is solved. 3) i have droped menu 'folder management', because is i think there is no reason to manage folders, each box have inbox, send, draft & trash. - But, if one wants to add more boxes to order messages ??? --> bugs with names of pages or points |
|||
| Dim 24 avril 2005 | - Automatic mail-account creation: after GLS, forum, dating and webmail finished. - system administrator : not a trivial task ( uses system functions and needs interaction with UNIX system inside). - make without trouble and without interaction with Unix system, a restricted version of the system: ~~~> WITH invitations system with both methods, inside account and by composing and sending inviting message, but WITHOUT mailboxes, receiving and storing messages. - install the system to some PHP hosting where they cannot access system functions. |
|||
| Lun 25 avril 2005 |
- 'dating forums' sub-folder of 'MainBox' containing all the forums one has created / invited to - "U" status is no more included in the "move to" statuses list - a link to view matches' full parameters - the username is no more displayed in the unreviewed folder (i don't know why, though) - anonimity of using dating system, revealing one's identity only to selected people.If I trash someone, I don't want that person to write to me. Seeing a pseudo gives the possibility to write to someone. - numbers in braces in geographical criteria are excluded - link to create/go to forum is always shown in each match, no option is associated with it in the "folders settings" - "folders settigns" link is now above the links 2 folders - visibility of "dating forums" folder is now optional - subscription to new dating forums is now optional - datings system - webmail ( restricted version inviting without mailboxes) - GLS |
|||
| Mer 27 avril 2005 | - "manage pseudos" for ? - "From" indicate pseudo but does not let the choice between pseudos ? - operations directly accessible from the same menu page, without an "options" of 2 entries. - address book, should be with the contacts system of the forum. |
|||
| Mer 27 avril 2005 | session was lost. - without logging out neither waiting a long time (half an hour ?) - without access ??? - Why do pages continue to display as if there was session with just empty pseudos ????? |
|||
| Mer 27 avril 2005 |
restricted version : - Delete the link "Webmail" - Include the menu of invitations functions as left menu of "Contact list". That is: Register new user - Add contact - Invitations tree. Each contact will be either an email address, a pseudo, or both. For each contact which has at least an email address, there will be a button "Send" to send email to that address, that may be an invitation email. If it had no pseudo yet, the new user can register and his new pseudo will be added to the contact info. If it already had pseudo, the "invitation" will send a reminder of login and pass instead of a new invitation. Note: the email address from registration should not automatically be added when one "add pseudo to contact list", for matters of anonimity. In the procedure of invitation by email, when receiver clicks to link for registration, he should not then see anything displayed but : - the title (registration) without link - the fields to fill : Login, password; pseudo for contact with inviter (if different from login) - "reminder:" question, secret answer; button "Register". email address ==> known by the system. |
|||
| Jeu 28 avril 2005 |
- user1 the "datings folder visible" is set but I do not see any dating folder in the forums system ? - "want children" should not be yes but diferent badnesses according to possibilities. - In unreviewed, there should be not links to modify status of only one match but a choice of status to move to, and a unique button to validate all. - invitations system, webmail and GLS. - forums system "for real use" : forums database be saved and accessible from further versions ? |
|||
| Ven 29 avril 2005 |
user1 the "datings folder visible" is set but I do not see any dating folder in the forums system ? - "dating forums" folder. created every time the user registers. - deleting dating account included in the system ? |
|||
| Sam 30 avril 2005 | - "want children" should not be yes but diferent badnesses according to possibilities. ~~> It is a common badness, that cannot be separated between one's badness for the other and conversely. There is no individual choice but a common choice, and the badness must be given by both for the same choice, which minimises the sum of 2 badnesses for this choice. - two numeric fields to be filled with the badnesses for "yes" and "no". |
|||
| Sam 30 avril 2005 | WEBMAIL: --------- What I want to see is: - Contact list page, a table of contacts with fields: Name - Comment (no Comment2 as it aims to be big so it would not hold in this table: click on name to see it with user info) - Email address - My comment (editable). * email address to a contact==> can write him a message, that can be an invitation message if there is no pseudo. If this invitation is used, the new pseudo is added in the field of the contact table. * On the left column instead of folders, links to register new user and to invitation tree. * instead of a mailbox, have for each email contact a forum reduced to a thread where new message is sent by email with a link with random number so that he can register or reply to the thread (so, the same display offer the two possibilities). ---------- OTHER --------- - trust system, - GLS - calendar and wiki |
|||
| Sam 30 avril 2005 |
Write email ~ click email address in contact page. |
|||
| 1
mai 2005 |
* forum to work with GLS --> each user a table of forums used to display folders. - --> each forum a table of users that is its invitations table. * invited users on a remote user forum, his rights in the forum can be checked locally ( local host). * Subscription to a forum should be stored at least in the forum's site, or maybe both. - in the forum's table, have the information of whether ((User is subscribed) and (there is no new message by another person)) If yes, at the next new message by another user, it will turn to no and inform the user's site. - The info on subscription is at the user's site. When user connects from home site to forum, if subscribed, the login request will come with the info to turn the above to yes. When subscribing, the simplest would be to do as if there was a new message; or make the request to the forum to turn to yes. |
|||
| * |
trust system ------------- * In his contacts list: each user A can choose to trust a contact B or not. * If yes, he does it under one of his pseudos, not for any public info but only for B's display. --> Then B will see it either from contact list (if he choosed to pu A in its contacts) or anyway by clicking "Trust received" on the left marginin of its contacts list, that will show the list of users that trusted him. He can validate or invalidate the trust received. He can choose what is default for new trust received: valid or invalid. (invalidation may be chosen for anonimity reasons towards that person, for further developments). * Then, the computer will compute the transitive relation generated by the relation of valid trust declaration, for giving each user the possibility to see (when displaying someone's info) if he indirectly trusts someone or not. * This question update every day. * useful for the server to regularly (every day ?) make a map of all users by equivalence class, where 2 users are in the same class if one indirectly trusts the other and conversely. --------- Complexification by network of independent servers --------- * Each server make the map for trust relations among its own users. So, for the subgraph of trust between its users it computes equivalence classes and publishes it for other servers, without saying how many people in each class, but only as the list of abstract ids of classes which contain users who received a trust by a user of another server (the classes who receive no trust by outside are known but stay unpublished). * So it publishes a list of abstract ids with the info of the relation of indirect trust (by internal chains of trust) between classes, and of trust from its own classes to the classes of other servers. -> Then, when a user A want to know the trust to a user B, A's server requests B's server about which class B belongs to or if B is not in a published class, which classes trust B. Then uses the union of graphs of all inter-site trusts and local trust. ------------ Complexification by different types of trust ------------ * There will be standard trust, but other trusts will be handled in parallel according to the same logic. * Any user can create a new kind of trust, called membership... |
|||
| 1
mai 2005 |
* trust system. * trust declaration not validated by the receiver --> used for computing trust from the viewpoint of declarer (for his display) without using it by those who trust him. --- * A membership = graph of trust computed the same way - Only users who choose to be members of this graph - Trust declaration for this membership, which is separate from usual trust (but I think it should be necessary to trust someone normally to be able to trust also this way). - A membership can be public or private. - public membership ==> gives non-members the possibility to view this trust towards people from the viewpoint of some existing member (who accepted this). ---- - Another kind of trust is with parties. It will be a modification of the normal trust computation, in the following way. * pairs of opposed parties. * For each pair of opposed parties, each user can choose to be either neutral (by default everyone is neutral) or of (only) one of both. * Suppose there is only one pair of opposed parties (pb with several) * one graph of normal trust will be replaced by 2 graphs of trust to be computed independently: ---> one G excluding the people of one party ---> the other G' excluding the people of the opposed party. --> Then, when A asks the computer whether he indirectly trusts B, the answer is defined by ((A indirecty trusts B by G) OR (A indirectly trust B by G')). ~~~~ So, if A is not neutral but to one party, he will only consider trust by the graph excluding the members of the opposed party. * If there are N pairs of opposed parties, it would not be rational to compute another graph for each of the 2^N ways to take parties. --> So, instead, for each pair of opposed parties there will be 2 graphs of trust as if nobody took any other party, and also a synthesis into one graph or relation, for computation by another server busy with another pair of opposed parties. But to make computation approach approximately the taking into account of an opposition when computing other opposition, we will consider as invalid any trust declaration between people of opposed parties. |
|||
| 1
may 2005 |
* Datings and WebMail system. |
|||
| 2
mai 2005 |
* SVN = new version of CVS (subversion control). * New version of GLS Global Login System specification #000001: Overview #000002: Data transfer between hosts #000003: Bookmarks #000004: Security #000005: Logging in =========================================================================== #000001: Overview ======================================= - given list of independent web hosts located @ different places each accessible by a different domain. Each host has its own set of user accounts. Common functions of GLS are: 1. Performing data transfer between hosts 2. Providing bookmarks =========================================================================== =========================================================================== #000002: Data transfer between hosts ======================================= 1. Functions description 2. Requests format description ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Functions description * GLS allow different independent hosts connect to each other directly and transfer some data. * Each host has a private and a public PGP keys and a list of other hosts' public keys. - We do not consider here the problem of how these data will be entered (let us enter them by hand). * GLS must contain a library (a PHP class) with following functions: a. Get a list of registered hosts b. Send a custom request to the remote host and get the response * GLS must also contain the second part, a library : a. Receive a request from the remote host b. Perform some pre-defined actions depending on the local destination of the request (described below) c. Return some data (if necessary) * GLS doesn't touch contents of the request. Its function is only in transmitting. 2. Requests format description * Request is some data sent from one host to another; the system contains many parts which use these functions, so each part will use GLS to send some necessary data. Format: - We will use RPC and packets in XML format. More precisely, GLS must have a function with parameters: " Host id " Request type " Request data GLS will access a table containing the following data for each host of the system: " Id " URL " Comment " Public PGP key The parts of the system, calling this function, will send ordinary PHP variables (arrays) as "Request data". --- GLS has to form an XML request from this data. --- GLS must include "Request type" into an XML request also. So after forming XML request, GLS sends the XML packet to the corresponding server (B). --- When the GLS library of the server B gets a packet from the server A, it looks at the "Request type" included in to the packet. Then depending on the value of the "Request type", it calls one of the functions of the system. You will be given a list of accordance "request type" - "function name and location". When the function responses, GLS sends the response back to A. =========================================================================== =========================================================================== #000003: Bookmarks ======================================= * User's home site will store some set of pages of foreign hosts to visit. The * user can manage this list (add/edit/delete bookmarks' names/links). These links must be clickable. A click will open a new explorer window at a place the bookmark leads to. Every user has it's own personal set of the links. * Every page of the remote host contains an "Add to my bookmarks" link (visible to the logged in users only, of course). When it's clicked, a corresponding request to the home host is sent. So, GLS must provide: a. Bookmarks managing page b. Adding bookmark (sends request to the home site) Now, more detailed description of what should happen when the user clicks the link: User's logging in into the home site (A) causes a corresponding session to A to be created. A has the list of opened sessions to foreign sites. From the beginning, this list is empty. When the user clicks the link leading to the foreign host, A produces a page with a redirection to B. This page contains an encrypted XML packet with data of: a. pseudo used b. preferred language c. time of request (the present time of computing this data that will be checked by B; the difference should be no more than a few seconds) d. what page one wants to access e. possibly, other info (later) So, the host B receiving the request from the user will decrypt this data (knowing from the request that it comes from A, and deducing from it what symmetric key to use for decryption) and, if the time is checked to be ok, open a session with session variables set: a. what host A it is from b. pseudo c. preferred language Then B sends back to the user the page wanted by one. If the user already has an opened session to B, A includes to XML only the page the user wants to access. The user can view the list of opened sessions and close some of them (this will send a logout request from home host to remote host - unless it is a request by the user to the remote host that will inform back the home host). Thus, GLS must also provide following: a. List of bookmarks b. List of hosts one has opened sessions to c. Computing an XML packet, creating a redirection page d. Getting a request from the user who hasn't been logged in yet and creating a session for him. Note: A and C points must be implemented separately: the redirection page is needed not only from the bookmarks list, but also from somewhere else. e. Remote logout: when A sends a request to B to close user's session =========================================================================== =========================================================================== #000004: Security ======================================= We have two tasks concerning security problem: a) Prevent hackers to trace (decrypt) data stream between the servers b) If the case somebody hacks some server, prevent him to access other servers. Earlier we had a solution to use SSL sessions between servers (send XML packets over HTTPS) but recently I've been told another idea from the developer of GLS, it is a little more simple but quite as secure as an older one. In a day or two we shall coordinate the solutions and I will include the most suitable into this specification. Concerning the point b), when the user gets the write access to the server, he certainly gets its private key. And he certainly accesses passwords of all the users of the server (even using hash-encrypting does not allow do avoid it: he can modify PHP files and thus create a logging of all the sent login data from logging in users). Anyway, the main idea of security is encrypting outgoing XML packets (from A to B) using the pair (A's private key, B's public key) and then decrypting them by B with the pair (B's private key, A's public key). That's how we provide two things: a) Security of data transmitting b) Confidence of the opponent is who we think he is (absence of the man-in-the-middle changing the received packets). =========================================================================== =========================================================================== #000005: Logging in ======================================= There is a little addition. GLS must include interface for users to login into their home hosts. There are many different parts of the system that are being developed independently, and each of them needs such interface. So there must be a page containing "login" and "password" fields and a submit button. Corresponding table in the DB is already created. When the user clicks submit, in the case the entered data is valid, GLS must create a new session. GLS must also check such things as session expiration time and changing user's password. If the user has successfully logged in, then he is shown a welcome page containing links to different parts of the system: -Forums -Web mail -Dating system ... -Options -Logout In the "options" menu he sees a link to change password and to choose a place (for example, webmail or forums) to be automatically loaded right after he logs in without showing this page of choices. But from the very beginning, this page must be shown by default. You will have to create a library with a function that would have to be called any time the user navigates to a new page of the system. This library will manage session variables (update session expiration time, etc). =========================================================================== |
|||
| 2
may 2005 |
-------- Dating ------- Fields for badness numbers: Badness numbers are not so large ! Intervals: Interval : badness Below []: [] From it to []:[] ..... And above :[] * list of nationalities and regions * when one puts a badness number then divides the region, have the number copied to all subregions. * Why is there still a badness number for a folder of nationalities when it is open ? |
|||
| 2
may 2005 |
=========================================================================== #000002: Data transfer between hosts ======================================= 1. Functions description 2. Requests format description ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Functions description * main feature of GLS is to allow different independent hosts connect to each other directly and transfer some data. * Each host has a private and a public PGP keys and a list of other hosts' public keys. * We do not consider here the problem of how these data will be entered (let us enter them by hand). ==> So, GLS must contain a library (a PHP class) with following functions: a. Get a list of registered hosts b. Send a custom request to the remote host and get the response ==> Thus, GLS must also contain the second part, a library which would: a. Receive a request from the remote host b. Perform some pre-defined actions depending on the local destination of the request (described below) c. Return some data (if necessary) * GLS doesn't touch contents of the request. Its function is only in transmitting. 2. Requests format description * Request is some data sent from one host to another * the system contains many parts which use these functions, so each part will use GLS to send some necessary data. Format: * We will use RPC and packets in XML format. More precisely, GLS must have a function with parameters: " Host id " Request type " Request data GLS will access a table containing the following data for each host of the system: " Id " URL " Comment " Public PGP key The parts of the system, calling this function, will send ordinary PHP variables (arrays) as "Request data". GLS has to form an XML request from this data. GLS must include "Request type" into an XML request also. So after forming XML request, GLS sends the XML packet to the corresponding server (B). When the GLS library of the server B gets a packet from the server A, it looks at the "Request type" included in to the packet. Then depending on the value of the "Request type", it calls one of the functions of the system. You will be given a list of accordance "request type" - "function name and location". When the function responses, GLS sends the response back to A. =========================================================================== * crypt data using symmetric key ( both crypting and authentication (signature)) * CPU use =========================================================================== #000005: Logging in ======================================= * GLS must include interface for users to login into their home hosts. * There are many different parts of the system that are being developed independently, and each of them needs such interface. ----- * There is only one login, which already exists and leads to the home page which has links to all other functions? ----- * So there must be a page containing "login" and "password" fields and a submit button. * Corresponding table in the DB is already created. * When the user clicks submit, in the case the entered data is valid, GLS must create a new session. GLS must also check such things as session expiration time and changing user's password. * If the user has successfully logged in, then he is shown a welcome page containing links to different parts of the system: -Forums -Web mail -Dating system ... -Options -Logout * In the "options" menu he sees a link to change password and to choose a place (for example, webmail or forums) to be automatically loaded right after he logs in without showing this page of choices. But from the very beginning, this page must be shown by default. * You will have to create a library with a function that would have to be called any time the user navigates to a new page of the system. This library will manage session variables (update session expiration time, etc). =========================================================================== * in the long term = having entry page displaying several things at the same time in several parts of the screen: - forums with new messages - calendar events - warnings about other things ----------------------------------------------------------------------- Date: Lun 2 mai 2005 11:59 * geographical criteria * 2 independent questions (handled in the same table for display commodity): - 1 where to meet - 2 where to live in the long term, in case it is for long relationship or marriage. ==> two common badnesses to be independently minimised on the set of all places. ==> "badness value" column refers to first meeting and should be called "badness value for first meeting", and "Badness value if: - Would have income there" should be 3 columns in the geographical table. * the tree of religions with true religions |
|||
| 2
may 2005 |
* In Unreviewed folder==> no visible distinction between statuses * I user1's Unreviewed folder. match "Your status: Unlisted"===>NO * view parameters * File should be filled before being sent. * can user fill info and criteria before choosing the dating pseudo ? |
|||
| 2
may 2005 |
=========================================================================== #000002: Data transfer between hosts ======================================= 1. Functions description 2. Requests format description ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. Functions description * main feature of GLS is to allow different independent hosts connect to each other directly and transfer some data. * Each host has a private and a public PGP keys and a list of other hosts' public keys. * We do not consider here the problem of how these data will be entered (let us enter them by hand). * So, GLS must contain a library (a PHP class) with following functions: a. Get a list of registered hosts b. Send a custom request to the remote host and get the response * include the function to -add a new host to the list -remove a host -change its data -display the list of hosts. * In a future development of the project, new hosts will be added/modified/removed to the list automatically. |
|||
| 3
may 2005 |
* crypt data using symmetric key because it provides both crypting and authentication (signature) by the same operation with little use of CPU. -- Symmetric key has one significant disadvantage: it should be changed from time to time. - At every new connect, we shall use encrypting with assymetric keys only for the beginning of the session, to generate a random symetric key. Then using a new key we shall perform data transfer much faster. * there is only one login, which already exists and leads to the home page which has links to all other functions. - The one which exists is a login which leads right to the forums. * datings, webmail, PWP * we NEED to have UNIQUE login page For example, why should a developer of webmail use a login page from forums? What we are going to do is: 1) when the login page of GLS is completed, 2) we are giong to exclude a login page from forums 3) and then include forums, datings, webmail andall other systems to the login page of GLS as modules |
|||
| 4
may 2005 |
======= PWP ======= 1. Should I write a real-time HTML-redactor allow user to create his PWP in real-time mode or an interface to allow user to upload his finished web-page from computer using https or ftp. 2. I offer to store site content not in folder called "/pseudo/" but to keep it in a database. It will be more useful according to the security. ==================== |
|||
| 4
may 2005 |
* crypt data using symmetric key ( crypting and authentication (signature)) * CPU * every new connect --> ( encrypting with assymetric keys the beginning of the session ===> get random symetric key). * using a new key ==> data transfer much faster. * only one login, which already exists and leads to the home page which has links to all otherfunctions. * The one which exists is a login which leads right to the forums. - datings - webmail - PWP * have UNIQUE login page * 1) when the login page of GLS is completed, 2) we are giong to exclude a login page from forums 3) and then include forums, datings, webmail andall other systems to the login page of GLS as modules *- the folders system (making lists of forums - the forums system (when one visits a particular forum). - in some future development it should be possible to have forums of different styles, for example one being an adaptation of PHPBB, listed in the same folders. - "ultimate version", info from the different parts to be displayed to the same screen that appears right after login: ~main folder ~calendar events ~bookmarks (small bookmarks list separate from the large bookmarks list accessed by a link)... |
|||
| 4
may 2005 |
* dating - GLS - PWP - hobbies and interests * "webmail" * contacts list * stored threads : person can reply online using his random number * mail invitation --> not used to register + one sends another invitation to the same person: it would be another random number that replaces the former one > |
|||
| 4
may 2005 |
======= PWP ======= 1. real-time HTML-redactor ==> user create his PWP in real-time mode ==> an interface to allow user to upload his finished web-page from computer using https or ftp. * better a real-time HTML-redactor ===> security + ===> page to be re-processed for headers and active links. ==> re-use existing wiki systems, splitting its functionnalities between - text formatting on the one hand - history - user accounts and editing rights * diversity of text formatting systems, that can be assembled with any of various contexts: personal pages, wikis and forums. * In further development, so, we would include the other aspect of wiki: have each page be editable by several users according to a system of rights, with history to check what has been done by everybody. * Several kinds of pages: some personal (to be edited by only one person); other collaborative, with tables of editing rights (or denials) and history. * The system of rights would be similar to the one of forums; system of handling rights, usable for forums as well as for wikis. |
|||
| 5
may 2005 |
1) left column was modified to options (invite, invitations, contacts) 2) you can compose message by contact list's link maybe it will be good to make 'to' field in composing message unchangable? P.S. There is new column in contact list, second from the left, it shows whether name is pseudo from tforum or not. |
|||
| 5
may 2005 |
* webmail * email accounts of new users |
|||
| 5
may 2005 |
* unfinished webmail/invitations * forum+dating |
|||
| 5
may 2005 |
* "webmail" * "Invite new user", the headers of anonymous registration : (top bar of login, "forgot password", "registration") must disappear !!! and be replaced by the headers of the account of the inviting user. - contacts list --> link is on the top bar of forums - "Comment" in contacts list. |
|||
| 5
May 2005 |
* full invitations tree from a given user which is not admin should not be visible to this user. ---> He should only see the people he directly invited himself, and : - the problems directly associated with each of them - the problems indirectly associated with each of them (=with people directly or indirectly invited by them) without showing the list of intermediates. * webmail * email accounts of new users |
|||
| 5
may 2005 |
*webmail *handle full mailboxes will be one thing that will need further work |
|||
| 5
may 2005 |
* invitations system by contacts * dating * webmail/invitations. * forum+dating |
|||
| 6
may 2005 |
* webmail/invitations. * forum+dating |
|||
| 9
may 2005 |
http://tforum.php.by/ *new version from http://php.net/downloads.php |
|||
| 10
may 2005 |
When you enter new record to the contact list: 1. Adds info about pseudo (if you enter pseudo) 2. Adds email (if pseudo is absent in database) |
|||
| * |
* By user1 I just made the following: Editing the English translation, replaced the version number 1.0 by 2.0. * the meaning of editing a translation --> making another translation that will be a further version after a given one ? * A user should be able to choose whether the translation he made is public or not, and change this fact. * If it was public and someone else used it, then he makes it private, just the other can continue using it while it does not appear anymore in the list. * Instead of adding new translation based on a given one, there should be: - add new translation, seeing first checked one, with defaut values the second checked one, blank if none. |
|||
| * |
When you enter new record to the contact list: 1. Adds info about pseudo (if you enter pseudo) 2. Adds email (if pseudo is absent in database) * user1's account bug after accident with new translation |
|||
| * |
1. Creating of the admin panel for the project. 2. Creating of the technical documentation. |
|||
| 10
may 2005 |
* contacts list. * invitations tree, "pseudo:user": it may be either, but why both ? |
|||
| 10
may 2005 |
* email address should not be
asked during an invitation by email ( this is already known). * specify if a user A wants to change his email address appearing in some contacts list of another user B. *Now let's just let B responsible for the email address he sees for A, independently of A's email address. |
|||
| 10
may 2005 |
* Editing the English translation + I replace the version number 1.0 by 2.0. * editing a translation ---> making another translation that will be a further version after a given one ? * A user choose whether the translation he made is public or not, and change this. ---> If it was public and someone else used it, then he makes it private, just the other can continue using it while it does not appear anymore in the list. * add new translation, seeing first checked one, with defaut values the second checked one, blank if none. |
|||
| 10
may 2005 |
When you enter new record to the contact list: 1. Adds info about pseudo (if you enter pseudo) 2. Adds email (if pseudo is absent in database) * webmail * user's account & transaltion |
|||
| 10
may 2005 |
* Webmail * FOrum * Dating |
|||
| 11
may 2005 |
================================================================== GLS: ================================================================== * smarty * remote function calls by sending xml-rpc messages, that are encrypted and signed with openssl ================================================================= |
|||
| 11
may 2005 |
* webmail |
|||
| 11
may 2005 |
1. Creating of the admin panel
for the project 2. Creating of the technical documentation |
|||
| 12
may 2005 |
==================================================================
GLS: ================================================================== * smarty. * full draft of remote function calls by sending xml-rpc messages, that are encrypted and signed with openssl. |
|||
| 13
may 2005 |
* PWP * server can cope with thousands of users |
|||
| 13
may 2005 |
thousands of users. |
|||
| 14
may 2005 |
PWP |
|||
| 14
may 2005 |
* after the trust system * complaints system. Complaints handled by forums: Any forum can be turned into a complaints forum. * In complaints forums, will happen anonymous invitations through GLS, in the following way. ---> An anonymous invitation of a user into a forum, is like an invitation as you know it, except that 1) There is no inviter. The inviter = "system" + some parameter (which party invited him - not sure it is useful). 2) More importantly, the forum's server does not know at first who is invited. It just knows what is the home site of the invited user, so sends this home site a request with some parameters, and according to the parameters, the home site will find a user that fits. 3) The invited user can first access the forum in read-only mode without a pseudo, so the invitation id of user into the forum stands for his pseudo. Then, if the user chooses to write to the forum, from his home site he includes one pseudo to access the forum. Then, the link to the forum will contain in included parameters both invitation id and pseudo, that will be recorded into the invitations table of the forum, in order to be still authenticated and write under the pseudo. |
|||
| 16
may 2005 |
################################################## # # Copyright (c) 2004-2005 TrustSystem # # This file is part of TrustSystem # # TrustSystem is free software; you can redistribute # it and/or modify it under the terms of the GNU # General Public License as published by the Free # Software Foundation; either version 2 of the # License, or (at your option) any later version. # # TrustSystem is distributed in the hope that it # will be useful, but WITHOUT ANY WARRANTY; # without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR # PURPOSE. See the GNU General Public License # for more details. # # You should have received a copy of the GNU # General Public License along with TrustSystem; if # not, write to: # # info@php.by ################################################## |
|||
| * |
* use LGPL. |
|||
| 16
may 2005 |
* PWP. |
|||
| 17
may 2005 |
* ( email invitation or message sent) ==> can choose sender name instead of the present "www-data". * anti-spam: - limit the number of sent messages to 20 per day - in message identify sender account. Either in the headers of the mail, or at the bottow of the message as is now the invitation. |
|||
| 18
may 2005 |
licence |
|||
| 19
may 2005 |
http://trust-forum.php.by/ |
|||
| * |
* making a new translation
from existing translations |
|||
| * |
* accounts and forums created * account "spoirier" |
|||
| * |
* phrases "PublicFOrums" and "MainBox" can't be translated? |
|||
| * |
* trust-forum.php.by * French interface |
|||
| 19
may 2005 |
*registering into the system |
|||
| 19
may 2005 |
* make a new translation |
|||
| 19
may 2005 |
* spelling mistakes * edit language file : version number = new one the interface ~~~>use the old version number ~~~> could not find it ~~~> empty values for translated words. ==> delete (disable) link "edit selected(left) translation". |
|||
| 19
may 2005 |
* Translation are present. |
|||
| 19
may 2005 |
* invite someone by email - link: "add email to contact list". - invitations system is not working - "pubilc" and translations system |
|||
| 20
may 2006 |
* "Pubilc" is corrected to "Public". * "Translations" * "Invitations" corrected: - 2 different links:add new pseudo/email * invite someone by email -- link "add email to contact list". -- invitations system is not working |
|||
| * |
* "Pubilc" is corrected to "Public". * "Translations" * "Invitations" * contact list - 2 different links: one to add new pseudo /email * email address as new contact |
|||
| * |
tforum.php.by equal to trust-forum.php.by, |
|||
| * |
http://trust-forum.php.by isn't
it? |
|||
| * |
http://trust-forum.php.by/?lang=en&action=registernew&parent=testuser01&key=990ec132d4d5b30f7227fc277a0d7b9e * registration page *wrong key --->Still no error message. * refuse the wrong URLs. |
|||
| * |
- SVN a ------------------------------------------------------ Issue for future development ------------------------------------ Place here your notices you have in mind for future realizations. ------------------------------------------------------ ------------------------------------------------------ General notices. ------------------------------------ General positions about the whole system here ------------------------------------------------------ ------------------------------------------------------ Webmail BUG ------------ Put WebMail Bug description HERE ------------------------------------------------------ ------------------------------------------------------ Invitation BUG ------------ Put description HERE ------------------------------------------------------ ------------------------------------------------------ Dating BUG ------------ Put description HERE ------------------------------------------------------ ------------------------------------------------------ Forum BUG ------------ Put description HERE ------------------------------------------------------ |
|||
| 20
may 2005 |
* spelling * 2 different links --> add new pseudo / email |
|||
| 20
may 2005 |
tforum.php.by |
|||
| 20
may 2005 |
tforum.php.by trust-forum.php.by, |
|||
| 20
may 2005 |
http://trust-forum.php.by/?lang=en&action=registernew&parent=testuser01&key=990ec132d4d5b30f7227fc277a0d7b9e + wrong key ==> registration page is correct? should refuse wrong urls! |
|||
| 20
may 2005 |
http://trust-forum.php.by
isn't it? |
|||
| 20
may 2005 |
URLhttp://spoirier.lautre.net/en/userdoc.htm |
|||
| 20
may 2005 |
* send an inviting message in a
language where no translation has been made ? * what if several translations have been made in this language ? |
|||
| 20
may 2005 |
trust-forum.php.by. |
|||
| 20
may 2005 |
* more items in the language
file, - every nationality * clearly separated by a line from items that strictly concern dating --> can choose to translate only the general interface without dating, and let other people continue the translation. Example : someone can make a French version letting all dating items in English, and someone else will use it to make a new version where all is translated. |
|||
| 20
may 2005 |
trust-forum.php.by. |
|||
| 21
may 2005 |
* forum comment size * create a private forum + created the public one again and put the private one to trash. ==> forum name (unlike its custom name) cannot be modified so that an empty private forum cannot be recycled for any other use as private forum. ---> admin can change forum name ---> what happens during invitation: the custom name of the forum for this user is added in the database as a copy of the forum name |
|||
| 22
may 2005 |
* forum on my web site: http://spoirier.lautre.net/philo/ * from http://spoirier.lautre.net/philo/ http://trust-forum.php.by/. make link on top of each thread. |
|||
| 22
may 2005 |
* disable the posting of messages in public forums by anonymous users. #spam |
|||
| 22
may 2005 |
* forum: in comment2 (')
character problem |
|||
| 23
may 2005 |
* registration page: link to documentation . - secret question - secret answer ==> can leave field blank |
|||
| 23
may 2005 |
* invite someone by email + the person registers ==> the pseudo of the invited person should appear in inviter's contacts in the SAME LINE as the email address used. |
|||
| 23
may 2005 |
* In public forums - paragraph without line break ==> it displays the paragraph in one line ==> it makes a hugely large table that requires horizontal scroll. Please correct ---> table width adapts to window. |
|||
| 23
may 2005 |
* people register. |
|||
| 24
may 2005 |
* My Comment field of contacts for new emails ==> do not add "Not member of trusted forum" * input the My Comment from user together with email address |
|||
| 24
may 2005 |
* make a new translation ==> unfinished line to be translated: You were succesfully registered in the system |
|||
| 24
may 2005 |
* add manually emails to the
pseudos * delete line of email without pseudo ==> line of email with pseudo disappear! * add again the email to the pseudo ==> email added to another pseudo |
|||
| 24
may 2005 |
* email anita.lice@gmail.com written in jamila (first line) * (second) anita line has blank email * update jamila line ==> fields blank update the anita line ==> anita.lice@gmail.com |
|||
| 24
may 2005 |
* correspondance between
pseudo/email contacts |
|||
| 24
may 2005 |
------------------------------------------------------ Invitation feature to add ------------ * add the inviter's pseudo to the contact of the invited person. |
|||
| 25
may 2005 |
------------------------------------------------------ Language Bug + Problem with forum ------------------------------------ * question "Do you want the user you" disturbing ==> better not ask any question ==> not display the invitations table to anyone except admin. ==> admin can configure the forum to show this table, either for all those who can read, or all those who can write, or only for admins. |
|||
| 25
may 2006 |
Webmail BUG --------- http://trust-forum.php.by/index.php?action=sendmail&dest=anita.lice@gmail.com&ispseudo=Y Notice: Undefined variable: languages in /h/phpby/htdocs.trust-forum.php.by/webmail/compose.php on line 164 |
|||
| 26
May 2005 |
========================================== Forum and dating --------------------------------------------------------------------------- * Language Bug + Problem with forum * display the invitations table to anyone except admin. * best --> admin can configure the forum to show this table, either for all those who can read, or all those who can write, or only for admins. * I would like to offer another solution. The idea is to detach an interface of the invitation to another page (Another Page). An only link "invite smb to this forum" on the page of the forum would have led to the Another Page. On the Another Page I would have placed: - a choice of pseudo to invite - a choice of access level to invite to - a choice of whether to allow the person view the invitations table if: - an inviter has this right or - access level is "A" (admin) As I see, if we decide to act like I described: - We do not lose the existing flexibility - We avoid an excessive tightness on the forums page - We make an inviting process more clear and visual - We get an interface without annoying messages - I don't need to make significant alterations into the database structure (actually, I don't need to make any) What do you think of this? --------------------------------------------------------------------------- 1 Language Bug + Problem with forum 2 One more language bug 3 A few bugs with datings ========================================== ------------------------------------------------------------------------------------------------ * add "Not member of trusted forum" in the My Comment field of contacts for new emails ==> Better would be to input the My Comment from user together with email address. ------------------------------------------------------------------------------------------------ * enter comment after entering of the email. * add manually emails to the pseudos * When I deleted then the line of email without pseudo, ==> the line of email with pseudo disappeared. ==> Then I wanted to add again the email to the pseudo, and the email was added to another pseudo ------------------------------------------------------------------------------------------------ * add/change/delete of pseudos and emails. * I have the email anita.lice@gmail.com written in the line of jamila (first line) whereas the (second) line of anita has blank email * update the line of jamila I find fields blank whereas when I update the line of anita I find the email anita.lice@gmail.com with it. ------------------------------------------------------------------------------------------------ * correspondance between my pseudo contacts and my email contacts ? ------------------------------------------------------------------------------------------------ * Invitation feature to add * add the inviter's pseudo to the contact of the invited person. ------------------------------------------------------------------------------------------------ * Contact is added to the inviter and invited during the registration of the new pseudo. |
|||
| 26
may 2005 |
* dating system * forum * invitations system * 3 things about contacts: - invited by email user has registered, ---> "Add invitation" line to disappear from the page "Compose new message" by the inviter to him. - display in contacts whether an invitation has been sent or not, before registration of course (since once registered it shoud be visible by the display of the pseudo in that line) ==> not very clear. - contacts list ==> alphabetical / chronological order. -----end of copy------- |
|||
| 27
may 2005 |
========================================== Forum and dating --------------------------------------------------------------------------- Language Bug + Problem with forum *question "Do you want the user you" bizarre - display the invitations table only to admin - admin can configure the forum to show this table ~~~~> for all those who can read ~~~~> all those who can write ~~~~> only for admins. * another solution. - interface of the invitation to another page - link "invite smb to this forum" (forum) --> Another Page with - a choice of pseudo to invite - a choice of access level to invite to - choose to allow the person view the invitations table if: - an inviter has this right or - access level is "A" (admin) * make functions of Another Page ==> Forum Info and/or invitations table pages itself instead of being to an isolated page --------------------------------------------------------------------------- 1 Language Bug + Problem with forum 2 One more language bug 3 A few bugs with datings *width of forum adapt to the window |
|||
| 27
may 2005 |
* Another Page as a pop-up. * forum info page h: the access by button and not by link --> not in new window ===> make a link |
|||
| 28
may 2005 |
* relation between the emails/
pseudos chosen in their invitations in my contacts, or was this info stored? |
|||
| 29
may 2005 |
*GLS *forums * dating in networks |
|||
| 30
may 2005 |
* GLS * forums * dating |
|||
| 30
may 2005 |
* comment2 of forum characters ( example '...) * language file You were succesfully registered in the system. * add manually emails to the pseudos - delete e line of email without pseudo --> the line of email with pseudo disappear - add email to pseudo --> email added to another pseudo ------------------------------------------------------------------------------------------------* add/change/delete of pseudos and emails * email anita.lice@gmail.com written in jamila linw # the (second) line of anita has blank email - update the line of jamila --> fields blank # update anita line --> anita email ------------------------------------------------------------------------------------------------* correspondance between my pseudo contacts / my email contacts ------------------------------------------------------------------------------------------------ * relation between email and pseudo to be visible in the contact list: - invite someone by email and this person registers by this invitatio --> his pseudo to appear to the same line as the email. - the pseudos of invited people appeared to new lines in contacts and I could not deduce from it who it was. - invited users (pseudos) appear in contacts list in the lines of the corresponding emails * add inviter's pseudo to invited person's contact. ------------------------------------------------------------------------------------------------* Contact is added to the inviter and invited during the registration of the new pseudo. |
|||
| 31
may 2005 |
* correspondance between my pseudo/contacts and my email contacts ------------------------------------------------------------------------------------------------ *table of invitations by email: Random number | Inviter | Invited email. * An entry added ( invitation by email sent) - random number modified if the same inviter sends again invitation to the same email (or it would also be OK if you keep the same random number and re-send it identically) * invitation URL = the random number ( ==> other data found by it from this table) * OK if contains other data (random number same in table) *table checked ---> coherence between random number and other data ==> including other data in the URL is useless. * new user posts registration form -corresponding entry in the above table is deleted -new pseudo is added to the inviter's contacts on the line of the invited email. * by which email I invited each of the 3 new members : orvils - aija avotinja - mors * entry page with login bar + public forums list: public forum have name -->are clickable |
|||
| Mer 1 juin 2005 |
- PWP. |
|||
| Mer 1 juin 2005 |
Webmail - fixed. - In comment2 of forums, I tried to correct where there was ' character but antislashes remain - Displaying comparison of translations I still see 46. You were succesfully registered in the system. Don - The width of forums does not yet fit with the with of window: it still makes one line per paragraph, whatever the length of the paragraph. |
|||
| Mer 1 juin 2005 |
-PWP.: organized into groups
where in each group are files with the same rights. For example we can
make directories like http://domain.com/directory/ and in each
directory are files with the same rights.Unless: I wonder: maybe a
group should be of the pages with same editing rights, but reading rights can differ from a page to another. So: first the user creates a group with a given rights system. The simplest, that can be the only one in the short term and it will be OK for now, is that it is personal: only one person can edit it. Another one is to re-use the system of forum rights for this task: there will be rights to read and edit as there was right to read and write. Then the question is to have one or several methods of text editing. One method would be the upload of an html file, in hope that there are not unsecure functionalities. Another would be bare text but I’m not sure it is interesting enough.But I think anyway we should re-use much of what already exists as wiki systems. Are there wikis with included images ? If not, we should add the possibility of images.Wiki systems include text editing methods, and also a system of headers with history. It is good to have headers and history, we will take them and complete the headers (and links) to fit with our GLS and bookmarks system. For the case of a personal page, the headers must contain the pseudo of author. - After that, it may be interesting to have the function to convert pages from a format to another (between html and wiki-type conventions, for example). - In the future--> to have an online TeX compiler: to edit a TeX file in my account from an internet cafe, save it to server, then run pdftex on server and get the resulting pdf file... |
|||
| Jeu 2 juin 2005 |
Webmail |
|||
| Dim 5 juin 2005 |
- trust system. - internal computation than about web, it will be worth trying another language. - forum+invitations+dating+GLS+PWP -f dating, GLS and PWP. |
|||
| Ven 10 juin 2005 |
- testing the GLS Links: http://tforum1.php.by/gls/ http://tforum2.php.by/gls/ http://tforum1.php.by/ http://tforum2.php.by/ |
|||
| Ven 10 juin 2005 |
-the documentation I wrote for users http://spoirier.lautre.net/en/userdoc.htm - GLS allow users to move their account from a site to another: first create a remote login, then let the first home site accept the new one as an authentication of the user, then copy or move folders. - dating system can work in a remote site, so that it needs not be moved with account. - admin installed the system without dating, users can still create a remote dating file using bookmark to some host that offers the hosting of such dating files for people deprived of this right by their admin. |
|||
| Dim 12 juin 2005 |
Here is the list of what's left to do with forums: 2. create link from the system's documentation page to http://spoirier.lautre.net/userdoc.htm 3. Let the forum's admin rename a forum. Q: When the forum's admin renames a forum, are these changes seen by people who: a. (if it's a public forum:) is already registered, or by only those who will be registered in future? b. (if it's a private one:) is already invited, or by only those who will be invited in future? I think it would be good not to rename this forum for users who ever viewed this forum. Because forum's name is an only thing the forum can be identified with. So people can just loose it. But doing as I said will cause database very quick pollution (concerning public forums only!). So what if renaming a public forum will apply to everybody immediately (except for those who already renamed the forum manually)? Concerning private forums I offer to do it the way I said. 5. GLS. GLS is almost finished. In a few days I'll review it and maybe some corrections will be necessary to be made. But there will be no significant ones. 7. Let the forum's admin place a custom link on top of each thread. 9. You asked me to make possibility to deny guests to write to public forums. But this possibility already exists. Admin of a public forum has to go to "edit forum rights" and deny to write to Guest ("Guest" is entered manually into the input area). 10. Correct the bug: In comments to forum, ' is displayed like \'. 11. Make help not only for people who have already logged in but for even everyone who hasn't registered yes. 12. Correct one more bug with "....Don'". 6. After this, go to http://help.berberber.com and ask for help with translating 14. Mova a part where one invites somebody to the forum to either the info page of the forum or to a new popup window. 15. Deny creating forums without names: In future I shall anyway develop a validator: there are many fields where we should take care of validness of input data. It may be written only after everything else is done. So is it very significant now? 16. Disallow forum windows to widen too much. ----------- Situation concerning datings. 1. Find a list of real nationalities, countries, languages, etc. 2. Exclude silly labels like ROOT_1, southpole11, etc. 3. Badness numbers mustn't be so large 4. In badness criteria, instead of: Below x1: [input] From x1 to x2: [input] From x2 to x3: [input] Above x3: [input] , why isn't actual variant enough? Except for "Below x1" anybody can put "From 0 to x1" and execpt for "Above x3" anybody can put "From x3 to 10000". Moreover, there is an input field for "other cases". -------------- This is a list of what's left to be done. After GLS is done, there'll be another significant task of integrating GLS to existing system. The most simple things (such as bugs with the ' symbol) will be done in a few days, maybe tomorrow or the day after tomorrow. I have three exams left in the university so I need to spend time on preparations also. If I forgot something in the actual list, please remind me. And please answer the questions above. |
|||
| Lun 13 juin 2005 |
12. Correct one more bug with "....Don'". (making language files properly encoded for display and translations) 16. Disallow forum windows to widen too much. 10. Correct the bug: In comments to forum, ' is displayed like \'. 2. create link from the system's documentation page to http://spoirier.lautre.net/userdoc.htm 11. Make help not only for people who have already logged in but for even everyone who hasn't registered yet. 14. Mova a part where one invites somebody to the forum to either the info page of the forum or to a new popup window. 3. Let the forum's admin rename a forum. Q: When the forum's admin renames a forum, are these changes seen by people who:> a. (if it's a public forum:) is already registered, or by only those who will be registered in future? b. (if it's a private one:) is already invited, or by only those who will be invited in future? I think it would be good not to rename this forum for users who ever viewed this forum. Because forum's name is an only thing the forum can be identified with. So people can just loose it. - database pollution (concerning public forums only!). - So what if renaming a public forum will apply to everybody immediately (except for those who already renamed the forum manually)? I do not see what big problem there is here. Each forum has a first name, then a custom name. At first use, the custom name is defined as a copy of the first name. Then the first name can be changed by admin but the custom name stays unchanged. 15. validness of input data. 6. After this, go to http://help.berberber.com and ask for help with translating 7. Let the forum's admin place a custom link on top of each thread. - Dating (details later) - Gls |
|||
| Lun 13 juin 2005 |
4. In badness criteria, instead of: Below x1: [input] From x1 to x2: [input] From x2 to x3: [input] Above x3: [input] the problem is that x2 is written twice in this list, the same for x2 etc. I wonder how you manage this. Must the user retype the value by hand ? If he does not do it, how is it interpreted ? What if he typed silly things like: from 1 to 4: from 3 to 5: ??? What is the value is exactly x2 ? If the value appeared only once and it is automatically interpreted as being reused. why isn't actual variant enough? Except for "Below x1" anybody can put "From 0 to x1" and execpt for "Above x3" anybody can put "From x3 to 10000". Moreover, there is an input field for "other cases". |
|||
| Sam 2 juillet 2005 |
1. GLS 12. Correct one more bug with "....Don'". (making language files properly encoded for display and translations) - make the forum at trust-forum.php.by actually running as it was before. 16. Disallow forum windows to widen too much. 10. Correct the bug: In comments to forum, ' is displayed like \'. 2. create link from the system's documentation page to http://spoirier.lautre.net/userdoc.htm 11. Make help not only for people who have already logged in but for even everyone who hasn't registered yet. 14. Mova a part where one invites somebody to the forum to either the info page of the forum or to a new popup window. ================================================================== 07/05/2005 ================================================================== 3. Let the forum's admin rename a forum. Q: When the forum's admin renames a forum, are these changes seen by people who: a. (if it's a public forum:) is already registered, or by only those who will be registered in future? b. (if it's a private one:) is already invited, or by only those who will be invited in future? I think it would be good not to rename this forum for users who ever viewed this forum. Because forum's name is an only thing the forum can be identified with. So people can just loose it. --> database very quick pollution> (concerning public forums only!). So what if renaming a public forum will apply to everybody immediately (except for those who already renamed the forum manually)? - Each forum has a first name, then a custom name. At first use, the custom name is defined as a copy of the first name. Then the first name can be changed by admin but the custom name stays unchanged. ================================================================== 07/06/2005 ================================================================== 15. Deny creating forums without names: In future I shall anyway develop a validator: there are many fields where we should take care of validness of input data. Now it is a problem that if forum has no name, it cannot be entered. 6. After this, go to http://help.berberber.com and ask for help with translating 7. Let the forum's admin place a custom link on top of each thread. ================================================================== 07/07/2005 ================================================================== - Dating (details later) - Gls 4. In badness criteria, instead of: Below x1: [input] From x1 to x2: [input] From x2 to x3: [input] Above x3: [input] the problem is that x2 is written twice in this list, the same for x2 etc. Must the user retype the value by hand ? If he does not do it, how is it interpreted ? What if he typed silly things like: from 1 to 4: from 3 to 5: ??? What is the value is exactly x2 ? If the value appeared only once and it is automatically interpreted as being reused. why isn't actual variant enough? Except for "Below x1" anybody can put "From 0 to x1" and execpt for "Above x3" anybody can put "From x3 to 10000". input field for "other cases". |
|||
| Dim 3 juillet 2005 |
- list of operations to be done to translations. bug : disappearing of the interface words by editing the translation and changing the version number (first step below). translations system: - No more editing of an existing translation. - The "Add new translation, based on selected one (left)" should be replaced by "Add new translation, seeing selected left translation, with fields filled with selected right translation" (blank fields if none). Problem: some fields have to be not blank because there will be links on these words. Make an error message if blank ? Or accept it but disable selecting it for use ? It may be useful to allow for a partial translation as a first work that can be completed later or by other people into a usable version. - The author of a translation can choose to let his translation public or not. If not, only him can see it in his list of tranlations. If public and someone else is using it, then made private, no problem to continue using it, in order to not create a bug. |
|||
| Lun 4 juillet 2005 |
================================================================== 07/03/2005 ================================================================== 1. GLS GLS can come last, with PWP. The url is rather http://spoirier.lautre.net/en/userdoc.htm |
|||
| Lun 4 juillet 2005 |
================================================================== 07/03/2005 ================================================================== 1. GLS 12. Correct one more bug with "....Don'". (making language files properly encoded for display and translations) I hope you do not forget: make the forum at trust-forum.php.by actually running as it was before. For now, it is a big bug so that one cannot even enter anything. |
|||
| Mer 6 juillet 2005 |
================================================================== 07/03/2005 ================================================================== 1. GLS 12. Correct one more bug with "....Don'". (making language files properly encoded for display and translations) 16. Disallow forum windows to widen too much. 10. Correct the bug: In comments to forum, ' is displayed like \'. 2. create link from the system's documentation page to http://spoirier.lautre.net/userdoc.htm 11. Make help not only for people who have already logged in but for even everyone who hasn't registered yet. 14. Mova a part where one invites somebody to the forum to either the info page of the forum or to a new popup window. ================================================================== 07/05/2005 ================================================================== 3. Let the forum's admin rename a forum. Q: When the forum's admin renames a forum, are these changes seen by people who: a. (if it's a public forum:) is already registered, or by only those who will be registered in future? b. (if it's a private one:) is already invited, or by only those who will be invited in future? I think it would be good not to rename this forum for users who ever viewed this forum. Because forum's name is an only thing the forum can be identified with. So people can just loose it. But doing as I said will cause database very quick pollution (concerning public forums only!). So what if renaming a public forum will apply to everybody immediately (except for those who already renamed the forum manually)? Concerning private forums I offer to do it the way I said. - Each forum has a first name, then a custom name. At first use, the custom name is defined as a copy of the first name. Then the first name can be changed by admin but the custom name stays unchanged. ================================================================== 07/06/2005 ================================================================== 15. Deny creating forums without names: In future I shall anyway develop a validator: there are many fields where we should take care of validness of input data. - forum has no name, it cannot be entered. 6. After this, go to http://help.berberber.com and ask for help with translating 7. Let the forum's admin place a custom link on top of each thread. ================================================================== 07/07/2005 ================================================================== - Dating (details later) - Gls 4. In badness criteria, instead of: Below x1: [input] From x1 to x2: [input] From x2 to x3: [input] Above x3: [input] the problem is that x2 is written twice in this list, the same for x2 etc. I wonder how you manage this. Must the user retype the value by hand ? If he does not do it, how is it interpreted ? What if he typed silly things like: from 1 to 4: from 3 to 5: ??? What is the value is exactly x2 ? If the value appeared only once and it is automatically interpreted as being reused, I think it is clearer. , why isn't actual variant enough? Except for "Below x1" anybody can put "From 0 to x1" and execpt for "Above x3" anybody can put From x3 to 10000". Moreover, there is an input field for "other cases". |
|||
| Mer 6 juillet 2005 |
http://trust-forum.php.by
updated. |
|||
| Mer 6 juillet 2005 |
make the forum at trust-forum.php.by - translations page once again |
|||
| Jeu 7 juillet 2005 |
1) Pubilc forums 2) Invitations to a forum |
|||
| Jeu 7 juillet 2005 |
1) Pubilc forums 2) Invitations to a forum |
|||
| Jeu 7 juillet 2005 |
backup problems |
|||
| Jeu 7 juillet 2005 |
- Not found "Add email to contact list", only "add pseudo" ! |
|||
| Ven 8 juillet 2005 |
- Window to edit an invalid message is much too small. - The number of "new" messages in forum should not be the number of old ! |
|||
| Ven 8 juillet 2005 |
- add invitation to a email sent. |
|||
| Ven 8 juillet 2005 |
Window to edit an invalid message is much too small. |
|||
| Ven 8 juillet 2005 |
The number of "new" messages in forum should not be the number of old ! |
|||
| Sam 9 juillet 2005 |
correction of email in contact list: - "add email to contact list" - add invitation to email - invitation tree. |
|||
| Dim 10 juillet 2005 |
- admin of public forum can invite someone to admin right ? So the rights system should be in 2 parts: invitations and denyence. As well for public as for private forums, the difference being that the list of rights to invite to is different. |
|||
| Lun 11 juillet 2005 |
Hello. To improve the system of writing and validating messages, here are some ideas (new interface keeping the same database structure): - When editing an invalid message I expected to edit also the message title. I see it is not the case now. - I propose that for writing new message as well as for editing invalid one, instead of one button to click with checkbox to valid, there will be three buttons to click: * Save: the message is stored invalid * Preview: same as save and reedit in the same screen. The thread is displayed, with the edited message (in another color ?) with links "Delete" - "Mark valid" only. On the bottom is again the edited message under the sentence "Reedit message:". * Post: same as save and mark valid. |
|||
| Mar 12 juillet 2005 |
-delete the messages in the public forum "Philosophie scolaire". system of sensorship (another kind of invalid marking) where admin can sensor a message and an author of message can also self-sensor his message, and people can visit the forum in 2 ways: sensored or unsensored. --> In unsensored mode, the sensored messages would appear in another color, with mention "Self-sensored" or "sensored by admin". - possible to completely delete the messages by Guest. - same message appears twice. Is there another explanation than the idea he copied-pasted his message ? There should be a kind of id of edited message so that the same messaege posted twice would only appear once. |
|||
| Mar 12 juillet 2005 |
-delete the messages in the public forum "Philosophie scolaire". Or, I think about a more spohisticated system of sensorship (another kind of invalid marking) where admin can sensor a message and an author of message can also self-sensor his message, and people can visit the forum in 2 ways: sensored or unsensored. In unsensored mode, the sensored messages would appear in another color, with mention "Self-sensored" or "sensored by admin". But anyway it should be possible to completely delete the messages by Guest. So anyway you can implement this deletion right now. Here the same message appears twice. Is there another explanation than the idea he copied-pasted his message ? There should be a kind of id of edited message so that the same messaege posted twice would only appear once. |
|||
| Mer 13 juillet 2005 |
GLS http://tforum1.php.by/gls and http://tforum2.php.by/gls. login at http://tforumX.php.by/gls you are immediately redirected to http://tforumX.php.by. SO now after logging in you have to go to http://tforumX.php.by/gls by hand. You may pay attention on "Bookmarks", "Default bookmarks" and "Congiguration" -"Common settings". - messages and admins of public forums - Datings |
|||
| Mer 13 juillet 2005 |
- versions - dating - GLS |
|||
| Jeu 14 juillet 2005 |
- GLS http://tforum1.php.by/gls and http://tforum2.php.by/gls. But please be careful: When you login at http://tforumX.php.by/gls you are immediately redirected to http://tforumX.php.by. - asking for contacts. SO now after logging in you have to go to http://tforumX.php.by/gls by hand. You may pay attention on "Bookmarks", "Default bookmarks" and "Congiguration"-"Common settings". - on each line is first the host (why a link on it ?) then the particular page to access there. But for "edit" I did not see anything interesting. What I think can be edited is the pseudo used, and preferred language. |
|||
| Jeu 14 juillet 2005 |
- system of invitations to forums: it must be in 2 parts as well for public as private forums: - Invitations system, where a user with a right invites someone else to at most the same right. Admin should not have any specific interface to modify this. - Denyance system: edited by admin. |
|||
| Ven 15 juillet 2005 |
* bookmarks and default bookmarks ? Ok. From the beginning there were bookmarks only (no default bookmarks). The user could click any of them to open session to a corresponding server. When the user registers, he has no bookmarks so we decided to add "default bokomarks" page where bookmarks to main pages of all the registered in the system servers would be listed. There the user has an option to add a "default" bookmark to his own list. Ok. > What is precisely the role of the /gls/ directory ? A developer of GLS didn't want to modify existing code so he placed everything he developed into a /gls/ directory. When I said I would integrate GLS into the system, I meant to move everything to root so that there would be an only login page (now there are two: in / and in /gls/). ========== - system of invitations to forums: for public as private forums: - Invitations system, where a user with a right invites someone else to at most the same right. Admin should not have any specific interface to modify this. - Denyance system: edited by admin. ========== - delete the messages in the public forum "Philosophie scolaire". Or, I think about a more spohisticated system of sensorship (another kind of invalid marking) where admin can sensor a message and an author of message can also self-sensor his message, and people can visit the forum in 2 ways: sensored or unsensored. In unsensored mode, the sensored messages would appear in another color, with mention "Self-sensored" or "sensored by admin". |
|||
| Ven 15 juillet 2005 |
- GLS http://tforum1.php.by/gls http://tforum2.php.by/gls. http://tforumX.php.by/gls you are immediately redirected to http://tforumX.php.by. SO now after logging in you have to go to http://tforumX.php.by/gls by hand. You may pay attention on "Bookmarks", "Default bookmarks" and "Congiguration"-"Common settings". - difference between bookmarks and default bookmarks ? - Every time you have to choose details concerning the result for the user that are not obvious, please tell me so that I can tell if it fits or not.What is precisely the role of the /gls/ directory ? |
|||
| Ven 15 juillet 2005 |
- GLS integrate 2 tforum.php.by but not yet to trust-forum.php.by |
|||
| Sam 16 juillet 2005 |
-admin can delete a message - delete the messages in the public forum "Philosophie scolaire". system of sensorship (another kind of invalid marking) where admin can sensor a message and an author of message can also self-sensor his message, and people can visit the forum in 2 ways: sensored or unsensored. In unsensored mode, the sensored messages would appear in another color, with mention "Self-sensored" or "sensored by admin". |
|||
| Sam 16 juillet 2005 |
interface will be integrated to info page of users and contacts list, later it will be used in forums, but the important part is internal calculation, and some exchange of data by GLS). |
|||
| Sam 16 juillet 2005 |
- public , private forums ==> invitations and denyence systems. - Does adding a pseudo to a black list mean blacklisting of this pseudo only, while an owner of this pseudo can still access a forum under another one? OK private forums (to preserve anonimity), but for public ones the user can always use another of his pseudos to access a forum, so there should be imlemented another meaning of blacklisting: complete blacklisting of the user BY blacklisting one of his pseudos. =================================================================== And one more question: - on private forums users can invite to R, W, A - on private forums admins can deny to R, W, A - on public forums users can invite to A - on public forums admins can deny to R, W Is it so? =================================================================== - every forum has its allowed by default list of actions (now there are only forums allowing to write and allowing nothing by default). These actions can be nothing, R, W. On every forum there is a system of invitations to a higher than the default right and a denyence of all rights. So I think, maybe there should also be forums which would allow to Read by default but allow noone to write without an invitation. It reminds an interview: a few ppl can ask while everybody's listening. |
|||
| Sam 16 juillet 2005 |
- difference between bookmarks and default bookmarks ? beginning: bookmarks only (no default bookmarks). user could click any of them to open session to a corresponding server. When the user registers, he has no bookmarks so we decided to add "default bokomarks" page where bookmarks to main pages of all the registered in the system servers would be listed. There the user has an option to add a "default" bookmark to his own list. - A home account is a sort of personal virtual browser. Every browser has its set of bookmarks which can be modified by user. When an organisation (Microsoft, Mozilla) distributes a browser, it comes with a default set of bookmarks.Not a bad idea of course. However, it would make no sense to let this default bookmarks list be the list of all registered domains of the web. One can as well distribute a browser with no default bookmarks at all. Indeed, the user has no problem visiting the web by inputting URLs by hand, or using search engines or directories.Indeed a directory is just a web site like any other. So we can make later directories of interesting bookmarks in the form of a wiki like any other.Indeed, when PWP(wiki) will be ready, the Help link will lead to a PWP, edited like any PWP by some people. This help page can contain bookmarks to other pages. This can be understood as a sort of list of default bookmarks. In some future, I dream of distributing a Trust-forum friendly browser software (or plug-in to an existing browser). This new brower will automatically switch its interface language into the user's language when user logs in to his home site, and download the user bookmarks to put in the place of browser bookmarks. We can continue conversation in forum. Please create threads: - "Forum" thread - "Dating" thread - "GLS" thread - "Other" thread |
|||
| Dim 17 juillet 2005 |
- public , private forums ==> invitations and denyence systems. - Does adding a pseudo to a black list mean blacklisting of this pseudo only, while an owner of this pseudo can still access a forum under another one? - forums will be remotely accessed trough GLS which only reveals to the forum's site one pseudo of the user, it would be impossible to automatically blacklist the whole user except if the home host cooperates to this (operates the blacklisting itself). But to access the private forum trough another pseudo, he needs another invitation. He may have invited himself but the admin can see the invitations table and choose to blacklist other pseudos invited by the blacklisted user. - it should be so for private forums (to preserve anonimity), but for public ones the user can always use another of his pseudos to access a forum, so there should be imlemented another meaning of blacklisting: complete blacklisting of the user BY blacklisting one of his pseudos. =================================================================== And one more question: - on private forums users can invite to R, W, A - on private forums admins can deny to R, W, A - on public forums users can invite to A - on public forums admins can deny to R, W Yes: on private forums admins can deny to R, W. - admin right can be lost only by resign if there is another admin. =================================================================== Hm. Now I think that if we generalize this, we can get another scheme: every forum has its allowed by default list of actions (now there are only forums allowing to write and allowing nothing by default). These actions can be nothing, R, W. On every forum there is a system of invitations to a higher than the default right and a denyence of all rights. ==> forums which would allow to Read by default but allow noone to write without an invitation. It reminds an interview: a few ppl can ask while everybody's listening. - PWP - possibility for admin to simply delete a message. - revised interface for editing and validating messages - rights system (same priority as dating). |
|||
| Lun 18 juillet 2005 |
- tested the registration But this way I created a useless account. - need the function for the system admin to delete an account (to get rid of spammers...). |
|||
| Lun 18 juillet 2005 |
- Unified version, that is, with a working contacts and invitations sytem where the new pseudo appears on the line of the email used for invitation - Let forum admin delete messages in forum with ask for confirm - Let this invitation be secure (must not work if we write another inviter or change the random number in the URL) -forum invitations system - interface of editing/validating (save/preview/post). - dating should work with GLS and PWP - webmail is not complete either - replacement for full webmail, I have an idea to make conversations possible by forum with unregistered people who only have an email address: send them email with the text of message and a GLS link in the body of message, by which they can visit the forum and reply. |
|||
| Lun 18 juillet 2005 |
- after timout the session is lost so the server forgot who the user is, I consider the following solution: Let the posting after timeout open a new session where the user is asked to login again. If he does, the operation (save, preview or post) is accomplished. If he does not, the message is lost. (This solution also protects from spam of false postings that could masquerade as posting after timeout). |
|||
| Mar 19 juillet 2005 |
have fixed following things: - editing title of message - deleting messages by admin (editing, also) - bug with posting a message after session timeout - posting the a message twice now we are working on invitations of admins of public forums and another presentation of managing messages (save-preview-post) concerning unification of versions: we have troubles with it, some things still don't work. We think, it'll be done by tomorrow's evening. |
|||
| Mar 19 juillet 2005 |
- editing title of message - deleting messages by admin (editing, also) - bug with posting a message after session timeout spammers maskerade as another user posting messages after timeout to put plenty of invalid messages for him in his forums ? - posting the a message twice - now we are working on invitations of admins of public forums and another presentation of managing messages (save-preview-post) |
|||
| Mer 20 juillet 2005 |
- add invitation to composed message. - capability of invitations can be forbiddened by admin. f.e., login as "grisha" "grisha", who is an admin. from his problem list, you can see every user("get list"), and check his ability of inviting. |
|||
| Jeu 21 juillet 2005 |
- add invitation to composed message. - capability of invitations can be forbiddened by admin. f.e., login as "grisha" "grisha", who is an admin. from his problem list, you can see every user("get list"), and check his ability of inviting. -admin right to the system (or login/pass of an admin). (I tried login:grisha pass:grisha and it does not work). |
|||
| Jeu 21 juillet 2005 |
- add invitation by email is not coherent with my possibility to invite by inside account |
|||
| Sam 23 juillet 2005 |
- translation, then you make a new update that uses a new version of language file ? Would the translation be lost ? |
|||
| Dim 24 juillet 2005 |
- trust-forum.php.by- |
|||
| Dim 24 juillet 2005 |
-browser (an IE) with reduced functionalities - link "Add new translation, based on selected one" - link Unsubscribe a forum in a folder |
|||
| Lun 25
juillet 2005 |
- email invitations system (with invited new login appear to the contact on the line of email) - trust system - contacts system. - in network with GLS ? - PWP ? |
|||
| Lun 25
juillet 2005 |
- translations system working - invitations system working. |
|||
| Mar 26
juillet 2005 |
my task consists of: 1 Language Bug + Problem with forum 2 One more language bug 3 A few bugs with datings - email invitations system |
|||
| Mer 27
juillet 2005 |
- email invitations system |
|||
| Jeu 28
juillet 2005 |
- possibility to invite an email to a forum.I just mentioned it in the public forum of trust-forum. - its interference with the valid/invalid messages, as a valid message sent by email cannot be made invalid anymore. |
|||
| Ven 29 juillet 2005 2 |
1. trust-forum.php.by . 2. Invitations & webmail. 3. GLS. tforum1.php.by/gls tforum2.php.by/gls. 4. Forums. - system of invitations to forums: it must be in 2 parts as well for public as private forums: - Invitations system, where a user with a right invites someone else to at most the same right. Admin should not have any specific interface to modify this. - Denyance system: edited by admin. - translations. - Datings : connect list of nationalities, countries and unite with GLS. 6. PWP. |
|||
| Sam 30 juillet 2005 |
1. trust-forum.php.by . 2. Invitations & webmail. no checkbox in composing message : "Add invitation ?" 3. GLS. tforum1.php.by/gls and tforum2.php.by/gls. - not mix user1@tforum1 visiting tforum2 with the user1 of tforum2 ? I find it not normal to see "Usermenu (user1). It should be "user1@tforum1". But there should be no usermenu in the final version 4. Forums. - system of invitations to forums: in 2 parts as well for public as private forums: - Invitations system, where a user with a right invites someone else to at most the same right. Admin should not have any specific interface to modify this. - Denyance system: edited by admin. * rights system. - invitations, admin editing and deyances 5. Datings. connect list of nationalities, countries and unite with GLS. There should be 2 independent questions (handled in the same table for display commodity): one is where to meet, the second is where to live in the long term, in case it is for long relationship or marriage. So that is two common badnesses to be independently minimised on the set of all places. - The "badness value" column refers to first meeting and should be called "badness value for first meeting", and "Badness value if: Would have income there" should be 3 columns in the geographical table. ---- Also, the intervals should be revised so that they adjust automatically the end of each with the start of the next (to type only once), without "other". |
|||
| Dim 31 juillet 2005 |
- email invitations system - including instructions for installation - integrating forums which is not done yet. - rights system - inviting an email address to a forum. --> calculating transitive relation generated by a given relation (as explained in public forum "Trust system" ? - finish dating system (up to later modification by adding new/modifying parameters in the scheme of existing ones) - PWP. |
|||
| Lun 1 août 2005 |
2. Invitations & webmail. -my inviting right was denied by system admin. - I need to have a login/pass of a system admin to see how it works - Anyway I need inviting right to test how it works - If someone is denied right to invite, he should not invite by inside account either. |
|||
| Lun 1
août 2005 |
2. Invitations & webmail. - I need to have a login/pass of a system admin to see how it works - Anyway I need inviting right to test how it works - If someone is denied right to invite, he should not invite by inside account either. |
|||
| Lun 1
août 2005 |
- release of GLS |
|||
| Mer 3 août 2005 |
- security: should not work with wrong random number or inviter ? |
|||
| Ven 12 août 2005 |
- GLS - dating - PWP |
|||
| Ven 12 août 2005 |
- todo page: http://spoirier.lautre.net/tf-todo.htm |
|||
| Ven 12 août 2005 |
GLS - dating - PWP |
|||
| Sam 13 août 2005 |
-the Save-Preview-Post interface |
|||
| Ven 12 août 2005 |
ttp://spoirier.lautre.net/tf-todo.htm |
|||
| Dim 14 août 2005 |
http://spoirier.lautre.net/tf-todo.htm |
|||
| Lun 15 août 2005 |
- http://spoirier.lautre.net/tf-todo.htm and - inviting email to forum ( substitute for the full webmail-invitations ), new forum rights, new folders system. (the integrating GLS to forum is seen as part of GLS task). (note: in orders of priority, the inviting email to forum is priority before the integrating GLS) |
|||
| Lun 15 août 2005 |
http://spoirier.lautre.net/tf-todo.htm
- inviting email to forum : ~ full webmail-invitations - new forum rights - new folders system - integrating GLS to forum |
|||
| Lun 29 août 2005 |
- Webmail/Invitations system. |
|||
| Mar 30 août 2005 |
Working plan: 1. Forum system a) New interface for posting/editing messages: Save-Preview-Post Now a new message can be stored valid or invalid according to checkbox "mark valid". It would be better to have 3 possibilities, and a different button to click for each, that would appear as well for a new message as for editing an existing invalid message: Save: store the message invalid (and display resulting thread with new message in the bottom) Preview: save and reedit message in the same screen Post: save and mark valid. b) New forum rights system Already done: So, 3 possible types of forums: - Default access =none : private forum - Default access = read (guest access = none or read): semipublic forum - Default access = write (guess access = none, read or write): public forum. It is needed to make possibility of adding admin rights for the Public forum's users. 2. Integration of GLS to forums system 3. Some modifications have to be made to the dating system... - dating system. |
|||
| Ven 2 septembre 2005 |
Please explain: -------------------------- As we understand, we need to add to the Rights System the possibility for the User which created Public Forum to invite admins, and to delete each other for the invited by admin. The question is: Should the admin be possible to delete inviter from the topic's admins list? |
|||
| Ven 2 septembre 2005 |
- Rights System the possibility for the User which created Public Forum to invite admins, and to delete each other for the invited by admin. - The question is: Should the admin be possible to delete inviter from the topic's admins list? 1) Any admin can invite another user as admin 2) Denial cannot be made against existing admins, except : * if done by forum creator against another admin, or * if done by another admin against himself (resign) 3) There will always be only one Forum creator, but he can resign and give this title to another admin. In this situation, a user that is not admin can be denied by an admin. Then another admin cannot directly invite this person as admin (it would be unefficient) but can do it anyway after cancelling the denial. Note: the implementation of point 3) is not necessary in the short term |
|||
| Ven 2 septembre 2005 |
Rights System : User (
created Public Forum) can invite admins, and delete each other for the invited by admin. - The question is: Should the admin be possible to delete inviter from the topic's admins list? 1) Any admin can invite another user as admin 2) Denial cannot be made against existing admins, except : * if done by forum creator against another admin, or * if done by another admin against himself (resign) 3) There will always be only one Forum creator, but he can resign and give this title to another admin. In this situation, a user that is not admin can be denied by an admin. Then another admin cannot directly invite this person as admin (it would be unefficient) but can do it anyway after cancelling the denial. |
|||
| Lun 5 septembre 2005 |
1. Save, Preview, Post for forum messages. 2. Changes in the Rights System Resign from admin rights, - Forum's creator have admin's rights independently from the Rughts Systems. Who will be the owner of the rights if the admin wants to make Resign? That's why he can't resign until he gives owner right to someone else (and loses his). OR, if it is a private forum where there is nobody else with right to the forum (they all resigned already), then the creator can delete the forum. In case of public or semi-public forum, I wonder if it makes sense to delete it... anyway, even a resign from such forum, if you ever defined it, would only be resign from supplementary rights and keeps the possibility to access the forum (except in case of reading denial). |
|||
| Lun 5 septembre 2005 |
1. Save, Preview, Post for forum messages. I just had a look. Not exactly as I expected. Instead of <input type=radio name=valid value=no> Save <br><input type=radio name=valid value=preview> Preview <br><input type=radio name=valid value=yes checked> Post <br><input type=submit value=»> I would like something like (not sure if it is correct html syntax: "name" or something else to make the difference between the "submit" buttons) <input type=submit name=no value=Save> <input type=submit name=preview value=Preview> <input type=submit name=yes value=Post> Did not you see things like this (for "preview" and "post", not "save") in some existing forums on the web ? |
|||
| Lun 5 septembre 2005 |
2. Changes in the Rights System - private forums, if one has admin right, the "edit forum rights" should be replaced by an "edit denials", but why not integrate it to the forum info page instead of having a separate page ? In the form "Creating new forum", there should be a difference when you will make the new folders system. |
|||
| Lun 5 septembre 2005 |
The "Save, Preview, Post for forum messages" should also concern the "edit message" screen. |
|||
| Lun 5 septembre 2005 |
1. Save, Preview, Post for forum messages. 2. Changes in the Rights System -Resign from admin rights, Question to you: ---------------------------------------------- Current forum is programmed in the next way: Forum's creator have admin's rights independently from the Rughts Systems. Who will be the owner of the rights if the admin wants to make Resign? |
|||
| Lun 5 septembre 2005 | Save, Preview, Post for forum
messages. 2. Changes in the Rights System - Resign from admin rights, - Forum's creator have admin's rights independently from the Rights Systems. Who will be the owner of the rights if the admin wants to make Resign? - That's why he can't resign until he gives owner right to someone else (and loses his). OR, if it is a private forum where there is nobody else with right to the forum (they all resigned already), then the creator can delete the forum. In case of public or semi-public forum, I wonder if it makes sense to delete it... anyway, even a resign from such forum, if you ever defined it, would only be resign from supplementary rights and keeps the possibility to access the forum (except in case of reading denial). |
|||
| Lun 5 septembre 2005 |
2. Changes in the Rights System * admin right, the "edit forum rights" should be replaced by an "edit denials", but why not integrate it to the forum info page instead of having a separate page ? In the form "Creating new forum", there should be a difference when you will make the new folders system. |
|||
| Lun 5 septembre 2005 |
The "Save, Preview, Post for forum messages" should also concern the "edit message" screen. |
|||
| Mar 6 septembre 2005 |
- Possibility to invite an email to a forum. - Integration of GLS to forums system - Email invitations system (whose main interest and deep fuctions are in fact included in the possibility to invite email to forum), dating corrections, translations, new folders system, |
|||
| Mar 6 septembre 2005 |
- Possibility to invite an email to a forum. - Integration of GLS to forums system - Email invitations system( invite email to forum) - dating corrections - translations - new folders system |
|||
| Mer 7 septembre 2005 |
1. Save, Preview, Post for forum messages. -make a message and ask Preview, no option appears with the displayed message, while there should be the options "Erase" and "Mark valid". (of course not "edit" because it is being edited already). But if the message is previewed and I ask for another preview, it acts like "save" instead, and not preview. |
|||
| Mer 7 septembre 2005 |
1. Save, Preview, Post for forum
messages. I notice that, if I make a message and ask Preview, no option appears with the displayed message, while there should be the options "Erase" and "Mark valid". (of course not "edit" because it is being edited already). But if the message is previewed and I ask for another preview, it acts like "save" instead, and not preview. |
|||
| Jeu 8 septembre 2005 |
- "Email invitations system ( invite email to forum)" I meant: "should be" included, of course. So that adding invitation to message will be virtually nothing more than what should already be working with inviting email to forum (i.e. possibility for invited person to register). - inviting email to a forum, and the GLS integration - adding invitation to email message if not already done, dating corrections, translations, new folders system - The trust system. - PWP. - calendar system. |
|||
| Jeu 8 septembre 2005 |
* "Email invitations system~can invite email to forum" - adding invitation to message ~ with inviting email to forum (i.e. possibility for invited person to register). - inviting email to a forum - GLS integration. - adding invitation to email message - dating - translations - new folders system - The trust system. - PWP. - calendar system. |
|||
| Jeu 8 septembre 2005 |
inviting emails to forum. |
|||
| Ven 9 septembre 2005 |
web browser |
|||
| Ven 9 septembre 2005 |
invalid message in a public forum, and when I want to edit it, all letters with accents are replaced in the editing window by encodings like é |
|||
| Ven 9 septembre 2005 |
This problem in editing message titles ("y" looks like "v") does not happen with Mozilla, neither Konqueror, so it is specific to Firefox. But I have another example of a web page with a form containing an "input type=text" which does not have this problem with the same Firefox. |
|||
| Ven 9 septembre 2005 |
(I tried everything with Microsoft IE and there is no problem). mozilla -the new public forum "new forum", there appears two people (mefisto Rodney) in the "members" column, but mefisto is neither creator nor author of a visible message. Maybe he put an invalid message ? |
|||
| Ven 9 septembre 2005 |
Firefox |
|||
| Ven 9 septembre 2005 |
- invalid message in a public forum - I want to edit it ==> all letters with accents are replaced in the editing window by encodings like é |
|||
| Ven 9 septembre 2005 |
editing message titles ("y"
looks like "v") specific to Firefox. |
|||
| Ven 9 septembre 2005 |
- Microsoft IE * fixed width font : Trust-forum . * in the new public forum "new forum": - 2 people (mefisto Rodney) in the "members" column but mefisto is neither creator nor author of a visible message. Maybe he put an invalid message ? |
|||
| Sam 10 septembre 2005 |
In my Main Box, there is in the source code of the page, end of line of forum named "mariupol": 0<td>N<td><!--<a href='index.php?action=viewpseudo&id=95'>spoirier</a>--> <a href='index.php?action=viewpseudo&id='><b></b></a> <a href='index.php?action=viewpseudo&id=94'><b>hitchkok</b></a> (why include my pseudo in an invisible way?) Is there an invisible pseudo (null string) ? |
|||
| Sam 10 septembre 2005 |
In my Main Box, there is in the
source code of the page, end of line of forum named "mariupol": 0<td>N<td><!--<a href='index.php?action=viewpseudo&id=95'>spoirier</a>--> <a href='index.php?action=viewpseudo&id='><b></b></a> <a href='index.php?action=viewpseudo&id=94'><b>hitchkok</b></a> (why include my pseudo in an invisible way?) Is there an invisible pseudo (null string) ? |
|||
| Mar 13 septembre 2005 |
1. Save Preview Post, you can
view at trust-forum.php.by install it at tforum.php.by later too. 2. Rights for public forums - admin is unable delete another admin but itself - does forum creator able to delete admins? - does forum creator able to delete itself from the creator's list? Who will be the forum's creator in this case. - it was an idea to unite Rights page with Info page. - integrate gls with the whole system - datings |
|||
| Mer 14 septembre 2005 |
2. Rights for public forums is not finished. - admin is unable delete another admin but itself Right. - does forum creator able to delete admins? Yes - does forum creator able to delete itself from the creator's list? Who will be the forum's creator in this case. No. There is no creator list, only one creator at every time. He can resign by transmitting his position to someone else (this function is not urgent to implement). In case of private forum, he can delete the forum if there is no other user. It would be interesting to let the superadmin delete a public forum. - it was an idea to unite Rights page with Info page. What do you mean by "rights page" ? One thing is denials table for editing by admin, one thing is display of table of invitations and denials, one thing is invitations system (already together with display of invitations table, right ?). Since they all concern the same invitations table, should be together. Only thing I'm still wondering about: ifever the invitations table was very big, one could be interested to see only the other info (or the info of only oneself's invitations) to not overload the screen. A possible way of handling this would be to have an info page with the only invitations one is involved in, and a separate page with the full invitations table if one is allowed to see it. It is left to integrate gls with the whole system and finish datings. What about the Email invitations system / inviting email to forum ? dating corrections. |
|||
| Mer 14 septembre 2005 |
1. We have made Save
Preview Post, you can view at trust-forum.php.by tforum.php.by later too. One thing is missing: the links "Erase" - "mark valid" at the previewed message. I was surprised to see the thread still in the preview mode after I asked Preview, then went away by asking for Mainbox, and came back. I did not think of preview as a status for message but only as a request, while the status remains "invalid". ----------------------------------------------------------- I see no reason to not save previewed message in database, since you already have the database prepared for this !!!! Why do you think I asked you to add the link: "Mark valid" to previewed message ? Because there is no reason not to do it, since a previewed message is a saved invalid message like all others, so the "mark valid" will work exactly like other cases !!!!! |
|||
| Mer 14 septembre 2005 |
2. Rights for public forums - admin is unable delete another admin but itself Right. We could imagine something more complicated but it would not be really useful, so let us stay with this, with the only below exceptions. - does forum creator able to delete admins? Yes - does forum creator able to delete itself from the creator's list? Who will be the forum's creator in this case. No. There is no creator list, only one creator at every time. He can resign by transmitting his position to someone else (this function is not urgent to implement). In case of private forum, he can delete the forum if there is no other user. It would be interesting to let the superadmin delete a public forum. - it was an idea to unite Rights page with Info page. What do you mean by "rights page" ? One thing is denials table for editing by admin, one thing is display of table of invitations and denials, one thing is invitations system (already together with display of invitations table, right ?). Since they all concern the same invitations table, I think they should be together. Only thing I'm still wondering about: ifever the invitations table was very big, one could be interested to see only the other info (or the info of only oneself's invitations) to not overload the screen. A possible way of handling this would be to have an info page with the only invitations one is involved in, and a separate page with the full invitations table if one is allowed to see it. Please tell me what you think about this. - integrate gls with the whole system - finish datings. - What about Email invitations system / inviting email to forum ? - dating. |
|||
| Mer 14 septembre 2005 |
1. We have made Save Preview Post, you can view at trust-forum.php.by We will install it at tforum.php.by later too. One thing is missing: the links "Erase" - "mark valid" at the previewed message.I was surprised to see the thread still in the preview mode after I asked Preview, then went away by asking for Mainbox, and came back. I did not think of preview as a status for message but only as a request, while the status remains "invalid". |
|||
| Mer 21 septembre 2005 |
http://tforum.php.by Short report is provided below. ---------------------------------------- R> One thing is missing: the links "Erase" - "mark valid" at the previewed message. R> I was surprised to see the thread still in the preview mode after I asked Preview, then went away by asking for Mainbox, and came back. I did not think of preview as a status for message but only as a request, while the status remains "invalid". Everything has been changed in preview message system. Now user can preview a message but the message does not have a status, and it is not being saved in database. Also the link "Cancel" used except "Erase". ------------------------------------------------------------------------ 2. Rights for public forums admin is unable delete another admin but itself - does forum creator able to delete admins? R> Yes Ok. Now forum creator can delete admins. Also here is a question if an admin (adminA) can delete invited admin (AdminB) if AdminA has invited adminB? - does forum creator able to delete itself from the creator's list? Who will be the forum's creator in this case. R> No. There is no creator list, only one creator at every time. He can resign by transmitting his position to someone else (this function is not R> urgent to implement). In case of private forum, he can delete the forum if R> there is no other user. Ok. I don't tough this now. Creator can't change his status for now. R> It would be interesting to let the superadmin delete a public forum. |
|||
| Jeu 22 septembre 2005 |
One thing is missing: the links "Erase" - "mark valid" at the previewed message. I was surprised to see the thread still in the preview mode after I asked Preview, then went away by asking for Mainbox, and came back. I did not think of preview as a status for message but only as a request, while the status remains "invalid". - Everything has been changed in preview message system. Now user can preview a message but the message does not have a status, and it is not being saved in database. Also the link "Cancel" used except "Erase". From the beginning I defined: "Preview" = "Save and reedit to the same screen". "Edit message" is not a status of message. "Preview" is not a status either. Nevertheless, message must be saved. status of previewed message remains: invalid. |
|||
| Jeu 22 septembre 2005 |
"Preview" should have the same effect as "save" on the database, just different effect to the display. Ok. Now forum creator can delete admins. Also here is a question if an admin (adminA) can delete invited admin (AdminB) if AdminA has invited adminB? - inviting email to a forum. |
|||
| Jeu 22 septembre 2005 |
http://tforum.php.by ---------------------------------------- One thing is missing: the links "Erase" - "mark valid" at the previewed message. I was surprised to see the thread still in the preview mode after I asked Preview, then went away by asking for Mainbox, and came back. I did not think of preview as a status for message but only as a request, while the status remains "invalid". Everything has been changed in preview message system. Now user can preview a message but the message does not have a status, and it is not being saved in database. Also the link "Cancel" used except "Erase". * "Preview" = "Save and reedit to the same screen". "Edit message" is not a status of message. Therefore, "Preview" is not a status either. I see no reason to not save previewed message in database, since you already have the database prepared for this !!!! "Mark valid" to previewed message : previewed message is a saved invalid message like all others, so the "mark valid" will work exactly like other cases. |
|||
| Jeu 22 septembre 2005 |
"Preview" should have the same effect as "save" on the database, just different effect to the display. * Ok. Now forum creator can delete admins. Also here is a question if an admin (adminA) can delete invited admin (AdminB) if AdminA has invited adminB? - inviting email to a forum. |
|||
| Sam 24 septembre 2005 |
-correct preview system. |
|||
| Sam 24 septembre 2005 |
http://tforum.php.by - email invitation to forum - preview system. |
|||
| Dim 25 septembre 2005 |
- rights system |
|||
| Jeu 29 septembre 2005 |
- email invitation to a forum - Email invitation to a forum - Preview correctly - GLS integration to forums system - New forum rights system |
|||
| Jeu 29 septembre 2005 |
- email invitation to a forum - Email invitation to a forum - Preview correctly - GLS integration to forums system - New forum rights system |
|||
| Lun 3 octobre 2005 |
spoirier.lautre.net/tf-todo page |
|||
| Lun 3 octobre 2005 |
- messages be sent to email when closing session, you can make the sending at posting or validating message instead (so that invalidating the message in a forum will be no more possible if an email other than oneself is subscribed to that forum). |
|||
| Lun 3 octobre 2005 |
spoirier.lautre.net/tf-todo |
|||
| Lun 3 octobre 2005 |
-pb: messages sent to
email when closing session, you can make the sending at posting or validating message instead (so that invalidating the message in a forum will be no more possible if an email other than oneself is subscribed to that forum). |
|||
| Ven 7 octobre 2005 |
- post any message in the new
public forum created by someone else. |
|||
| Ven 7 octobre 2005 |
- I cannot post any message in the new public forum created by someone else. |
|||
| Lun 10 octobre 2005 |
Questions: 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? 3. Does it make possible invited users to see the forum without registering? |
|||
| Mar 11 octobre 2005 |
- Email invitation to a forum. 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? Yes, any user with write right can invite an e-mail to a forum with writing write. - allow user with reading right to invite email for reading right only, you can do it. But as "to be serious", an admin of a forum should be a "real user" and not a mere email, I don't see the interest of inviting an email for admin right. 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? - Like any invitation: for example you can let it in the same field as "invite pseudo to forum", with a checkbox "it is an email". Or you can instead put form "Invite email to forum" just below the form "Invite pseudo to forum". Indeed these 2 things are similar (I think the good way would be to put emails to the same forum rights table, and its entry (line of mysql table) with the "invitation id to this forum" (incremental number), right and inviter, will be preserved when email registers to become a user; just a pseudo will be then added on the pseudo element of this line. 3. Does it make possible invited users to see the forum without registering? Yes. Just like GLS access to the forum by a user of another host in fact (so some part of your work may be useful for these 2 purposes at the same time). Namely, its entry in this forum's invitation table is what stands for an "account", so with possibilities limited to the use of this forum, as opposed to the general possibilities of doing so many other things (use of folders, forum creation, configuration, dating...), that a registered user of this host has. |
|||
| Mar 11 octobre 2005 |
- Email invitation to a forum. 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? Yes, any user with write right can invite an e-mail to a forum with writing write. - allow user with reading right to invite email for reading right only. But as "to be serious", an admin of a forum should be a "real user" and not a mere email, I don't see the interest of inviting an email for admin right. 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? Like any invitation: for example you can let it in the same field as "invite pseudo to forum", with a checkbox "it is an email". Or you can instead put form "Invite email to forum" just below the form "Invite pseudo to forum". Indeed these 2 things are similar (I think the good way would be to put emails to the same forum rights table, and its entry (line of mysql table) with the "invitation id to this forum" (incremental number), right and inviter, will be preserved when email registers to become a user; just a pseudo will be then added on the pseudo element of this line. 3. Does it make possible invited users to see the forum without registering? Yes. Just like GLS access to the forum by a user of another host in fact (so some part of your work may be useful for these 2 purposes at the same time). Namely, its entry in this forum's invitation table is what stands for an "account", so with possibilities limited to the use of this forum, as opposed to the general possibilities of doing so many other things (use of folders, forum creation, configuration, dating...), that a registered user of this host has. |
|||
| Ven 14 octobre 2005 |
- my private forums that I use as a draft space. It was saved after timeout, then I logged in again and I saw it saved. I did nothing more. But now I look for it and I don't find it. |
|||
| Ven 14 octobre 2005 |
- I put a message this morning
or last night in one of my private forums that I use as a draft space. - It was saved after timeout - I logged in again and I saw it saved. I did nothing more. ==> now I look for it and I don't find it. Did it disappear or do I not remember well what I did ? http://trust-forum.php.by/index.php?action=showforum&id=15 |
|||
| Mar 18 octobre 2005 |
- invitation tree that I saw long ago after inviting by inside account, should be corrected too |
|||
| Mar 18 octobre 2005 |
- invitation tree |
|||
| Jeu 20 octobre 2005 |
- not handle choice between methods of sending forum messages to an email |
|||
| Jeu 20 octobre 2005 |
-choice between methods of
sending forum messages 2 email |
|||
| Jeu 27 octobre 2005 |
- "Save-Preview-Post" ------------------------------------------------------------------------ 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? 3. Does it make possible invited users to see the forum without registering? ------------------------------------------------------------------------ 1. Finish a 1st release. 2. Make a full documentation for the release, including -1- Database structures -2- Functionality description -3- Relational description -4- Structure description -5- Principals description -6- Project dictionary and helpful information 3. Make some sort of design for the 1st release 4. Prepare to the 2nd release -1- Make a full documentation -2- Make a full projecting of the system -3- Make a coding of the kernel parts -4- Test the system -5- Develop all main features -6- Test them -7- Prepare design for the 2nd release -8- Prepare programs for migrating from 1st to the 2nd release -9- Run the project. |
|||
| Ven 28 octobre 2005 |
We have corrected
"Save-Preview-Post" issue. ------------------------------------------------------------------------ 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? As any invitation, an invitation of an email to a forum is an invitation with a specific right. And an invited email to a forum is very similar to an invitation of a GLS remote user to a forum. In fact, it does not really matter to me whether a user with only reading or writing right can invite an email (but for GLS, of course all the possibilities must be available just as for other users of the same site). Because the most important thing is the possibility to create a new forum and to invite an email to it; and in the long term, the email system will no longer exist. 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? 3. Does it make possible invited users to see the forum without registering? - viewing invitations table - one thing is the inviting a user to a higher right one has (no specific interface for admin here - why not let it be done inside the invitations table display), - one thing is the editing denials by admin. Here is a copy of what I sent you October 11: ******** Questions: 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? - any user with write right can invite an e-mail to a forum with writing write. allow user with reading right to invite email for reading right only, you can do it. But as "to be serious", an admin of a forum should be a "real user" and not a mere email, I don't see the interest of inviting an email for admin right. 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? Like any invitation: for example you can let it in the same field as "invite pseudo to forum", with a checkbox "it is an email". Or you can instead put form "Invite email to forum" just below the form "Invite pseudo to forum". Indeed these 2 things are similar (I think the good way would be to put emails to the same forum rights table, and its entry (line of mysql table) with the "invitation id to this forum" (incremental number), right and inviter, will be preserved when email registers to become a user; just a pseudo will be then added on the pseudo element of this line. 3. Does it make possible invited users to see the forum without registering? - Just like GLS access to the forum by a user of another host in fact (so some part of your work may be useful for these 2 purposes at the same time). Namely, its entry in this forum's invitation table is what stands for an "account", so with possibilities limited to the use of this forum, as opposed to the general possibilities of doing so many other things (use of folders, forum creation, configuration, dating...), that a registered user of this host has. |
|||
| Ven 28 octobre 2005 |
1. Finish a 1st release. 2. Make a full documentation for the release, including -1- Database structures -2- Functionality description -3- Relational description -4- Structure description -5- Principals description -6- Project dictionary and helpful information 3. Make some sort of design for the 1st release 4. Prepare to the 2nd release -1- Make a full documentation -2- Make a full projecting of the system -3- Make a coding of the kernel parts -4- Test the system -5- Develop all main features -6- Test them -7- Prepare design for the 2nd release -8- Prepare programs for migrating from 1st to the 2nd release -9- Run the project. 1) Email invitations system, Possibility to invite an email to a forum, Save-Preview-Post (are most urgent). - New forum rights system, - new folders system that will have to be done: maybe some aspect of it should be already included for sake of consistency with the new rights system). - Also, integration of GLS to forums system because you did GLS some time ago and it would be a shame to not release it with the system. 2) translations system, - new folders system - dating system - dating system - more parameters to add along the same scheme - integration with PWP - documentation for the release 3) developments (PWP ) |
|||
| Ven 28 octobre 2005 |
- GLS integration - inviting email to forum |
|||
| Ven 28 octobre 2005 |
We have corrected
"Save-Preview-Post" issue. 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? - As any invitation, an invitation of an email to a forum is an invitation with a specific right. - And an invited email to a forum is very similar to an invitation of a GLS remote user to a forum. - user with only reading or writing right can invite an email (but for GLS, of course all the possibilities must be available just as for other users of the same site). - Because the most important thing is the possibility to create a new forum and to invite an email to it; and in the long term, the email system will no longer exist. 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? 3. Does it make possible invited users to see the forum without registering? - "Edit forum rights" page are you speaking about ? ~ viewing invitations table ~ inviting a user to a higher right one has (no specific interface for admin here - why not let it be done inside the invitations table display) ~ one thing is the editing denials by admin. ******** Email invitation to a forum. Questions: 1. Who can invite e-mail addresses to forums? Any user with read/write rights or forum admin? Yes, any user with write right can invite an e-mail to a forum with writing write. - reading right to invite email for reading right only - But as "to be serious", an admin of a forum should be a "real user" and not a mere email, I don't see the interest of inviting an email for admin right. 2. Where should be form with inviting emails? Should it be on the "Edit forum rights" page? - Like any invitation: let it in the same field as ~~ "invite pseudo to forum" ~~ checkbox "it is an email". Or you can instead put form "Invite email to forum" just below the form "Invite pseudo to forum". Indeed these 2 things are similar (I think the good way would be to put emails to the same forum rights table, and its entry (line of mysql table) with the "invitation id to this forum" (incremental number), right and inviter, will be preserved when email registers to become a user; just a pseudo will be then added on the pseudo element of this line. 3. Does it make possible invited users to see the forum without registering? * entry in forum's invitation table is what stands for an "account" - use of folders - forum creation - configuration - dating... |
|||
| Ven 28 octobre 2005 |
1. Finish a 1st release. 2. Make a full documentation for the release, including -1- Database structures -2- Functionality description -3- Relational description -4- Structure description -5- Principals description -6- Project dictionary and helpful information 3. Make some sort of design for the 1st release 4. Prepare to the 2nd release -1- Make a full documentation -2- Make a full projecting of the system -3- Make a coding of the kernel parts -4- Test the system -5- Develop all main features -6- Test them -7- Prepare design for the 2nd release -8- Prepare programs for migrating from 1st to the 2nd release -9- Run the project. - Email invitations system - Possibility to invite an email to a forum - Save-Preview-Post (are most urgent). - New forum rights system - GLS to forums system 2) - translations system - new folders system - dating system - PWP |
|||
| Ven 28 octobre 2005 |
- GLS integration - inviting email to forum |
|||
| Lun 31 octobre 2005 |
Lisp |
|||
| Lun 31 octobre 2005 |
- invite email to the forum - allow to the user without registration see the forum ad write to the forum... |
|||
| Lun 31 octobre 2005 |
http://tforum.php.by or at http://trust-forum.php.by ??? - bug : write in public forums very quickly |
|||
| Mar 1 novembre 2005 |
- invite email to the forum and allow to the user without registration see the forum ad write to the forum... Well, I don't see why you see an obstacle here: 1) GLS access from one's account at a site A to a forum at a site B, one can see the forum and write to the forum in site B without an account on site B, but only by one's entry in the forum rights table (in case of a private forum) ? 2) With email it is the same except that the GLS process to open a session is replaced by the access by a link present at the bottom of the email message, containing a verification code. I understand that this is less secure than GLS because the use of this link may make it visible by third parties which can also use it until a new message is sent with a new code. - bug in public forums. trust-forum.php.by. - delete the public forums "new forum" and "philo" |
|||
| Mar 1 novembre 2005 |
- add invitation to composed email message, and the invitations tree, seems to have been fixed. |
|||
| Mar 1 novembre 2005 |
- invite email to the forum and allow to the user without registration see the forum ad write to the forum... 1) Do you agree that with GLS access from one's account at a site A to a forum at a site B, one can see the forum and write to the forum in site B without an account on site B, but only by one's entry in the forum rights table (in case of a private forum) ? 2) With email it is the same except that the GLS process to open a session is replaced by the access by a link present at the bottom of the email message, containing a verification code. I understand that this is less secure than GLS because the use of this link may make it visible by third parties which can also use it until a new message is sent with a new code. - delete the public forums tests "new forum" and "philo" |
|||
| Mar 1 novembre 2005 |
- system to add invitation to composed email message - invitations tree |
|||
| Mer 2 novembre 2005 |
- change the Comment field of a public forum, and: - the ' character is replaced by \' - Accents in French do not pass, they are replaced by non accentuated letters. |
|||
| Mer 2 novembre 2005 |
* change the Comment field of a public forum, and: - the ' character is replaced by \' - Accents in French do not pass, they are replaced by non accentuated letters. |
|||
| Jeu 3 novembre 2005 |
In the public forum "Discussions en français" I see that according to info: Pseudos who have posted messages (admins in bold): Rodney spoirier Guest Djhaidgh But among messages there is none from Djhaidgh Can you explain this please ? email invitation, GLS, forum rights |
|||
| Jeu 3 novembre 2005 |
It looks like Djhaidgh is the author of the message which appears in the forum as from Guest. Was it posted normally or after timeout or ???? |
|||
| Jeu 3 novembre 2005 |
- public forum "Discussions en
français" I see that according to info: Pseudos who have posted messages (admins in bold): Rodney spoirier Guest Djhaidgh But among messages there is none from Djhaidgh - email invitation - GLS - forum rights |
|||
| Jeu 3 novembre 2005 |
It looks like Djhaidgh is the
author of the message which appears in the forum as from Guest. Was it posted normally or after timeout or ???? |
|||
| Ven 4 novembre 2005 |
- invitations a - PWP |
|||
| Ven 4 novembre 2005 |
When I edit a message with accents, the accents appear encoded. |
|||
| Ven 4 novembre 2005 |
When I edit a message with
accents, the accents appear encoded. |
|||
| Sam 5 novembre 2005 |
text encoding is not all right when editing a title of a message (I tried by preview function). This and the comments of forum, you should fix soon. |
|||
| Lun 7 novembre 2005 |
- invitation of email to forum - new system of rights and denials in forums ? Or one of them |
|||
| Lun 7 novembre 2005 |
- invitation of email to forum - new system of rights and denials in forums |
|||
| Mar 8 novembre 2005 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I tried to make the email invitation system, and it's almost finished, but i confronted with few questions: 1. I was thinking about who can see and manage the invitation in the system and i made it the way when User who has invited can see and admin the invitation which posted by him. Also Admin of a forum can see and manage all of email invitation connected to this forum. The question is am i right or not, should i change it? 2. How should i make output of Pseudo(name) of invited by email User? By email or name Guest is enough? Because i see lots of changes in current system if we deside to store email for each message. 3. I've done that email invitations for Public forums are not stored in DB, so the information about them are not shown any more after being sent. Also the owner of message is shown as Guest. Should it be stored it in DB? R> -------------------------------------------------------------------- R> I wait for you news but I recall you the bug of text encoding: I R> just noticed now that the text encoding is not all right when editing a R> title of a message (I tried by preview function). This and the comments of R> forum, you should fix soon. R> -------------------------------------------------------------------- Is it also about editing with symbols "'"? I'll fix it asap. |
|||
| Mer 9 novembre 2005 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. I was thinking about who can see and manage the invitation in the system and i made it the way when User who has invited can see and admin the invitation which posted by him. Also Admin of a forum can see and manage all of email invitation connected to this forum. What do you mean by "can see and admin the invitation" concretely ? 2. How should i make output of Pseudo(name) of invited by email User? By email or name Guest is enough? Because i see lots of changes in current system if we deside to store email for each message. I imagine you may mean the following: until now, in the database the author of a message was identified by an id (maybe incremental number in the forum invitations table ? it would be right), which in the display appears as the pseudo according to what is in the forum invitations table. Then, the email author of a message will also be identified by invitation id in the forum, and it would appear in the display in the form of the email address instead of pseudo. 3. I've done that email invitations for Public forums are not stored in DB, so the information about them are not shown any more after being sent. Also the owner of message is shown as Guest. Should it be stored it in DB? ----------------------------------------------------------- |
|||
| Mer 9 novembre 2005 |
- editing with symbols "'"? I'll fix it asap. - character ' passes well, and there is no problem with display, but there is a problem when I tried to edit the message: in the title and message body, French accentuated letters appear encoded in the editing window (then they still appear OK on display). Also, I recall you that there is a problem for comments of forums ' become \' and accentuated letters become non accentuated. |
|||
| Mer 9 novembre 2005 |
- email invitation system 1. I was thinking about who can see and manage the invitation in the system and i made it the way when User who has invited can see and admin the invitation which posted by him. Also Admin of a forum can see and manage all of email invitation connected to this forum. - Well, i've made page where User can invite by email to forum. This page looks like "Edit rights" page. All the information about email invitations is stored in database (DB) and User or forum Admin can see who is invited (emails, date) with form of adding new invitation. The difference between User with forum admin rights (forum Admin) and simple User (user who has write permission) on the page "Invite email to forum" is that simple User can only see (and remove) the emails added by himself and Admin can see (remove) emails entered by all users of the forum. After your question i only can ask may users see invited emails after they has been added at all? ____________________________________________________________________ 2. How should i make output of Pseudo(name) of invited by email User? By email or name Guest is enough? Because i see lots of changes in current system if we deside to store email for each message. R> I imagine you may mean the following: until now, in the database the R> author of a message was identified by an id (maybe incremental number in R> the forum invitations table ? it would be right), which in the display R> appears as the pseudo according to what is in the forum invitations table. R> Then, the email author of a message will also be identified by invitation R> id in the forum, and it would appear in the display in the form of the R> email address instead of pseudo. R> Does it answer your question, or is the situation different ? Now in the database the author of a message is identified by an id (incremental number in the forum users table), which in the display appears as the pseudo according to what is in the forum users table. But users who was invited by email invitation don't have pseudo in forum users table. Now it is only possible to post new messages as Guest. I can understand that it is not a good way but forum messages in database are not connected with email invitations and it was not worked over in past. Maybe there is a way how to connect them: to register new user with pseudo=invited email. I need to see some argumentations about this problem. ______________________________________________________________________ 3. I've done that email invitations for Public forums are not stored in DB, so the information about them are not shown any more after being sent. Also the owner of message is shown as Guest. Should it be stored it in DB? R> Don't worry too much about the case of public forums. But I don't R> understand your last question "Should it be stored it in DB?": to store R> what ? The question was about should an information about email invitation to public forum be stored in the invitation table of the database (DB). "to store what ?" To store id, email, date, forum_id, pseudo_parent_id and secretkey as for private forums. Now i see that probably it's not nesessary and maybe it would be better to remove the link for page "Invite email to forum" from public forums. |
|||
| Mer 9 novembre 2005 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - email invitation system 1. I was thinking about who can see and manage the invitation in the system and i made it the way when User who has invited can see and admin the invitation which posted by him. Also Admin of a forum can see and manage all of email invitation connected to this forum. - "can see and admin the invitation" concretely ? 2. How should i make output of Pseudo(name) of invited by email User? By email or name Guest is enough? Because i see lots of changes in current system if we deside to store email for each message. - in the database the author of a message was identified by an id (maybe incremental number in the forum invitations table ?), which in the display appears as the pseudo according to what is in the forum invitations table. - Then, the email author of a message will also be identified by invitation id in the forum, and it would appear in the display in the form of the email address instead of pseudo. 3. I've done that email invitations for Public forums are not stored in DB, so the information about them are not shown any more after being sent. Also the owner of message is shown as Guest. Should it be stored it in DB? |
|||
| Mer 9 novembre 2005 |
- editing with symbols "'"? I'll fix it asap. - message in public forum of tforum. The character ' passes well: in the title and message body, French accentuated letters appear encoded in the editing window. - comments of forums ' become \' and accentuated letters ==> non accentuated. |
|||
| Jeu 10 novembre 2005 |
- email invitations - http://tforum.php.by |
|||
| Jeu 10 novembre 2005 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. I was thinking about who can see and manage the invitation in the system and i made it the way when User who has invited can see and admin the invitation which posted by him. Also Admin of a forum can see and manage all of email invitation connected to this forum. The question is am i right or not, should i change it? - What do you mean by "can see and admin the invitation" concretely ? Well, i've made page where User can invite by email to forum. This page looks like "Edit rights" page. All the information about email invitations is stored in database (DB) and User or forum Admin can see who is invited (emails, date) with form of adding new invitation. The difference between User with forum admin rights (forum Admin) and simple User (user who has write permission) on the page "Invite email to forum" is that simple User can only see (and remove) the emails added by himself and Admin can see (remove) emails entered by all users of the forum. All right. > After your question i only can ask may users see invited emails after they has been added at all? Invited emails are just like any invited user. I told you the thing is similar to the invitation of a GLS remote user. In the invitation of GLS remote user, everything appears with no difference between local users and remote users. The only difference I think about is that in remote access to forum, one does not see a left bar with folders list, and maybe the top bar is different... You should first make a working plan for GLS integration, then consider what can be common with invited email. I'll try to be more specific. Now in the database the author of a message is identified by an id (incremental number in the forum users table), which in the display appears as the pseudo according to what is in the forum users table. But users who was invited by email > invitation don't have pseudo in forum users table. Now it is only > possible to post new messages as Guest. I can understand that it is > not a good way but forum messages in database are not connected with > email invitations and it was not worked over in past. Maybe there is a > way how to connect them: to register new user with pseudo=invited > email. I need to see some argumentations about this problem. User invited by email has no pseudo in forum users table, but he must have id, and the id is connected with the email address. You can either make another column in the forum users table for the email address, or place the email address in the pseudos column, and make another column for the binary (or ternary) question: is this an email address or a normal pseudo (or a GLS remote pseudo). Anyway, it is not good to have messages posted as guest. And anyway, when GLS integration will be done, GLS remote user will post under their remote pseudo with host, not as guest !!! Again, I recall you that there is a difference between: - The system users table, where a user (login/pass) is connected with the list of his pseudos, his folders, the list of his forums and associated folders, dating account. The GLS remote users are not listed here, neither the email invited users. - Each separate forum's users table, with rights and invitations. Here appear GLS remote users by their pseudo, and invited emails. ______________________________________________________________________ 3. I've done that email invitations for Public forums are not stored in DB, so the information about them are not shown any more after being sent. Also the owner of message is shown as Guest. Should it be stored it in DB? Don't worry too much about the case of public forums. But I don't understand your last question "Should it be stored it in DB?": to store what ? The question was about should an information about email invitation to public forum be stored in the invitation table of the database (DB). "to store what ?" To store id, email, date, forum_id, pseudo_parent_id and secretkey as for private forums. Now i see that probably it's not nesessary and maybe it would be better to remove the link for page "Invite email to forum" from public forums. Yes, you can just remove it. One thing that might be interesting would be the subscription, that is, to receive to an email all messages posted to a public forum. But unless it is very easy to do, we can do without it. |
|||
| Jeu 10 novembre 2005 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - email invitation system 1. who can see and manage the invitation in the system and i made it the way when User who has invited can see and admin the invitation which posted by him. Also Admin of a forum can see and manage all of email invitation connected to this forum. - User can invite by email to forum. This page looks like "Edit rights" page. All the information about email invitations is stored in database (DB) and User or forum Admin can see who is invited (emails, date) with form of adding new invitation. The difference between User with forum admin rights (forum Admin) and simple User (user who has write permission) on the page "Invite email to forum" is that simple User can only see (and remove) the emails added by himself and Admin can see (remove) emails entered by all users of the forum. - can users see invited emails after they has been added at all? - Invited emails are just like any invited user. I told you the thing is similar to the invitation of a GLS remote user. In the invitation of GLS remote user, everything appears with no difference between local users and remote users. The only difference I think about is that in remote access to forum, one does not see a left bar with folders list, and maybe the top bar is different... - Now in the database the author of a message is identified by an id (incremental number in the forum users table), which in the display appears as the pseudo according to what is in the forum users table. But users who was invited by email invitation don't have pseudo in forum users table. Now it is only possible to post new messages as Guest. I can understand that it is not a good way but forum messages in database are not connected with email invitations and it was not worked over in past. Maybe there is a way how to connect them: to register new user with pseudo=invited email. User invited by email has no pseudo in forum users table, but he must have id, and the id is connected with the email address. You can either make another column in the forum users table for the email address, or place the email address in the pseudos column, and make another column for the binary (or ternary) question: is this an email address or a normal pseudo (or a GLS remote pseudo). Anyway, it is not good to have messages posted as guest. And anyway, when GLS integration will be done, GLS remote user will post under their remote pseudo with host, not as guest !!! Again, I recall you that there is a difference between: - The system users table, where a user (login/pass) is connected with the list of his pseudos, his folders, the list of his forums and associated folders, dating account. The GLS remote users are not listed here, neither the email invited users. - Each separate forum's users table, with rights and invitations. Here appear GLS remote users by their pseudo, and invited emails. ______________________________________________________________________ 3. I've done that email invitations for Public forums are not stored in DB, so the information about them are not shown any more after being sent. Also the owner of message is shown as Guest. Should it be stored it in DB? R> Don't worry too much about the case of public forums. But I don't understand your last question "Should it be stored it in DB?": to store what ? The question was about should an information about email invitation to public forum be stored in the invitation table of the database (DB). "to store what ?" To store id, email, date, forum_id, pseudo_parent_id and secretkey as for private forums. Now i see that probably it's not nesessary and maybe it would be better to remove the link for page "Invite email to forum" from public forums. Yes, you can just remove it. One thing that might be interesting would be the subscription, that is, to receive to an email all messages posted to a public forum. |
|||
| Ven 11 novembre 2005 |
- email invitation. - The invitation should appear at the same place as the other invitation (the one of a pseudo), that is, at the forum info page. One reason is that in your new page there is no link back to the forum. But instead of adding it, just include the email invitation with the previous invitation. |
|||
| Ven 11 novembre 2005 |
- Did you notice, it takes a long time to enter the forum - I then posted a new message under pseudo, but it was not sent to the email. ==> new posted messages should be sent to email. - I registered from email access, but then when I logged in under inviter identity, I did not see the new login name on the line of the contact table for this email. Also I notice that the registration should not ask for email since the email is already known !!! - The invitation message should not be from "www-data" <www-data@kama.neolocation.net> but from pseudo@host of the inviter. - Also, it should not be sent at the time of invitation itself, since it will be included again at the bottom of posted messages from the forum. Ifever one wanted to send this pure invitation anyway, the link "Resend invitation" is here for this. |
|||
| Ven 11 novembre 2005 |
- unify the "Compose message" page with the info page on the email. So it would give the link to possible forum where this email has been invited. - "private forums where he has posted" should probably be replaced by "where he has writing right". - have together with this, in any user info page, a link "Create new private forum and invite this user there". the message posted by user and seen by email access is not marked as read !!! |
|||
| Ven 11 novembre 2005 |
- GLS integration - email invitation. - The login bar on top in email access: NO. The user need not authenticate himself, since he is already authenticated. But there should be a link "Close session". It should also be save-preview-post for email invited user. |
|||
| Ven 11 novembre 2005 |
- the email invitation. The invitation should appear at the same place as the other invitation (the one of a pseudo), that is, at the forum info page. One reason is that in your new page there is no link back to the forum. But instead of adding it, just include the email invitation with the previous invitation. |
|||
| Ven 11 novembre 2005 |
- long time to enter the forum - I then posted a new message under pseudo, but it was not sent to the email. So, new posted messages should be sent to email. - I registered from email access, but then when I logged in under inviter identity, I did not see the new login name on the line of the contact table for this email. Also I notice that the registration should not ask for email since the email is already known !!! - The invitation message should not be from "www-data" <www-data@kama.neolocation.net> but from pseudo@host of the inviter. - Also, it should not be sent at the time of invitation itself, since it will be included again at the bottom of posted messages from the forum. Ifever one wanted to send this pure invitation anyway, the link "Resend invitation" is here for this. |
|||
| Ven 11 novembre 2005 |
- unify the "Compose message" page with the info page on the email. ==> gives link to forum where this email has been invited. - "private forums where he has posted" replaced by "where he has writing right". - have a link "Create new private forum and invite this user there". - the message posted by user and seen by email access is not marked as read !!! |
|||
| Ven 11 novembre 2005 |
- GLS integration -email invitation. - The login bar on top in email access is nonsense. - user need not authenticate himself, since he is already authenticated. - link "Close session". - save-preview-post for email invited user. |
|||
| Sam 12 novembre 2005 |
- translations with GLS. - translations file for dating - translations in GLS: * each site own list of translations files. --> each site : own versions --> each site : own different program components. - The home account is one component, - each forum (accessed by GLS) is another component (even if they share the same list of translation files) - dating is another component. ==> sentences to translate in each site can be different. - GLS remote user comes to a site, make his own choice of translation. But when he comes for the first time, he does not know what available translations there are, so the home site can only say what language to choose, and the remote site will set the default version for this language. So, there must be: 1) Data of the default language of this user, given during authenticating connection by the home site 2) In each site, the admin choosed what is the default translation in each language 3) Possibility for user to choose another translation in the remote site. If this choice has been done, it has priority. If not, the translation used will be the default translation for the language given during authentication. ~~~> data of the eventual choice of translation should be added to the forum invitations table. Unless it will be stored in the home site (info first sent by GLS from remote site) and transmitted again during each authentication. what is best? Maybe storing in home site will once appear better, in particular for users that want to just visit remote public forums and who therefore need no entry in forum invitation table. Or maybe it would be good to create a visitors table in each site just for this purpose... - email invitation to a forum, I would not require to have a choice of precise translation, however at least the choice of language seems to be necessary. Maybe store info on language or translation in the forum invitations table, or maybe create an embryo of account for this purpose. |
|||
| Sam 12 novembre 2005 |
- translations with GLS. - separate translations file for dating - translations in GLS: First, the thing is that when there will be a important network, each site will have its own list of translations files. The reason is that there will be freedom to different site to develop their own versions, and also their own different program components. - The home account is one component, - each forum (that is accessed by GLS) is another component (even if they share the same list of translation files), - and dating is another component. So the set of sentences to translate in each site will have the possibility to be different. * When a GLS remote user comes to a site, he will be interested to make his own choice of translation. But when he comes for the first time, he does not know what available translations there are, so the home site can only say what language to choose, and the remote site will set the default version for this language. So, there must be: 1) Data of the default language of this user, given during authenticating connection by the home site 2) In each site, the admin choosed what is the default translation in each language 3) Possibility for user to choose another translation in the remote site. If this choice has been done, it has priority. If not, the translation used will be the default translation for the language given during authentication. So, I think the data of the eventual choice of translation should be added to the forum invitations table. Unless it will be stored in the home site (info first sent by GLS from remote site) and transmitted again during each authentication. Not sure what is best. Maybe storing in home site will once appear better, in particular for users that want to just visit remote public forums and who therefore need no entry in forum invitation table. Or maybe it would be good to create a visitors table in each site just for this purpose... In the case of email invitation to a forum, I would not require to have a choice of precise translation, however at least the choice of language seems to be necessary. Maybe store info on language or translation in the forum invitations table, or maybe create an embryo of account for this purpose. |
|||
| Mar 15 novembre 2005 | - Save Preview Post system - rights system rebuilded - investigating of the current system - bugs corrections, adding functions not listed in todo list. - email invitations. |
|||
| Mer 16 novembre 2005 |
Done: - Save Preview Post system - rights system rebuilded - investigating of the current system - bugs corrections, adding functions not listed in todo list. and working on email invitations. - Email invitations |
|||
| Mer 16 novembre 2005 |
- rights system rebuilded |
|||
| Mer 16 novembre 2005 |
trust-forum.php.by and
tforum.php.by I expected to see, in forums where I am admin, whether public or private, no more link "Edit forum rights" but a link to a page with functions of viewing forum rights and editing forum denials (and this table can also possibly be used as an interface to invite to a higher right, but I do not require this). |
|||
| Mer 16 novembre 2005 |
- Save Preview Post system - rights system rebuilded - investigating of the current system - corrections - email invitations. |
|||
| Mer 16 novembre 2005 |
- rights system |
|||
| Mer 16 novembre 2005 |
both sites trust-forum.php.by tforum.php.by I expected to see, in forums where I am admin, whether public or private, no more link "Edit forum rights" but a link to a page with functions of viewing forum rights and editing forum denials (and this table can also possibly be used as an interface to invite to a higher right, but I do not require this). |
|||
| Mer
16 novembre 2005 |
- rights system |
|||
| Ven 18 novembre 2005 |
- forum rights system |
|||
| Ven 18 novembre 2005 |
- rights system |
|||
| Lun 21 novembre 2005 |
When I invited someone from
inside account, we noted it is not good that the password appears on
the screen. |
|||
| Lun 21 novembre 2005 |
When I invited someone from inside account, we noted it is not good that the password appears on the screen. |
|||
| Mar 22 novembre 2005 |
-GLS+ email invitations - new rights system |
|||
| Mar 22 novembre 2005 |
- GLS+ email invitations - rights system |
|||
| Lun 28 novembre 2005 |
- rights system. |
|||
| Lun 28 novembre 2005 |
- make changes to the most functions of the code to add just a bit of functionality to the rights system. - new rights system |
|||
| Lun 28 novembre 2005 |
- functionality to the rights system. - GLS integration - remote translation - rights system |
|||
| Mar 29 novembre 2005 |
- GLS system. - Save-preview-post - email invitations system. - rights system 1) modification of structure of rights table 2) modification of the interface by which the rights data are displayed and modified in this table (invitations, denials) 3) modification of the function that calculates a user's right from this table. - forums to calculate rights in a different way |
|||
| Mar 29 novembre 2005 |
- encoding wrong in forum
comments in tforum.php.by. |
|||
| Mar 29 novembre 2005 |
- rights system was nearly
finished. |
|||
| Mar 29 novembre 2005 |
- GLS system. - Save-preview-post - email invitations system. - rights system ~~~~> contain a function that calculates the right of a user in a forum, so that the rights system can be easily modified by modifying the computation of this function. 1) modification of structure of rights table; 2) modification of the interface by which the rights data are displayed and modified in this table (invitations, denials); 3) modification of the function that calculates a user's right from this table. - forums to calculate rights in a different way, from other data that will be developed later. |
|||
| Mar 29 novembre 2005 |
- rights system was nearly finished. |
|||
| 29-Nov-2005 |
User with W rights ==> can
create new thread |
|||
| text encoding in forum comment |
||||
| 29-Nov-2005 |
User with writing rights - can create new thread if there is already new threads if there is no new threads |
|||
| text encoding in forum coding -
including accents |
||||
| text boxes length |
||||
| Email invitation system |
||||
| GLS integration |
||||
| English interface for access |
||||
| 30-Nov-2005 |
create new thread - input thread attached link - only admin can edit link |
|||
| 2-Dec-2005 |
implementation of inviting email
to forum |
|||
| explain present rights system |
||||
| new rights systems |
||||
| new folder system |
||||
| dating system |
||||
| translation system |
||||
| 2-Dec-2005 |
1) dating_sped04.rtf from 27.02.2005 2) GLS_spec_1.04.doc from 02.05.2005 3) spec2.todo.doc from 18.08.2004 4) specification.doc from 18.08.2004 * Email invitation * GLS integration system |
|||
| 3 -
Dec 2005 |
email system: contact list ==> add email ( + invitation to join) ==> see invitation tree If Admin ==> see invitation chains ==> see users with registration problems more than X ==> set 0 problems to see all users ==> forbid invitations to some users ==> manage problem lists : add, delete, edit pb If NOT Admin ==> see ONLY users invited by yourself ==> user test01 and pass tu1234 Admin rights On forum ==> Forum creator or Invite rights : invite email to forum ( key) |
|||
| 3-Dec-2005 |
* dating_sped04.rtf : february
2005 * GLS_spec_1.04.doc : may 2005 * spec2.todo.doc : august 2004 * specification.doc : august 2004 |
|||
| http://spoirier.lautre.net/tf-todo.htm |
||||
| contact list ==> email
invitations |
||||
| email invitation 2 forum |
||||
| in database: message's author
known by ID ( increment in forum invitation table) in table: see the pseudo corresponding to this ID |
||||
| email author of a message ==>
database: invitation ID in forum forum: display email adress |
||||
| once email is registered ==>
all messages changed email adress to Pseudo |
||||
| the inviter can appear under a
different pseudo ? |
||||
| message identified with ID (
forum users table), displayed with pseudo |
||||
| email invited have no pseudos in
forum users table ==> messages posted only as Guest ??? connect forum messages / em,ail invitations? pseudo=invited_emails? |
||||
| email invited user: no pseudo,
has an id. ID connected to email adress ==> forum user table: new column ( email adress) or email adress in pseudo column? / new column for question? ==> email adress, pseudo or GLS pseudo? |
||||
| shouldn't show Guest on the
interfaces |
||||
| System User Table : user (
login/pass) connected with list of pseudos list of folders list of forums associated folders dating account GLS remote users not listed email invited users not listed here |
||||
| separate forum's user tables -
rights and invitations |
||||
| GLS remote users appear with
pseudo and invited emails |
||||
| * |
info about email invitation to
public_forum: stored in invitation table? |
|||
| store : id, email, date,
forum_id, pseudo_parent_id, secretkey as for private forums |
||||
| remove link "invite email to
forum" from public forum |
||||
| subscription: receive to email
all messages posted to public forum |
||||
| * |
test email invitation : email
should appear in forum info page as pseudo |
|||
| need link back to forum |
||||
| include email invitation with
invitation |
||||
| under pseudo, post new message
==> new message should be sent to email |
||||
| register from email access:
login under inviter identity ==> see new login name on line of
contact for this new email |
||||
| registration should not ask for
email: email already known |
||||
| invitation message from
pseudo@myhost |
||||
| invitation not sent at the time
of invitation. include it at the bottom of posted message from the forum "resend invitation" |
||||
| email access : post message and
seen by email access should be marked as read |
||||
| email access: login bar user need not authenticate himself ( already authenticated) "Close session" link |
||||
| email access: save-preview-post |
||||
| * |
email : unify page info and
compose message ==> show links to possible forums this email has
been invited |
|||
| private forum where he has
posted ==> where he has writing rights + any user info page add: " create new private forum and invite user there" |
||||
| invite someone from inside
account ==> password should not appear on screen |
||||
| * |
separate translation file for
dating |
later |
||
| GLS translation: each site has list of translations files ==> develop own versions and own components |
||||
| home account = one component each forum ( GLS) = one component who share same translation files dating = one component ==> set of sentences to translate will be different |
||||
| * GLS user comes to a site: he choose sets of translations * GLS for 1st time: does not know what translations are available Home site: say what language and then remote site takes this language |
||||
| * default user language (
authenticated connection to home site) * in each site: admin choose default language translation * user can choose another translation in remote site. If not language used is the default ==> forum invitation table: data for language choice OR stored in homesite ( info sent by GLS to home site) then transmitted during each authentication. Home site: good for users who just want to visit public forum and need no entry in forum invitation table OR visitor table on each site ? --- email invitation to a forum: choice of language? store info in forum invitation table ? on language? |
||||
| * Rights System |
Forum where I am admin (
public/private) - no more links edit forum rights links with : viewing forums rights and editing forum denials |
|||
| * calculate the righst of a user
in a forum * modify forum rights: modify structure of right tables / interface / calculation |
||||
| 4-Dec-2005 |
no invitation ==> can
register and see public forums? |
|||
| Forum Creator ==> Contact
List ==> Invite Emails Invitation ==> right to register to trust-forum ( can add in invite email) After Registration ==> User has access to all forums invited Forum Creator ==> post messages to emails ( mark message valid or someone has seen it?) |
||||
| every message to forum ==>
sent to emails emails : message content + forum link with secret key+ optional link to forum |
||||
| link to forum lets you see all
the forum, not just the message |
||||
| user invited get access to all
the forums he is invited to |
||||
| oustide forums, IN contact list
==> send message to emails |
||||
| In forum: creator ==> invite email messages written ( WRights) ==> saved ==> Then posted ( marked valid) when marked or someone read it ==> send to emails ( valid on users table + read rights) ==> marked READ |
||||
| 4-dec-2005 |
without invitation: on index
page, everybody can register? and see public forums? |
|||
| later can close this : register
only through invitation / decide which forums not visible everywhere.
Denial of guest |
||||
| * |
creaor of forum + contact list
==> can invite emails |
|||
| this invitation gives right to
register to trsut-forum |
||||
| make this right an optional
choice? |
||||
| after registration, user has
access to all forums he was invited |
||||
| * |
invited to only one forum |
|||
| case: invited by many forums? |
||||
| * |
creators can post message via
email and email do not contain invitation |
|||
| * |
outside forum, from contact
list, one can post messages to an email |
|||
| in a forum, a creator can invite
an email a writing rights ==> all messages posted to forum and not email ==> saved as message in thread THEN after posted on forum, and marked as VALID, THEN it is sent to all emails in forum table of users ==> Marked as read |
||||
| message is posted to email after
marked as valid or after somebody has seen message |
||||
| 4-Dec-2005 |
creator of forum: chooses to
send message to email decides if to invite ==> every message to this forum duplicated to this email ==> email message: copy of message + link to thsi forum + secret key + optional registration invitation |
|||
| access to forum and righst to
register are different! |
||||
| can later on a user migrate his
site to another? |
later? |
|||
| from message, the email sees all
the forum. A key is generated for this email. |
||||
| the key is deleted after
deleting email from the forum |
||||
| after registration of email: user access all forums he was invited ( R,W, Admin) |
||||
| his parent is only one person (
link used to register) |
||||
| 14-Dec-2005 |
user invites user@host, user
invited by user@host. If local invite user@host1, on local user@host1 can invite user@host2 Folder: pseudo inviter 2 forum@host forum table: pseudo1@host1 invites pseudo2@host2 |
|||
| 20-Dec-2005 |
R,W,Admin,Creator Rights Only Creator can lower another admin level Admin can change R,W users |
|||
| create 2 tables or 2 columns in
table: Invitation to rights / denial to rights |
||||
| One general type of forum ( and
not 2 forum) : public / private forum are 2 of possible 3 cases |
||||
| 20-Dec-2005 |
email users invited only with RW
rights |
|||
| manage comments for remote users
==> put it in "forum invitation table", comment modification |
||||
| the key for security is a random
number |
||||
| mark message as read when it is
sent to some emails |
||||
| XML - formatted and encrypted
data |
||||
| sends : server host, language,
remote function name, arguments to function |
||||
| access to remote host : bookmark, or links. OR communication between servers for other purposes |
||||
| bookmarks links contains pseudo,
hostID, language, secret string |
||||
| all communication encrypted (
through bookmark, or directly between servers) |
||||
| session contains : pseudo,
userid,id,language ==> user ( pseudo, hostid) |
||||
| 21-Dec-2005 |
other users can not invite
emails to ADMIN rights email invited can post messages only if he has W rights |
|||
| local users name pseudo(comment)
or pseudo@host |
||||
| hosts have nicknames not similar
to domain names. |
||||
| there is an info page of users :
click on pseudo leads to pseudo info page. for email users : info page says if it has invitation or not ( by you or by someonesels) |
||||
| the link holds secret infos:
inviter, forumID, email rights |
||||
| * |
encrypt useng private key and
send to remote host: all info crypted by symmetric keys and the keys were renewed regularly by PG. Symmetric keys ( crypting and signature) |
|||
| if session is open ==>
requests contains url to remote host, no key verification required. |
||||
| if user access server through
SSL, hide URL on internet and parameters? ==> money exchanged
to be stored? |
||||
| UTF-8 : French keyboard for
letters |
||||
| 21-Dec-2005 |
URL
http://trust-forum.php.by/index.php?action=showthread&id=2 global list of thread for the forum ---> should be http://trust-forum.php.by/index.php?action=showthread&forum=1&id=2 local list of threads linked to the forum number |
|||
| System robustness for 1000 users |
||||
| Database structure for the tables |
||||
| 22-Dec-2005 |
is email invitation finished? |
|||
| 24-Dec-2005 |
forum translation to utf-8 |
|||
| 24-Dec-2005 |
forum translation to utf-8 to be
done tomorrow - accents - text size - comment length |
|||
| 25-Dec
2005 |
short length of comment or
cutting of comment --> to do? |
|||
| ? accessing forum after session
ending |
||||
| 25-Dec-2005 |
? pb of accessing forum after
session ends |
|||
| email invitation and comment
lengths? |
||||
| 26-Dec-2005 |
thread list ==> link called
creating thread |
|||
| PB: create private forum with
same name as existing public forum ==>identify forum by ID and not Name ==> different forums with same name should be allowed except : same server fopr both public/semi-public! |
||||
| 26-Dec-2005 |
? link to create thread from
thread |
|||
| forum should be identified by ID
not by name |
||||
| 30-Dec-2005 |
new thread folders and rights |
|||
| 30-Dec
2005 |
||||
| Jan-2006 |
avant derniere version |
|||
| 3
Jan 2006 |
-? email invitations |
|||
| 4
jan 2006 |
specification of - forums with gls - email invitations, - new rights system - new folders structure. Receive this document for ackowledgement. |
|||
| 5
Jan 2006 |
what usr should see and be able
to do |
|||
| 6
Jan 2006 |
- GLS - forums - new rights systems -user folders ( tree structure, semi-public bookmarks and others) |
|||
| 6
Jan 2006 |
1) GLS 2) forums 3) new rights system 4) user folders - folders as before -tree structure - features described in tf-todo page semi-public forums bookmarks |
|||
| 8
Jan 2006 |
- forums - GLS between host - New right system - Folder System Trust forum with new rights system With GLS to access forums and o visit bookmarks |
|||
| 8
Jan 2006 |
-forums -GLS between hosts -new rights system -user folders ==> trust-forum -new rights system -using GLS ( acces forums , visit bookmarks). |
|||
| 9
Jan 2006 |
GSL module working alone ==> workflow diagrams use case diagrams and others FILENAME : forums_invitation1.1.DOC |
|||
| 9
Jan 2006 |
specification of trust-forum -forums -GLS -invitations -new rights system -user folders. ==> GLS module. ==> workflow diagrammas use-case diagrammas |
|||
| 10
Jan 2006 |
GLS offers transparency of
accessing multi-site based forums later add wikis and dating |
|||
| 10
Jan 2006 |
- "Global Login System provides transparency of accessing of multi-host based forums." + dating, wikis + new features |
|||
| * |
- Main menu consist of points + Forums + Bookmarks + Datings + Contact list + Configuration + Logout |
|||
| * |
dating - appearance of datings optional - other features |
|||
| * |
+ User folders: - same folder ==> different types of forums - few semipublic forum: ==> empty tree: no |
|||
| * |
+ 2 root folders: - mainbox - public forums : within it ==> + semipublic + public + forums -divided by horizontal line -move forums -move folders? |
|||
| 10
Jan 2006 |
* GLS ==> access multi-host
based forums * Later additions: - wikis - dating * New - ForumsDating: more features to be added later on * User folders: - different type of forums on the same folder? - if no semiforum ==> empty tree? * forums are classified to their type ( not good) : some users might want to list forums of different types * folder = list of bookmarks with a display infos * local folder listing remote forums % rights user have in those remote forums - link forum or info page with Inside a folder, make a division with titles:"default bookmarks" renamed "default public folder" * public forum link user folder | default bookmarks - default bookmarks ==> remote hosts public and semipublic forums ~ forum content - folder trees understanding * bookmark page : no division left and right ==> only user bookmarks * edit current pseudo ( name, comment, default folders) ==> if pseudo name change ( edit), then identification not OK ==> if pseudo has invitation then forum put there? * pb : add new translation /edit new translation version number in translation should not be changed make new versions from existing one ( precise who fill it ==> field filled by) on top of fields: can view existing versions * no version - except private can be edited * private and public translations differences |
|||
| * |
forum creation form: name folder ( one of user folder) pseudo ( one of pseudos) comment type (public, private, semi-public) right to guest ??? dependance/independance from folders |
|||
| * |
user rights? can't read ==> not there can write ==> can see the form to write message at bottom admin ==> see "edit denials" , edit/delete to all messages |
|||
| * |
Forum info: - 2 comments ( one short, one long) - forum type ( public, semipublic, private) - list of invitations AND denials invitation or denial can be empty invitation with the date denial with the date ==> ask if should add with button add denial day Admin can only change deny level |
|||
| 10
Jan 2006 |
1. guest: forum rights ==> access for public/semipublic forums 2. Email invited user: email received key ==> access public/semipublic forum 3. Trust-forum invitation ==> key received in trust-forum email invitation |
|||
| * |
remote users: * their rights ==> forums only according to their rights * no folder : list of public forums? * no multiple pseudos for now * no create forum * no invite to trust forum * no contacts ( link to home host list of contacts) contact list ==> poup up of his owm host contacts page ----> remote forum doesn't get the list of private contacts ( private info) add pseudo to contact list ==> only on his home remote site, so new actual host can not know the pseudos |
|||
| * |
server to call remote function: - encode name and arguments ( XML) - encrypt public key - signed with private key CPU issues difference: invitation to trsut forum \% particular forum |
|||
| * |
forum id, invitation level and
deniance level of email |
|||
| tables ==> forumid, email ,
invitation id nay user : forum right ==> calculated from data on forum invitation table |
||||
| * |
pbs of mixing public/private
forum in same folder |
|||
| 11
Jan 2006 |
Folders: - main Box - user folders ( subfolders = tree structure) - public(semipublic) forums - bookmarks |
|||
| * |
Difference remote users # local
users main menu: forum, contact list,exits 1. forums: remove users ==> their rights ==> can use user folder are at home site user folder has no folder at remote host ==> list of public and semi public only ? list local private forums he can access? 2. contact list ==> pop-up of local host contact list 3. selectbox ==> user can be invited as would a local user do? pb: put the content of one remote site into the new site? 4. no invitation tree, no register new 5. close remote session 6. folder list contains only public forum folders |
|||
| 11
jan 2006 |
Same folder: -mix public / private forums ==> not done - so, there are folders: 1) MainBox 2) user folders ( subfolders in ==> tree structure) 3) public (semipublic) forums 4) bookmarks |
|||
| * |
* "registration to trust-forum, using key received from trust-forum user" 1.Guest ( public / semipublic forums % forums rights) 2.Email invited user ( public/semipublic/private % email received key) 3.Trust-forum invitation key - by email registration to trust-forum |
|||
| * |
* email invited user ==>
invited to forum ==> NOT invited to to trust-forum. |
|||
| * |
* Remote user - Visit/Use forums = f(rights) - main menu? - No folders (except public forums list ?) - Not multiple pseudos (later?) - Not create forums - Not invite to trust-forum - Not have contacts (pop-up link to home host) - invite another to this remote forum (- GLS trust-forum user: now - invite email ( contact list) to remote forum - "From contacts list" ==> pop-up user home site. contact ==> invite to remote forum. |
|||
| * |
* user's contact ( private
data) ==> to remote host |
|||
| * |
+ Main menu consists 1."forums" 2."contact list" 3."exit" |
|||
| * |
+ 1.In forums: remote user use forums % rights. 2.In contact list remote user ==> pop-up contact list from remote user 4. remote host: no "invitation tree" no "register new" |
|||
| 11
Jan 2006 |
3. closes remote session Do NOT
closes window |
|||
| * |
5. folder list ==> only
"public forums" folder. |
|||
| * |
6. remote server to call
remote function |
|||
| * |
i.XML ==> Encode
(function name and arguments) ii.Encrypt (public key) : openssl iii.Sign encrypted ( private key) : openssl ----> CPU evaluation ----> test with large number of users on 2 hosts clicking at same time |
|||
| * |
A. differences between - invitation to trust-forum - invitation to a particular forum |
|||
| * |
B. ==> emails_ forumid, invitation level deniance level of email |
|||
| * |
C. from some table, the key gives * forumid (= which forum) * email address * invitation id (= line in the forum invitations table) |
|||
| * |
D.Righ2forum = calculate_right
(forum_invitations table). |
|||
| * |
Re[6]: trust-forum (remote user) invites ~ (local user) invites - select pseudo:host from selectbox. ==> solution here : pop-up from remote host? "forum info page" ==> local host remote functions |
|||
| 12
Jan 2006 |
remote site should never get
remote user's contact list! |
|||
| 14
jan 2006 |
table : forums_users |
|||
| 14Jan2006 |
forum specifications: t : forum_invitations_1.2.zip |
|||
| 15
Jan 2006 |
Main Box ==> private
forums and derived folders and subfolder ==> copies of link to public forum SemiPublic Forums Public Forums |
|||
| * |
bookmarks : all page no default bookmarks here default bookmarks ="remote publuc forums" are accessed by libk on forum screen |
|||
| 15
january 2006 |
remote host should not access
remote user's contact list pop-up ( local home) of remote user : - link to local host - invitation tree - NO registration new ( this is local host) the pop-up is not a page of remote host ==> link to home account? |
|||
| * |
use existing forums only existing forums and semi public forums |
|||
| * |
rights calculation: function=
max(invitation, denyance) |
|||
| bookmarks in bookmarks page list of default bookmarks: list from remote hosts ==> user can access from remote forums s, so no need |
||||
| ? what should go on bookmarks? ? pb of translation in remote host? ? add possibility to change passwords? |
||||
| 15
jan 2006 |
* contact list should not be
returned to remote host |
|||
| * |
* function(getting contact
list) calls only when remote user has open session |
|||
| * |
* why contact list should not be
returned directly to remote host, even user have open session? |
|||
| 15
jan 2006 |
Re_trust-forum.msg | Re_trust-forum.msg |
|||
| * |
remote user contact list %
privacy of remote user |
|||
| 16
Jan 2006 |
||||
| 16
Jan 2006 |
* dating link |
|||
| * |
* "Edit current pseudo (name,
comment, default folder of forums)" ==> user identified by id, id will never be changed. programmer want to change pseudo name!!! |
|||
| * |
*"default folder of forums" do: pseudo invited 2 forum ==> forum put in this folder ? - default folder = folder = "forums" link. ==> subscribed forums with new messages. |
|||
| * |
1. "add new/edit own translation (based on switches)". once I edited own translation i was using + I modified version number. ==> pb --> solution: "version number" should never be edited. --> new version from (=with fields filled by) one existing version, while viewing (on top of fields) existing other version - no existing version (except private version ?) can be edited. |
|||
| * |
# private and public
translations. |
|||
| * |
-"version number"=newness of this translation. -make public translation or private translation. |
|||
| * |
1. no reading right ==> can't see it writing right ==> see form 2 write message admin right ==> see the link "edit denials" edit/delete to all messages. |
|||
| * |
2. user can define his access by
links see directly his access level. |
|||
| * |
3. admin links to change
invite/deny level: NO !!! |
|||
| 17
jan 2006 |
2 pseudos from same person can
be on remote host, but emost host can not know these 2 people are the
same! ==> discussion about if the pseudi can be modified |
|||
| * |
default folders forums link clisck ==> folder = default folder has subscribed forums with new messages subscribed forums with new messages into a default folder ( not priority!) |
|||
| * |
version number : see novelty f
translation -->? version number is user controlled or system controlleds? ==> translation for later |
|||
| 17
Jan 2006 |
1. "Edit current pseudo (name, comment, default folder of forums)" --> user identified by id id never changed. |
|||
| * |
===>???? SEEMS HERE DESIGN NOT GOOD * user has 2 other pseudos ==> 3 ids, |
|||
| * |
--> remote users identified
(pseudo, id) ==> function to get id from pseudo when one will enter by hand a pseudo. invitations from contacts list ==> pseudo and id |
|||
| * |
--> update pseudo name
in remote site |
|||
| * |
==>essential: remote
sites no way to know that 2 given pseudos are from the same user (for the same reason as remote site should not get user's contacts list). |
|||
| * |
- remote server get only pseudo
name and pseudo id. ==> no way to get userid from pseudoid for remote server. ==> tables of remote pseudos updated by global query (if user chanes his name he says all remote hosts about it). i think this is not bad because user changes pseudos's name not often. |
|||
| * |
- "default folder" is a folder let another folder the role ~ main box make subscribed forum with new messages appear to different folders according to conditions. |
|||
| * |
==? ok, no default folder |
|||
| * |
1. "version number" |
|||
| * |
2. - private/public flag to all of the translations to protect the translation if user likes. - translations system ==> later |
|||
| 18
jan 2006 |
pseudo names changing ==> for
later on? |
|||
| ??? usenet protocole? |
||||
| translation flags to protect
translations |
||||
| BUG in previous version |
||||
| 18
Jan 2006 |
Forum Invitation: forum_invitations_1.3.DOC |
|||
| 19
Jan 2006 |
check box : move selected forum
to another folder private forum ==> main box public forum ==> removed from user folder ( public forums) |
|||
| * |
delete bookmaks, add comments to
it, change order of these |
|||
| * |
do not remove pseudos forgot password link |
|||
| * |
invitation viewing access ( user
only) - list of all invitations, - list of all denies link to rights table : rights editor buy no deny level. |
|||
| 19
Jan 2006 |
Guest ==> no key from trust
user |
|||
| home link for remote users
==> contact list |
||||
| * |
forum rights: just one function
==> can change it later on user enter forum ==> call function ==> get rights ==> put in session variable |
|||
| * |
inside user folders, can create
subfolders |
|||
| * |
remote host should not have
access to local user list of folders ? to which folder add remote forum? user can change pseudo he access remote public forums or public forums |
|||
| * |
list of all remote sites, user
goes there eith chosen pseudo or anonymously? if anonymous, no
writing right! ==> pop-up to choose pseud ( ~ contact list) throwable pseudos do not have same rights as pseudos forum accessible in read only mode |
|||
| * |
divide long threads in many pages |
|||
| 20
Jan 2006 |
throwable pseudos |
|||
| 20
jan 2006 |
threwable pseudo for later |
|||
| 23
jan 2006 |
1) can click on user info page
and see the info page 2) link back to home site for remote user: - create forum - invite user to forum with W or Admin - post message to forum |
|||
| 23
Jan 2006 |
there are some questions
to you: 1) pseudo invited, do other pseudos have access? 2) remote user ==> throwable pseudo (only read rights). ==> write/administrate ==> pop-up window-->pseudo |
|||
| 24
Jan 2006 |
if user pseudo invited,
the other pseudo can't be used ???? pseudo inviting same user pseudo |
|||
| * |
1) goes to public forum (
from default bookmarks) : can be anonymous, Read only no writing 2) has option of choosing anonymous pseudo and of putting a name on it for public forum 3) for private remote forum, only invited pseudo |
|||
| 25
Jan 2006 |
- if have private forum with
user : not allowed to open another private forum with this user ==> private forum in a list with "he has written" # "he has writing rights" can see all the private forum he has with a user, and if there are messages on it. can transmit it on remote hosts??? |
|||
| 25
Jan 2006 |
- session ends just as it starts |
|||
| * |
- user info page. 1) (GLS): user1@host1 sees in forum@host2 message from user3@host3, and clicks for info page: ===> info page at host3. 2) Link home site => new forum with this user. This interface makes: - Create new private forum - Invite this user to the forum, to writing right to admin - Post the first message to this forum. |
|||
| * |
this link should be at the pseudo info page, yes? |
|||
| * |
1. - From folder or
bookmark to remote forum choose pseudo ( anonymous, throwable) add below the folder, among "actions": change pseudo used if public forum. |
|||
| * |
- From folder or at bookmark to a remote private forum, ==> only use pseudo invitated with |
|||
| * |
- selectbox 2 select pseudo ===> visit thread # pseudos (same user) invited to same thread select box appera only if (>1) pseudo invited. |
|||
| 26
Jan 2006 |
user info page : see forums where - pseudo wrote messages - pseudo didn't write message, but has reading right - create new forum -add user to forum - create first message in forum |
|||
| * |
forums_pseudo, forums_messages,
forum_folders, dating tables |
|||
| 26
Jan 2006 |
1.I have a private forum to
someone |
|||
| * |
2. person did not write there ==> write there if want to write to this person ==> no new forum to this person |
|||
| * |
2 Solutions: * private forum in the list ( user info page) with 'he has written" --> "he has writing right" * # in this new list : forums - old list # the others. 1) in the user info page to see forums, where 1.1) this pseudo wrote messages 1.2) this pseudo have more than reading right, but did not write any messages 2) user info page, possibility to 2.1) create new forum 2.2) add user to forum 2.3) create first message in the forum |
|||
| 27
Jan 2006 |
admin panel to manage pseuods |
|||
| 1st
Feb 2006 |
documents on what should be
administered trust-_forum database structure |
|||
| 2nd
Feb 2006 |
bmp version of database structure Trust-forum_DB.zip |
|||
| 7
Feb 2006 |
Panel admin: forum_adminpanel_1.0.DOC | |||
| 8
Feb 2006 |
personal web pages to be updated
later |
|||
| 8
Feb 2006 |
admin panel |
|||
| * |
==>????? ==> forum_adminpanel.doc ==> 01_info.doc |
|||
| 13
Feb 2006 |
admin panel documentation forum_adminpanel1.2.doc |
|||
| 12
Feb 2006 |
||||
| * |
||||
| * |
can delete an invitation edit denials modify who is the owner |
|||
| * |
User Type: - Administrator - Guest - Normal User -Email User -GSL remote user - GSL anonymous ? |
|||
| 12
feb 2006 |
admin panel + files |
|||
| 13
Feb 2006 |
pseudo is inactivated - if deleted ==> messages deleted - if he owns forums, the ownership should be given to other |
|||
| 13Feb
2006 |
dating specifications - calculations - check before accessing database that user has right to do it ==> check user rights and URL forum_dating.doc |
|||
| 13
Feb 2006 |
"If pseudo = user name –> deletes after user confitmation "Pseudos" ==> "pseudos # username" |
|||
| * |
* list of users==> user ==> pseudos only 1 pseudo in list ==> deletes ( user account deactivating/deleting) |
|||
| * |
* create global list of pseudos
(# from usernames) |
|||
| * |
"ii.Forums accesses. Access list to any forum modified with owner rights (read forum_invitations.doc)." DO NOT modify invitations OK : - Delete an invitation - Edit denials - Modify the "who is the owner" (to anyone). ==> forum ownership ? |
|||
| * |
Type of user: - Administrator - Guest - Normal user - Email user - GLS remote user - Later, GLS anonymous user |
|||
| 13
Feb 2006 |
dating.doc file sent |
|||
| 13
Feb 2006 |
GLS, email invitations |
|||
| 15
Feb 2006 |
they describe existing code
==> then he can add ideas on it |
|||
| 15
Feb 2006 |
Datings: -see what is wrong -you have new ideas about datings. - look every displayed page |
|||
| 18
Feb 2006 |
admin panel : allow/disallow
free registration |
|||
| 20
Feb 2006 |
"conversation about user": - see pictures which are clearer - advice on the quality of the photo * protecting sql tables and sql commands |
|||
| 21
Feb 2006 |
* "advices forum / photo" ==> "conversations about new user" - GLS + forums integration - SQL-unsecured |
|||
| 23
Feb 2006 |
Check user rights Parse URL parameters |
|||
| 23
Feb 2006 |
- datings specification - bugs: check if user rights ==> databases ==> check user rights. ==> parse URL parameters. |
|||
| 23
Feb 2006 |
- check user rights. - parse URL parameters. |
|||
| 23
Feb 2006 |
- dating specifications * fix the holes - check user rights - check URL parameters No URL ==> SQL diretly! forum_datings1.0.doc |
|||
| 26
Feb 2006 |
folder status and calculations
of matches |
|||
| 26
Feb 2006 |
- folders statuses - calculations of matches. |
|||
| 28
Feb 2006 |
dating system database |
|||
| 28
Feb 2006 |
trus forum databases : Trust_forum_db_datings.vsd (0.14 MB), Trust_forum_db_datings.gif (0 |
|||
| 11
mars 2006 |
tforum1.php.by,
tforum2.php.by - register to both of this hosts - invite from one host to another - rights |
|||
| 12
mars 2006 |
I see it is still "pubilc forums". Will it ever end ? * What's this "Webmail" ?????? * No Save-Preview-Post ! * No change in folders nor in way to create new forum. * Did you once more base your work on obsolete version ???? |
|||
| 12
mars 2006 |
links are www.tforum1.php.by/gls and www.tforum2.php.by/gls - remote user invitation to forum - remote user post messages to remote forum and other |
|||
| 13
mar 2006 |
* list of invalid messages. ( pseudo, thread name, message header, message body) * invite author of invalid message to help forum (saying messages must be validated). * For the gls: the address is http://tforum1.php.by/gls/ (without www) * guest see forums that user cannot see. * "default bookmarks" (==> "remote public forums") left margin of folders instead of main menu) one appears like a guest to tforum2 (as concerns interface). ==> save-preview-post appear ==> identity (pseudo@home) on the top * forum "For TF1" empty, without possibility to write. |
|||
| 13
mars 2006 |
the mathematics there |
|||
| 15
mar 2006 |
Total sum of penalties. 1. language. Penalty of others language (Lg, 0 to 40) + my willingness to study his language (Wl, 0 to 2). ==> This is totally false ! 2. Personal info. Penalty of other’s gender (Ge) + penalty of other’s Smoking habits (Sh) + penalty of other’s Drinking habits (Dh) + p. of other’s birth year (By) + p. of other’s + p. of other’s marital status (Ms) + p. of other’s “children already in charge” (Cc) + p. of other’s Height (Ht) + p. of other’s Weight (Wt) + p. of other’s Eyes color (Ec) + p. of other’s Hair color (Hc) + p. of other’s Hair style (Hs) + p. of other’s Nationality (Nt) + p. of other’s Ethnicity (Et) + p. of other’s Religion (Rl) + p. of other’s Education (Ed) + p. of other’s Income (In) + p. of other’s Handicap (Ha) + p. of other’s Type of relationship (Tr) + p. of other’s Want children (Wc). - Want children = exception (common badness) - Same for pets. 3. place of a meeting. Penalty for other’s region for first meeting (Fm) + p. for other’s possibility to have income (Oi) + p. for other’s willing I have income (Mi). * common badness = place for first meeting. common badness = minimum over all places of (sum of both badnesses for this place). * common badness =long term living place * this last badness ==> integrated to type of relationship: whether this relationship involves long living together. * common badness contribution of (type of relationship and long term living) = Minimum on relationship types of( (sum of both badnesses for this relationship type)+(common badness for long term living place if this relationship type involves it, 0 else)). ==> total sum of A to B is Ta = Lg + Wl + Ge + Sh + Dh + By + Ms + Cc + Ht + Wt + Ec + Hc + Hs + Nt + Et + Rl + Ed + In + Hf + Tr + Wc + Fm + Oi + Mi. ==> except common badnesses... Total sum of B to A is Tb = Lg + Wl + Ge + Sh + Dh + By + Ms + Cc + Ht + Wt + Ec + Hc + Hs + Nt + Et + Rl + Ed + In + Hf + Tr + Wc + Fm + Oi + Mi. > T = Ta + Tb. No: T = Ta + Tb + common badnesses If ((Ta<=40) and (Tb<=40) and (T<=70)) return true. ------------------------------------------------------------------------ Date: Jeu 16 mars 2006 21:34 > Total sum of penalties. 1. language. Language knowledge level (Lg, 0 to 40) Language badness is (Lga + Lgb) = min ==> I said you seem to have completely missed language profile specification. ------------------------------------------------------------------------ Date: Jeu 16 mars 2006 22:50 "language profile specification"? ==> "dating_spec_04.rtf" ==> "datings" thread. |
|||
| 17
mar 2006 |
==>
"dating_spec_04.rtf" ( 27 february 2005) |
|||
| 14
mars 2006 |
Total sum of penalties. 1. language. Penalty of others language (Lg, 0 to 40) + my willingness to study his language (Wl, 0 to 2). 2. Personal info. Penalty of other’s gender (Ge) + penalty of other’s Smoking habits (Sh) + penalty of other’s Drinking habits (Dh) + p. of other’s birth year (By) + p. of other’s + p. of other’s marital status (Ms) + p. of other’s “children already in charge” (Cc) + p. of other’s Height (Ht) + p. of other’s Weight (Wt) + p. of other’s Eyes color (Ec) + p. of other’s Hair color (Hc) + p. of other’s Hair style (Hs) + p. of other’s Nationality (Nt) + p. of other’s Ethnicity (Et) + p. of other’s Religion (Rl) + p. of other’s Education (Ed) + p. of other’s Income (In) + p. of other’s Handicap (Ha) + p. of other’s Type of relationship (Tr) + p. of other’s Want children (Wc). 3. place of a meeting. Penalty for other’s region for first meeting (Fm) + p. for other’s possibility to have income (Oi) + p. for other’s willing I have income (Mi). So, total sum of A to B is Ta = Lg + Wl + Ge + Sh + Dh + By + Ms + Cc + Ht + Wt + Ec + Hc + Hs + Nt + Et + Rl + Ed + In + Hf + Tr + Wc + Fm + Oi + Mi. Total sum of B to A is Tb = Lg + Wl + Ge + Sh + Dh + By + Ms + Cc + Ht + Wt + Ec + Hc + Hs + Nt + Et + Rl + Ed + In + Hf + Tr + Wc + Fm + Oi + Mi. T = Ta + Tb. If ((Ta<=40) and (Tb<=40) and (T<=70)) return true. If match is true: How to define language (just recommendation to opponents, they can talk any language they want). Language Lga + Lgb = min |
|||
| 16
mars 2006 |
Total sum of penalties. 1. language. Language knowledge level (Lg, 0 to 40) Language badness is (Lga + Lgb) = min 2. Personal info. Penalty of other's gender (Ge) + penalty of other's Smoking habits (Sh) + penalty of other's Drinking habits (Dh) + p. of other's birth year (By) + p. of other's + p. of other's marital status (Ms) + p. of other's "children already in charge" (Cc) + p. of other's Height (Ht) + p. of other's Weight (Wt) + p. of other's Eyes color (Ec) + p. of other's Hair color (Hc) + p. of other's Hair style (Hs) + p. of other's Nationality (Nt) + p. of other's Ethnicity (Et) + p. of other's Religion (Rl) + p. of other's Education (Ed) + p. of other's Income (In) + p. of other's Handicap (Ha) Common badnesses: Type of relationship (Tr) + p. of other's Want children (Wc). Tr is calculated is min (Tra + Trb), Wc is calculated as min (Wca + Wcb) 3. place of a meeting. Penalty of first time meeting (Fm): (Fma + Fmb) = min Penalty for long term living (Ll): If Tr = (Long relationship or marriage), Ll = minimum over all geographical areas, of the sum of both badnesses for each other on this area, where the badness of a person A for the other B in an area is the one affected by B to the situation regarding income that A declared in this area. If Tr = (correspondence or short relationship), Ll = 0 4. result. So, total sum of A to B is Ta = Lg + Ge + Sh + Dh + By + Ms + Cc + Ht + Wt + Ec + Hc + Hs + Nt + Et + Rl + Ed + In + Ha Total sum of B to A is Tb = Lg + Ge + Sh + Dh + By + Ms + Cc + Ht + Wt + Ec + Hc + Hs + Nt + Et + Rl + Ed + In + Ha Tc (common badness) = Tr + Wc + Fm + Ll. T = Ta + Tb + Tc. If (Tc>40) return false. If ((Ta<=40) and (Tb<=40) and (T<=70)) return true. If match is true: How to define language (just recommendation to opponents, they can talk any language they want). Language Lga + Lgb + Wla + Wlb = min. |
|||
| 16
mars 2006 |
"language profile specification"? ==>"dating_spec_04.rtf", in trust-forum, "datings" thread. Total sum of penalties. 1. language. Language knowledge level (Lg, 0 to 40) Language badness is (Lga + Lgb) = min => NO : see language profile specification. file : Dating_Spec_04.rtf |
|||
| 17
mars 2006 |
dating.htm |
|||
| 18
mar 2006 |
example: A set next values: B set next values: 1. not speaking - 40 40 2. something - 30 35 3. a little - 20 30 4. manage well - 10 20 5. good - 5 10 6. very good/native - 0 0 there are 2 languages, l1 and l2 language A B l1 6(ver good/native) 4(manage well) l2 2(something) 1(not speaking) ready to learn other's 2 1 common badness is 0 + 20 = 20, because (6+4) > (2+1) ==> No, there is no common badness for languages ! * quality of conversation is 5, because B set 4 for l1 and he is ready to learn other's language (1) so quality is 4+1 = 5, but not 6 Yes. Therefore, B's badness for A is 5 and A's badness for B is 10. * define badnesses of knowledge skills not by user but by admin, globally for all host. ==> I don't agree. .doc file |
|||
| 18
mars 2006 |
example: A set next values: B set next values: 1. not speaking - 40 40 2. something - 30 35 3. a little - 20 30 4. manage well - 10 20 5. good - 5 10 6. very good/native - 0 0 there are 2 languages, l1 and l2 language A B l1 6(ver good/native) 4(manage well) l2 2(something) 1(not speaking) ready to learn other's l. 2 1 common badness is 0 + 20 = 20, because (6+4) > (2+1) quality of conversation is 5, because B set 4 for l1 and he is ready to learn other's language (1), so quality is 4+1 = 5, but not 6 * define badnesses of knowledge skills not by user but by admin, globally for all host. ==> ARE THESE CORRECT? ------------------------------------------------------- Date: Lun 20 mars 2006 23:01 * rigourous in formulas ? * diversity of languages * diversity of languages in dating formulas? ------------------------------------------------------- Date: Mer 22 mars 2006 22:26 hobbies or interests: * values more than "yes/a little/no" 1) music style (rock, pop, blues, dark, dnb, rnb, etc) 2) team sport playing (yes / a little / no) 3) computer games playing (yes / a little / no) 4) programming (yes / a little / no) 5) guitar playing (yes / a little / no) (or maybe musical instruments playing) 6) drawing (yes / a little / no) 7) dancing (yes / a little / no) 7) collectioning (stamps, coins, micro-models, cards, posters, etc) |
|||
| 19
mar 2006 |
dating mathematics. For languages ==> diversity of languages role. * quality of conversation in one language as you did ==> final quality of conversation = maximum of qualities between all languages. * common badnesses want pets: (cat(s)/dog(s)/both or more/other/none). * penalty of first time meeting (Fm): "min over places (Fma + Fmb)" " if Tr = (Long relationship or marriage), " the type of relationship = free variable ( not fixed value). 1) Ll = minimum over all geographical areas, of the sum of both badnesses for each other on this area, where the badness of a person A for the other B in an area is the one affected by B to the situation regarding income that A declared in this area. 2) Tr= min over types t of relationship ((Tra(t) + Trb(t) + Ll) if t=Long relationship or marriage, (Tra(t) + Trb(t)) else). Tc (common badness) = Tr + Wc + Fm + pets. (you must not repeat Ll here as it is integrated in Tr) "If match is true:" your file ends on this unfinished sentence. |
|||
| 19
mar 2006 |
dating mathematics Totalsumofpenalties.htm |
|||
| 21
mar 2006 |
Quality of conversation = max over all languages, of the quality of conversation in each language. |
|||
| 21
mar 2006 |
Penalty for long term living (Ll) must not be calculated using Type of relationship, but the contrary ? Add Hobbies and interests. ~ items of personal info, with values (No/a little/yes) (and badness for each of no/a little/yes of the other). (so this requires no more programming, just adding more elements to a list) |
|||
| 21
mar 2006 |
quality of conversation fixed : Totalsumofpenalties.htm ==> : Totalsumofpenalties2.htm |
|||
| 22
mar 2006 |
dating system: add status D+ (Delayed+) ~ as D except that D+/N ==> D+/U in the same way as S/N is changed to S/U, with the difference that U/D+ appears last, after U/N. |
|||
| 22
mars 2006 |
* tforum1.php.by/gls * tforum2.php.by/gls * "admin panel + SQL protection" * datings will be started * further point in dating system: - add status D+ (Delayed+) ~ D - except that D+/N ---> D+/U ) ~ ( S/N -> S/U) - U/D+ appears last, after U/N. |
|||
| 23
mar 2006 |
hobbies or interests: i think it is good to make values not only "yes/a little/no" but more different values 1) music style (rock, pop, blues, dark, dnb, rnb, etc) I rather thought things like rock (yes / a little / no) pop (yes / a little / no) Unfortunately it makes things rather heavy. But... I'm just thinking of a way to simplify thingks by considering music as a common choice (contrary to other interests that can be made separately by each partner), therefore can be handled by common badness. 7) collectioning (stamps, coins, micro-models, cards, posters, etc) I think collectioning is too unsignificant thing to be considered. |
|||
| 23
mar 2006 |
* strange: create a private forum in the public forum folder ! ==> public forum folder NOT included in the list of folders to create a forum in. |
|||
| 23
mar 2006 |
dating system: add a status D+ (Delayed+) that would be the same as D except that D+/N is changed to D+/U in the same way as S/N is changed to S/U, with the difference that U/D+ appears last, after U/N. Would it be easy to include ? ==>the task is to create new status D+ (Delayed+). difference between D and D+ is in order of representation of matches, yes? ==> No, the order of representation of mathes is the difference between U/D+ and U/S (and all other U/*). The difference between D and D+ is that D/N is stable whereas D+/N is changed into D+/U. * Public forum proposed as a folder for new forum ==> pb for specification and database structure for folders. * Public forum folder = public folder (user can't play with) * public forum ==> in the Public forum folder but the user creating it wants it in his personal folder too. |
|||
| 23
mar 2006 |
* further point in dating system: - add status D+ (Delayed+) ~ D except that D+/N --> D+/U ) ~ ( S/N --> S/U) difference that U/D+ appears last, after U/N. ==> create new status D+ (Delayed+). difference between D and D+ is in order of representation of matches ???? |
|||
| 23
mar 2006 |
* order of representation of mathes is the difference between U/D+ and U/S (and all other U/*). * The difference between D and D+ is that D/N is stable whereas D+/N is changed into D+/U. * Public forum proposed as folder for new forum ==> misunderstanding on the specification ==> PB: database structure for folders. * Public forum folder = public folder use can't play with? * public forum ==> in the Public forum folder - user creating it,==> see it in his personal folder * public forums in "public forums" user can to copy public forum to one of his user folders. ==> this public forum accessible from - "public forums" folder - "user folder" (or something derived). |
|||
| 29
mar 2006 |
* "Edit forum rights -> NO * "Edit forum denials" -> YES |
|||
| 30
mar 2006 |
datings: the tree of regions |
|||
| 30
mar 2006 |
* datings: - tree of regions - tree of religions. * not sql-session ==> enable edit function in admin panel |
|||
| 31
mar 2006 |
- Need all the countries ==> all the blocks ==> regions in countries ==> cities and villages - Religions: list of all the religions degree of practicing - intelligence. ==> low/average/above average/high. ==> file treesofinstances.htm |
|||
| 2
april 2006 |
* divide Russia, USA, China, Africa, Australia on south\west\north\east parts. or maybe Africa have to be divided on countries (abt.50 items) - Religions: I did not know about the existence of Monophysite Quakers Nominal * http://en.wikipedia.org/wiki/List_of_religions * intelligence.==> low/average/above average/high do you think somebody will trully say that his/her intelligence is low? |
|||
| 3
april 2006 |
* "edit forum denies" in the forum info ==> "edit forum rights" button in forum > menu at http://tforum1.php.by/gls, ---> you can to edit invitation level and deny level. NO ==> reasons -==> Invitations: made by any user can only increase level, (other conditions), no special case for admin here; ==> Denials: edited by admin. ==> Possibly you could keep editing invitations, but only by superadmin (admin of trust-forum). |
|||
| 3
april 2006 |
I just said without thinking, we can keep editing invitation by superadmin =>>> NO Finally, even this is not right; but just letting superadmin delete an invitation would be right. |
|||
| * |
* "edit forum denies" in forum info ==> "edit forum rights" button in forum menu at http://tforum1.php.by/gls --> edit invitation level and deny level. |
|||
| * |
editing invitation via
superadmin? ==> NO : superadmin delete only invitation * "edit forum rights" ==> NO * rights presentation. a) invitation set once ( invitation) b) deny set any time by admins of forum c) invitation removed by superadmin (an only one person, holder of host) ==> NO : invatation level can modified after invitation |
|||
| 4
april 2006 |
a) invitation is set only once, at the moment of invitation ==> Not exactly: it can be increased, the stronger invitation replacing the previous weaker one. b) deny can be set any time by admins of forum c) invitation can be removed by superadmin (an only one person, holder of host) Why only one person ? For example, in the association of web hosting where I have my site, there are about half a dozen roots. - invitation level can be increased by new invitation but not edited by admin. - main idea of new rights system: no more editing invitation by admin, but make deniances instead. ==> for invitation "No special interface for admin" ==> "deniances, edited by admin" |
|||
| 4
april 2006 |
* admin should not edit invitations * as much as possible, every operation modifying something in the system must be signed. * An invitation is signed by the inviter. * But if the admin of a forum creates or modifies an invitation that was done by someone else, then this brings a false declaration: that someone did something (made an invitation) while in fact it was not done by this person but by the forum admin. This is something wrong that should be avoided. |
|||
| 4
april 2006 |
* admin should not edit invitations: * every operation modifying something in the system must be signed. * An invitation is signed by the inviter. if the admin of a forum creates / modifies an invitation that was done by someone else, then ==> brings a false declaration: that someone did something (made an invitation) while in fact it was not done by this person but by the forum admin. ==> This is something wrong that should be avoided. 1) invitation can not be changed, it can be increased by another invitation 2) invitation can be removed by super-admin(s) 3) forum admins can visit "edit forum denies" interface 4) "edit forum rights" is renamed to "edit forum denies" |
|||
| 4
april 2006 |
* rights presentation. - invitation is set once, at the moment of invitation ==> NO it can be increased --> stronger invitation % previous weaker one. * t "http://spoirier.lautre.net/tf-todo.htm", - Denyances, edited by admin, from "rights and deniances" page that forum admin can access * admin of forum ==> can edit invitations and deniances. * deny set any time by admins of forum * invitation removed by superadmin (an only one person, holder of host) ==> Why only one person ? half a dozen roots. - invatation level can be modified after invitation * can be increased by new invitation but not edited by admin. * new rights system: no more editing invitation by admin but make deniances instead. * tf-todo page : - invitation "No special interface for admin" as opposed to "deniances, edited by admin". * "Edit forum rights page" ==> NO |
|||
| 4
april 2006 |
* admin should not edit invitations: - operation modifying something in the system --> signed. - An invitation = signed by the inviter. - if admin of a forum creates / modifies an invitation that was done by someone else, then ==> false declaration: that someone did something (made an invitation) ==> NO 1) invitation not be changed, can increase by another invitation 2) invitation removed by super-admin(s) 3) forum admins can visit "edit forum denies" interface 4) "edit forum rights" is renamed to "edit forum denies" |
|||
| 9
april 2006 |
* bugs : editing/validating of messages and translations. |
|||
| 13
april 2006 |
- access remote public forums ==> choose pseudo - can write in remote public forum - "Remote public forums" link : in the left margin instead of top bar - Invitation to deny level should not exist - invitation below the default level should not exist |
|||
| 13
april 2006 |
- Invitation to deny level
should not exist - invitation 2 default level : * read in semipublic forum * write in public forum - invitation below the default level should not exist p1 invites p2 on forum ==> add the link to the forum in his main box. * invite somebody, invitation level more than default level? ==> yes . Do not invite to reduce his right ! |
|||
| 13
april 2006 |
- invite email to forum. - On the page http://tforum1.php.by/gls/index.php?action=showforum&id=23 * adding message * save-preview-post |
|||
13 april 2006 |
- Invitation to deny level should not exist --> invitation = default level : read in semipublic forum ==> no write in public forum ==> no ---> sollicitation to visit the forum ---> invitation below the default level should not exist * going to invite somebody, invitation level should be more than default level? |
|||
| 14
april 2006 |
email invitations to forum |
|||
| 15
april 2006 |
* can add email to contacts * inviting email from contacts in a forum |
|||
| 15
april 2006 |
* invite email to forum. * invite email from contact list - In contact list==> click on an email http://tforum1.php.by/gls/index.php?action=sendmail&id=4 - Inviting email to forum effect? ==> appear in invitations table in forum info page. - Little remark: in http://tforum1.php.by/gls/index.php?action=contactlist - buttons to appear in interface language ? ------------------------------------------------------------------------ Date: Sam 15 avril 2006 12:41 - invitation : in forum invitations table (in forum info page) - Email message title (forum message title), better sender name (author of message @ host, no more www-data@kama.neolocation.net) contain the body of the message posted to the forum and be sent every time a message is posted, - SAVE-PREVIEW-POST everywhere - email accessed forum: * no login form * no link to registration * LOGOUT link==> other (login , registration) |
|||
| 15
april 2006 |
- the invite email to forum - invite email from contact list. - on forum page, invite anybody from your contact list. - if email in contact list, can invite it to forum. |
|||
| 16
april 2006 |
* right denies page * NO "From contact list" |
|||
| 16
april 2006 |
* "from contact list": - add denial to someone that was not invited - " input myself" ==> public forum NOT for semipublic forum NOOO fot private forum. * add denial using contact list in the public forum - in forum info creator name = link ~ pseudo http://tforum1.php.by/gls/index.php?action=foruminfo&id=9 logged in as spoirier "Invitations you take part in:" shows pseudo permission invited by Date ivan read tu 2006-03-08 Invitation to read in a public forum : NO |
|||
| 16
april 2006 |
Date:
Dim 16 avril 2006 21:18 - forum info, creator name = link ~ pseudo - http://tforum1.php.by/gls/index.php?action=foruminfo&id=9 "Invitations you take part in:" pseudo permission invited by Date ivan read tu 2006-03-08 * right denies page NO "From contact list" - invitation should be visible in forum invitations table (in forum info page) - Email message should have better title (the title of the forum message) - better sender name (author of message @ host, no more www-data@kama.neolocation.net) - contain the body of the message posted to the forum and be sent every time a message is posted, - SAVE-PREVIEW-POST should be everywhere - On top of email accessed forum ==> no login form nor link to registration ==> LOGOUT link ( other login and registrations) |
|||
| 18
april 2006 |
So in the short term I see the following most urgent problems to be fixed: - local user of tforum1, access local public forums of tforum1 that guest can access ==> users have at least the same rights as guest - Edit forum denies: "Add new permission" button==>"Add new denial" - email invitation 2 forum invitation appear in invitations table each posted message to the forum ==> marked as read because ==> email address email message sent to invited email Sender email = pseudo@host Sender name = Comment (pseudo) Subject = [Forum name] Forum message subject body = posted forum message + access key (+ automatic comment). - error : back button ==> Warning: mysql_fetch_assoc() http://tforum1.php.by/gls/index.php?action=logout makes - public forums, guest ==> pseudo info pages empty! "Name"= pseudo |
|||
| 18
april 2006 |
- output of Pseudo(name) of invited by email User? => By email or name Guest ? store email for each message ==> pb????!!! message auhor = id ( forum invitation table) ==> display is pseudo - the email author of a message ~ invitation id in the forum ==> display in the form of the email address instead of pseudo. * invited email register ==> all forum messages previously posted under his email now displayed as having been posted under his new login name or pseudo * can appear to his inviter under different pseudo ? -------- * Invited emails ~ invited user. * ~ invitation of a GLS remote user. no difference between local users and remote users. * only difference :remote access to forum -no left bar of folders list - the top bar * working plan for GLS integration ==> commonalities with invited email. ---------- * email invitation. - The invitation at the forum info page. - link back to the forum. ==> include the email invitation with the previous invitation. - long time to enter the forum - new posted messages should be sent to email. - I registered from email access ==> but then when I logged in under inviter identity,==> see the new login name on the line of the contact table for this email. ==> do not ask for email(known) - The invitation message NOT from "www-data" <www-data@kama.neolocation.net> but from pseudo@host - not sent at time of invitation ==> include again at the bottom of posted messages from the forum. ==> link "Resend invitation" - the message posted by user and seen by email access ==> mark as read !!! - email access not authenticate himself (already authenticated) - should be a link "Close session". - It should also be save-preview-post for email invited user. -------- additional features "Compose message"+info page on the email ==> link to forum where this email has been invited. -- "private forums where he has posted" ==> "where he has writing right". ==> put in user info page ==> link "Create new private forum and invite this user there". * invit from inside account==> NO password on screen. ---------- (...) -------- * rights system - trust-forum.php.by - tforum.php.by * Forum where Admin ==> forums ==> * No links "Edit forum rights" * link to a page with functions of viewing forum rights and editing forum denials (and this table can also possibly be used as an interface to invite to a higher right, but I do not require this). It looks like it is not the case yet. (...) |
|||
| 18
April 2006 |
* admin panel can move message from public forum to another * in a public forum, forum admin can move a message from a thread to another. |
|||
| 19
april 2006 |
* output of Pseudo(name) of invited by email User? By email or name Guest ? * in the database author of a message identified by an id (forum invitations table) ==> display pseudo % forum invitations table * email user ==> email |
|||
| 19
April 2006 |
* make output of Pseudo(name) of invited by email User? ==> By email or name Guest is enough * in database the author of a message was identified by an id ( forum invitations table) * in the display appears as the pseudo % the forum invitations table * what should it be shown at the "author" field of message, posted by email user ==> email or simply "guest" - at this moment it named as "guest" - by his email better store username instead of user id. |
|||
| 23
april 2006 |
* email invitations * folders rights |
|||
| 23
april 2006 |
admin panel |
|||
| 24
april 2006 |
dating ==> presentation of intervals for badness (height, birth |
|||
| * |
link
http://spoirier.lautre.net/tf-todo.htm didn't you ? ==> sets of doc sent : Specification.zip (0.03 MB), Spec2.Todo.zip (< 0.01 MB), GLSspec_1.04.zip (< 0.01 MB), Dating_Spec_04.zip (0.01 MB) |
|||
| 25
april 2006 |
http://spoirier.lautre.net/tf-todo.htm
? |
|||
| 25
april 2006 |
get at
http://spoirier.lautre.net/tf-todo.htm ? |
|||
| 28
April 2006 |
* " write in remote public forums (13 April)." Yes, under the pseudo chosen in 3. *" move “remote public forums” to left margin (13 April)." * "adding message should be as “save-preview-post” " ==> in all cases ==> except guest GLS access ==> local ~ remote user * "# some buttons are in the local language, but not in interface language (15 April)." => "All buttons in interface language". * "can add deny to not invited person" ==> I read "from contacts list" in edit denies page ? ==> ? in private forum where it seemed to be already possible. * " forbid somebody to access public forum (18 April)." * "from:, author: and other fields of emails readable" - forum message content in email message - email receive emails ~ each posted message to forum. ==> send all forum messages to email ~ mailing list. * "update forums==>drop incorrect forums" What do you mean ? Isn't this a matter of admin panel ? * "to check when guest clicking user info" What do you mean ??????? * "email invited person ==> “email” but not “guest” " ==> Bugfixing1.htm |
|||
| 29
April 2006 |
* forum owner "Owner" ( ~= "creator") but can be transmitted. - only one person - transmit ownership ==> lose ownership. - Ownership ==> admin right - transmit ==> giving him admin rights too. - ownership transfer interface : choose in existing admins. ==> give it to someone who is not admin 1st give this person admin right |
|||
| 29
april 2006 |
* "it should be possible to add deny to not invited person" - already case : edit deny pages has "from contacts list" - private forum : * "For example to forbid somebody to access public forum (18 April)." - user can create another pseudo for public forums - can deny somebody to be an admin of private forum * for any type of forum, an admin can forbid anyone who is not already admin (and even this case if one is owner) from being admin ==> make ineffective an invitation of that user to be admin (though this does not really prevent anything as the admin who wants to make invitation can start by removing this protection). * "owner" ( "creator") - this position can be transmitted. - only one person - transmit it ==> lose it. *owner of forum can to: 1) give ownership to smb else. 2) deny other admins of forum ==>Bugfixing2.htm |
|||
| 30
April 2006 |
* bug fixes * admin panel * datings. |
|||
| 30
april 2006 |
For any type of forum an (admin+OWNER) can forbid anyone who is not already admin from being admin ==> make ineffective an invitation of that user to be admin (BUT admin who wants to make invitation can remove this protection). * use deny ==> person prevented from being admin * not invited user ==> deny for admin --> not useful *denies to not invited persons are: read to semipublic forum read or write to public forum * bug fixing admin panel datings |
|||
| 30
april 2006 |
- deny somebody to be admin of private forum ? - forum, an admin can forbid anyone who is not already admin (and even this case if one is owner) from being admin ==> make ineffective an invitation of that user to be admin (but the admin who wants to make invitation can start by removing this protection). * possible to prevent somebody to be an admin of forum using deny *denies to not invited persons are: read to semipublic forum read or write to public forum - admin panel with sql protection - datings |
|||
| 1st
may 2008 |
* why did messages come from www-data@kama.neolocation.net |
|||
| 2
may 2006 |
1) 30 march. forum creation page fixed. 2) 30 march. translations fixed. 3) 30 march. owner rules fixed. 4) 30 march. "stars" instead of password. 5) 30 march. "default bookmarks" renamed to "remote public forums". 6) 4 april. invitation algorithm fixed. invitation can be set once, or increased by another invitation ? admin can set deny level. 7) 8 april. invitations/denies interface fixed. you can see 8) 13 april. bugs with remote invitation when it is impossbile to read/write in remote forum where you are invited. 9) 19 april. forum info page updated. correct "invitations you take part in", posters of messages. * - messages sent to invited emails? ==> should this messages marked read and not editable by author? ---> Yes marked as read (--> no editable by non-admin, as any read message) * mark this as read only after visiting of forum by anybody (email or user or remote user) * email sent messages cannot be reedited before reading |
|||
| 2
may 2006 |
1) 30 march. forum creation page fixed. 2) 30 march. translations fixed. 3) 30 march. owner rules fixed. 4) 30 march. "stars" instead of password. 5) 30 march. "default bookmarks" renamed to "remote public forums". 6) 4 april. invitation algorithm fixed. invitation can be set once, admin can set deny level. 7) 8 april. invitations/denies interface fixed. 8) 13 april. bugs with remote invitation when it is impossbile to read/write in remote forum where you are invited. 9) 19 april. forum info page updated. correct "invitations you take part in", posters of messages. * messages sent to invited emails? ==> mark this messages as readen only after visiting of forum by anybody (email or user or remote user) |
|||
| 4
may 2006 |
translation system - add new translation seeing first selected one with fields filled with (possibly blank) second selected (instead of the present two possibilities: edit or add based on only one). (then, maybe with it or maybe later, will be the possibility to have private vs public translation) |
|||
| 8
mai 2006 |
admin panel with sql protection w datings |
|||
| 8
may 2006 |
admin panel specification, |
|||
| 9
mai 2006 |
* admin-panel specification attached *"global" point * forum settings precision * add to admin panel task - can move message from public forum to another - inside public forum, forum admin can move message from a thread to another. - Inside public forum, ==> forum admin AND super-admin * opposite to every message link "move message": - admin can select, to what thread move this message. * admin-panel work + sql-protection work * " Users can be added, renamed, or closed" - closing reversible: ==> the operation "reopen" * " Any forum can be renamed, deteled, added." * adding forum: as anyone can create a forum, what sense does it make to add specially the function to add a forum by superadmin in admin panel ? I see it as unnecessary. |
|||
| 9
may 2006 |
admin-panel specification attached. "global" point forum settings precision * add to admin panel task: - can move message from a public forum to another. - inside a public forum, the an admin can move a message from a thread to another. * Inside a public forum ==> forum admin but not super-admin? ---> link "move message" admin select thread to move this message. * admin-panel work + sql-protection work ==> file forum_adminpanel_1.3.htm |
|||
| 10
may 2006 |
* "save", "preview", "post" buttons, one 1. Save: store the message marked invalid 2. Preview: save (like 1.) and reedit to the same screen 3. Post: store the message marked valid |
|||
| 10
may 2006 |
- link to forum info ( public forum --> local user creator) - message as remote user toto@tforum2 in the public forum at tforum1, appears as posted by "admin" (and author did not appear when I was toto@tforum1). - save-preview-post missing |
|||
| 10
may 2006 |
* "save", "preview", "post" buttons |
|||
| 16
may 2006 |
admin panel + sql-protection |
|||
| 16
may 2006 |
* admin panel : logging as 'admin' 'admin' * - removing of denies by superadmin - adding denies to not invited persons - ownership transferin - email web interface, where you can to send trust-forum invitation |
|||
| 17
may 2006 |
* impossibility for a normal user to access a local public forum (unless there had been read denial to that user but I suppose it was not the case ?) |
|||
| 18
may 2006 |
1) translations: 1) use translation 2) compare 2 translations 3) edit translation. while editing ==> can create new translation with default values of edited translation. * translations could be public or private. - public translations could be used by anybody, - private translations could be used only by creator. 2) it could be possible to do some actions using one interface: 1) invite user to trust-forum 2) create private forum 3) left a message there 4) invite this user to this forum 3) datings: i will send updated specification, with list of religions and geografical areas |
|||
| 18
may 2006 |
registered access to
(semi)public forums |
|||
| 19
may 2006 |
1) translations: there should be 3 points: 1) use translation 2) compare 2 translations 3) edit translation. while editing, it is possible to create new translation with default values of edited translation. * create new translation under displayed values from selected first translation, with fields filled by selected second (possibly blank) translation. * modified translation = new translation + version number. * old translation ==> private to make people forget about it. * translations could be public or private. - public translations could be used by anybody - private translations could be used only by creator. * private translations can be switched to only by creator ( other users using a public translation that becomes private can keep it). 2) it could be possible to do some actions using one interface: 1) invite user to trust-forum 2) create private forum 3) left a message there 4) invite this user to this forum ( 2,3,4) 1. interface = link from the info page of a given user (that can be a user of any site or an email address from contacts). * register to tforum2 (forgot the login and pass) --> allow for public registration --> give admin login/pass in tforum2 |
|||
| 10
may 2006 |
* do not display URL with key in the screen to invite email to trust-forum. * title of email message = [forum name] subject of forum message. * key repeated on the bottom of each forum message received by email. * allow save-preview-post to email user |
|||
| 21
may 2006 |
tforum1.php.by/gls/ * (spoirier) have admin right to trust-forum. *know or control who has admin right to trust-forum: only the "admin" user ? * link to register a new user from inside an account (except adding user from admin panel, which does not work). * invitation by email * input by hand a username to invite to a forum. * no access to tforum2 => n create or login to another account in tforum1 |
|||
| * |
- Subscribing to a forum ==> display forum name in mainbox with the number of new messages - move forum to another folder (the folder list popup charge) - subscribe/unsubscribe to a forum from the folder display |
|||
| * |
Trust-forum invitations still
come from "www-data". |
|||
| * |
(tforum1.php.by/gls/). * non-admin users (normal users, GLS remote and email users). * quick start of conversation * remaining details of admin panel * new translations system * datings |
|||
| * |
* test the new installation but I had a problem that I cannot register to tforum2 (I forgot the login and pass I created there). ==> allow for public registration or give me admin login/pass in tforum2 for me to allow it. ==> user "toto" password "titi"= super-admin of tforum2. ==> "spoirier" password "fkuix"= super-admin of tforum1. * admin panel. 1) translations: there should be 3 points: 1) use translation 2) compare 2 translations 3) edit translation. while editing, it is possible to create new translation with default values of edited translation. More precisely, create new translation under displayed values from selected first translation, with fields filled by selected second (possibly blank) translation. I think any modified translation is a new translation, that should be given a new version number. Then it is possible to make old translation private to make people forget about it. it will be like version control system. i mean that system will save all of modifications of translation, giving uniq version number to every of modification. ok, it is possible to do. ==> each new version will have a new version number, but can the user have any control on how the version number actually look like (for example, to decide whether, after 0.2.6 it will be named 0.2.7 or 0.3.0, or a version name other than a number provided it is different than previous version names...)? * translations could be public or private public translations used by anybody private translations used only by creator. ==> private translations can be switched only by creator (==> users using a public translation that becomes private can keep it). * if i will switch my translation form public to private, those who used this translation, also will use it, isn't it? ==> not have a bad surprise at their next login like when one year ago, I modified version number of currently used translation and the interface became suddenly empty and unusable... * 2) one interface: 1) invite user to trust-forum 2) create private forum 3) left a message there 4) invite this user to this forum (2,3,4) ( 1) interface by a link from the info page of a given user (that can be a user of any site or an email address from contacts). (2, 3, 4)link in user info page --> link from user info page (user's site), with name "Start conversation" ~~~~~~> interface at oneself's site + form gathering fields of creating forum (except forum type which is fixed as private: so, forum name, folder, by whom, comments) and writing a message there. * link in user info page --------------------------------------------------------------------- Date: Dim 21 mai 2006 20:36 * "my comment" field in contacts list --------------------------------------------------------------------- Date: Dim 21 mai 2006 20:51 - spoirier@tforum1 ( write access to private forum "lala") invites toto@tforum2 with writing write ==> toto@tforum2 rights (invitation table ) - Invitation table (Invitations you take part in:) ==> home site of every user (every user ~ (pseudo, host)). - From toto@tforum2 with open session in tforum1 I logged out from account in tforum2, yet session in tforum1 remained open. It should be closed by logout of tforum2. |
|||
| * |
info page of a remote user can be seen from local site: http://tforum1.php.by/gls/index.php?action=viewpseudo&id=1&host=1 * how it works internally ? * info page content ==> home site of that user |
|||
| 21
may 2006 |
* register to tforum2 --> login and pass forgotten. * allow for public registration or give me admin login/pass in tforum2 for * user "toto" password "titi"= super-admin of tforum2. * user "spoirier" password "fkuix": super-admin of tforum1. * 1) translations: there should be 3 points: 1) use translation 2) compare 2 translations 3) edit translation. while editing, it is possible to create new translation with default values of edited translation. * create new translation ( displayed values from selected first translation, with fields filled by selected second (possibly blank) translation. * modified translation = new translation ( new version number) * make old translation private --> people forget about it. * ~ version control system system save all of modifications of translation + uniq version number to every of modification - translations : public or private public translations can be used by anybody private translations only used by creator - ==> private translations can be switched only by creator ( other users using a public translation that becomes private can keep it). - switch my translation form public to private those who used this translation, also will use it, isn't it? one interface: 1) invite user to trust-forum 2) create private forum 3) left a message there 4) invite this user to this forum (1) interface ==> link from the info page of a given user (user of any site or an email address from contacts). (2, 3, 4)link in user info page |
|||
| 22
mai 2006 |
Save-preview-post : also for GLS
remote users. |
|||
| * |
* info page of a remote user: http://tforum1.php.by/gls/index.php?action=viewpseudo&id=1&host=1 -(how it works internally) ? - info page content must mention --> user homesite - define what pseudo is what user belongs to? * display in the page user home server URL ("host=1"). * info accessed from remote session received using GLS function displayed in user interface. ==> tforum1 --> request to tforum2 "what is the name and info of your pseudo number 1?", --> result to online user. ==> Another way of doing is : direct request of the tforum1 user to site tforum2, though he is there a GLS remote user. * new version <--> new version number, - user control version number look ( after 0.2.6 ~ 0.2.7 or ~ 0.3.0 )? - add 0.0.1 to current level by default t user can change this number to something more, but not less than it is. |
|||
| 22
may 2006 |
* info page of a remote user from local site: http://tforum1.php.by/gls/index.php?action=viewpseudo&id=1&host=1 * contents of the info page must mention what is the home site of that user. * no way to define what pseudo is what user belongs to --> information accessed from remote session - GLS function and displayed in user interface. --> show remote user info in local site * information in remote session. * structures of data sent/receiving remote user info. * each new version ~~~~> new version number, - user controls how the version number look like (for example, to decide whether, after 0.2.6 it will be named 0.2.7 or 0.3.0, or a version name other than a number provided it is different than previous version names...)? --> next version number is an addition of 0.0.1 to current level by default ---> user can change this number directly to something more, but not less than it is. |
|||
| 23
may 2006 |
* version name =word+number. For example for the same language: John 0.0.1 John 0.0.2 John 0.1.0 John 0.1.1 John 1.0.0 John 1.1.0 Peter 0.0.1 Peter 0.1.0 Peter 0.1.1 Peter 0.1.2 Peter 0.2.0 Peter 1.0.0 Standard 0.0.1 Standard 0.1.0 Alternative 0.0.1 Alternative 0.1.0 ==> 2 number components? 0.1 instead of 0.0.1 |
|||
| 24
may 2006 |
* Translations: version name = creator pseudo + number OR version name independent of pseudos - every translation mention author (a pseudo) - version names independent of author translations list==> who (a pseudo) is the author of every version + creation date. * 3 components number vs 2 components |
|||
| 24
May 2006 |
Translations: * version name = an pseudo of creator? * 3 components number is better than 2 components only x.x version number |
|||
| 25
may 2006 |
datings: * there are nationalities, ethnicities, eyes color, hair style, education and others. * catalogs have to be adjusted (coordinates) between us. |
|||
| 26
may 2006 |
* 1) nationalities http://drupal.org/node/11614 * tree - people put badnesses to big groups and not to every nationality separately, if they prefer * 2) ethnicities http://en.wikipedia.org/wiki/List_of_ethnic_groups http://www.answers.com/topic/list-of-ethnic-groups * between 20 and 100 elements ? * 3) eyes color it would be colormap (example attached), hair color would be selected from this map. * simple finite list of colors with their name, each illustrated by a picture with this uniform color. (except that some people have mixed hair colors...) 4) hair style 1. curly 2. straight 3. wavy 4. afro 5. glamourous 6. spikey 7. platted 8. wacky 9. short-fringed 10. long 11. short 12. skin * illustration of each in some help page 5) education 1. no education 2. primary school 3. secondary school 4. undergraduate (college) 5. Bachelor 6. Master 7. Doctor * domain of study (hard sciences / social sciences / medecine / ... / multidisciplinary / none). ==> check separately yes/no for every domain * upgrade translations system of datings, all of nationalities/ethnicities/hair styles/regions/religions would be added to list of translation ==> separate translation file for datings independent of the forums and other system elements. ==> more features for the datings translations ( big list) ==>I expected a tree of regions. ---> cile colormap.JPG |
|||
| 27
may 2006 |
À list of between 10 and
40 ethnicities |
|||
| 28
may 2006 |
* regions : visa problems harder barrier to travelling than distances. La Reunion Vs Madagascar --> "remote developed regions" ( La Reunion, Mauritius and Hong Kong) --> La Reunion : subregion of Africa. Geographically = African Politically = French ==> place for a meeting or long-term living, before the bad virus that is striking there now, I would have not given it comparable badness to the whole undivided Africa. * http://news.google.com/news?hl=en&ned=us&q=chikungunya&ie=UTF-8 * manage colormap. * easy to select element in a colormap --> give a badness to every possible color of a match, in a way that will not require any expertise by the user (as it is for being used by everybody only once !). * finite set of colors will be used (5x5 matrix for example) * hair color and eyes color ~ 5 to 12 elements. * list of translations ==> directories (system, nationalities, ethnicities, regions etc). |
|||
| 28
may 2006 |
* alphabetical order ==> treesofinstances.htm |
|||
| 29
may 2006 |
-one billion people are catholic, some division can be found there. - What do you think of the division between roman-catholic and eastern-catholic ? http://en.wikipedia.org/wiki/Eastern_Rite * Christian Catholic lightly catholic Roman catholic Eastern catholic ... * "lightly Christian" (whereas Evangelics cannot be any lightly Evangelics...). * "Non-religious" should contain subcategories Atheist Agnostic Deist Spiritual Indifferent * delete the religion "Spiritism" ==> Nonreligious/spiritual * # Neo-Paganism 1 million # Unitarian Universalism 800,000 # Rastafari movement 600,000 # Scientology 500,000 # Zoroastrianism 180,000 to 250,000 |
|||
| 29
may 2006 |
* list of science domains ( http://www.google.com/Top/Science/ ) * list of main categories of study "painting" and "theatre" ==> "arts" * domains of possible higher education * possible other large domains of professional activity that do not necessarily require higher education. Agriculture Anomalies and Alternative Science Astronomy Biology Chemistry Computer Science Earth Sciences Environment History of Science Math Museums News and Media Philosophy of Science Physics Publications Science in Society Social Sciences Software Technology About translations: 1. System (all of text in interfaces) 2. Personal 2.1 Languages (language names) 2.2. personal info 2.2.1 gender 2.2.2 birth year 2.2.3 marital status ........ etc 2.2.x ethnicity 2.2.x+1 nationality 2.2.x+2 religion ........ etc 2.3. place of meeting (region names) * subcategory : personal info only a couple of items 1. System 2. langages 3. marital status 4. regions 5. nationalities 6. ethnicities 7. religions ...... x. other (those elements of personal info that have too few elements to be a translation subcategory) * titles to separate them in the display of translation files when one is adding a new translation or comparing 2 translations ? |
|||
| 29
may 2006 |
* in a GLS access to a forum headers as in local access: - link to forum info page ( + "edit forum denies" = LINK) - Make an invitation - New thread (if writing right) * add a local page (that is a page hosted at user's home) to bookmark: this has not the GLS access functionality of a bookmark, but it is a link that user may be interested to add to his list anyway. |
|||
| 29
may 2006 |
this is a list of science domains ( http://www.google.com/Top/Science/ ) Agriculture Anomalies and Alternative Science Astronomy Biology Chemistry Computer Science Earth Sciences Environment History of Science Math Museums News and Media Philosophy of Science Physics Publications Science in Society Social Sciences Software Technology About translations: 1. System (all of text in interfaces) 2. Personal 2.1 Languages (language names) 2.2. personal info 2.2.1 gender 2.2.2 birth year 2.2.3 marital status ........ etc 2.2.x ethnicity 2.2.x+1 nationality 2.2.x+2 religion ........ etc 2.3. place of meeting (region names) "System" catalog contains everything except lists of personal info |
|||
| 30
may 2006 |
"NOT display the URL with key in the screen to invite email to trust-forum." --> the next page NOT "your message has been sent" BUT back to contacts list. * Email users canot mark invalid their posted messages - posting to email every messages - email user not receive his own messages - messages are normally marked read only if they are read by someone ELSE. * see login form on the top while they should see "exit" link instead * there is a "back" link which leads nowhere. (but, contrary to GLS users, it is OK if email users cannot create threads, see info page or invite another user) * forum info page: invitations table does not show from which hosts users are. * In admin panel ==> know who invited a given user ( registered by invitation) * invitation to trust-forum ==> provide each other in contacts list. * Users with only reading right to a forum should NOT have possibility to create a new thread. But users with writing right should (I see in public forum that it is not the case). * Logout from one's home should close all remote sessions. * separate, in GLS access to the root page, private # public forums; --> not appear to the same page. * New thread, invitation and edit forum denies links appear inside a thread but also to the list of threads. * "set new owner" => in forum info page and/or in forum edit denies page, not in the threads list. * Edit denies page links back to forum and to forum info. * Forum info should link to edit forum denies. * turlututu@tforum1 invited spoirier@tforum1 to read in turlu forum of tforum1 spoirier@tforum1 invited toto@tforum2 to read there turlututu@tforum1 invited spoirier@tforum1 to write there spoirier@tforum1 had well writing right and invited toto@tforum2 to write too, but toto@tforum2 never got this right. ________ - As spoirier@tforum1 with write access to private forum "lala" I invited toto@tforum2 with writing write. However, this only gave reading right to toto@tforum2 (invitation table displays it is only invitation to read though I clicked on "write"). - Invitation table (Invitations you take part in:) does not show what is the home site of every user, it should show it (every user is identified by the pair (pseudo, host)). - From toto@tforum2 with open session in tforum1 I logged out from account in tforum2, yet session in tforum1 remained open. It should be closed by logout of tforum2. _____________ - input by hand (pseudo+host) for invitation. moved to forum info page - new interface of forum creation+inviting user, - display of pseudo information, please include a Host field, not only for info about user from another host. |
|||
| 30
may 2006 |
*Accents and ' characters do not work anymore. |
|||
| 31
may 2006 |
* detailed list and easy list: regions, nationalities and other? * tree structure of regions as a subtree of the tree of items for interface translation files ? Agriculture Astronomy Biology Chemistry Computer Science Earth Sciences Environment History Math Arts Philosophy Physics Social Sciences Technology |
|||
| 31
may 2006 |
* regions | religions: * list of science domains ( http://www.google.com/Top/Science/ ) * list of categories of study * "painting" + "theatre" ==> "arts" * list from higher education * domains of professional activity * list Agriculture Astronomy Biology Chemistry Computer Science Earth Sciences Environment History Math Arts Philosophy Physics Social Sciences Technology * About translations: 1. System (all of text in interfaces) 2. Personal 2.1 Languages (language names) 2.2. personal info 2.2.1 gender 2.2.2 birth year 2.2.3 marital status ........ etc 2.2.x ethnicity 2.2.x+1 nationality 2.2.x+2 religion ........ etc 2.3. place of meeting (region names) ===> better 1. System 2. langages 3. marital status 4. regions 5. nationalities 6. ethnicities 7. religions ...... x. other ( personal info that have too few elements to be a translation subcategory) * how is this categorisation used ? --> titles to separate them in the display of translation files when one is adding a new translation or comparing 2 translations ? --> usual tree structure. when user is clicking "compare" or "edit" sees list of categories - every category is a link - this link --> list of strings to translate. ===> treesofinstances3.htm |
|||
| Dim 2 juillet 2006 |
tforum1 or 2/gls -remaining bugs: I tried in the remote forum http://tforum2.php.by/gls/index.php?action=newreply&id=2 to make accents and brackets <>, things work well except the " and ' which become \" and \'. (I did not check encoding of accents and special characters in other fields, please do) Moreover, a second click to http://tforum2.php.by/gls/?action=showremoteforum&id=2&rs=1a5f8148b8db8e8fc49e36d25308bc5f&h=8834540474d1f75168017e541fd9df5f has led to a very strange web page which I send you attached. - Include a way to know whether a forum is public or private, as a line in forum info page. |
|||
| Tue, 4 Jul 2006 |
only one host: trust-forum =
"serious use"
for now only one host. - all text encoding and some display of forum type ? In http://tforum1.php.by/gls/index.php?action=newreply&id=2&loggedin (so, in preview function) the insertion of \ before " or ' still happens (whereas it does not happen in other operations). In http://tforum2.php.by/gls/?action=showremoteforum&id=2&rs=5066d5c26826749342763e6d73f438ec&h=8834540474d1f75168017e541fd9df5f it happens no more (and chinise characters are no more reproduced) but the fixed big font that was occuring still remains. What is it ? I did not check in comments fields (all pseudo comments, contact comments, forum comments), with French accents, and ",',>,< characters. I hope you did it. - forum type can be viewed from the forum info page. is it OK? |
|||
| Mer 5 juillet 2006 |
text encoding in comments field
of pseudo is wrong too. |
|||
| Mar 11 juillet 2006 |
- pb: Text encoding. - preview function should not say "new reply" |
|||
| Dim 23 juillet 2006 |
In a preview at remote site (from a tforum2 user) http://tforum1.php.by/gls/index.php?action=newreply&id=27 the " and ' appeared with additional \ in editing fields. I pressed "Preview" a second time. See the result attached, with a big surprise on the top of the page (yes I voluntarily included some nasty > and < characters...) Moreover, "change" link from home folder for name of remote forum, has no effect. |
|||
| Mer 26 juillet 2006 |
tforum2.php.by/gls/, tforum1 ==> there is additional \ before " and ' in message sent to email (invitation form from contacts list) and the text area for message title seems high in the second (index1) attached file. - not receiving to email the message from forum aaa that I invited myself to. |
|||
| Mer 26 juillet 2006 |
BUGS: As an email user of a forum, I wanted to preview (http://tforum1.php.by/gls/index.php?action=newreply&id=28) a message with vicious characters |
|||
| OCT-2006 |
New Version |
|||
| Dim 1 octobre 2006 |
BUGS LIST "5. The edit message by forum admin does not modify the message" ==> deleting message did not work, now it is working well. "7. There should be a link from forum info page to denies page" and conversely and back from edit denies to forum "9. Contrary to editing by author, the editing by forum admin does not need save-preview-post." Yes. In case the same person is both admin and author, the difference is defined by whether the message is marked as read or not. So the remarks 8 and 9 are the same remark. " 10. There should be some visible indication that one is in preview mode, and what is, among displayed messages, the message that is being edited. " Do you have propositions of possible ways before doing it ? "6. The "Change owner" does not propose a correct list of people to transmit this right to (should be the other admins of this forum)" By the way, what about the change owner by trust-forum admin ? There should be a possiblity for him to take control of a forum, for example if forum owner and only admin is no more using the system. " 11. From contacts list, when I send a message, on my email I receive nothing, no matter whether I check "add invitation" or not." I noticed this is working again. Now in this function the question is: - to let user choose the message subject. Other bugs I listed and do not find in your document: - Convert the text encoding of old database to new format - Still fixed fonts appear for remote user, see attached file - I just said you should unite the naming of local site: Pseudos who have posted messages (admins in bold): escaper@Local forum spoirier@Local forum Aliaksandr@Local forum ----------------> - Title field of forum message being edited by email user appeared blank is it fixed? - Sometimes title field appears two lignes high - Multiple occurences of the same forum in folders (the maximum occurences should be 3: among public forums if it is public or semipuble ; once in user folder if one was chosen; once in mainbox if subscribed and new message, or by default if private forum, or if chosen) : the moving operation of a forum to another folder should be corrected. - forum <expressions> by email user be visible at display to himself ? |
|||
| Dim 1 octobre 2006 |
- unify the name of local host: Pseudos who have posted messages (admins in bold): escaper@Local forum spoirier@Local forum Aliaksandr@Local forum Invitations you take part in: pseudo permission invited by Date spoirier@trust-forum write escaper@trust-forum 2005-07-28 mefisto@trust-forum write escaper@trust-forum 2005-07-10 people@trust-forum admin escaper@trust-forum 2006-04-11 Aliaksandr@trust-forum admin spoirier@trust-forum 2006-03-04 Lastly, Don't you see something very wrong in the attached page ? I went there through pages http://trust-forum.php.by/index.php?action=viewpseudo&id=93&host=0 http://trust-forum.php.by/index.php?action=showforum&id=13 The forums list accessible from pseudo info page should be the list of private forums, hosted on either of both hosts of oneself and this pseudo if different (or just here if local), where both oneself and this pseudo has writing access (well, at first it was said to be where he had written messages, but it may be good to include the case of unused writing access in order to avoid creating a new forum). - task of quick discussion start from link in pseudo info page. |
|||
| Dim 1 octobre 2006 |
01_10_2006_bugs.doc another list of bugs: 1. When I ask to delete folder, it asks for confirmation with a warning (bogusly text encoded, please ensure nothing else is bogusly encoded like this) which says that if I confirm, I will lose my invitation to the forums that are in this folder. ==> NO: invitation to a forum should never be lost by deleting a folder. All forum titles should just be moved to the parent folder (is what you called "root", isn't it ?) with unchanged invitation. 2. the folder of a forum can be chosen to be "none" which should be interpreted as a synonymous for "mainbox" in the case of a private forum, and as only appearing among public forums in the case of a public or semipublic forum. 3. Remote users should have the same use of a given forum as local users, in particular they should be able to make invitations of any user (from any site) to a given forum. I had noticed the absence of a form to make invitation in remote forum info page while I wanted to check the use of contacts list from home site pop-up for remote site. 4. When sending message with possible invitation to email from contacts list, add to the form a field "title" or "subject" to input the message subject (instead of "invitation to trust-forum" that may be a default value of this field that can be edited) 5. The edit message by forum admin does not modify the message 6. The "Change owner" does not propose a correct list of people to transmit this right to (should be the other admins of this forum) 7. There should be a link from forum info page to denies page 8. When a message is marked as read (so no more editable by author), it should not be let invalid again, so the save and preview do not fit. 9. Contrary to editing by author, the editing by forum admin does not need save-preview-post. 10. There should be some visible indication that one is in preview mode, and what is, among displayed messages, the message that is being edited. 11. From contacts list, when I send a message, on my email I receive nothing, no matter whether I check "add invitation" or not. - Then I invited the email to an old private forum. On my email I received the invitation not immediately, only after a few minutes. Before receiving it, I wrote a message and clicked on Preview. The server did not respond (so I got an error page from the browser saying the server does not respond). |
|||
| Lun
16 octobre 2006 |
16_10_2006_task.doc “edit” instead of “save-preview-post” only in edit form, only for read messages. Title should be one line high. To make message body little bit bigger. Check edit form (title and body) using next string: ²&é »’(-è_çà)=s”d”f<sdf>sdf. check user rights at operations: denies page (if not admin, not to see denies list); forum info (if not admin, not to see link to denies page); at “showfolder” page, invalid list of members of forum. to check compliance of http://trust-forum.php.by and http://tforum1.php.by, http://tforum2.php.by; to make a mechanism of distinguishing of previewed message in messages list (edit form is situated under the previewed message). check admin panel for display characters At pseudo info page, it could be possible to do 3 actions in one step: create private forum left a message there invite this user to this forum Translations. In translations page should be 3 points: 1) use translation 2) compare 2 translations 3) edit translation. translations could be public or private. public translations could be used by anybody, private translations could be used only by creator. Creating new version prompts new version number, but this number can be edited. |
|||
| 17-Oct-2006 |
Accents problems |
|||
| save-preview-post ==> Edit,
modify? |
||||
| gsl_messages tables = error
==> one messagetables/forum ( local or remote users) |
||||
| remove/local users : same on
forum |
||||
| text message size |
||||
| title fields height:
http://tforum1.php.by/gls/index.php?action=showforum&id=4 |
||||
| fields encoding: - message body - message title ( display, preview or edit by local, remote or email user) - thread name - forum name - forum comment - forum comment2 - pseudo - pseudo comment - pseudo - comment2 - translated item field |
||||
| Function change owner |
||||
| Forum & Remote User ==> forum info page ==> user invitation User invited: can be at any host |
||||
| Forum & Email Invited - mark Valid = sending message + makr as read = post button PB: message sent ==> not marked as read PB: preview, Mark Valid, Edit, Post==> mailbox ==> message twice there PB: message different from message received in mail PB: invitation tree PB: link to bottom of email sent ==> page sorry |
||||
| Pseudo Info Page link to : - create private forum - leave a message on this forum - invite user to forum |
||||
| Inside Forum Creation form &
Forum Info Page : - invitation form |
||||
| leave translation for now |
||||
| 18-Oct-2006 |
trust-forum.php.by
--------> newest
version obsolete tforum1.php.by --------> obsolete http://tforum2.php.by --------> ? http://tforumx.php.by/gls --------> ? http://tforumx.php.by/gls -------> newest versions |
|||
| "change owner" - admin panel, forum setting, edit deny? |
||||
| SuperAdmin Ownership (
trust-forum admin): Forum ==> Admin can give ownership to another admin ==> becomes simple Admin ===> NOT to trust-forum admin |
||||
| Creator of a Forum ==>
invitation line as Admin ==> transmit ownership from one admin to
another admin : invited to admin by creation. Forum Invitation Table |
||||
| 18-Oct-2006 |
2 ways of changing Forum Owner: - By owner - By Trust Forum Admin |
|||
| Fill Forum Invitation Table when
rights not given by invitation - creation - take ownership by trust-forum admin - input by hand Invitation line ==> invited by system |
||||
| 14
feb 2007 |
*diagrams ( class, ...) *different hosts |
|||
| 14
feb 2007 |
Lisp language |
|||
| 15 feb 2007 |
http://spoirier.lautre.net/trust-forum-1.4.0.zip |
|||
| 15 feb 2007 |
Goal: Add a new protocol on the internet network which would work on top of |
|||
| 16 Feb 2007 |
* no use to reinter passwords (
~ passport) * remove dating adverts ownership from hosts ==> make it democratic |
|||
| 17 Feb 2007 |
bug to fix:* "forgotpassword".~~~~> Sylvain is asking former programmer |
|||
| 18 Feb 2007 |
not sure
forgotpassowrd suitable ==> center for passwords |
|||
| 20 Feb 2007 |
check online communication :
dating system + programmers discussion |
|||
| ???? ask frozen team Java system |
||||
| 20 Feb 2007 |
monetary system : additional
feature --> pb : for it to be put on different servers --> pb : how to stabilise this currency exchange rate with other currencies |
|||
| 20 Feb 2007 |
Install databases on mysql server : phpby01.sql.gz passwords : admin or Mr Poirier's account |
|||
| 21 Feb 2007 |
asked Sylvain for more info on
money system asked Sylvain about what I need to start first with: - testing - debugging - new software |
|||