phone number censor and links

miniepicness

opaline wrote:
i tried posting a ten-digit number but it got censored, so i retyped it over 9000 times and i did some weird stuff and i put a space between all numbers

Who wants spaces in their project links?

Raytracing

If your so worried just make about 50 blank projects in advance so the cant be censored

CellularData

Raytracing wrote:
If your so worried just make about 50 blank projects in advance so the cant be censored

…how does that solve the issue

miniepicness

Raytracing wrote:
If your so worried just make about 50 blank projects in advance so the cant be censored

you'd need to make like 90000 for it to get past the censor.
Maybe even 900000000 because some phone numbers are really long

Last edited by miniepicness (April 15, 2018 23:56:41)

miniepicness

bump

1000652

If they're gonna keep that phone number censor in place, the least they should do is to find a way to skip project IDs that are 10 or 11 digits long and move on to 12 digits so that users can still share their projects in comments without the project ID getting censored.

when I receive [ newProjectId v]
if <<(lastProjectId) < [1000000000]> or <(lastProjectId) > [99999999999]>> then 
change [lastProjectId v] by (1)
else
change [lastProjectId v] by (99000000001)

end

CellularData

1000652 wrote:
If they're gonna keep that phone number censor in place, the least they should do is to find a way to skip project IDs that are 10 or 11 digits long and move on to 12 digits so that users can still share their projects in comments without the project ID getting censored.
when I receive [ newProjectId v]
if <<(lastProjectId) < [1000000000]> or <(lastProjectId) > [99999999999]>> then 
change [lastProjectId v] by (1)
else
change [lastProjectId v] by (99000000001)

end

The problem is that after that there are a TON of other blocked numbers. A lot of different countries have a lot of different ways of writing phone numbers, so it can be hard to find an amount of digits that isn't blocked

1000652

CellularData wrote:
1000652 wrote:
If they're gonna keep that phone number censor in place, the least they should do is to find a way to skip project IDs that are 10 or 11 digits long and move on to 12 digits so that users can still share their projects in comments without the project ID getting censored.
when I receive [ newProjectId v]
if <<(lastProjectId) < [1000000000]> or <(lastProjectId) > [99999999999]>> then 
change [lastProjectId v] by (1)
else
change [lastProjectId v] by (99000000001)

end
The problem is that after that there are a TON of other blocked numbers. A lot of different countries have a lot of different ways of writing phone numbers, so it can be hard to find an amount of digits that isn't blocked

I'm pretty sure that the phone number censor only censors 10-or-11-digit-long numbers, unless I'm missing something important.

PkmnQ

I would suggest binary if the for the limit of 500 characters didn't exist.

ZZ9PluralZAlpha

miniepicness wrote:
so itll be scratch.mit.edu/griffpatch/1/

I know I'm late to discussing this, but as far as I've seen, links when Scratch was in it's 1.4 days were in this format, but using the ID numbers in the URL that they use today.

Buffek

1000652 wrote:
CellularData wrote:
1000652 wrote:
-snip
The problem is that after that there are a TON of other blocked numbers. A lot of different countries have a lot of different ways of writing phone numbers, so it can be hard to find an amount of digits that isn't blocked
-snip-.

For example, in Poland, the numbers are all +48 000 000 000
With the 0s being the number and we can just write 000 000 000…

And I noticed that the censor detects 0000000000 but who has a number like THAT?

MrFluffyPenguins

My idea: Always have 8 or 9 random numbers!

CellularData

Mr_PenguinAlex wrote:
My idea: Always have 8 or 9 random numbers!

Not sure what you mean here, but it won't work because we've already used all of the 8 digit URLs and will soon have used all of the 9 digit ones too.

LionHeart70

Buffek wrote:
And I noticed that the censor detects 0000000000 but who has a number like THAT?

As far as I know, phone numbers can't start with a 0 (in the US, at least).
I also don't think phone numbers can be all the same number, so..

Raytracing wrote:
If your so worried just make about 50 blank projects in advance so the cant be censored

What if someone wants to make a remix?

miniepicness

bump?

-ShadowOfTheFuture-

Wow, I never thought of this…

Yeah, this will probably end up becoming a serious problem in the near future.

MrFluffyPenguins

Oh my god. This could happen with studios, too!
And forum posts, but that doesn't seem like much of a problem.

Flowermanvista

Well i had a super simple idea that would make a Base64 project ID system (the way YouTube does it) viable:

When the project ID is generated, pass it through the swear filter, and if it's bad, generate a different one.

PkmnQ

Let's try hexadecimal except it gets retried every time it filters.
Although if we get a ten digit hexadecimal string without letters, it still could be a problem so encode it again.
e.g.
155885897 -> 313535383835383937 or 94AA149 depending on what way.

Actually no, I have a better idea.
Base 26 with retries.
155885897 -> MCCFKK
It will only be applied if it senses that the project id will be greater than 10, so that there are no problems of previous projects having problems.

Last edited by PkmnQ (June 19, 2018 11:32:05)

miniepicness

PkmnQ wrote:
Let's try hexadecimal except it gets retried every time it filters.
Although if we get a ten digit hexadecimal string without letters, it still could be a problem so encode it again.
e.g.
155885897 -> 313535383835383937 or 94AA149 depending on what way.

Actually no, I have a better idea.
Base 26 with retries.
155885897 -> MCCFKK
It will only be applied if it senses that the project id will be greater than 10, so that there are no problems of previous projects having problems.

what if we just convert it into talki
um yeah thats a good idea except if it can spell out swears

Discuss Scratch