I'll probably be posting the very early development files to the server over the next week so you can play around, so let me know if you'd like guest accounts for the time being. Keep in mind - i'm not thinking about interface until the engine is working properly, and then i'll be getting someone who can actually design to give me a hand with the interface.

I'll also give out the URL for the changelog, so you can keep track of the really geeky parts of the development if you're interested.
Otherwise, i'll keep you posted through this blog.

m


Friday, July 26, 2002
19:16
a little more in depth explanation of how the site will work:

The root passage is created, and all users can read it. The root passage is the first passage in a story. Whoever creates the first passage, defines a number of properties for that story, which will be explained later.

Registered users (those who have created an account on the site, have a username and password) can then login to the site, and post another passage at the second level (ie. child of the root passage)

when a passage is posted, it must be validated before it is visible online - this is to ensure the quality of the passage is adequate, there is no unsuitable content, the length is about right etc. initially, the posts will be validated by the hyperprotagonist, but as the site grows, and more content is required to be validated, hypereditors will be appointed, who also have permission to validate passages.

passages have a maximum length. the maximum length can be different for each story, as longer length passages will have the effect of producing more developed stories, shorter passaged stories will be more rapidly produced.
each story also has a maximum 'width', which is the number of follow up passages any node (ie. passage) can have. This is usually infinite, but may be set to lower for competition purposes.

Anyone registered can post to the node, apart from the author who wrote the previous passage. This is to stop a single person writing an entire story. It is possible that two authors could alternate however.

the process of posting follow up passages progresses whilst the story is below its 'minimum height' - which is the number of levels the passages has reached (ie. root - 1st level - 2nd level etc) is above the story defined level, when someone can post a 'completion request'. That author is then allowed to write two-five sequential passages to complete the story as they see fit. Any number of complete requests can be posted to a node above the minimum height, ie. the story can have any number of endings. Once a completion has been made, the nodes within that final set of passages are not closed - additional authors can continue to add passages below that - creating a story which has several endings, and any depth.



19:10
created initial phase database, three tables, the users, passages and stories tables.
they have enough functionality to start adding story content. i'm going to start building the basic functionality to add content now.
i've also done a little on the layout of the site - but i need to work on the inks for the pages first so i can see exactly what i need include on each page.

also - thinking about legal issues - copyright, who owns the work? obviously its not a single author, and in the spirit of collaboration, people won't kick up a fuss, but if someone does, and they want ownership - if i pull them out of the story thread, it kills the passages below it. i need to get some legal advice on that..
equally, if we do go ahead and publish any of the stories.. royalties go to whom?? probably best to simply donate it all to charity.


Thursday, July 25, 2002
17:05
nicer template for this page done now too :)



16:57
hyperconsequence_dev is born!
This blog basically keeps track of the development process of the hyperconsequence_

So far, we've created the holding page, and whacked up an about_ page for brief detail on what the site is and should be, and a notify me_ page for registering users - and we've already got 4 people in there! (one of them is me though ;)

There is a basic users table with nothing more than email and reg_date for the time being.. that will need completely revamping for the hyperbuilders, but that can come in time :)