Discuss Scratch
- Discussion Forums
- » Suggestions
- » make community guidelines breaking projects unviewable instead of just unsharing them
- gdpr5b78aa4361827f5c2a08d700
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
Erm, that isn't how it works. If an external tool can easily access a supposedly restricted endpoint from an API, then that's bad security (not even security at all). Also, I think the OP means that unshared projects should be completely private, just like they're meant to be, and that you can't just GET https://api.scratch.mit.edu/projects/{id}/ (or the relevant endpoint), and have access to an unshared project.Scratch doesn't endorse external tools or are responsible for what they do so no supportAll you have to do is literally just turbowarp.org/PROJECTID.Turbowarp and forkphrous are outside of the Scratch Website, so i assume they're external tools. Again, having to use an unofficial tool to view unshared projects is bad enough. Maybe if there was a way to view unshared Scratch projects inside the Scratch Website i'd support, but there isn't so for now, No support.as already explained, you can You already can't..you are aware what an api request is, right? Your computer has to send them every time you load a webpage. and if youve been on scratch for a while you will know that sites like turbowarp and forkphorus do this and allow you to view unshared projects jesus christ if you have to send an api request to view it it's already bad enough, so no support
EDIT: there seems to be lots of people misunderstanding what an API is here, so maybe check your knowledge?
Last edited by gdpr5b78aa4361827f5c2a08d700 (April 25, 2021 16:26:13)
- PkmnQ
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
I don't know how the API works, but I'm gonna assume that it asks for the information from the server. If so, the server could just check if it has some unviewable flag set, and if it is, it tells the API to send a specific unviewable project JSON.
Last edited by PkmnQ (May 7, 2021 13:06:25)
This is an account that exists.
Here, have a useful link:
The Official List of Rejected Suggestions by Za-Chary
- gdpr5b78aa4361827f5c2a08d700
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
The API is the server, it handles Scratch's backend. I don't know how the API works, but I'm gonna assume that it asks for the information from the server. If so, the server could just check if it has some unviewable flag set, and if it is, it tells the API to send a specific unviewable project JSON.
- PkmnQ
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
Then where does it store the unshared?The API is the server, it handles Scratch's backend. I don't know how the API works, but I'm gonna assume that it asks for the information from the server. If so, the server could just check if it has some unviewable flag set, and if it is, it tells the API to send a specific unviewable project JSON.
This is an account that exists.
Here, have a useful link:
The Official List of Rejected Suggestions by Za-Chary
- gdpr5b78aa4361827f5c2a08d700
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
All projects are stored in object storage internally. When the frontend wants to get any project, shared or unshared, it asks the API for it.Then where does it store the unshared?The API is the server, it handles Scratch's backend. I don't know how the API works, but I'm gonna assume that it asks for the information from the server. If so, the server could just check if it has some unviewable flag set, and if it is, it tells the API to send a specific unviewable project JSON.
- han614698
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
not really. Turbowarp works for anything really.jesus christ if you have to send an api request to view it it's already bad enough, so no supportno, just making it so you cant just send an api request and get the project, or if thats not doable then yes, deleting Like deleting it?
<Scratch Wikian | Forum Helper | Almost to 6000 Posts! | Please be aware I may mistype things, my wrist is fractured>
Credit to -gge for the icons in my signature | I condensed all this code into five lines using [p] tags, idk why
- lovecodeabc
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
You already can't… +just removing the ability to view it(even for the owner) would be problematic, as some people want to be able to see what was wrong with their project fix it(you can't fix an issue if you can't see it) and request for it to be put back up(via contact us).Yeah
WHAT IS THE POINT
Highlight + Ctrl + Shift + down to see full sig
Check out my thingymagings!
Click on them to go to them
Click on them to go to them
© 2019 - 2023 lovecodeabc. All Rights Reserved under Title 17 of the United States Code, and especialy under Section 101-513. Unauthorized Use Prohibited, except under 17 USC § 107, Fair Use. cease and desist letters go brrrrrrr
Uh oh, did the kumquats come again?
Click here!!!OR ELSE I WILL EAT YOUR COOKIESSSSSSSSSSSSSS AND ALSO MAYBE YOUR MOM, WHO KNOWS??
;
- PkmnQ
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
What if internally the API checks if it's set to unviewable first, and if it is, it requires the session id of either an ST member or the project maker (or alternatively it always requires one but it just ignores it if it's viewable) and if it isn't it returns some 403 forbidden or something like that?
This is an account that exists.
Here, have a useful link:
The Official List of Rejected Suggestions by Za-Chary
- Yellowsheep43
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
How about instead, we just warn the user before they reshare the removed project on why the project was removed. And maybe make it so you can't reshare the project unless you change something.
How to use scratchblocks \ How to make your project popular \ The Do's and Do Not's of the Suggestions Forum
Highlight this and use Ctrl + Shift + Down arrow to see the rest of my signature!
My signature is an evil kumquat factory
When [Post v] :: #ffd900Angry David
if <(Kumquats available? :: #00ff7b) = <True :: #517d48> :: #d642e3> then :: #00e32d
Make evil kumquats :: #00d5ff
end
Haha invisible block go brrr :: cap :: #ffffff
It's spelled AMONG US, not Amogus! Know the difference!
(((((I reside in the ((Questions About Scratch :: #00e8a2 stack) :: #00e8c1 stack) and ((Suggestions :: #00e8a2 stack) :: #00e8c1 stack) forums :: #ff0073) :: #ffae00) :: #ffd500) :: #00ff2a) :: #0095ff) :: #8c00ff hat
I spend a bit of time everywhere <Except the wiki :: #94634a> :: #dd00ff cap
(_/(._. v)|_ :: #0051ff) :: #55ff00 hat // This is an unnamed servant that restocks on kumquats constantly
As long as Signal (When gf clicked :: #ff0059) [given v] {
Produce Kumquats :: #08d16d
} :: #9a0f2a
I enjoy [Among Us v], [FNF v], [Roblox v], [Memes v], [Object Shows v], and [Anthropomorphic animals v]:: #08b0d1 cap
- plqaokwsijeduhrfyg
- Scratcher
500+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
That solves nothing as you could still view them unshared and the entire premise of this suggestion is to stop that. How about instead, we just warn the user before they reshare the removed project on why the project was removed. And maybe make it so you can't reshare the project unless you change something.
- Maximouse
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
It should work like this for all unshared projects, not just censored ones. What if internally the API checks if it's set to unviewable first, and if it is, it requires the session id of either an ST member or the project maker (or alternatively it always requires one but it just ignores it if it's viewable) and if it isn't it returns some 403 forbidden or something like that?
- Steve0Greatness
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
There's no need for this, unsharing does the job.
/hj is the worst tone indicator. It's confusing and ambiguous. I hate it. The point of tone indicators is to indicate tone, or the way that a piece of text should be read, but what does “half joking” mean? Do you just wake up in the morning and think “wow, I really have something I want to talk about seriously but also kinda not, IDK you decide.” It's useless. I hate it. It just provokes a deep rooted anger within me whenever I see it. People just comment /hj as if it makes any sense. It doesn't. Oh wow, it's a tone indicator that's has a relative meaning, how useful, I'll use it in every comment I post. NO. STOP IT. You're a tone indicator, you have only one job, and yet you sit there doing nothing apart angering me.
/srs
^^^ (there's more below)
This one is useful because it tells you that this signature is fully 100% serious. (/srs) Who would've thought that tone indicators needed to tell you something about the piece of text they're attached to? /s
I'm serious, I'm not even going to put multiple (/hj)s a the end of my signature as to mock the previous paragraph for not getting the point of something(like previous version of my signature). /srs
- TopCode
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
see but it doesnt There's no need for this, unsharing does the job.
The following is my signature:
MAKE PROJECTS REMOVED BY THE ST UNVIEWABLE PLEASE LIKE NOW
Once upon a time, CatBlocks were brought into the world of Scratch. They became quite dear to us, and were close to our hearts. But then, an evil kumquat ate them. We will always keep them in our hearts, and we promise to remember them forever.
Proud king of 500th page of minecraft topic
that sounds so cringe
No amount of rest can pass this night
- Scratchfangs
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
- gdpr5b78aa4361827f5c2a08d700
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
what was that word that i just read..?This ruins Turbowarp and previews, no support. Also ruins my TV-14 series that I have on Discord lol. then they would probably restrict API access to unshared projects altogether.
- TopCode
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
“I have on Discord”This ruins Turbowarp and previews, no support. Also ruins my TV-14 series that I have on Discord lol. then they would probably restrict API access to unshared projects altogether.
hol up
The following is my signature:
MAKE PROJECTS REMOVED BY THE ST UNVIEWABLE PLEASE LIKE NOW
Once upon a time, CatBlocks were brought into the world of Scratch. They became quite dear to us, and were close to our hearts. But then, an evil kumquat ate them. We will always keep them in our hearts, and we promise to remember them forever.
Proud king of 500th page of minecraft topic
that sounds so cringe
No amount of rest can pass this night
- Scratchperson1000000
- Scratcher
500+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
uhh yeah you can there's a glitch that happens sometimesI don't see the point in this suggestion, you can't open unshared projects in Scratchthey are not the same, you can view unshared projects, you wouldnt be able to view an unviewable one. Unviewable and unsharable are the same thing
DJHNVLKJUDHFIUYHDLKUHDKLFJUYGDKJFGDHMFGMDBKJSDBCKSNICUNDCHICUGUYDSGFUHGADJFIEUGAFKJ
- Scratchperson1000000
- Scratcher
500+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
HOW WOULD THAT RUIN YOUR TV-14 SERIESThis ruins Turbowarp and previews, no support. Also ruins my TV-14 series that I have on then they would probably restrict API access to unshared projects altogether.(removed by quoter - please don't mention any unmoderated chat sources) lol.
DJHNVLKJUDHFIUYHDLKUHDKLFJUYGDKJFGDHMFGMDBKJSDBCKSNICUNDCHICUGUYDSGFUHGADJFIEUGAFKJ
- han614698
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
(removed by quoter - don't remove things from your quotes if your asking follow up questions about it)This ruins Turbowarp and previews, no support. Also ruins my TV-14 series that I have on then they would probably restrict API access to unshared projects altogether.(removed by quoter - please don't mention any unmoderated chat sources) lol.
<Scratch Wikian | Forum Helper | Almost to 6000 Posts! | Please be aware I may mistype things, my wrist is fractured>
Credit to -gge for the icons in my signature | I condensed all this code into five lines using [p] tags, idk why
- dhuls
- Scratcher
1000+ posts
make community guidelines breaking projects unviewable instead of just unsharing them
How did you manage to say Discord.This ruins Turbowarp and previews, no support. Also ruins my TV-14 series that I have on Discord lol. then they would probably restrict API access to unshared projects altogether.
Anyway, the purpose of TurboWarp is not to view unshared projects. It is to speed up projects. The ability to see unshared projects is a problem with the API, which is what the OP is asking to fix, not a problem with TurboWarp. Also, if you need to share TV-14 Scratch Projects just upload them to Google Drive, OneDrive, or some other cloud storage provider.
- Discussion Forums
- » Suggestions
- » make community guidelines breaking projects unviewable instead of just unsharing them