Make remixed projects not shareable until the user makes a change

scratchfoundation / scratch-www

Standalone web client for Scratch

https://scratch.mit.edu

BSD 3-Clause "New" or "Revised" License

1.6k stars 847 forks source link

Make remixed projects not shareable until the user makes a change #2130

Closed kyleplo closed 6 years ago

kyleplo commented 6 years ago

I think that you shouldn't be allowed to share remixes until you make a change. This would be useful because many users just remix projects as spam, or to pretend the project is their own, and not make any changes to it. Some other users are so desperate to get this feature that they invent their own "remix detectors" (and some do work, not sure how). Also, projects should take the parent project's comment enabled/disabled status. My parents at first didn't want comments enabled, but if someone remixed (without changing a thing) and then commented on the remix, it would still basically be a comment for me, when I disabled comments.

Steps to Reproduce

N/A

Operating System and Browser

All

benjiwheeler commented 6 years ago

I like this idea. It might be a bit tricky to implement, but possible.

apple502j commented 6 years ago

No Support, there are two allowed case:

The author might use remix to transfer the projects to their test accounts.
Some people might use remix to translate strings inside Notes. (like SDS)

benjiwheeler commented 6 years ago

Thanks for the counter-examples. Not sure if this change makes sense or not. I will bring it up for long-term discussion. For now, I'm going to close it as something that we do not have plans to implement, but we'll revisit it after 3.0 launch.

apple502j commented 5 years ago

@benjiwheeler After one year are you going to revisit it?

benjiwheeler commented 5 years ago

@apple502j Thanks for the reminder. I'll bring this up with the team. Do you have thoughts on whether it makes sense to do or not, on balance? Seems like it might help in most cases, but might be very annoying in some cases.