jromagnoli wrote:

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

jromagnoli wrote:

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

dvargasews wrote:

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

The4thPixel wrote:

jromagnoli wrote:

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

dvargasews wrote:

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

This example is quoted from the original post. Please read the whole post before adding your reply. Thanks!

[] follows [] :: sensing boolean

[] is a Username :: sensing boolean

EDO2012 wrote:

no support

[] follows [] :: sensing boolean

[] is a Username :: sensing boolean

This doesn't seem to really have much of a useful purpose.

when green flag clicked 
if <[(username)] follows [VideoGamerCanInvent]> then 
broadcast [start game]
else
say [Sorry, but game cannot be accessed unless you follow VGCI. Go follow him today!]

VideoGamerCanInvent wrote:

This is a nice idea, but it will be used for the wrong reasons if it is added.

For example…

when green flag clicked 
if <[(username)] follows [VideoGamerCanInvent]> then 
broadcast [start game]
else
say [Sorry, but game cannot be accessed unless you follow VGCI. Go follow him today!]

I know this is probably not what you want to use them for but this is how some Scratchers would use them.

No Support

dvargasews wrote:

jromagnoli wrote:

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

I gave an example in the original post.

if <(username) follows [jromagnoli]?> then
switch costume to [love, fave, remix v]
else
switch costume to [follow, love fave v]
end :: cend

_Elektron_ wrote:

Semi supporr it would be useful but would cause a lot of lag

dvargasews wrote:

_Elektron_ wrote:

Semi supporr it would be useful but would cause a lot of lag

Specifically, which block would cause the lag?

WolfCat67 wrote:

dvargasews wrote:

_Elektron_ wrote:

Semi supporr it would be useful but would cause a lot of lag

Specifically, which block would cause the lag?

Probably the list of all Scratch usernames… That one would be a computer killer, I bet.

jromagnoli wrote:

WolfCat67 wrote:

dvargasews wrote:

_Elektron_ wrote:

Semi supporr it would be useful but would cause a lot of lag

Specifically, which block would cause the lag?

Probably the list of all Scratch usernames… That one would be a computer killer, I bet.

I think it would be too long. That's over 15 million users. Isn't the list limit like 10 million?

dvargasews wrote:

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

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)

.

Please read my earlier comment.

(https://[]  ::operators reporter)

(user ID)

(id of account []::sensing)
(name of account id()::sensing)
("About me" of account id()::sensing)
("What I'm working on" of account id()::sensing)
(Featured Project of account id()::sensing)
<account id() [exists v]::sensing> // exists, is a New Scratcher, is a Scratcher
(how many accounts that [exist v] are there::sensing) // exist, are New Scratchere, are Scratchers

when green flag clicked
if <(username) follows [NAME OF PROJECT CREATOR]::sensing> then 
broadcast [start v]
else
say [follow me to play]
end

TOLORS wrote:

1.5 Social action reporter blocks
This block could be used to obtain the current number of loves, favorites, or views of the project. Similar blocks could return the number of loves or followers that the user or creator has. But, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves, favorites, and the like. These blocks could also make people think that getting these social actions are important, or that Scratch is about fame. In reality, if a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.

Byron_Inc wrote:

No support.
1. This can lead to PMing.
2. People can make hate when they found that the user isn't following Scratcher XXX.
3. This will clog up the data, as it's a lot info.

Col_Cat228 wrote:

This could be abused in a thousand ways

when green flag clicked
if <(username) follows [NAME OF PROJECT CREATOR]::sensing> then 
broadcast [start v]
else
say [follow me to play]
end

And its way too similar to Social Action blocks, which is rejected.

TOLORS wrote:

1.5 Social action reporter blocks
This block could be used to obtain the current number of loves, favorites, or views of the project. Similar blocks could return the number of loves or followers that the user or creator has. But, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves, favorites, and the like. These blocks could also make people think that getting these social actions are important, or that Scratch is about fame. In reality, if a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.

<[] is following []?::sensing>

TOLORS wrote:

1.5 Social action reporter blocks
This block could be used to obtain the current number of loves, favorites, or views of the project. Similar blocks could return the number of loves or followers that the user or creator has. But, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves, favorites, and the like. These blocks could also make people think that getting these social actions are important, or that Scratch is about fame. In reality, if a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.

<[] is an existing username?::sensing>

(all existing usernames::sensing)

(all people [] following::sensing)

TOLORS wrote:

1.5 Social action reporter blocks
This block could be used to obtain the current number of loves, favorites, or views of the project. Similar blocks could return the number of loves or followers that the user or creator has. But, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves, favorites, and the like. These blocks could also make people think that getting these social actions are important, or that Scratch is about fame. In reality, if a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.

(all people following []::sensing)

TOLORS wrote:

1.5 Social action reporter blocks
This block could be used to obtain the current number of loves, favorites, or views of the project. Similar blocks could return the number of loves or followers that the user or creator has. But, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves, favorites, and the like. These blocks could also make people think that getting these social actions are important, or that Scratch is about fame. In reality, if a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.