Censoring shouldn't affect share dates

bunnyCoder16

Even the first project on scratch has been affected by this.

https://scratch-mit-edu.ezproxyberklee.flo.org/projects/104#:~:text=%C2%A9,Feb%2002%2C%202022

Last edited by bunnyCoder16 (May 13, 2022 17:30:54)

Latexbeast

support! I hate mass reporting!!

randomguy3513

support but i think there should be a last updated along with the realeese date

bunnyCoder16

randomguy3513 wrote:
support but i think there should be a last updated along with the realeese date

That is a great idea!!
Maybe you hover over the release date and you can see the last updated date.

blablablahello

I believe a “creation date” would also work (share date changes, but creation date always stays as the day the project first got created)

sharkode

Bump

sharkode

bump

sharkode

bump

nuclear_news

support

shadic52

Support all the way

jbthepig

Support. Especially if the project was falsely reported, the creator shouldn't be attacked for copying a project that actually belongs to them.

ChloeKohli

It's been a while, I hope this isn't necroposting…
SUPPORT <3

medians

when green flag clicked
set [page v] to [1]

-An_Unnamed_User-

medians wrote:

when green flag clicked
set [page v] to [1]

this is the wrong topic to test code blocks. you should test blocks in here.

-Valtren-

-An_Unnamed_User- wrote:
medians wrote:
when green flag clicked
set [page v] to [1]
this is the wrong topic to test code blocks. you should test blocks in here.

actually I think they're trying to bump the topic

Goldensun_Silverdrop

I support this idea. @Coderwe2's suggestion is also great (about having an original day and reshare day)

FluffyBumblebees74

sharkode wrote:
Changing the share date can cause confusions to which project is original, which leads to false reports and more auto censoring, also, some mass reporters want a project to be taken down to cause confusion, if we keep the original share date, it might reduce the number of mass reporting

Edit: This includes both auto censor and legitimate censoring by ST, as it could also cause confusion and sometimes ST censor things by mistake

Support. There should be a release date of the project, and the date when it was last updated.

EXAMPLE

First Shared: May, 14, 2007
Last Updated: May, 15, 2007

Hope this suggestion gets accepted!

Knightbot63

bump. 2nd or 3rd page

DifferentDance8

sharkode wrote:
because it wouldn't be good. (#76)

It could also be a double edged sword.

As a good example, almost every single game on scratch gets temporarily unshared and then reshared. Like, Appel was originally released late 2020, but many updates have happened and now the upload date says “Aug 19, 2022”.

And the hypothetical exploit sharkode was talking about is the bad example.

sharkode

DifferentDance8 wrote:
(#102)
sharkode wrote:
because it wouldn't be good. (#76)
It could also be a double edged sword.

As a good example, almost every single game on scratch gets temporarily unshared and then reshared. Like, Appel was originally released late 2020, but many updates have happened and now the upload date says “Aug 19, 2022”.

And the hypothetical exploit sharkode was talking about is the bad example.

I don't see a point in including manual unsharing, since you know the consequences and are ok with them if you unshare it manually

Discuss Scratch