When the studio host gives up being the host and makes someone else the host, it happens automatically and no confirmation message appears on the new host's screen. This is a problem for studio hosts who accidentally make a banned/deleted/inactive user the host. So, my suggestion is that the original studio host has to wait for the new studio host to accept before being the new studio host. So, how this would work is that the new studio host would get a pop-up in the curators tab saying:

You've been chosen to become the studio host! Accept Decline

When the new studio host clicks “Accept”, they will become the new studio host.
When they click “Decline”, the message disappears and their rank doesn't change.
Pros:
Helps with studios who could accidentally made an inactive Scratcher the host
Cons:
Takes longer for the host transferring to finish
So, what do you think?

I was thinking about this too, this would make it harder for someone to have a studio handed over to them without them knowing. I can imagine a sticky topic being suddenly migrated to another account without warning.

Yeah

Support, some people may not want to be made the ‘host’ of a studio, they should be able to decline the responsibility if they want.

Support, if I don't want to get into a studio, I need to ignore the invitation. What if I don't want to become the host?

I agree with this, I think the owner is responsible if the studio has something rude in there (I think, not 100% sure), so someone can just create a studio, invite people in there, change the description to something horrible, and then give the studio to a poor manager before reporting it.

Also, I think the same thing should go for promoting someone

What would happen if the following sequence of steps occur?

• I try to make you the host of my studio.
  
  
• You don't want to be the host, so you don't accept the request.
  
  
• I find someone else to be the host of my studio, and they accept the request.
  
  
• Now you suddenly decide to accept the request, effectively taking ownership from the user who wanted to be the host.
  

Should there be a system that prevents this from happening?

I was thinking you should receive it in your messages when the older host wants to transfer to you, not a pop-up (unless you're referring to messages)

Feel free to add it to the OP, but at least credit me in it.

For the suggestion itself, I can see how this can be useful. Now they don't have to realize they changed into a host manually. But transfers do take a while too, especially if the user themselves isn't very active.

Za-Chary wrote:

What would happen if the following sequence of steps occur?

• I try to make you the host of my studio.
  
  
• You don't want to be the host, so you don't accept the request.
  
  
• I find someone else to be the host of my studio, and they accept the request.
  
  
• Now you suddenly decide to accept the request, effectively taking ownership from the user who wanted to be the host.
  

Should there be a system that prevents this from happening?

As a suggestion to the suggestion, I think the pop-up/message would be deleted.

Za-Chary wrote:

What would happen if the following sequence of steps occur?

• I try to make you the host of my studio.
  
  
• You don't want to be the host, so you don't accept the request.
  
  
• I find someone else to be the host of my studio, and they accept the request.
  
  
• Now you suddenly decide to accept the request, effectively taking ownership from the user who wanted to be the host.
  

Should there be a system that prevents this from happening?

The request no longer appears when you decline it.

bump

AlfabetonsOfficial wrote:

The request no longer appears when you decline it.

But “not accepting” a request is not quite the same as “declining” it. “Declining” seems to imply that you click a button saying that you don't want to be the host. “Not accepting” is not clicking the accept or decline buttons.

I think @mrcreatorluigi above had a good idea about having the pop-up disappear, presumably when a second request is sent.

then what if it assumes that “ not accepting it” for 3 days = decline and you cant promote someone else until the first person accepts/decline(or auto decline) it

dave-alt-4 wrote:

then what if it assumes that “ not accepting it” for 3 days = decline and you cant promote someone else until the first person accepts/decline(or auto decline) it

YKW? I'll update the OP to add a decline button. That way, nobody gets confused.

How about this: You can only send one host request every day.

Also idea: The studio activity will display if the host request has been declined.

Support! I can't believe this isn't in scratch already! (also is it like going from creator to manger bc i've never used the studio host feature b4)

Za-Chary wrote:

What would happen if the following sequence of steps occur?

• I try to make you the host of my studio.
  
  
• You don't want to be the host, so you don't accept the request.
  
  
• I find someone else to be the host of my studio, and they accept the request.
  
  
• Now you suddenly decide to accept the request, effectively taking ownership from the user who wanted to be the host.
  

Should there be a system that prevents this from happening?

a message appears, saying “Oops! Only one scratcher can become host! Do you want to cancel making OwOmasterlunarae host?” if yes is clicked it sends something to the person saying “Request canceled” in place of accept and decline, and an (X) appears.

OwOmasterlunarae wrote:

Za-Chary wrote:

What would happen if the following sequence of steps occur?

• I try to make you the host of my studio.
  
  
• You don't want to be the host, so you don't accept the request.
  
  
• I find someone else to be the host of my studio, and they accept the request.
  
  
• Now you suddenly decide to accept the request, effectively taking ownership from the user who wanted to be the host.
  

Should there be a system that prevents this from happening?

a message appears, saying “Oops! Only one scratcher can become host! Do you want to cancel making OwOmasterlunarae host?” if yes is clicked it sends something to the person saying “Request canceled” in place of accept and decline, and an (X) appears.

Nope. The message disappears for the person who got it when you don't respond in time and someone else is the host.

Better system: “First come, first served.” The first person to accept a studio invite to become the host, will be the host, and anyone else who tries to click the link will not be acceptedeth. Perhaps there should be a limit on how many people thou can attempteth to transfer ownershipe to… And perhaps there will be a timeout, if the user does not respond?

mrcreatorluigi wrote:

I was thinking you should receive it in your messages when the older host wants to transfer to you, not a pop-up (unless you're referring to messages)

Feel free to add it to the OP, but at least credit me in it.

For the suggestion itself, I can see how this can be useful. Now they don't have to realize they changed into a host manually. But transfers do take a while too, especially if the user themselves isn't very active.

Za-Chary wrote:

What would happen if the following sequence of steps occur?

• I try to make you the host of my studio.
  
  
• You don't want to be the host, so you don't accept the request.
  
  
• I find someone else to be the host of my studio, and they accept the request.
  
  
• Now you suddenly decide to accept the request, effectively taking ownership from the user who wanted to be the host.
  

Should there be a system that prevents this from happening?

As a suggestion to the suggestion, I think the pop-up/message would be deleted.

Hmm, maybe it should be like the alerts from the scratch team with the X to close.

ScolderCreations wrote:

Better system: “First come, first served.” The first person to accept a studio invite to become the host, will be the host, and anyone else who tries to click the link will not be acceptedeth. Perhaps there should be a limit on how many people thou can attempteth to transfer ownershipe to… And perhaps there will be a timeout, if the user does not respond?

could lead to something like

original host : hi A , I'll make you host
A ; ok
original host :*transfers A*
*A was on vacation*
*2 days later*
original host : maybe he doesn't want to be host *transfer B to host*
B :immediately accepts
*like almost immediately after that*
A : hey , original host , you promised to give me host I'm gonna report u for tricking the community