This is a read-only archive of the old Scratch 1.x Forums.
Try searching the current Scratch discussion forums.

#26 2010-03-04 02:31:33

billyedward
Scratcher
Registered: 2008-01-03
Posts: 500+

Re: Differentiate between mesh clients.

You can set an id variable, of each one.
All that has to happen is that when a new project is connected, the client project generates the id number.
It then broadcasts to the host that it is a) connected and b) to tell it to get the value of the id (from the variable sensor, since it was the last connected).

Now, the host has a variable called something like 'sendto.'
It sets this to the id of the client which it wishes to send a broadcast to, and then sends the broadcast. All of the receiver blocks should have an if at the top that says:
<if><<  <not> <( <{ id }> <=> (sensor value (sendto) )> >>
|<stop script>
<end>[/blocks]
This way, all scripts triggered on a client with the wrong id are terminated.

Understand?


"I'd love to change the world, but they haven't released the source code yet."
Check out the latest version of Streak --> http://billy.scienceontheweb.net/Streak

Offline

 

#27 2010-03-04 08:21:59

sparks
Community Moderator
Registered: 2008-11-05
Posts: 1000+

Re: Differentiate between mesh clients.

I understand, but anyone wanting to read the information need only get rid of that bit of script to read everything... and It's the ID numbers that need to be kept private in order to stop someone changing theirs to someone elses and pretending to be them.


http://img541.imageshack.us/img541/7563/scratchbetabanner.png

Offline

 

#28 2010-03-04 11:05:48

markyparky56
Scratcher
Registered: 2008-03-20
Posts: 1000+

Re: Differentiate between mesh clients.

sparks wrote:

a good test of something like this is where you get someone else to try and hack it - eg, get the name or password of someone else to see how secure the information is, before setting it up, also hacking it yourself! if there's no way for YOU to do it, there probably isn't a way, seeing as you scripted it. I'm going to have a look at how some web data is encrypted and copy that.

i'm thinking if each project upon startup generates a random order in which to muddle up the characters it sends, then as long as the host has a copy of that random order to decode it at the other end, the data will be muddled up to any other viewer. the flaw with that is that the random order needs to be sent at some point, and someone can see it then and make a note.

I don't want to use substitution as it requires lots of scripting and really slows down data sending.

What your getting into know, as i see it, requires BYOB, and if you use BYOB, then you can use its compiler, to make it almost completely fool proof, so that unless the person someone how manages to de compiler the exe and get at its variables, which i dont think is possible, its safe!


http://j.mp/jgVnTq
Check out my game engine development site: NewDawn I'm a Level 171 Scratcher.I am http://bit.ly/nkvLNT

Offline

 

#29 2010-03-14 04:43:18

sparks
Community Moderator
Registered: 2008-11-05
Posts: 1000+

Re: Differentiate between mesh clients.

I thought that the Compiler for BYOB didn't actually compile the project, just opened it in full screen.


http://img541.imageshack.us/img541/7563/scratchbetabanner.png

Offline

 

#30 2010-03-14 05:53:06

markyparky56
Scratcher
Registered: 2008-03-20
Posts: 1000+

Re: Differentiate between mesh clients.

sparks wrote:

I thought that the Compiler for BYOB didn't actually compile the project, just opened it in full screen.

There is no true compiler for scratch, but it does make it an .exe but you do view it in Presentation mode. Iv only used the chirp compiler before, but there shouldn't much of a difference. Except that the BYOB one works with homemade blocks.


http://j.mp/jgVnTq
Check out my game engine development site: NewDawn I'm a Level 171 Scratcher.I am http://bit.ly/nkvLNT

Offline

 

Board footer