The ST is pulling out their hair over cloud variables, and I stop and think, “How about making a new rank?”

A “Trusted Scratcher” would recieve:

1. More leniency from being banned.
2. Ability to use Cloud Lists and so on.
3. Some other random special privileges, like projects having a higher probability of being viewed, more likely for the ST to listen, etc.

How would it work? You have no say over it. If the ST likes your projects and sees you've been following the rules(Is “the rules” a Scratcher?) then they can make you one. Violate rules, and *BLOOP* no more trusted status. You should only be able to recover it once, or not at all. Wait, more leniency, I said? Ah, yes. Sometimes the ST makes mistakes; Scratchers like Nathmorr and thisisntme got banned when it was an accident. These could be examined more closely.

So there it is. Hope you like my idea, and I hope the ST likes it. It could clean up the whole Cloud Data mess, and reward people who stick to the rules. Any ideas to improve this? The idea is incomplete, and may need a little(or a lot of) bending to work out.

P.S. This idea still won't/can't unban chatrooms! Sorry. That isn't the idea here. I agree with the ST that chatrooms are a bit too much, realistically. No matter what they do, though, Cloud Data makes more moderation for them. Oops.

I like the idea, it could allow scratchers who spend lots of time and energy to get rewarded in certain ways. It would also give new scratchers something to aim for, but there should be a mid ground in my opinion, just to keep it more even and less daunting.

Standard

Respected

Trusted
————————————————————————————–

What do you think of a setup like that? Everyone would start out as standard and move up to respected without too much trouble, and then after remaining with scratch even longer they would get trusted. It would also leave less of a blaring difference between scratchers with this extra mid-ground (respected).
The benefits? It shouldn't really be anything too incredibly pronounced, but it should hold some weight.

Standard = limited cloud capability, 60 second post wait time (both are just to keep spamming and illegal projects from being done, it would also keep major cloud data usage at bay. If they are serious about cloud data, then all they have to do is earn respected. If they aren't motivated enough to try to earn respected, then it isn't a huge deal anyways)

