Discuss Scratch
- Discussion Forums
- » Suggestions
- » Beta Projects
![[RSS Feed]](//mv-ezproxy-com.ezproxyberklee.flo.org/scratchr2/static/__35b9adb704d6d778f00a893a1b104339__//djangobb_forum/img/feed-icon-small.png "[RSS Feed]")
![[RSS Feed]](http://mv-ezproxy-com.ezproxyberklee.flo.org/scratchr2/static/__35b9adb704d6d778f00a893a1b104339__//djangobb_forum/img/feed-icon-small.png "[RSS Feed]"){kind=icon}
- R4356th
-
Scratcher
1000+ posts
Beta Projects
I am aware that adding users to work on projects is rejected but this is something different.
During collaborating with other Scratchers, it sometimes becomes necessary to share projects with collaborators. The feature I am suggesting will solve this matter.
What It Will Be
It will be a platform for sharing project which are being made without making them available on search, profiles, studios and the Explore tab. However, they will be available to every Scratcher who uses this platform, not only collaborators, also a new tag would be available in the Explore tab and, the project would be available in “What's Happening”. Projects shared on the platform can be reported also. “See Inside” will not be disabled. Collaborators will be able to make edits to the projects.
Restrictions
This feature will not be available for New Scratchers, since that could cause moderation issues.
How This Will Work
Every user who wants to use this platform will have to get an account for that first. The username will be the same, because otherwise moderation issues may occur. The user who will share a project will be able to add collaborators. That user will also be able to decide if collaborators can directly make edits or not(in which case, the collaborators will have to comment or download the file, make edits and share it). Once making a project is done, it could be shared on the main website, and when it will be done, it will go the profile of the collaborators, as well as the user who shared the project.
During collaborating with other Scratchers, it sometimes becomes necessary to share projects with collaborators. The feature I am suggesting will solve this matter.
What It Will Be
It will be a platform for sharing project which are being made without making them available on search, profiles, studios and the Explore tab. However, they will be available to every Scratcher who uses this platform, not only collaborators, also a new tag would be available in the Explore tab and, the project would be available in “What's Happening”. Projects shared on the platform can be reported also. “See Inside” will not be disabled. Collaborators will be able to make edits to the projects.
Restrictions
This feature will not be available for New Scratchers, since that could cause moderation issues.
How This Will Work
Every user who wants to use this platform will have to get an account for that first. The username will be the same, because otherwise moderation issues may occur. The user who will share a project will be able to add collaborators. That user will also be able to decide if collaborators can directly make edits or not(in which case, the collaborators will have to comment or download the file, make edits and share it). Once making a project is done, it could be shared on the main website, and when it will be done, it will go the profile of the collaborators, as well as the user who shared the project.
Last edited by R4356th (April 13, 2020 12:18:42)
- Za-Chary
-
Scratcher
1000+ posts
Beta Projects
How does your method prevent private messaging from occurring? If two users want to share personal information with each other, they can just start a collaboration and do it without any trouble, because there is no risk of someone else seeing the project and reporting it. The “How This Will Work” also sounds a lot like a shared account, which are not allowed anyway.
- R4356th
-
Scratcher
1000+ posts
Beta Projects
How does your method prevent private messaging from occurring? If two users want to share personal information with each other, they can just start a collaboration and do it without any trouble, because there is no risk of someone else seeing the project and reporting it. The “How This Will Work” also sounds a lot like a shared account, which are not allowed anyway.The messages will be public.
- R4356th
-
Scratcher
1000+ posts
Beta Projects
How does your method prevent private messaging from occurring? If two users want to share personal information with each other, they can just start a collaboration and do it without any trouble, because there is no risk of someone else seeing the project and reporting it. The “How This Will Work” also sounds a lot like a shared account, which are not allowed anyway.Why does it sound like a shared account to you? Please elaborate and do not reject before replying.
- scratchykit5743
-
Scratcher
1000+ posts
Beta Projects
kind of against the share part of scratch motto, but an alternative could be a username blocking script and/or random letters for the name (at first).
- R4356th
-
Scratcher
1000+ posts
Beta Projects
kind of against the share part of scratch motto, but an alternative could be a username blocking script and/or random letters for the name (at first).That is banned.
That does not look like a duplicate to me.-snip-Never mind, I did not read the suggestion closely enough. I think it might be a good idea to honestly consider if this suggestion is a duplicate of this one; I'm not sure if it is, so I'll leave this open for now.
- Monna-Uka
-
Scratcher
1000+ posts
Beta Projects
Support. Normally people on Scratch doesn't look on BETAs much, so having this will be good.
- R4356th
-
Scratcher
1000+ posts
Beta Projects
Support. Normally people on Scratch doesn't look on BETAs much, so having this will be good.Thank you!
- R4356th
-
Scratcher
1000+ posts
Beta Projects
I edited another part. The project will go not only to the profile of the user who shared the project, but also, to the profile of the collaborators once it is shared.
- ResExsention
-
New Scratcher
1000+ posts
Beta Projects
This is effectively private messaging.
You either share it or you don't. I don't think we should add a halfway point where you can go, "Meh, I think I'll make it so that only my friends will be able to see it because almost nobody will be looking for unplayable, indev projects."
without making them available on search, profiles, studios and the Explore tab.
You either share it or you don't. I don't think we should add a halfway point where you can go, "Meh, I think I'll make it so that only my friends will be able to see it because almost nobody will be looking for unplayable, indev projects."
- R4356th
-
Scratcher
1000+ posts
Beta Projects
This is effectively private messaging.I request you to reread this.
- ResExsention
-
New Scratcher
1000+ posts
Beta Projects
This is effectively private messaging.I request you to reread this.
I request you to reread my post.
- WindOctahedron
-
Scratcher
1000+ posts
Beta Projects
I can see where this is going… it's time to switch to logic!This is effectively private messaging.I request you to reread this.
I request you to reread my post.
[…] without making them available on search, profiles, studios and the Explore tab.This means that the only way you can find them is through a link (maybe through “What's happening?”, though).
That is the definition of unlisted projects, which is included in “Restrict sharing”, which is rejected:
4.1 Disable “See Inside” or restrict sharingSo ResExsention is right - this is effectively private messaging.
[…]
Restricting sharing so that only certain users can view the project is also not going to be implemented. It is important for projects to be publicly shared for everyone to see so people can report them if they are inappropriate. Only allowing certain users to view projects could increase the chances of inappropriate projects being shared on the website. “Unlisted projects,” similar to a YouTube feature, will also not be implemented for the same reason. It could also be used for private messaging; for more information, see #7.1 on this list.
Last edited by WindOctahedron (April 13, 2020 09:39:55)
- Monna-Uka
-
Scratcher
1000+ posts
Beta Projects
Changed to semi-support. Maybe make a #BETA tag in Explore tab will be better.
- R4356th
-
Scratcher
1000+ posts
Beta Projects
I can see where this is going… it's time to switch to logic!Ah, now I see it! Hmm, it actually would be a good idea to make the project available in “What's Happening”. But it is not being an unlisted project.[…] without making them available on search, profiles, studios and the Explore tab.This means that the only way you can find them is through a link (maybe through “What's happening?”, though).
That is the definition of unlisted projects, which is included in “Restrict sharing”, which is rejected
Changed to semi-support. Maybe make a #BETA tag in Explore tab will be better.Agreed. Changing it.
- python_megapixel
-
Scratcher
500+ posts
Beta Projects
This seems like a very confusing way of achieving collaboration. There are a few problems:
- A project which does not appear on profiles, studios or in “Explore” can effectively only be accessed with a link. In reality, nobody is going to want to sit there and guess the 9-digit number of a project, so Beta projects won't get looked at and nothing innappropriate will be reported. it's pretty much equivalent to private collaboration, which is a big no-no.
- The only other alternative is for the ST to approve every change to one of these “Beta Projects” which would put far too much of a strain on the Scratch Team, given that there is the public website and forums to moderate as well.
- If it's possible for the project owner to set it so that collaborators have to download and re-share, rather than editing directly, how is that different to the current system.
- Discussion Forums
- » Suggestions
-
» Beta Projects