xouzouris wrote:

I'm working on the client - server communication. Also, kop.

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? ?

Site Submitted>Site Reviewed>Site Added to Scratchedia

MonkeyBop 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? ?

I have an idea, but it would involve a lot of hassle and using a scratch mod. So anyway, Adacraft supports an extension called CloudLink. CloudLink enables communication between multiple projects. So there would be a main Scratchedia project, a project to submit websites and a project to process websites.

Site Submitted>Site Reviewed>Site Added to Scratchedia

I could help a bit, I guess, when it comes to basic Adacraft questions.

101Corp wrote:

Add a scratch SB3 file into a server, open SB3 and make sure it is in a Scratchedia programming language to easily move it into Scratchedia and check for non scratch friendly content, if none add the site to Scratchedia and remove the site from the server. Can have the site where you make an account and you can look at messages to see if your site got approved, when it will be added, if it is added yet, etc. Contact Ancoder for that. Ancoder can help you. Ancoder is a Python/HTML god. Well mostly Python and lots of HTML.

101Corp wrote:

MonkeyBop 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? ?

I have an idea, but it would involve a lot of hassle and using a scratch mod. So anyway, Adacraft supports an extension called CloudLink. CloudLink enables communication between multiple projects. So there would be a main Scratchedia project, a project to submit websites and a project to process websites.

Site Submitted>Site Reviewed>Site Added to Scratchedia

I could help a bit, I guess, when it comes to basic Adacraft questions.

How do you use cloudlink? I need to figure this out

101Corp wrote:

Add a scratch SB3 file into a server, open SB3 and make sure it is in a Scratchedia programming language to easily move it into Scratchedia and check for non scratch friendly content, if none add the site to Scratchedia and remove the site from the server. Can have the site where you make an account and you can look at messages to see if your site got approved, when it will be added, if it is added yet, etc. Contact Ancoder for that. Ancoder can help you. Ancoder is a Python/HTML god. Well mostly Python and lots of HTML.

Also quoted just in case you want to see this

xouzouris wrote:

101Corp wrote:

MonkeyBop 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? ?

I have an idea, but it would involve a lot of hassle and using a scratch mod. So anyway, Adacraft supports an extension called CloudLink. CloudLink enables communication between multiple projects. So there would be a main Scratchedia project, a project to submit websites and a project to process websites.

Site Submitted>Site Reviewed>Site Added to Scratchedia

I could help a bit, I guess, when it comes to basic Adacraft questions.

How do you use cloudlink? I need to figure this out

101Corp wrote:

Add a scratch SB3 file into a server, open SB3 and make sure it is in a Scratchedia programming language to easily move it into Scratchedia and check for non scratch friendly content, if none add the site to Scratchedia and remove the site from the server. Can have the site where you make an account and you can look at messages to see if your site got approved, when it will be added, if it is added yet, etc. Contact Ancoder for that. Ancoder can help you. Ancoder is a Python/HTML god. Well mostly Python and lots of HTML.

Also quoted just in case you want to see this

I'm curious, why do think we should make separate projects for submiting and proccessing websites? What are the advantages?

ToastersUnited wrote:

xouzouris wrote:

101Corp wrote:

MonkeyBop 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? ?

I have an idea, but it would involve a lot of hassle and using a scratch mod. So anyway, Adacraft supports an extension called CloudLink. CloudLink enables communication between multiple projects. So there would be a main Scratchedia project, a project to submit websites and a project to process websites.

Site Submitted>Site Reviewed>Site Added to Scratchedia

I could help a bit, I guess, when it comes to basic Adacraft questions.

How do you use cloudlink? I need to figure this out

101Corp wrote:

Add a scratch SB3 file into a server, open SB3 and make sure it is in a Scratchedia programming language to easily move it into Scratchedia and check for non scratch friendly content, if none add the site to Scratchedia and remove the site from the server. Can have the site where you make an account and you can look at messages to see if your site got approved, when it will be added, if it is added yet, etc. Contact Ancoder for that. Ancoder can help you. Ancoder is a Python/HTML god. Well mostly Python and lots of HTML.

Also quoted just in case you want to see this

I'm curious, why do think we should make separate projects for submiting and proccessing websites? What are the advantages?

scratch has only 5mb of code allowed

kkidslogin wrote:

Life is busy, but I'll try to make more time for Scratch(edia) sorry.

IGABMS wrote:

Guys, who ever is in charge- can we swich our focus and rename the topic to another project that we have more motivation for?

xMysticalCoder wrote:

Shoot i forgot about this. I was scrolling through my mail and found it again. E.

am i fired yet? if not anyway I can help out?

xouzouris wrote:

xMysticalCoder wrote:

Shoot i forgot about this. I was scrolling through my mail and found it again. E.

am i fired yet? if not anyway I can help out?

Nah you're not fired, but I you'd like, you could work on the interface. Have you guys created a programming language for scratchedia? Also for some reason auto-correct has the word scratchedia…

ToastersUnited wrote:

xouzouris wrote:

xMysticalCoder wrote:

Shoot i forgot about this. I was scrolling through my mail and found it again. E.

am i fired yet? if not anyway I can help out?

Nah you're not fired, but I you'd like, you could work on the interface. Have you guys created a programming language for scratchedia? Also for some reason auto-correct has the word scratchedia…

It has scratchedia because you type it a lot.

ToastersUnited wrote:

xouzouris wrote:

xMysticalCoder wrote:

Shoot i forgot about this. I was scrolling through my mail and found it again. E.

am i fired yet? if not anyway I can help out?

Nah you're not fired, but I you'd like, you could work on the interface. Have you guys created a programming language for scratchedia? Also for some reason auto-correct has the word scratchedia…

Also, im working on one using ancoders parser

xouzouris wrote:

xMysticalCoder wrote:

Shoot i forgot about this. I was scrolling through my mail and found it again. E.

am i fired yet? if not anyway I can help out?

Nah you're not fired, but I you'd like, you could work on the interface. Have you guys created a programming language for scratchedia? Also for some reason auto-correct has the word scratchedia…