A few days ago, I wanted to make a Scratch program to model contagious diffusion (If you don't know what that is, look it up.) I planned to make a project where I would leave the following message in the profile of each of my followers that said,

Iff (if and only if) you are receiving this message, go to https://scratch.mit.edu/projects/137194132/ and follow the instructions there. You do not need to do any of the instructions that you have already done if you have already received this message.

However, as well as needing cloud lists in order for the project to work, some blocks that I needed to prevent trolling weren't there. These include

<[] follows []>

,

<[] is a username>

,

(list of all Scratch usernames :: list)

,

(list of all Scratch accounts that [] follows :: list)

, and

(list of all Scratch accounts that follow [] :: list)

This post is done now, and please look at the project and click “See Inside” to see exactly what I want to do.

About the

(list of all Scratch usernames :: list)

block… I feel like that would cause a bit of lag, no?

Also, I'm removing the red from the first to blocks for you.

[] follows [] :: sensing boolean

[] is a Username :: sensing boolean

Hope this helps in some way. Also, um…
No support for the first one, would cause too much lag.
No support for the bottom one, as someone could be following a thousand people and would cause too much lag.
Support for the others, though, as there doesn't seem to be a problem with them. However, if you make a project that can only be accessed by your followers, I don't think that would be good.

when gf clicked
if <not <(username) follows [Sigton] :: sensing>> then
say [you must follow me to play the project!]

That's a pretty big problem…

Sigton

Sigton wrote:

when gf clicked
if <not <(username) follows [Sigton] :: sensing>> then
say [you must follow me to play the project!]

That's a pretty big problem…

Sigton

It sounds as if the whole point of this block, even as stated by the OP, is to exclude features from non-followers, even if in the OP's case it is a sort of social experiment (I looked up contagious diffusion and I still didn't really understand how it relates to the project). For that reason, no support.

Sigton wrote:

when gf clicked
if <not <(username) follows [Sigton] :: sensing>> then
say [you must follow me to play the project!]

That's a pretty big problem…

Sigton

This. You could see inside and remove the script, but good luck manipulating cloud.
This could happen, too:

when green flag clicked
if <(username) follows [alexphan] :: sensing> then
say [Why are you following alexphan he sucks please unfollow him
end

Fortunately, it is possible to get a list of your followers. Just go to griffpatch's 20,000+ followers project and copy-paste the HTML code in the editor

stickfiregames wrote:

Sigton wrote:

when gf clicked
if <not <(username) follows [Sigton] :: sensing>> then
say [you must follow me to play the project!]

That's a pretty big problem…

Sigton

It sounds as if the whole point of this block, even as stated by the OP, is to exclude features from non-followers, even if in the OP's case it is a sort of social experiment (I looked up contagious diffusion and I still didn't really understand how it relates to the project). For that reason, no support.

Agreed. Technically, that can be used to block people from a project and that could cause trouble on the website. I see where the creator of the OP is going with this, but for the reason I stated, sorry, but I am not supporting this.

This would be cool, regarding contagious diffusion, but as mentioned above, it cold be abused in lots of ways. So no support.

Also, I don't think you need the iff. Someone could still visit that project via yor profile and not the one you're working on… unless it were unshared on phosphorus.

Support for all blocks except for the third. It seems quite laggy, considering Scratch has over 15 million users, and doesn't seem to have a good use. But the others seem helpful.

Sigton wrote:

when gf clicked
if <not <(username) follows [Sigton] :: sensing>> then
say [you must follow me to play the project!]

That's a pretty big problem…

Sigton

You can already do this by creating a list and manually updating it whenever someone follows you.

