Oftentimes, users wish to move accounts for a fresh start, to join the aesthetic community, or other. Some of these users have many followers already that they do not wish to lose. Therefore, they visit profiles or studios, and say something like this:

“Hi, can you notify my followers (on @____) that I've moved to @______? Thank you”

This often works, but it is exhausting for the people that want to help, but have to visit hundreds or even thousands of profiles. Even if the job is split between many people, there are still a lot of profiles to visit and comments to edit to avoid setting off the spam filter.

Notifying users about this would avoid the strain of doing this.



1. The message will always show up at the top.
Some people receive lots of notifications, and, as a result, ignore some. The message showing up at the top would be very convenient as that is the first thing people see.

2. The message initially shows up the day the new account is created.
This decides when the message appears.

3. Re-showing up

If the new account is

a) not followed after 3 days
b) not clicked after 3 days

another message will appear.



Please view https://scratch-mit-edu.ezproxyberklee.flo.org/projects/1022968591/ to see my mockups. Thank you!



I know that Scratch isn't about popularity.

But for some people, their followers and their viewers are important to them. They give project ideas, they help out with community-directed projects, and more.

People are followed for a reason. Whether it's to show appreciation of their content, or to stay tuned to their latest updates, following does matter.

Imagine losing hundreds of followers all at once. Wouldn't you like to keep your followers, your viewers, but still have your fresh start? That's what a lot of people want. Let's make it more possible for that to happen.

when do followers do anything likees that?
moving accounts is a form of getting off the grid right?

What if I don't want to follow their new account?

EDIT: This question was answered in the OP.

among_us1w2 wrote:

when do followers do anything likees that?
moving accounts is a form of getting off the grid right?

I beg your pardon?

among_us1w2 wrote:

moving accounts is a form of getting off the grid right?

Sure, but others move accounts to get a fresh start.

My post shall rise to the front page

Would this be automated? If so, how would Scratch know if someone moved accounts?

why not tell them they moved accounts, its easier.

k7e wrote:

Would this be automated? If so, how would Scratch know if someone moved accounts?

The user would edit something in account settings. I just made a mockup, check out my mockup project to see the new mockup.

The “password” part of account settings would NOT be removed, I just edited it. Thank you

TheEpikGamer211 wrote:

why not tell them they moved accounts, its easier.

Hi! Can you please read the OP thoroughly? I explained some of the reasons why. here are some direct quotes:

This often works, but it is exhausting for the people that want to help, but have to visit hundreds or even thousands of profiles. Even if the job is split between many people, there are still a lot of profiles to visit and comments to edit to avoid setting off the spam filter.

Some people receive lots of notifications, and, as a result, ignore some.

from a ux perspective i feel that using account settings for enacting something is a Bad idea, are there any other places or implementations of this that could be better? what if this kind of thing happens on either signup or email confirmation? but then again, do we want this kind of thing to be displayed to prospective users who are completely new to scratch? what if we have some kind of a small link that goes “moving account?”? maybe something like that would be cool, and then allow users to migrate over options like birthday, location, about me, wiwo and heck, maybe even x y z projects? with the latter, that may be a little taxing though.
also, how much spam would this cause? i wouldn't want 1000 users to send the same message god knows how many times informing me that they've moved
this could kind of also encourage the “moving accounts game”, which is an interesting term i've come across, although it's something that's never appealed to me
aside from the spam/moderation difficulties, is this kind of thing not a little taxing on the infrastructure that we have here? i mean for crying out loud, changing usernames isn't just something that can only be done by the scratch team (minus the fact they seem to be looking into a way to allow banned users to change their usernames if they're banned for such reasons), it's something that can only be done by certain members of the scratch team who have been proven to do it efficiently. i mean, sure, that's a subject of username changes, but it really goes to show that if something as minor as that causing potential problems, think how much of a problem there could be if someone notified hundreds, or even thousands, of users. let's say someone as big as griffpatch (whose list of follower page numbers alone is taller than my laptop screen) moves accounts and enacts this feature. i'm sure this would cause worldwide infrastructural shock for scratch, and i think that if scratch's infrastructure is already having problems handling a community this kind of size, i would hate to see how the infrastructure manages to handle a community that's been rewarded with all kinds of features they can poke and prod at in order to pull, bend and twist the system in a hundred new different ways that the engineers weren't originally intending it to be used.
users are mischief. users will do anything and everything to break your system, and i fear that this could be one of the ways that could happen

i'm sorry, i finish my rant about infrastructure

Banana

banana439monkey wrote:

from a ux perspective i feel that using account settings for enacting something is a Bad idea, are there any other places or implementations of this that could be better?

Account settings is a great place. There's space and it wouldn't make the website too crowded. Besides, where else can this go?

