I don't know if this is already implemented and I don't want to try as it risks my account security (neither should you, so don't try it), but if not, please make it so you can't say your own password (the password don't turn into X, instead, you get a warning saying that you should never disclose your password and it would be similar to an ordinary chat filter violation, but without getting muted)

Edit: Many people said if you set your password is something ordinary it would affect your conversation with other users, however, this is actually a feature as you shouldn't set your password as something you would use in everyday conversation

But what are we supposed to ban (more specific)? And if you know that giving out your password is bad, then why would someone do it anyway?

The servers don't know your password. It's hashed if Scratch has the right security. No support. Implementing this would actually make the security worse.

What if the password is the name of your hamster? Germil? What if you want to talk about him?

“Omg my hamster XXXXXX is so cute!!”

DinoMaster20 wrote:

What if the password is the name of your hamster? Germil? What if you want to talk about him?

“Omg my hamster XXXXXX is so cute!!”

You shouldn't set your password as something ordinary

lolecksdeehaha wrote:

The servers don't know your password. It's hashed if Scratch has the right security. No support. Implementing this would actually make the security worse.

It checks every word of your comment and encrypts each one of them to see if it matches your password, like when logging into your account

sharkode wrote:

(#5)

DinoMaster20 wrote:

What if the password is the name of your hamster? Germil? What if you want to talk about him?

“Omg my hamster XXXXXX is so cute!!”

You shouldn't set your password as something ordinary

That doesn't change the problem. People still do it.

sharkode wrote:

lolecksdeehaha wrote:

The servers don't know your password. It's hashed if Scratch has the right security. No support. Implementing this would actually make the security worse.

It checks every word of your comment and encrypts each one of them to see if it matches your password, like when logging into your account

I feel like this is awfully more work than this problem deserves. We already have a report system and making an entirely new filter to stack onto the filters on the comments we already have would be a problem.

what if someone's password is “scratch”?

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

-Morni- wrote:

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

No only your own password, you shouldn't set your password as something obvious anyways

sharkode wrote:

No only your own password, you shouldn't set your password as something obvious anyways

Just because you shouldn't do something, doesn't mean that you can't.

sharkode wrote:

-Morni- wrote:

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

No only your own password, you shouldn't set your password as something obvious anyways

Uh many ppl passwords are something like scratch, shark, cat or something, so the bots couldnt be able to detect that this is the password, if it cant detect, so its no use of having this feature

-Morni- wrote:

sharkode wrote:

-Morni- wrote:

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

No only your own password, you shouldn't set your password as something obvious anyways

Uh many ppl passwords are something like scratch, shark, cat or something, so the bots couldnt be able to detect that this is the password, if it cant detect, so its no use of having this feature

What do you mean by that

dave-alt-4 wrote:

what if someone's password is “scratch”?

They shouldn't, it's their fault for using such an obvious password

sharkode wrote:

-Morni- wrote:

sharkode wrote:

-Morni- wrote:

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

No only your own password, you shouldn't set your password as something obvious anyways

Uh many ppl passwords are something like scratch, shark, cat or something, so the bots couldnt be able to detect that this is the password, if it cant detect, so its no use of having this feature

What do you mean by that

Leave it, i think i am bad at explaining

How is this filterbot going to detect if the user has put a common word as their password and then used that in a sentence? And please don't respond with, “They shouldn't put that as their password,” because that doesn't answer the question.

sharkode wrote:

(#14)

-Morni- wrote:

sharkode wrote:

-Morni- wrote:

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

No only your own password, you shouldn't set your password as something obvious anyways

Uh many ppl passwords are something like scratch, shark, cat or something, so the bots couldnt be able to detect that this is the password, if it cant detect, so its no use of having this feature

What do you mean by that

I think they are saying that is your project is scratch, and the filterbot goes:
“I love XXXXXXX!”
Then many people would know their password.

And don't say they shouldn't put it as their password. They do. Saying they shouldn't make that their password won't fix the problem at hand.

DinoMaster20 wrote:

sharkode wrote:

(#14)

-Morni- wrote:

sharkode wrote:

-Morni- wrote:

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

No only your own password, you shouldn't set your password as something obvious anyways

Uh many ppl passwords are something like scratch, shark, cat or something, so the bots couldnt be able to detect that this is the password, if it cant detect, so its no use of having this feature

What do you mean by that

I think they are saying that is your project is scratch, and the filterbot goes:
“I love XXXXXXX!”
Then many people would know their password.

And don't say they shouldn't put it as their password. They do. Saying they shouldn't make that their password won't fix the problem at hand.

The filter makes it the message cannot be sent instead of changing the password to to X

sharkode wrote:

(#19)

DinoMaster20 wrote:

sharkode wrote:

(#14)

-Morni- wrote:

sharkode wrote:

-Morni- wrote:

I dont support, already scratch makes 10-11 digits no. to XXX XXX XXXX just cuz it thinks it is a phone number, now if we add password one, it can make any word XXXXXX which is annoying

No only your own password, you shouldn't set your password as something obvious anyways

Uh many ppl passwords are something like scratch, shark, cat or something, so the bots couldnt be able to detect that this is the password, if it cant detect, so its no use of having this feature

What do you mean by that

I think they are saying that is your project is scratch, and the filterbot goes:
“I love XXXXXXX!”
Then many people would know their password.

And don't say they shouldn't put it as their password. They do. Saying they shouldn't make that their password won't fix the problem at hand.

The filter makes it the message cannot be sent instead of changing the password to to X

And then the user just can't say “Scratch”? The name of the website?