Respected = no cloud limit, no post wait time (since they're probably not going to spam at this point)

Trusted = Slightly higher chance of being viewed, more keyword search tags per project (this may be all that's needed to make their projects more popular)

I don't know, I whipped up that list in a few minutes, and some of the ideas were derived from failord, but what do you think?

I don't think it would be a good idea to create social classes on this website any more than absolutely possible. This would create a lot of people bragging and saying that their post is more important than someone else's because they have a higher rank. Also…
-No user should get more leniency in banning just because they've been around longer - inappropriate and disrespectful comments shouldn't be allowed by anybody and everybody should get banned the same.
-Any Scratcher (i.e. not New Scratcher) should be allowed to use all cloud data, because it is an important part of programming and the people who have been on for a while will complain that they can't make any leaderboards or anything
-Seniority should not affect popularity. If a user posts a good project, it should have the same likelihood of being viewed as if it were posted by anyone else.

jvvg wrote:

I don't think it would be a good idea to create social classes on this website any more than absolutely possible. This would create a lot of people bragging and saying that their post is more important than someone else's because they have a higher rank. Also…
-No user should get more leniency in banning just because they've been around longer - inappropriate and disrespectful comments shouldn't be allowed by anybody and everybody should get banned the same.
-Any Scratcher (i.e. not New Scratcher) should be allowed to use all cloud data, because it is an important part of programming and the people who have been on for a while will complain that they can't make any leaderboards or anything
-Seniority should not affect popularity. If a user posts a good project, it should have the same likelihood of being viewed as if it were posted by anyone else.

Yeah, I agree.

We shouldn't have a special place just for special people, who only get decided special by the ST.

mhm, which is why bragging would be totally unacceptable, I said that it could work but… there's always those little things that get in the way

actually, now that I think about it for more than 2 minutes, I agree. This isn't a good idea, too many unforeseen consequences. Sorry

Hmmm… Yeah, just tossing an idea out there. Now that I think about it, it IS flawed. I guess the ST can close the topic.

bullelk12 wrote:

I like the idea, it could allow scratchers who spend lots of time and energy to get rewarded in certain ways. It would also give new scratchers something to aim for, but there should be a mid ground in my opinion, just to keep it more even and less daunting.

Standard

Respected

Trusted
————————————————————————————–

What do you think of a setup like that? Everyone would start out as standard and move up to respected without too much trouble, and then after remaining with scratch even longer they would get trusted. It would also leave less of a blaring difference between scratchers with this extra mid-ground (respected).
The benefits? It shouldn't really be anything too incredibly pronounced, but it should hold some weight.

Standard = limited cloud capability, 60 second post wait time (both are just to keep spamming and illegal projects from being done, it would also keep major cloud data usage at bay. If they are serious about cloud data, then all they have to do is earn respected. If they aren't motivated enough to try to earn respected, then it isn't a huge deal anyways)

Respected = no cloud limit, no post wait time (since they're probably not going to spam at this point)

Trusted = Slightly higher chance of being viewed, more keyword search tags per project (this may be all that's needed to make their projects more popular)

I don't know, I whipped up that list in a few minutes, and some of the ideas were derived from failord, but what do you think?

No. Absolutely not.

lalala3 wrote:

bullelk12 wrote:

I like the idea, it could allow scratchers who spend lots of time and energy to get rewarded in certain ways. It would also give new scratchers something to aim for, but there should be a mid ground in my opinion, just to keep it more even and less daunting.

Standard

Respected

Trusted
————————————————————————————–

What do you think of a setup like that? Everyone would start out as standard and move up to respected without too much trouble, and then after remaining with scratch even longer they would get trusted. It would also leave less of a blaring difference between scratchers with this extra mid-ground (respected).
The benefits? It shouldn't really be anything too incredibly pronounced, but it should hold some weight.

Standard = limited cloud capability, 60 second post wait time (both are just to keep spamming and illegal projects from being done, it would also keep major cloud data usage at bay. If they are serious about cloud data, then all they have to do is earn respected. If they aren't motivated enough to try to earn respected, then it isn't a huge deal anyways)

Respected = no cloud limit, no post wait time (since they're probably not going to spam at this point)

Trusted = Slightly higher chance of being viewed, more keyword search tags per project (this may be all that's needed to make their projects more popular)

I don't know, I whipped up that list in a few minutes, and some of the ideas were derived from failord, but what do you think?

No. Absolutely not.

ikr, very bad idea, sorry

bullelk12 wrote:

lalala3 wrote:

bullelk12 wrote:

I like the idea, it could allow scratchers who spend lots of time and energy to get rewarded in certain ways. It would also give new scratchers something to aim for, but there should be a mid ground in my opinion, just to keep it more even and less daunting.

Standard

Respected

Trusted
————————————————————————————–

What do you think of a setup like that? Everyone would start out as standard and move up to respected without too much trouble, and then after remaining with scratch even longer they would get trusted. It would also leave less of a blaring difference between scratchers with this extra mid-ground (respected).
The benefits? It shouldn't really be anything too incredibly pronounced, but it should hold some weight.

Standard = limited cloud capability, 60 second post wait time (both are just to keep spamming and illegal projects from being done, it would also keep major cloud data usage at bay. If they are serious about cloud data, then all they have to do is earn respected. If they aren't motivated enough to try to earn respected, then it isn't a huge deal anyways)

Respected = no cloud limit, no post wait time (since they're probably not going to spam at this point)

Trusted = Slightly higher chance of being viewed, more keyword search tags per project (this may be all that's needed to make their projects more popular)

I don't know, I whipped up that list in a few minutes, and some of the ideas were derived from failord, but what do you think?

No. Absolutely not.

ikr, very bad idea, sorry

Yeah.

I'm afraid some Scratchers could think they were better than others. And other Scratchers could feel harmed. I don't think that's an option, I mean, imagine: you have the New Scratcher Status, then you finally are a Scratcher and what happens? Oh no, you're not trusted. I mean, I would be really frustrated and disappointed.

LiFaytheGoblin wrote:

I'm afraid some Scratchers could think they were better than others. And other Scratchers could feel harmed. I don't think that's an option, I mean, imagine: you have the New Scratcher Status, then you finally are a Scratcher and what happens? Oh no, you're not trusted. I mean, I would be really frustrated and disappointed.

Yeah

I think there should just be scratcher+ rank and you must post 20 unique projects and be on the site for >1 year , you must'nt have broken any rules - the rank is the same to normal except capable of using cloud lists with strings - everyone should be able to use variables.

Tbtemplex97 wrote:

I think there should just be scratcher+ rank and you must post 20 unique projects and be on the site for >1 year , you must'nt have broken any rules - the rank is the same to normal except capable of using cloud lists with strings - everyone should be able to use variables.

We'll eventually have cloud lists with strings for everyone.

mythbusteranimator wrote:

Tbtemplex97 wrote:

I think there should just be scratcher+ rank and you must post 20 unique projects and be on the site for >1 year , you must'nt have broken any rules - the rank is the same to normal except capable of using cloud lists with strings - everyone should be able to use variables.

We'll eventually have cloud lists with strings for everyone.

Did you not read the first post?
The scratch team doesn't want to give everyone cloud lists as people could spam and crash the servers

Well, many bad things, e.g.
New Scratcher named ‘hi50hello12’ joins scratch
hi50hello12 wants to use cloud lists/variables
hi50hello12 can't because (s)he is a new scratcher
hi50hello12 quits scratch and never joins again.


See what i mean?

SFollis wrote:

Well, many bad things, e.g.
New Scratcher named ‘hi50hello12’ joins scratch
hi50hello12 wants to use cloud lists/variables
hi50hello12 can't because (s)he is a new scratcher
hi50hello12 quits scratch and never joins again.


See what i mean?

They wouldn't leave because of that, new scratchers would probably not be able to use them anyway - if a new scratcher wishes to use cloud then they prove to ST they can be trusted.

SFollis wrote:

Well, many bad things, e.g.
New Scratcher named ‘hi50hello12’ joins scratch
hi50hello12 wants to use cloud lists/variables
hi50hello12 can't because (s)he is a new scratcher
hi50hello12 quits scratch and never joins again.


See what i mean?

Probably wouldn't happen if ST gives them fair warning. Plus anybody who isn't willing to reach full Scratcher rank probably isn't cut out for it anyway.

And it's also current policy that only full Scratchers can use them, which makes sense. Think about it- if you get kicked out for misusing Cloud Data, you just start up a brand-new account. I think I read that the one game called Roblox has that problem. Full Scratcher status keeps down the amount of moderation they have to do and helps prevent spammers.

Lastly I'd like to say that it really isn't that hard to become a full Scratcher, I became one pretty quick and I didn't mind being a New Scratcher in the first place. If the ST just has a message that carefully explains why you have to be a full Scratcher to use Cloud Data, they should understand.

I'd like to see the topic closed now. I thought the idea was good, but it didn't take much for me to see the opposite. That's the whole reason I brought it up to be discussed.

Closed by request of topic owner.