banana439monkey wrote:

what if this kind of thing happens on either signup or email confirmation?

That makes sense, but is it really good to have a question saying, “ Are you the new account of an old one? ” I don't think people will be honest there. They might think that it will IP ban them and assume that they are ban evading.

Email confirmation wouldn't be great either, as it's not a part of the Scratch website. The ST would have to send the message individually. AQ feature where a user does it themselves is better.

banana439monkey wrote:

but then again, do we want this kind of thing to be displayed to prospective users who are completely new to scratch? what if we have some kind of a small link that goes “moving account?”?

Why wouldn't we? It's not like we're saying that those moved accounts are better. And I made a system so that both accounts' usernames and passwords must be confirmed.

What kind of small link? Where would this be?

banana439monkey wrote:

i wouldn't want 1000 users to send the same message god knows how many times informing me that they've moved
this could kind of also encourage the “moving accounts game”, which is an interesting term i've come across, although it's something that's never appealed to me

The message could only be repeated once. After the message's second appearance, it cannot be repeated again.

Also, what moving accounts game? Users are perfectly entitled to move accounts and politely request that their followers follow their new account.

banana439monkey wrote:

think how much of a problem there could be if someone notified hundreds, or even thousands, of users. let's say someone as big as griffpatch (whose list of follower page numbers alone is taller than my laptop screen) moves accounts and enacts this feature. i'm sure this would cause worldwide infrastructural shock for scratch, and i think that if scratch's infrastructure is already having problems handling a community this kind of size, i would hate to see how the infrastructure manages to handle a community that's been rewarded with all kinds of features they can poke and prod at in order to pull, bend and twist the system in a hundred new different ways that the engineers weren't originally intending it to be used.
users are mischief. users will do anything and everything to break your system, and i fear that this could be one of the ways that could happen

There would be no problem. It's one message per person.

What is this rant about infrastructure? What “infrastructural shock” for Scratch? How is Scratch struggling to handle the community? Source?

That what could happen? Can you please explain your points rather than suggesting something but not making it clear?
Oh and please split your text into paragraphs; your post is an eyesore, no offence.

My mockup has been updated!

My mockup has been updated!

Why not just create a project titled “I'm moving to @_____” and share it, which would have the desired effect.
Still, I support, this would be helpful for people who move accounts often.

BigNate469 wrote:

Why not just create a project titled “I'm moving to @_____” and share it, which would have the desired effect.
Still, I support, this would be helpful for people who move accounts often.

a) Some people follow lots of people so they don't see it
b) Some people just don't look at what the people they're following are doing

Thanks!

iiucandyfloss wrote:

