Pages: 1
Topic closed
I like the whole cloud variables thing, but can't this violate scratch's code and allow people to add PMing? I understand that it would be good for many other things such as surveys, but it might work. Any idea why the ST didn't think twice about it?
Last edited by ImagineIt (2012-05-13 08:04:55)
Offline
That's similar to something I was wondering, which is whether or how cloud variables will be "moderated". Even if it's something as simple as a high score list, what happens when someone puts in a naughty word instead of their name?
Offline
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.
Offline
scimonster wrote:
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.
you can easily use hash algorithm to allow only certain people being able to view a chat using passwords...
can be a bit problematic, if used correctly ST must manually look up vars in the DB...
Offline
roijac wrote:
scimonster wrote:
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.you can easily use hash algorithm to allow only certain people being able to view a chat using passwords...
can be a bit problematic, if used correctly ST must manually look up vars in the DB...
You could just check the scripts to see the method they use to hash them.
Offline
roijac wrote:
scimonster wrote:
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.you can easily use hash algorithm to allow only certain people being able to view a chat using passwords...
can be a bit problematic, if used correctly ST must manually look up vars in the DB...
A bit of modification could change that.
I'm not too worried.
Offline
their is a simple answer:
add a moderate option on you project so when clicked you must log in to your account. from the moderate interface on you project have options that do things such as:
delete things from cloud list
ban accounts from a chat
clear a list
or change names
Offline
RedRocker227 wrote:
roijac wrote:
scimonster wrote:
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.you can easily use hash algorithm to allow only certain people being able to view a chat using passwords...
can be a bit problematic, if used correctly ST must manually look up vars in the DB...You could just check the scripts to see the method they use to hash them.
use SHA algorithm (even md5 is ok if you replace pass often enough)
Offline
i saw a projec that had a list where u could use it as a ch@room so i don't think th@ this will b a problem *_*
Offline
See, here's a script that will only allow 2 users into a chatroom (me and my test) while not allowing anyone else to see what is inside the chatroom, so therefore, PMing.
when gf clicked add [TorbyFork234] to [approved usernames v] add [TorbyFork234_Test] to [approved usernames v] hide list [(cloud) chatroom v] forever if <<username>=<item (any v) of [approved usernames v]>> show list [(cloud) chatroom v] ask [what do you want to say?] and wait add <join<join<username>[ ]<answer>>> to [(cloud) chatroom v] end
Last edited by TorbyFork234 (2012-05-14 10:14:31)
Offline
I was thinking the same thing, and decided they would probably add numbers, but we all know ways to get around numbers, I mean, if we had to use bytes... XD
So I was thinking they might have to make it so there are only a few blocks, such as vote on [ ] or add me to [ ]. (voting would be adding one to a cloud variable though, so maybe that could still be bypassed. (using some kind of number translating but having it use this block in a repeat loop.)
Maybe they should just make hat blocks like, When im clicked vote { }
when im clicked add me to
Then it would be impossible to program something to have letter communication between users. (unless they told the user to click me 5 times to say yes, 3 times for no... etc. )
Offline
scimonster wrote:
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.
Say, will sprites be able to be controlled by cloud variables? So that, say, I could make a passcoded game, that only a few people knew the password to, and then we could control out own characters based off of what the cloud variables tell them to do?
Offline
Cozyhut3 wrote:
scimonster wrote:
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.Say, will sprites be able to be controlled by cloud variables? So that, say, I could make a passcoded game, that only a few people knew the password to, and then we could control out own characters based off of what the cloud variables tell them to do?
I guess you could.
Offline
Cozyhut3 wrote:
scimonster wrote:
Well, PMing, no. Chatting, people (including me) plan to make chatroom projects.
And if someone puts inappropriate text into a cloud list, the ST can be contacted, or the project owner could remove it.Say, will sprites be able to be controlled by cloud variables? So that, say, I could make a passcoded game, that only a few people knew the password to, and then we could control out own characters based off of what the cloud variables tell them to do?
If you made it a password someone could look inside and get it. Username sensors would be a better solution.
Offline
Topic closed
Pages: 1