xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

Hi, just asking, why will you need a bad word blocker if you are using whitelisting? If you use whitelisting, bad words are already out of the question, right?

Actually, we thought of using whitelist in order to prevent random people from making inappropriate websites while we're making Scratchedia, when It's released, there woBecausen't be whitelist. That's where we'll use the bad word blocker.

Guys… it's compulsory to use Whitelisting if you are making a Cloud project on Scratch, unless you are all tired of Scratch and would like to be blocked. I am on Project Meower as a cloud dev and I'm in charge of the actual phrases selection system on the client side. Meower is using Whitelisting, just a more complicated one. We stored every possible sentence on a list and only let them select each phrase as long as it's a valid option. As for negotiations with the ST, it's just to ensure that the phrases stay safe and that we are actually sticking to whitelisting as Meower has made the Whitelist as open as possible, thus meaning that we would need to negotiate with the ST. For the internet on Scratch, if you want to allow people to code websites, better stick to a language like Scratch, and only allow certain phrases to be displayed on the web page. If you are going to allow users to type out their own web page, then, find a way to predefine every possible website a person can type…

OK, but we should at least give users the illusion of freedom. Also why should the programming language be similar to scratch?

DragonfruitTV wrote:

xouzouris wrote:

DragonfruitTV wrote:

xouzouris wrote:

