This might be useful if someone made a new account and wanted to transfer their projects or if someone sold their project (like scratch clearly states you can in the FAQ)
to clarify, the system i was thinking of is like the studio invite system - you get a message, you go into the studio to accept, and in the process, you can also see what type of studio it it

edit1: here's some bonus ideas for this suggestion (thanks, @da-ultimate-creater):

da-ultimate-creater wrote:

–snippity snip snip–
The person who wants to change the ownership selects a user to send the ownership to, and they have to enter their password to confirm.
Then, the receiving user receives a message saying that they can claim ownership of a project. They also get a message suggesting to see inside before they claim the ownership, to see if everything follows the guidelines. If it doesn't, they can simply report it, since the ownership hasn't transferred yet.
–snip–
The process above can help reduce spam projects sent by random people.

edit3: and this:

da-ultimate-creater wrote:

–snipping the irrelevant quote about spam–

This could be prevented by placing a max amount of projects you can send an ownership change request thingy to or an option to prevent you from receiving any new projects.

edit2: as everyone's been saying, this function should only work if the project is shared.

Semi-support. This could be really useful for collabs and stuff, but this could also be misused, like if someone changed the ownership of an inappropriate project. I suggest that there be two parts:

The person who wants to change the ownership selects a user to send the ownership to, and they have to enter their password to confirm.
Then, the receiving user receives a message saying that they can claim ownership of a project. They also get a message suggesting to see inside before they claim the ownership, to see if everything follows the guidelines. If it doesn't, they can simply report it, since the ownership hasn't transferred yet. If they want to receive the ownership, they must enter their password, too.

The process above can help reduce spam projects sent by random people.

can this be used to private message or does the project have to be shared in order to transfer ownership?

Dan0da0man wrote:

can this be used to private message or does the project have to be shared in order to transfer ownership?

I feel like it would be too slow, especially if @da-ultimate-creater changes were added

Bump?

What if you could let every manager in a studio that you choose edit the project?

tagrim123 wrote:

What if you could let every manager in a studio that you choose edit the project?

This specifically would fall under TOLORS 2.1:

TOLORS wrote:

2.1 Adding users to work on projects
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations but also because it could lead to private messaging; for more information, see #7.1 on this list. This suggestion includes live editing (similar to Google Docs) and other forms of private collaboration. If you would like to work on a project with another Scratcher, you can remix each others' projects.

At the moment, a turn-based collaboration system for shared projects is NOT rejected. You can discuss it on this topic.

To OP, how would you stop people creating a lot of innapropriate spam with this feature (similar to the spam remixes recently)?
Other than that this is a great idea (although you could probably achieve a similar outcome with the turn-based collaboration suggestion)

I support only if it’s only for shared projects (or else it will count as private sharing, which is rejected), and has the improvement of da-ultimate-creater.

AquaKelpie53 wrote:

(#7)
To OP, how would you stop people creating a lot of innapropriate spam with this feature (similar to the spam remixes recently)?

not op but: this feature is very similar to studio host transferring, although studio hosts can only be transferred to existing managers so there isn't really a possibility for message spam there.
maybe there could just not be a notification for this, and the receiving user would instead accept the transfer by going to the project's page (where an “accept transfer” button would appear). if a user wanted to notify someone else of a transfer request they could still comment on their profile.

as for this suggestion: this would also be useful for collabs too (alongside cases like the account transferring OP mentioned), and would probably be simpler to do than other built-in collaboration suggestions. i support this.

FreshTheCat wrote:

(#1)
or if someone sold their project (like scratch clearly states you can in the FAQ)

i'm fairly sure that only applies to selling .sb3 files offsite, not selling ownership of a project on the scratch website (the same way selling accounts isn't allowed).

This could be nice, but there are workarounds:

Backpacks

Remixing

Copying someone's idea/code and giving credit.

oh no! the bump bomb has exploded!

BUMP BUMP BUMP BUMP BUMP
BUMP BUMP BUMP BUMP BUMP BUMP

Neat but of course this could inevitably be used for spam by spamming someone with 1000 projects. Otherwise its a good idea, likely make you input the password of the account your sending it too?

luig64ds wrote:

Neat but of course this could inevitably be used for spam by spamming someone with 1000 projects. Otherwise its a good idea, likely make you input the password of the account your sending it too?

Yes, I've edited the post to add this!

Ba dum BUMP!
*a very low-quality audio clip of applause plays*

luig64ds wrote:

Neat but of course this could inevitably be used for spam by spamming someone with 1000 projects. Otherwise its a good idea, likely make you input the password of the account your sending it too?

This could be prevented by placing a max amount of projects you can send an ownership change request thingy to or an option to prevent you from receiving any new projects.

bump
uu
m m
p p

I like this idea because if someone is leaving scratch a collaborator or friend can take over the page, change the description or update the game if need be

My proposal for how this could work is that both accounts must be following each other, and the project must be shared
You could have a cooldown of 4-8 minutes to avoid spam
There should be no password writing involved, why is anyone suggesting this?

sandetsun wrote:

I like this idea because if someone is leaving scratch a collaborator or friend can take over the page, change the description or update the game if need be

My proposal for how this could work is that both accounts must be following each other, and the project must be shared
You could have a cooldown of 4-8 minutes to avoid spam
There should be no password writing involved, why is anyone suggesting this?

As a sort of ‘confirm that you want to actually change ownership’ or if you stayed logged in on a shared device, avoid losing your projects to some random classmate that's jealous about your popular projects and tries to send the projects to their own account

Bump