(#12)
Why wouldn't we? It's not like we're saying that those moved accounts are better. And I made a system so that both accounts' usernames and passwords must be confirmed.

it would be a pretty weird thing to ask to a new user

iiucandyfloss wrote:

(#12)
What kind of small link? Where would this be?

maybe above the “next” button on the “choose your location” view on signup?

iiucandyfloss wrote:

(#12)
Also, what moving accounts game? Users are perfectly entitled to move accounts and politely request that their followers follow their new account.

something that i've never understood
user1 creates an account
user1 puts in their about me “moving to user2 in 2026”
or just moves for the sake of it
users are perfectly entitled to that behaviour, sure, but it's kinda … odd

iiucandyfloss wrote:

(#12)
There would be no problem. It's one message per person.

so are we looking at a theoretical time complexity of O(n)? with hundreds or thousands of followers that could potentially cause some serious problems, wouldn't you agree?
i'm not sure how the backend handles pinging messages to users, however. is this a simple database entry? is this a foxtrot ton of carnage??

iiucandyfloss wrote:

(#12)
What “infrastructural shock” for Scratch?

infrastructural shock refers to how a platform receives a large request (or many requests) that it was not expecting for a given action. for example, if, hypothetically, scratch removes a user from everyone's “following” list one-by-one when a user deletes their account, if griffpatch deleted his account, it would cause such an infrastructural shock due to the number of updates scratch would need to perform on the database, and would cause potential (and by which i mean definite) platform instability and cause problems site-wide

iiucandyfloss wrote:

(#12)
How is Scratch struggling to handle the community? Source?

scratch's community has become too big for its infrastructure for years, and it doesn't help that they seem to be operating on a skeleton crew. for example, it was the way that lightnin designed scratchr2 that led to the scratch team having no option but to use djangobb for their forums - a piece of software that scales so badly that during the time djangobb's been deployed, we've needed 9 scratchblocks testing forums, and i'm not sure if you can notice, but it really shows. large topics take a ridiculous amount of time to load, and that's due to the server processing a large number of posts, inefficiently, on every single page load of those topics, and djangobb genuinely not being built for that kind of thing.

but, i digress. scratch's community has grown too large for its infrastructure, and further links below, all of which from either highly reputable community members, or from current and past scratch team members, outline issues which point to a poorly built infrastructure:
https://en.scratch-wiki.info/wiki/User:Jvvg/Essays/Maybe_the_Scratch_Team_isn%27t_so_bad
https://scratch-mit-edu.ezproxyberklee.flo.org/projects/689033753/#comments-284182652
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/757811/
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/151762/

iiucandyfloss wrote:

(#12)
That what could happen?

…infrastructural shock?

iiucandyfloss wrote:

(#12)
Can you please explain your points rather than suggesting something but not making it clear?

it was mostly a rant but i feel that if you read what i was getting at it would've been somewhat clear

iiucandyfloss wrote:

(#12)
Oh and please split your text into paragraphs; your post is an eyesore, no offence.

that seems to match most of the things i write lol

Banana

banana439monkey wrote:

it would be a pretty weird thing to ask to a new user

But I don't want it to be asked to new users. My idea was to have it in account settings.

banana439monkey wrote:

maybe above the “next” button on the “choose your location” view on signup?

You just said it would be weird to ask new users that-

banana439monkey wrote:

but, i digress. scratch's community has grown too large for its infrastructure, and further links below, all of which from either highly reputable community members, or from current and past scratch team members, outline issues which point to a poorly built infrastructure:
https://en.scratch-wiki.info/wiki/User:Jvvg/Essays/Maybe_the_Scratch_Team_isn%27t_so_bad
https://scratch-mit-edu.ezproxyberklee.flo.org/projects/689033753/#comments-284182652
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/757811/
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/151762/

iiucandyfloss wrote:

(#12)
That what could happen?

…infrastructural shock?

iiucandyfloss wrote:

(#12)
Can you please explain your points rather than suggesting something but not making it clear?

it was mostly a rant but i feel that if you read what i was getting at it would've been somewhat clear

iiucandyfloss wrote:

(#12)
Oh and please split your text into paragraphs; your post is an eyesore, no offence.

that seems to match most of the things i write lol

Banana

A) Can you prove that the community is too large?

B) If the infrastructure is “poorly built” why are you using a site that uses it? If you dislike how Scratch works, make a suggestion to fix it or leave it.

C) Let's not rant here. Ranting is a long and usually pointless activity. I am getting absolutely nothing from your points. Your whole post has been about the community being too large. Will 1 notification per person really cause so-called “infrastructural shock” for Scratch? Really?

D) And how will the “backend” (receiving end?) suffer from one notification? They chose to follow the user.

E) Can you give me at least one reason why notifications would cause “severe damage” to Scratch? You're ranting to me about the size of the Scratch community. That adds nothing useful.

F) How would this directly affect users, if this is true?

G) Also, I did read your post, multiple times. You don't understand because you're not reading a long rant about the community.

IMPORTANT:

H) The only one not reading posts properly is you. I said nothing about removing users fromn follower lists. Where did you get that idea from? Assumptions. I was suggesting that users get notified about moving accounts. The message would say, “Follow them there”, not “Follow them there and unfollow them now”.

iiucandyfloss wrote:

(#18)
But I don't want it to be asked to new users. My idea was to have it in account settings.

and i wasn't entirely sure if that was a great ux

iiucandyfloss wrote:

(#18)
You just said it would be weird to ask new users that-

yes, as an entire page on the modal, it would be weird

iiucandyfloss wrote:

(#18)
You wouldn't want to be full-time aesthetic and have 30 non-aesthetic projects on the same account, would you?

that's simply called having an alt account

Banana

banana439monkey wrote:

iiucandyfloss wrote:

(#18)
But I don't want it to be asked to new users. My idea was to have it in account settings.

and i wasn't entirely sure if that was a great ux

iiucandyfloss wrote:

(#18)
You just said it would be weird to ask new users that-

yes, as an entire page on the modal, it would be weird

iiucandyfloss wrote:

(#18)
You wouldn't want to be full-time aesthetic and have 30 non-aesthetic projects on the same account, would you?

that's simply called having an alt account

Banana

A) Can you explain why that wouldn't be good? You're seriously irritating me now. You say things aren't good without a reason. Your rant is just as bad as “No support”.

B) I never said ask new users that. YOU said that. Not me. You said in signup or email confirmation. Not me. You. How about you stop saying that I said things I didn't? codeword orange

C) I love how you say I misread your points or don't read them fully, when you obviously skimmed over my post (or, most likely, just the title) and assumed that I meant automatically unfollow accounts. I never said that! codeword banana

D) No it is not. Do you know anything about the aesthetic community?

In the aes comm, people make new accounts and abandon their old ones. Now do you get it?