Bumped

oh for nuclear warheads sake,WHY DOES EVERYONE KEEPS SAYING “ItS PRoJEcts!1!!” reallysoftuser already talked about it!
anyways,support as it can help with the situation of my backpack(filled and hard to use.)

I wasn't really all into it, until I saw the mockups. This is a great way to express creativity to other people. Full support.

Still needs to be added, and maybe singular assets too like a single sprite/code piece.
Especially since you would need like too many different projects for tutorials, or code sharing.

Please can you explain more, I am confused, until that time I won't Support or No Support

Scratch On!

VedanshS933 wrote:

Please can you explain more, I am confused, until that time I won't Support or No Support

Scratch On!

What do you need explanation on?

bumped

You know what? I'm surprised I haven't said this yet on this suggestion, but 100% support. I can see how useful this could would be.

Imagine if someone wanted to make a platformer, but they weren't professional at it.
Well, this is where Backpacks would come in handy.
They could search up “Platformer sprites/scripts/sounds” in Backpacks, and the corresponding Backpacks would appear.

Bumped.

Honestly, I think this is creepy, just for privacy's sake. First, I use the backpack to move assets across my personal projects. Assets that are not shared on the Scratch website are not under Scratch's Creative Commons license. Wouldn't this mean that anything I backpack would automatically be under that license, whether I shared it or not? Then, if I did not want to put something private in my backpack, I would have to download it, and that's inconvenient. The backpack is the only way to transport individual scripts. This would defeat the whole purpose of the backpack. Also, it would be too easy for someone to steal something with no proof that they didn't make it, since it could very well come from something unshared. In addition, it would be impossible to credit someone if their name wasn't attached to whatever was in the backpack. Scenario: Someone backpacks a script. Another person sees this script in the backpack and uses it in his own project. How will he know who to give credit to? It's untraceable. Long story short, if this suggestion was implemented, I would never use the backpack again. How would I move individual scripts?

TheAnimalKingdom42 wrote:

Honestly, I think this is creepy, just for privacy's sake. First, I use the backpack to move assets across my personal projects. Assets that are not shared on the Scratch website are not under Scratch's Creative Commons license. Wouldn't this mean that anything I backpack would automatically be under that license, whether I shared it or not? Then, if I did not want to put something private in my backpack, I would have to download it, and that's inconvenient. The backpack is the only way to transport individual scripts. This would defeat the whole purpose of the backpack. Also, it would be too easy for someone to steal something with no proof that they didn't make it, since it could very well come from something unshared. In addition, it would be impossible to credit someone if their name wasn't attached to whatever was in the backpack. Scenario: Someone backpacks a script. Another person sees this script in the backpack and uses it in his own project. How will he know who to give credit to? It's untraceable. Long story short, if this suggestion was implemented, I would never use the backpack again. How would I move individual scripts?

To counteract this, the solution would be to make the default backpack “My Backpack” private, but any of the backpacks you make after this one public (unless unshared).

reallysoftuser wrote:

2GS6 wrote:

This solution is hood but I have to agree with GoboThePlant. It could end in unmoderated messaging

No you cant change whats in a public backpack, only the person who made it can

Take a kit someone else published, put a message in it, then someone else takes it, adds a message, then it repeats

Gamer_Logan819 wrote:

reallysoftuser wrote:

2GS6 wrote:

This solution is hood but I have to agree with GoboThePlant. It could end in unmoderated messaging

No you cant change whats in a public backpack, only the person who made it can

Take a kit someone else published, put a message in it, then someone else takes it, adds a message, then it repeats

Public backpacks would just be moderated the same way as projects, so this couldn't possibly be an issue. You could do this same thing with projects.

reallysoftuser wrote:

TheAnimalKingdom42 wrote:

Snip

To counteract this, the solution would be to make the default backpack “My Backpack” private, but any of the backpacks you make after this one public (unless unshared).

Okay, then I've no objection to this, although it could easily be used to create spam. This is a good idea.

TheAnimalKingdom42 wrote:

reallysoftuser wrote:

TheAnimalKingdom42 wrote:

Snip

To counteract this, the solution would be to make the default backpack “My Backpack” private, but any of the backpacks you make after this one public (unless unshared).

Okay, then I've no objection to this, although it could easily be used to create spam. This is a good idea.

maybe it would stop you from making new backpacks if you make a lot in a small ammount of time

Kinda reminds me of GitHub Gists. Instead of making a new repository for a just a snippet of code, you could just create a gist. Ful support.

Support! This would be really great! I think that if someone uses the assets of someone's backpack, it would automatically show credit.

bumped

Bumped