ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

when green flag clicked
forever
send me a message: [ChocolatePi is now following you.] :: extension
end

but what if I"m not actually following you? oohh…

My point: You could use this to forge real messages, such as alerts.

It is only sent to the project creator so that would be pointless.

when green flag clicked
ask [What would you like to send?] and wait
send me a message: (answer) :: extension

And it would be sent as “Untitled-5 sent you a message: ‘this is what I want to send’”

i see.

but what if the answer was “(*#&@($*&#(@^&$*&#*@$^”?

Good point.

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

when green flag clicked
forever
send me a message: [ChocolatePi is now following you.] :: extension
end

but what if I"m not actually following you? oohh…

My point: You could use this to forge real messages, such as alerts.

It is only sent to the project creator so that would be pointless.

when green flag clicked
ask [What would you like to send?] and wait
send me a message: (answer) :: extension

And it would be sent as “Untitled-5 sent you a message: ‘this is what I want to send’”

i see.

but what if the answer was “(*#&@($*&#(@^&$*&#*@$^”?

Good point.

like “THIS GAME IS HORRIBLE YOU HAVE NO LIFE GET A LIFE GO HOME THIS GAME IS (*@#&(*&ING HORRIBLE”

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

when green flag clicked
forever
send me a message: [ChocolatePi is now following you.] :: extension
end

but what if I"m not actually following you? oohh…

My point: You could use this to forge real messages, such as alerts.

It is only sent to the project creator so that would be pointless.

when green flag clicked
ask [What would you like to send?] and wait
send me a message: (answer) :: extension

And it would be sent as “Untitled-5 sent you a message: ‘this is what I want to send’”

i see.

but what if the answer was “(*#&@($*&#(@^&$*&#*@$^”?

Good point.

like “THIS GAME IS HORRIBLE YOU HAVE NO LIFE GET A LIFE GO HOME THIS GAME IS (*@#&(*&ING HORRIBLE”

Hmm… two people could create this same project and then private message between each other. To fix that, any project that uses this as a private messaging system (instead of a notification system) would not be allowed and could be reported and then would be removed. Also, each message should have a report button if even though you used it as a notification system someone typed a bad message that got sent to you. The system would keep a log of users so the ST could see the username.

OmnipotentPotato wrote:

savaka wrote:

djdolphin wrote:

when green flag clicked
forever
send me a message: [I'm wastin' server space.] :: extension
end

Duplicate messages in 1 minute ignored maybe?

when green flag clicked
forever
send me a message: (i) :: extension
change (i) by [1]
end

Why would anyone want to waste server space anyway?

savaka wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

when green flag clicked
forever
send me a message: [ChocolatePi is now following you.] :: extension
end

but what if I"m not actually following you? oohh…

My point: You could use this to forge real messages, such as alerts.

It is only sent to the project creator so that would be pointless.

when green flag clicked
ask [What would you like to send?] and wait
send me a message: (answer) :: extension

And it would be sent as “Untitled-5 sent you a message: ‘this is what I want to send’”

i see.

but what if the answer was “(*#&@($*&#(@^&$*&#*@$^”?

Good point.

like “THIS GAME IS HORRIBLE YOU HAVE NO LIFE GET A LIFE GO HOME THIS GAME IS (*@#&(*&ING HORRIBLE”

Hmm… two people could create this same project and then private message between each other. To fix that, any project that uses this as a private messaging system (instead of a notification system) would not be allowed and could be reported and then would be removed. Also, each message should have a report button if even though you used it as a notification system someone typed a bad message that got sent to you. The system would keep a log of users so the ST could see the username.

OmnipotentPotato wrote:

savaka wrote:

djdolphin wrote:

when green flag clicked
forever
send me a message: [I'm wastin' server space.] :: extension
end

Duplicate messages in 1 minute ignored maybe?

when green flag clicked
forever
send me a message: (i) :: extension
change (i) by [1]
end

Why would anyone want to waste server space anyway?

Your solution is way too complicated. And how would this even be useful?

savaka wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

OmnipotentPotato wrote:

ChocolatePi wrote:

when green flag clicked
forever
send me a message: [ChocolatePi is now following you.] :: extension
end

but what if I"m not actually following you? oohh…

My point: You could use this to forge real messages, such as alerts.

It is only sent to the project creator so that would be pointless.

when green flag clicked
ask [What would you like to send?] and wait
send me a message: (answer) :: extension

And it would be sent as “Untitled-5 sent you a message: ‘this is what I want to send’”

i see.

but what if the answer was “(*#&@($*&#(@^&$*&#*@$^”?

Good point.

like “THIS GAME IS HORRIBLE YOU HAVE NO LIFE GET A LIFE GO HOME THIS GAME IS (*@#&(*&ING HORRIBLE”

Hmm… two people could create this same project and then private message between each other. To fix that, any project that uses this as a private messaging system (instead of a notification system) would not be allowed and could be reported and then would be removed. Also, each message should have a report button if even though you used it as a notification system someone typed a bad message that got sent to you. The system would keep a log of users so the ST could see the username.

OmnipotentPotato wrote:

savaka wrote:

djdolphin wrote:

when green flag clicked
forever
send me a message: [I'm wastin' server space.] :: extension
end

Duplicate messages in 1 minute ignored maybe?

when green flag clicked
forever
send me a message: (i) :: extension
change (i) by [1]
end

Why would anyone want to waste server space anyway?

Some people just like to watch the world burn.

No support. It would cause more harm than good.
For the purposes described here, you could simply make a list, and add to the list instead of sending a message.

Cyoce wrote:

No support. It would cause more harm than good.
For the purposes described here, you could simply make a list, and add to the list instead of sending a message.

A cloud list, which doesn't exist yet. And it wouldn't notify you.

savaka wrote:

Cyoce wrote:

No support. It would cause more harm than good.
For the purposes described here, you could simply make a list, and add to the list instead of sending a message.

A cloud list, which doesn't exist yet. And it wouldn't notify you.

Yes, but it wouldn't be worth the trouble. It would require a mound of work by the ST, and what are you going to use it for, anyway? People could just comment if they want to give feedback. It's just overall not helpful and could spam easily, creating tons of more moderation for people like Cheddargirl. not to mention you could also send threatening messages…

No support

savaka wrote:

djdolphin wrote:

when green flag clicked
forever
send me a message: [I'm wastin' server space.] :: extension
end

Duplicate messages in 1 minute ignored maybe?

when green flag clicked
forever
send me a message:(x) :: extension
change [x v] by (0.1)
end

ChocolatePi wrote:

savaka wrote:

Cyoce wrote:

No support. It would cause more harm than good.
For the purposes described here, you could simply make a list, and add to the list instead of sending a message.

A cloud list, which doesn't exist yet. And it wouldn't notify you.

Yes, but it wouldn't be worth the trouble. It would require a mound of work by the ST, and what are you going to use it for, anyway? People could just comment if they want to give feedback. It's just overall not helpful and could spam easily, creating tons of more moderation for people like Cheddargirl. not to mention you could also send threatening messages…

It sends it to yourself, and a project where the user can type a message to send would not be allowed. (similarly to how chat rooms are not allowed)

ChocolatePi wrote:

not to mention you could also send threatening messages…

I hadn’t even thought of that.

change [support v] by (-1)

I think this is a good idea.

For the wasting server space point: Well, it's possible to write a bot to constantly upload giant projects to Scratch, but nobody cares about that, huh?

And what about cloud variables? Although they have their limits, it still is possible to waste server space with them.

So, in order to prevent “waste of server space”:
1) User has to be Scratcher rank to use block
2) Can only send any message every minute

And people are saying “oh, you can send threats” and “oh, people will be mean” - it only sends what the creator of the project programs it to send to the creator of the program.
It would be disabled as soon as you clicked “see inside”.

And projects which allowed people to type custom messages to the creator would be taken down.

+1.

I support on two conditions:
1. any changes to the project by anyone other than the creator instantly disables the messaging system.
2. all messages must be confirmed by the user before being sent to the creator, simply by signing your name (username, that is)

Zro716 wrote:

I support on two conditions:
1. any changes to the project by anyone other than the creator instantly disables the messaging system.
2. all messages must be confirmed by the user before being sent to the creator, simply by signing your name (username, that is)

1. How can anyone other than the creator change the project in the first place?
2. Why not just “Would you like to send message <message>? (Y/N)”

Cyoce wrote:

Zro716 wrote:

I support on two conditions:
1. any changes to the project by anyone other than the creator instantly disables the messaging system.
2. all messages must be confirmed by the user before being sent to the creator, simply by signing your name (username, that is)

1. How can anyone other than the creator change the project in the first place?
2. Why not just “Would you like to send message <message>? (Y/N)”

1. like how cloud variables won't update if you change the code. once you remix the project unlocks however.
2. that could work too

Zro716 wrote:

I support on two conditions:
1. any changes to the project by anyone other than the creator instantly disables the messaging system.
2. all messages must be confirmed by the user before being sent to the creator, simply by signing your name (username, that is)

1. I actually said that
2. Or just a username-block-like alert

AonymousGuy wrote:

I think this is a good idea.

For the wasting server space point: Well, it's possible to write a bot to constantly upload giant projects to Scratch, but nobody cares about that, huh?

And what about cloud variables? Although they have their limits, it still is possible to waste server space with them.

So, in order to prevent “waste of server space”:
1) User has to be Scratcher rank to use block
2) Can only send any message every minute

And people are saying “oh, you can send threats” and “oh, people will be mean” - it only sends what the creator of the project programs it to send to the creator of the program.
It would be disabled as soon as you clicked “see inside”.

And projects which allowed people to type custom messages to the creator would be taken down.

+1.

Agree with your 2 things.
And here is a new block:

<last message successful? :: extension>

To do this:

when this sprite clicked
if <(costume #) = [1]> then
    send me a message: (data) :: extension
    if <last message successful? :: extension> then
        switch costume to [data sent v]
    else
        say [Data not sent! Try again in 1 minute] for (3) secs
    end
end

(I ended up necro-bumping this because there was a duplicate of this suggestion)

I have some ideas to change the suggestion and make it harder to private message:

• You can only place the block once in each project.
  
• You can't insert reporter blocks, only typing into the text box is allowed.
  
• The block won't activate if another user clicks the “See inside” button.
  

This could be used for private messaging.
For example:

ask [Send me a message!] and wait
notify creator (answer)::control

D-ScratchNinja wrote:

You can only place the block once in each project.

In that case, I doubt many people would find this useful, as they would not be able to use it for much.

You can't insert reporter blocks, only typing into the text box is allowed.

How would this work?

The block won't activate if another user clicks the “See inside” button.

I do not think that would be very helpful.

That said, it might be okay if there were a dropdown list, like this:

notify creator [someone viewed your project v]::control

I do not know what else would be in the list.

My response to nerdiebirdy's post:

nerdiebirdy wrote:

D-ScratchNinja wrote:

You can only place the block once in each project.

In that case, I doubt many people would find this useful, as they would not be able to use it for much.

I agree with you for certain projects, but it does solve a problem where users could add one block for every letter, number, and symbol, potentially making it easier to private message.

You can't insert reporter blocks, only typing into the text box is allowed.

How would this work?

notify creator (variable) ::control //This would not be allowed,

notify creator [message] ::control //But this would.

The block won't activate if another user clicks the “See inside” button.

I do not think that would be very helpful.

This is like Cloud Variables, and it would prevent users from activating it manually. Otherwise, they could type out something and send the creator a private message that way. Maybe I can word it a different way: users cannot activate it after seeing inside the project.

D-ScratchNinja wrote:

• You can only place the block once in each project.
  
• You can't insert reporter blocks, only typing into the text box is allowed.
  

These two things make it almost useless.