when green flag clicked
delete (all v) of [The4thPixel's Followers v]
add [FollowerName] to [The4thPixel's Followers v]
add [FollowerName] to [The4thPixel's Followers v]
add [FollowerName] to [The4thPixel's Followers v]
add [FollowerName] to [The4thPixel's Followers v]
when green flag clicked
if <not <[The4thPixel's Followers v] contains (username) ?>> then
say [Sorry, you need to be following The4thPixel to play this project.]
end

Things like that and what you mentioned shouldn't be allowed. I hate the idea of something not being implimented just because it can be abused.

The4thPixel wrote:

Things like that and what you mentioned shouldn't be allowed. I hate the idea of something not being implimented just because it can be abused.

I can't think of any way to use the < follows > block without involving some form of allowance to some and not to others. Some features can be abused, though they have other features that make up for it. This just doesn't appear to.

Sigton

The list blocks that list the followers…and the one that lists all the usernames on Scratch… there are so many people on Scratch, that Scratch would probably freeze with those. If you were saying it, the speechbubble would be bigger than the page. Sorry but I think 1/10 support.

ZZ9PluralZAlpha wrote:

stickfiregames wrote:

Sigton wrote:

when gf clicked
if <not <(username) follows [Sigton] :: sensing>> then
say [you must follow me to play the project!]

That's a pretty big problem…

Sigton

It sounds as if the whole point of this block, even as stated by the OP, is to exclude features from non-followers, even if in the OP's case it is a sort of social experiment (I looked up contagious diffusion and I still didn't really understand how it relates to the project). For that reason, no support.

Agreed. Technically, that can be used to block people from a project and that could cause trouble on the website. I see where the creator of the OP is going with this, but for the reason I stated, sorry, but I am not supporting this.

Obviously, projects that abused it would be reported, and the Scratch Team would take appropriate action.

redglitter wrote:

The list blocks that list the followers…and the one that lists all the usernames on Scratch… there are so many people on Scratch, that Scratch would probably freeze with those. If you were saying it, the speechbubble would be bigger than the page. Sorry but I think 1/10 support.

It would more be used for things like

(item (random v) of [list of all Scratch accounts v] :: list)

or

(length of [list of all Scratch accounts v] :: list)//total number of Scratch accounts

, not what you mentioned, and there might be a feature to stop that script to prevent lagging, or prevent something like

say (list of all Scratch accounts :: list)

from ever being used in the first place by only making it accessible in

(item ( v) of [list v] :: list)

and

(length of [ v] :: list)

.

dvargasews wrote:

ZZ9PluralZAlpha wrote:

stickfiregames wrote:

Sigton wrote:

when gf clicked
if <not <(username) follows [Sigton] :: sensing>> then
say [you must follow me to play the project!]

That's a pretty big problem…

Sigton

It sounds as if the whole point of this block, even as stated by the OP, is to exclude features from non-followers, even if in the OP's case it is a sort of social experiment (I looked up contagious diffusion and I still didn't really understand how it relates to the project). For that reason, no support.

Agreed. Technically, that can be used to block people from a project and that could cause trouble on the website. I see where the creator of the OP is going with this, but for the reason I stated, sorry, but I am not supporting this.

Obviously, projects that abused it would be reported, and the Scratch Team would take appropriate action.

Also, people could just use, “See Inside.”

Lataliat wrote:

1. This would be cool, regarding contagious diffusion, but as mentioned above, it cold be abused in lots of ways. So no support.

2. Also, I don't think you need the iff.
3, Someone could still visit that project via yor profile and not the one you're working on… unless it were unshared on phosphorus.

I numbered it for you so you'd know what each of my responses was a response to.
2. I don't want trolling or lying on the project.
3. But then the person wouldn't have the message.
3. I shared the project so people who want to respond to this could look inside to see how the coding worked and understand what I wanted.
1. Projects that abused this feature would be reportable.

But for the blocks to be memory efficient they would need to make a request. What would you want this to do

when green flag clicked
reset timer
if <[jokebookservice1] follows [jokebookservice1]>
end
say (timer)

This will cause an internet request to check if I am following myself, (which I am), and as such will make it say something like “5”. Just wanted to raise this.

It's fine with Cloud Data because it stores a local copy of the variable, as well as sending this local copy to the cloud. Cloud also loads before the project has finished loading.

However, dynamic request like that might be a bit harder.

dvargasews wrote:

(list of all Scratch usernames :: list)

How many people use Scratch now; 15 million?
To generate a list of 15 million items it would take a long while, and to retrieve data it would also take ages. To use this block there would be huge performance implications.

Sigton

Sigton wrote:

dvargasews wrote:

(list of all Scratch usernames :: list)

How many people use Scratch now; 15 million?
To generate a list of 15 million items it would take a long while, and to retrieve data it would also take ages. To use this block there would be huge performance implications.

Sigton

Please read my earlier comment.

dvargasews wrote:

redglitter wrote:

The list blocks that list the followers…and the one that lists all the usernames on Scratch… there are so many people on Scratch, that Scratch would probably freeze with those. If you were saying it, the speechbubble would be bigger than the page. Sorry but I think 1/10 support.

It would more be used for things like

(item (random v) of [list of all Scratch accounts v] :: list)

or

(length of [list of all Scratch accounts v] :: list)//total number of Scratch accounts

, not what you mentioned, and there might be a feature to stop that script to prevent lagging, or prevent something like

say (list of all Scratch accounts :: list)

from ever being used in the first place by only making it accessible in

(item ( v) of [list v] :: list)

and

(length of [ v] :: list)

.

Would

 (Random Scratch Username)

be useful?

redglitter wrote:

Would

 (Random Scratch Username)

be useful?

You could just use

(item (random v) of [list of all Scratch usernames v] :: list)

.

No support. The only good use I could think of for this is targeted advertising in the project outro.