This is such chaos! I'm not talking about bad planning, but all the problems we are having with getting the password through.

jasperjay wrote:

This is such chaos! I'm not talking about bad planning, but all the problems we are having with getting the password through.

Yeah, we need to get more organized. TeeMee, at least try my website idea. Sound good? I am going to see if I can get the name of a fruit to you using my system.

I'd suggest pear!

On a more serious note though, I think that we should at least try Radical's idea. If it works, it works, but if it doesn't, then we can carry on with the timetable.

Xelanybor101 wrote:

I'd suggest pear!

On a more serious note though, I think that we should at least try Radical's idea. If it works, it works, but if it doesn't, then we can carry on with the timetable.

I agree. This is a collab. We should be friendly, try new ideas. If they fail, at least we tried and proved we can work together. If we want to accomplish great things, we need to work together! This is a nice friendly collab, and we need to keep it that way. So, I think we should try Radical's website idea. And if we fail, at least we will have tried.

Look, we can have website just for the password system, but everything else has to be based on scratch. I don't want us to just abandon rankware platform, because we have put a lot of work into it

By the way, no matter what you do, you will still have to share public information to the new user (all messaging on scratch is public) which other people could use to get the password too. If someone else joins the website pretending to be the new user, you wont be able to tell who is the real one.

ok i have an idea. we need to have the recruitment process happen on a website.

code needs to be given to only one user.
this must happen externally
no personal information about the user may be leaked on scratch
so we have an account system with no personal information on a new website
but users have to sign up there first instead of on the forum
this is basically because we have to know an off-scratch account explicitly tied to the user, and nobody else. if they only signed up to the website when they were going to be promoted, pepole viewing the forum could realise they are going to be promoted and will make a new account copying thier username and making it before the real person does.

so…
in terms of a requirements specification for the new website, i guess you can consider the following:

The website can have whatever free domain ending you choose, I know hostinger is quite good for free domains.
The name of the website would be RankwareRecruitment.
It needs to be as simple as possible.
There needs to be an account system.
Therefore there needs to be a sign up / sign in system.
There should be a link to the website on the main post on this forum.
To sign in, they should only need to provide their scratch username and a password (but not their scratch account password!) and fill in the standard recruitment form we have on our forum.
Data then tied to an account will be a sort of pre-rank, which can be one of (pending, rejected or accepted), and then whether they can see the password or not.
A user would have a page for them which would either be blank, or have the password on it if they became allowed it.
If user becomes allowed the password, one of the admin would be able to activate some field of text on their page to say the password.

One last note, DONT MAKE ANOTHER RANKWARE ACCOUNT. We only need one. All projects, even the in-development ones have to be shared, but have something in the title saying whether they are in development or not. A duplicate would be made once a project is finished.

Teemee -

right. thats all the account security system debate over and done with. im now going to finish some stuff with rankware platform.

TeeMee123 wrote:

Letsplayally, i need you to tidy up the front post as there are a couple of issues
1) We need to keep the name as rankware everywhere, to avoid confusion.
2) we aren't reqruiting at the moment.
also at some point i will write a paragraph or two to summerise the rankware platform systemm for when it is made.

Done!

Look, the system has already been created & tested. The Scratch Wiki trusts it! The code is a SHA1 hash of a user's agent, the hour rounded, & other stuff. You MUST comment the code, it not only checks that the code was commented, it checks that it was comment BY THE USER SIGNING UP. Sounds secure to me.

TeeMee123 wrote:

All projects, even the in-development ones have to be shared

Theres' gotta be a better way


Also, hostinger reveiews all new website creations MANUALLY so I use x10hosting instead

Not ready yet, but when it is, it will likely be at http://rankware.comlu.com/index.php/Special:RequestAccount

EDIT : Added “likely” – when it comes to free hosting, can never promise anything

Actually, they get to pick their password ( does not even have to be scratch password )

teemee-
Sorry but I have no idea what you meant by that first comment

TeeMee123 wrote:

i made dis https://scratch.mit.edu/projects/94438660/

I like it but what does it have to do with Rankware?

RankwareProgramming wrote:

teemee-
Sorry but I have no idea what you meant by that first comment

The code you will have to comment will look somewhat like this:



9q8nu234o8ru9384u3984ur9384j98wu3498f38jn94un9r


It will change every half hour, and must be from your house and browser. You cannot comment the code at your house and then request an account in the computer lab at school.

And one more thing, the key to anti-impersonation. If I am trying to impersonate you, it wouldn't work, even if I was on the same house and browser as you. Because, not only does it check that the code was commented, it checks that it was commented by the user signing up. So I would comment it in my own account, and the software would not find it.

radical, i have no idea what you are talking about. whatever it is you are suggesting seems way to complicated.

1000th post on this thread!

Sorry, I had to do that.