If anybody (that I've missed, in the collab) wants to be whitelisted in my project, tell me.

I do.

Are you in the collab?

Yes.

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

Hi, just asking, why will you need a bad word blocker if you are using whitelisting? If you use whitelisting, bad words are already out of the question, right?

Actually, we thought of using whitelist in order to prevent random people from making inappropriate websites while we're making Scratchedia, when It's released, there woBecausen't be whitelist. That's where we'll use the bad word blocker.

Guys… it's compulsory to use Whitelisting if you are making a Cloud project on Scratch, unless you are all tired of Scratch and would like to be blocked. I am on Project Meower as a cloud dev and I'm in charge of the actual phrases selection system on the client side. Meower is using Whitelisting, just a more complicated one. We stored every possible sentence on a list and only let them select each phrase as long as it's a valid option. As for negotiations with the ST, it's just to ensure that the phrases stay safe and that we are actually sticking to whitelisting as Meower has made the Whitelist as open as possible, thus meaning that we would need to negotiate with the ST. For the internet on Scratch, if you want to allow people to code websites, better stick to a language like Scratch, and only allow certain phrases to be displayed on the web page. If you are going to allow users to type out their own web page, then, find a way to predefine every possible website a person can type…

OK, but we should at least give users the illusion of freedom. Also why should the programming language be similar to scratch?

Because unless you don't allow people to view others code, they can add in not too nice words as comments and make life hard for you guys. As for illusion of freedom, that's what Meower's doing. However, you must redefine the whole website, so may I suggest you only allowed moderators to make sites, and other people who want sites must submit the site through other projects.

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

Hi, just asking, why will you need a bad word blocker if you are using whitelisting? If you use whitelisting, bad words are already out of the question, right?

Actually, we thought of using whitelist in order to prevent random people from making inappropriate websites while we're making Scratchedia, when It's released, there woBecausen't be whitelist. That's where we'll use the bad word blocker.

Guys… it's compulsory to use Whitelisting if you are making a Cloud project on Scratch, unless you are all tired of Scratch and would like to be blocked. I am on Project Meower as a cloud dev and I'm in charge of the actual phrases selection system on the client side. Meower is using Whitelisting, just a more complicated one. We stored every possible sentence on a list and only let them select each phrase as long as it's a valid option. As for negotiations with the ST, it's just to ensure that the phrases stay safe and that we are actually sticking to whitelisting as Meower has made the Whitelist as open as possible, thus meaning that we would need to negotiate with the ST. For the internet on Scratch, if you want to allow people to code websites, better stick to a language like Scratch, and only allow certain phrases to be displayed on the web page. If you are going to allow users to type out their own web page, then, find a way to predefine every possible website a person can type…

OK, but we should at least give users the illusion of freedom. Also why should the programming language be similar to scratch?

Because unless you don't allow people to view others code, they can add in not too nice words as comments and make life hard for you guys. As for illusion of freedom, that's what Meower's doing. However, you must redefine the whole website, so may I suggest you only allowed moderators to make sites, and other people who want sites must submit the site through other projects.

Why should they submit the site through other projects and not one project? Also,I haven't understood how we're supposed to make the safe text system. Is it going to be whitelisted or blacklisted? Is it going to have phrases or words?

kkidslogin wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

Hi, just asking, why will you need a bad word blocker if you are using whitelisting? If you use whitelisting, bad words are already out of the question, right?

Actually, we thought of using whitelist in order to prevent random people from making inappropriate websites while we're making Scratchedia, when It's released, there woBecausen't be whitelist. That's where we'll use the bad word blocker.

Guys… it's compulsory to use Whitelisting if you are making a Cloud project on Scratch, unless you are all tired of Scratch and would like to be blocked. I am on Project Meower as a cloud dev and I'm in charge of the actual phrases selection system on the client side. Meower is using Whitelisting, just a more complicated one. We stored every possible sentence on a list and only let them select each phrase as long as it's a valid option. As for negotiations with the ST, it's just to ensure that the phrases stay safe and that we are actually sticking to whitelisting as Meower has made the Whitelist as open as possible, thus meaning that we would need to negotiate with the ST. For the internet on Scratch, if you want to allow people to code websites, better stick to a language like Scratch, and only allow certain phrases to be displayed on the web page. If you are going to allow users to type out their own web page, then, find a way to predefine every possible website a person can type…

OK, but we should at least give users the illusion of freedom. Also why should the programming language be similar to scratch?

Because unless you don't allow people to view others code, they can add in not too nice words as comments and make life hard for you guys. As for illusion of freedom, that's what Meower's doing. However, you must redefine the whole website, so may I suggest you only allowed moderators to make sites, and other people who want sites must submit the site through other projects.

Why should they submit the site through other projects and not one project? Also,I haven't understood how we're supposed to make the safe text system. Is it going to be whitelisted or blacklisted? Is it going to have phrases or words?

Q: What is blacklisting?

Q2: What does “NFE” stand for?

kkidslogin wrote:

Can we just do a whitelist of words? I've seen a lot of projects that just use that.

kkidslogin wrote:

Q2: What does “NFE” stand for?

GuitarGuyPlayz wrote:

kkidslogin wrote:

Can we just do a whitelist of words? I've seen a lot of projects that just use that.

again, the ST will NFE the project if you do that.

xouzouris wrote:

kkidslogin wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

Hi, just asking, why will you need a bad word blocker if you are using whitelisting? If you use whitelisting, bad words are already out of the question, right?

Actually, we thought of using whitelist in order to prevent random people from making inappropriate websites while we're making Scratchedia, when It's released, there woBecausen't be whitelist. That's where we'll use the bad word blocker.

Guys… it's compulsory to use Whitelisting if you are making a Cloud project on Scratch, unless you are all tired of Scratch and would like to be blocked. I am on Project Meower as a cloud dev and I'm in charge of the actual phrases selection system on the client side. Meower is using Whitelisting, just a more complicated one. We stored every possible sentence on a list and only let them select each phrase as long as it's a valid option. As for negotiations with the ST, it's just to ensure that the phrases stay safe and that we are actually sticking to whitelisting as Meower has made the Whitelist as open as possible, thus meaning that we would need to negotiate with the ST. For the internet on Scratch, if you want to allow people to code websites, better stick to a language like Scratch, and only allow certain phrases to be displayed on the web page. If you are going to allow users to type out their own web page, then, find a way to predefine every possible website a person can type…

OK, but we should at least give users the illusion of freedom. Also why should the programming language be similar to scratch?

Because unless you don't allow people to view others code, they can add in not too nice words as comments and make life hard for you guys. As for illusion of freedom, that's what Meower's doing. However, you must redefine the whole website, so may I suggest you only allowed moderators to make sites, and other people who want sites must submit the site through other projects.

Why should they submit the site through other projects and not one project? Also,I haven't understood how we're supposed to make the safe text system. Is it going to be whitelisted or blacklisted? Is it going to have phrases or words?

Q: What is blacklisting?

Q2: What does “NFE” stand for?

Blacklist is the opposite of whitelist. A whitelist is a list of people who are allowed to do something. A blacklist is a list of people who aren't allowed to do something.

IGABMS wrote:

xouzouris wrote:

kkidslogin wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

xouzouris wrote:

-Mysticoder- wrote:

Hi, just asking, why will you need a bad word blocker if you are using whitelisting? If you use whitelisting, bad words are already out of the question, right?

Actually, we thought of using whitelist in order to prevent random people from making inappropriate websites while we're making Scratchedia, when It's released, there woBecausen't be whitelist. That's where we'll use the bad word blocker.

Guys… it's compulsory to use Whitelisting if you are making a Cloud project on Scratch, unless you are all tired of Scratch and would like to be blocked. I am on Project Meower as a cloud dev and I'm in charge of the actual phrases selection system on the client side. Meower is using Whitelisting, just a more complicated one. We stored every possible sentence on a list and only let them select each phrase as long as it's a valid option. As for negotiations with the ST, it's just to ensure that the phrases stay safe and that we are actually sticking to whitelisting as Meower has made the Whitelist as open as possible, thus meaning that we would need to negotiate with the ST. For the internet on Scratch, if you want to allow people to code websites, better stick to a language like Scratch, and only allow certain phrases to be displayed on the web page. If you are going to allow users to type out their own web page, then, find a way to predefine every possible website a person can type…

OK, but we should at least give users the illusion of freedom. Also why should the programming language be similar to scratch?

Because unless you don't allow people to view others code, they can add in not too nice words as comments and make life hard for you guys. As for illusion of freedom, that's what Meower's doing. However, you must redefine the whole website, so may I suggest you only allowed moderators to make sites, and other people who want sites must submit the site through other projects.

Why should they submit the site through other projects and not one project? Also,I haven't understood how we're supposed to make the safe text system. Is it going to be whitelisted or blacklisted? Is it going to have phrases or words?

Q: What is blacklisting?

Q2: What does “NFE” stand for?

Blacklist is the opposite of whitelist. A whitelist is a list of people who are allowed to do something. A blacklist is a list of people who aren't allowed to do something.

I was thinking a whitelist for words/not people.

ToastersUnited wrote:

kop

xouzouris wrote:

ToastersUnited wrote:

kop

What?

ToastersUnited wrote:

xouzouris wrote:

ToastersUnited wrote:

kop

What?

Kop attempt
King of page

kkidslogin wrote:

Probably me again… I have no idea how many times I've been KOP when Codingland was still running the place.

xouzouris wrote:

kkidslogin wrote:

Probably me again… I have no idea how many times I've been KOP when Codingland was still running the place.

Same. Wait, has Codingland completely quit?

kkidslogin wrote:

I'm currently working on a python server that distributes a currency known as “SoSC Credits”… It will allow currencies to be used in the website. The way it works is that every person who makes a SoSC Bank Account will get 500 credits, so there is a total number of 500 * number of accounts credits always in circulation, so we will never have inflation.

So far you can get a bank balance and create a new account, on the server-side. On the scratch_side, you can only get your bank account, but I will add account creation tonight. After that, the only thing needed is to be able to give money to other accounts for transactions. I may also allow the server to recognize when a new project wants to join in.

kkidslogin wrote:

I'm currently working on a python server that distributes a currency known as “SoSC Credits”… It will allow currencies to be used in the website. The way it works is that every person who makes a SoSC Bank Account will get 500 credits, so there is a total number of 500 * number of accounts credits always in circulation, so we will never have inflation.

So far you can get a bank balance and create a new account, on the server-side. On the scratch_side, you can only get your bank account, but I will add account creation tonight. After that, the only thing needed is to be able to give money to other accounts for transactions. I may also allow the server to recognize when a new project wants to join in.