megaman100

I got an idea! It would be nice to see previous versions of projects, user pages, and more. They should also have an edit log for projects, user pages and so on.

Wahsp

Potential for private measaging?

LionHeart70

Eeh.. not sure how to feel about this. Often if someone deletes something from a description, that means they don't want anyone to see it anymore, so it'd almost be like reading someone's diary.

Wahsp wrote:

Potential for private measaging?
How so?

TheAdriCoolManDude

It has a potential for secret snooping. It means people can see things that they mistakenly wrote. No support.

megaman100

TheAdriCoolManDude wrote:

It has a potential for secret snooping. It means people can see things that they mistakenly wrote. No support.
I got a solution! Whenever you edit your userpage, you should have the ability to make the previous revision, acessable or not.

TheAdriCoolManDude

megaman100 wrote:

TheAdriCoolManDude wrote:

It has a potential for secret snooping. It means people can see things that they mistakenly wrote. No support.
I got a solution! Whenever you edit your userpage, you should have the ability to make the previous revision, acessable or not.
Okay, if that is allowed, it is okay. But I'm at Semi-Support: As it may be nice, I don't see it as very useful.

Wahsp

LionHeart70 wrote:

Eeh.. not sure how to feel about this. Often if someone deletes something from a description, that means they don't want anyone to see it anymore, so it'd almost be like reading someone's diary.

Wahsp wrote:

Potential for private measaging?
How so?
Write something and then get rid of it, someone can see what was there before

SeperateTitan92

I like the idea about the change log and I like the idea with the solution, but not really everything else.

Cub56

No support - someone may have accidentally typed something private and then removed it, so people could go out of their way to snoop and find out what they wrote before.

SeperateTitan92

Cub56 wrote:

No support - someone may have accidentally typed something private and then removed it, so people could go out of their way to snoop and find out what they wrote before.

Yeah. I recently almost put personal stuff on a project, and if I did and people looked at the old version…

apple502j

No support, can be used to see things removed by ST

Cub56

Also for projects, the creator might not want people to see older versions.

SeperateTitan92

apple502j wrote:

No support, can be used to see things removed by ST
You could make it so the ST could remove things permanently.

ScratchDiogoh

SeperateTitan92 wrote:

apple502j wrote:

No support, can be used to see things removed by ST
You could make it so the ST could remove things permanently.
Support for this

SeperateTitan92

ScratchDiogoh wrote:

SeperateTitan92 wrote:

apple502j wrote:

No support, can be used to see things removed by ST
You could make it so the ST could remove things permanently.
Support for this
Thanks!

TheAdriCoolManDude

megaman100 wrote:

TheAdriCoolManDude wrote:

It has a potential for secret snooping. It means people can see things that they mistakenly wrote. No support.
I got a solution! Whenever you edit your userpage, you should have the ability to make the previous revision, acessable or not.
Guys, have you decide to read this? Nobody seems to.

megaman100

TheAdriCoolManDude wrote:

megaman100 wrote:

TheAdriCoolManDude wrote:

It has a potential for secret snooping. It means people can see things that they mistakenly wrote. No support.
I got a solution! Whenever you edit your userpage, you should have the ability to make the previous revision, acessable or not.
Guys, have you decide to read this? Nobody seems to.
In addition you should be able to make any older revisions accessible or not.

SeperateTitan92

megaman100 wrote:

TheAdriCoolManDude wrote:

megaman100 wrote:

TheAdriCoolManDude wrote:

It has a potential for secret snooping. It means people can see things that they mistakenly wrote. No support.
I got a solution! Whenever you edit your userpage, you should have the ability to make the previous revision, acessable or not.
Guys, have you decide to read this? Nobody seems to.
In addition you should be able to make any older revisions accessible or not.

That would work! You could also just heave a ‘linked projects’ section where you could put projects that are related but might not have actually been uploaded and can only be accessible from there. If you set the title to ‘older versions’ then put all of the older versions in there, it would do the same thing pretty much. I think there should also be a change log (attached to that?) maybe? What would the point of seeing older versions actually be for MOST projects though. Some would be nice, but others would just be pointless, so it would be cool to be able to use it for other things as well.

ZappyBarbecue10

megaman100 wrote:

I got an idea! It would be nice to see previous versions of projects, user pages, and more. They should also have an edit log for projects, user pages and so on.
I only support the projects part . Though I'm thinking of it being something like this:

Scratch Team could add a little text at the bottom which displays the current version of a project (which could either be set to a number that represents the number of times a project has been edited, or, better yet, the version number the project's creator wants to give to it). By clicking on it, you will be sent to a page that will have all of the versions of the project. But the creator can decide which versions are available and what aspects of a version are not. For example, the creator can make the version 0.0.5 of their project public, but not its title, instructions or the notes and credits.

Another aspect that could be added is linking other projects as newer versions of a project, even if they were made by other people. The project that is on the other page will just count as the original's newer version, and comment sections will fuse (comments will still be ordered by newest to oldest). The original project's creator always decides which projects should they put as newer versions of their project. In case the project's creator is going to be inactive, they can pass the power of deciding which projects will be newer versions of a project to a scratcher that has made a version of the project. Then, when the creator of the project is active again, the current scratcher that's deciding about the newer versions gives the power back to the project's creator. This would greatly help to organize collabs. A “linked projects” function could also be made, in which the person in charge of deciding about the project's future updates can make different categories (for example, sequels and good remixes).

The Scratch Team could also add a little text at the bottom of every comment that indicates which was the project's version at the time the comment was made. Though in order to avoid confusion, comments can only be made in the last version of the project, so there's only one comment section in a single project and people don't criticize it because of aspects that were present in previous versions.

So, yeah, I want to see what you guys and gals think of this detailed description
By the way, please note that I'm just theorizing and I don't acknowledge which aspects of this are possible to implement by the Scratch Team.