TLTP is working :)

oh i should say, XTM works again and i've done heavy optimization on it (i thought there was running short on memory).

in TLML 0.6 i'll also update XTM.
with TLML 3 & 6 char per prim XTM support will change, and 4/8 char mode will be added. This unification is needed to make changing modes easier (currently 3/6 & 5/10 require the prim to be rotated differently, that is what is being addressed.).

"the browser is open source (and the implied license requires it)"

Where is the license for this? I'm no lawyer but I'm almost sure that when you post code to a forum or Wiki without any specified license.. it becomes public domain by default.

ahhh you see thats where your wrong, under US copyright law, anything created, is automaticly copyright. From the copyright licensing is derived. Nowhere that i know of does it say that I forfit my rights to my works upon publishing them here. Even if it did say so somewhere it i could argue that it was a mistake to publish it here, as i was unaware of that restriction (which is alowed under copyright law). With copyright law, the owner(s) hold all the rights.

The goal of this project was to be free and open source.

I would say: If a simple majory of the script was writen by us you must keep the script open source (full perms). If then a simple majority you can distribute closed source but this only applies to my scripts, you will have to talk to Jesrad about her scripts.

This may change as we may decided on a more formal license.

OK I don't remember who told me that but maybe they were wrong. I think you should really pick a license though to be on the safe side.. This sounds very cool but I'll wait for the next version to play with it

Nothing ever becomes public domain "by default", but only through being told so explicitly by whoever owns it, in all the countries that signed the Berne Convention on intellectual property. The only "by default" rights you have on protected works are fair-use rights.

My scripts for TLTP are freely modifiable and redistributable, as long as you allow free (as in beer and speech) further redistribution and modification.

TLML will be released shortly, i've gotten most of the bugs beaten out of it, and gotten it back within memory constaints. I implemented proposal B with a few minor modifications. Currently i'm working on revamping XTM. I've already posted preliminary documentation to the wiki; but not the scripts.

Woot! I can't wait to try out the new stuff.

You mean the browser can't be distributed as no-mod even if the source is also distributed with it, like in a notecard for example?

Not exactly. Just that it wouldn't matter - there's nothing stopping someone else from making their own browser with those scripts, making it full permissions, and connecting to your server - any way they like.

I was thinking something like a secure client-server system where the server has instructions to make items that can be browsed by a client, but the user of the client should not be able to see the data. Basically the client should make a requests to the server to request a TLML page. The server would need a way to valide the client. I was thinking something like

both scripts have
string secret = "'übersecretkeyword";

First the client send a request to server. When receiving the request, the server needs to validate the request with something like

integer timestamp = llGetUnixTime();
llSay(CHANNEL, (string)timestamp);

then the client does

listen(integer channel, string name, key id, string message) {
   if(id == serverkey) {
      llSay(CHANNEL, llMD5String(secret, (integer)message));
   }
}

then finally the server does

listen(integer channel, string name, key id, string message) {
      string digest = llMD5String(secret, timestamp);
      if(digest == message) {
         //authenticated, do stuff here
      }
}

For each item the client requests to see it can then do things like change the channel that data is sent on etc. to make it difficult to intercept the actual TLML data that is sent.

A secure TLTP plugin could be made, the TLTP url handler could be extended. Basicly a black box script, this script would be closed source but free to use. If it were to use MD5 it could be incredibly annoying to hack. Brute forcing a nonce is possible (6->12 hours), but much harder to brute force the input string.

Updates:
TLML 0.60 release candidate has been released.
I've updated the documentation.
TLTP will need a new command added to hide & show prims by group, i'll get to that in a bit.
XTM i'm working on currently, it will be added shortly.