Milovana.com

Ok...

I've just blitzed this board with a few suggestions. Originally I had them all in a single post but then that makes it hard to consider and even comment on each one separately.

This is another suggestion that's impossible for 1.0, but I'm throwing out here anyway for future consideration once it's possible to have programmable logic behind the teases:

Allow tease authors to store not just per-session variables, but per-teasee variables as well. Asking "Do you have a shoe-lace?" at the begining is only important to use per tease, but it would also be great to have variables that can be re-used in multi-tease campaigns (imagine what "A week of torment" could be like if the teases interacted with each other) or simply remembered the next time the same teasee goes to the same tease, as in "Last time you only lasted 15 minutes, let's see if we can improve that."

The persistent variables would probably be stored as a six column table... tease author, teasee, variable name, variable value, some datestamp of when it was last accessed (or failing that, modified) and maybe variable type (number, string, etc) if you need that. Setting or retriving the variable would update the datestamp, and you could keep things clean by deleting rows out of the table with a datestamp older than, say, six months. As a tease author, it would be great to be able to see how your tease was going by looking at this table, but if there are privacy/security concerns then you could make it so nobody, even the authors, can see the variables, and they are only retrievable per tease.

functions would probably be like set-persistant-value(name, value) and get-persistant-value(name), and the functions would add the keys of the author and the teasee as it looks up to the table.

PS: If you do this you'll probably want some temporary table too that gives a list of variable names per tease author, so that tease authors can look and see what variable names they've already used, just to make it easier on them.

Great suggestions, camel. I've read them all and I just wanted to drop a line to let you know that I'll go through them and give you my thoughts in a minute.

First of all: Thanks for the suggestions. It's great to hear people are thinking in similar directions!

So, before I get to the meat of it, I want to emphasize that I continuously walk the line between not including the community enough and spoiling the surprise of a cool new feature suddenly appearing on the page.

Right now, all my attention is directed towards the upcoming page re-design, but I still want to explain why we don't go ahead and add interactive features to webteasing right now.

To me, I think the single most beautiful feature about webteasing is that anyone can write them. If we start implementing too many features, you will need to be a programmer just to write a webtease.

With that being said, I want to add that I'm open to simple additions to the scheme. For example we are planning to allow authors to add a timer to a page. (Thanks to surfcreanative for the idea!)

However, apart from the sector of webteases there is still room for something with a little more interactivity where the more technically inclined of us are developing all kinds of cool stuff. This is what I continue to refer to "the secret project" .

I don't to give out more details at this point, it will be quite a while until we can finally release that to the public, so I'd rather not blow out all the hints at once. If there is any community in the world which can value a good tease it's got to be this one.

I will get in touch with camel and who knows, maybe we'll soon have a new man on board. The bigger the team, the earlier you'll see results.

seraph0x,

create 2 Editor:

- 1 simple (actualy)
- 1 advanced (your secret project )

When somebody will start a new webtease, can choice the Editor.

Thats exactly what I'm planning to do.