Scratch

well, we've had our first Scratcher attempting to vote with a test account as well as his own    It seems such a shame to remove them 

No need to promise, the MySQL database lists all voters - it's just not public.

Does anyone know how to spawn unlimited code boxes with Javascript?

The site now has a privacy policy, which is pretty important. Feel free to read and suggest changes: http://www.theblocklibrary.site11.com/p … ement.html

Last edited by sparks (2011-07-07 13:56:15)

Magnie wrote:

Do we even have records the passwords they use?

No.

I think maybe you should add it to the nav bar and put the nav bar on there.
Also, you may want to include your password policy there too. The link from Share a Block works now though. 
Speaking of that, I think it would look better in a table, so that they're not centered weirdly.

There's a minor grammar thing where it says

<li>To help us reduce the amount of fraudulant data shared - making the site safer to use.</li>

It should have a dash, not a hyphen. 

<li>To help us reduce the amount of fraudulant data shared &mdash; making the site safer to use.</li>

scimonster wrote:

I think maybe you should add it to the nav bar and put the nav bar on there.
Also, you may want to include your password policy there too. The link from Share a Block works now though. 
Speaking of that, I think it would look better in a table, so that they're not centered weirdly.

There's a minor grammar thing where it says

Code:

<li>To help us reduce the amount of fraudulant data shared - making the site safer to use.</li>

It should have a dash, not a hyphen. 

Code:

<li>To help us reduce the amount of fraudulant data shared &mdash; making the site safer to use.</li>

I'll make that change then, I was planning to link the full privacy policy in the password policy page anyway 

Any idea where theSucessor is? He never finished working on his blockspec to image system!

I'm planning to email the Scratch team asking a few questions, I thought it may be a good idea for the other librarians to read and contribute to my draft before I send it though.

Last edited by sparks (2011-07-07 14:50:33)

scimonster wrote:

I think your message is good. You may want to list who the librarians, in case they don't know.

Plan.

I'm not sure that "affiliated" is the right word or not, we want connections to the Scratch site to increase traffic and make users feel safer on our site but at the same time we don't want to make the Scratch team liable for any breaches in copyright or law on our site.

sparks wrote:

Does anyone know how to spawn unlimited code boxes with Javascript?

var codeboxcontainer = document.getElementById('cbc');
function addcodebox(code) {
codeboxcontainer.innerHTML += code;
}

if the code box container has an id of cbc
and you run addcodebox() with the code box code for the first parameter it will work.

@comp55, that would certainly make users feel safer...

LS97-Test wrote:

sparks wrote:

@comp500, that would certainly make users feel safer...

I would agree with comp's idea more. You still never know what the site could do with the password. I never share my default pass with non-trusted sites either! 

Last edited by comp500 (2011-07-09 03:14:52)

Well for now using the API is the only way we can go ahead and confirm people sharing blocks are who they say they are!

What sort of "privacy stuff"? What would be great is if you could use <php? include() ?> to add a login page from the Scratch site but without refreshing the page after the information has been entered you wouldn't be able to get true or false back as a confirmation boolean... A page with redirect would be good then, I suppose, as long as people knew the POST name for the login button on that particular API it would work...

Last edited by sparks (2011-07-12 10:46:50)