ackvonhuelioLvl 41
- Edited
[WUT] Adam
how are you manually changing the frozen property?
[WUT] Adam
how are you manually changing the frozen property?
ackvonhuelio You know the object that's returned from https://studio.code.org/v3/channels/channel_id? You can modify that however you like, and even add new properties that go completely unused, and then save that by sending a POST request to the same URL with that modified object as the body of the request.
They most likely removed it because of chats. Tbh, it would've been better if they removed the keyValues()
instead of removing the whole project gallery, since it'll prevent chats while projects still being able to be published. I am working on a project that's pretty big but probably only the gamelab forum gets to see it. And Retro Pong, I had 2.7k visits on that thing and I even promised to make a new ball but they'll probably never get to see it. Without keyValues()
instead of the project gallery, I would've been fine with that.
Why was I given a strike?
[WUT] Adam
huh i guess i'll have to try that out...
wait what's stopping someone from getting rid of the "id" property
bad idea ahead ... or changing the thumbnail of a featured project to nsfw stuff 😱...
ackvonhuelio You can't change the id
property. It automatically resets it to the channel ID.
[WUT] Adam
what about the bad idea
well boys, it was fun while it lasted
DragonFireGames
nuh uh
ackvonhuelio guess i gotta go to khan now
[WUT] Adam Didn't you figure it out once and then proceed to spam the public project list so bad you were called to the office at school to talk about it.
DragonFireGames No, that was figuring out how to report projects programmatically and then doing so on every public project on the site.
I win :D
[WUT] Adam Yep, that's exactly what I was thinking. If publish requests can be hacked then the frozen
property should be changeable as well. And if you can edit a featured project, that means chats are actually still possible. Crazy thing is that I had been using the API a few days ago and noticed the new frozen
property, but didn't think anything of it.
ackvonhuelio Owokoyo explained that thumbnails can be hacked (part 4), but you need an authorization token first. Once that's figured out, both the thumbnail and frozen
property should be changeable.
Binary_Coder It's also possible to just use another project's thumbnail as the thumbnail, and then setting the channel ID in thumbnailUrl
to that project. Here's the easiest way to accomplish that:
thumbnailURL
to the channel ID of the thumbnail project, and then POST it to the server.The "authorization" is really just being logged into the code.org account that owns the project.
[WUT] Adam Okay, that's good to know. Never had much success with POST requests before but I'll give it another shot.
Also, does this mean that you could change the data in https://studio.code.org/api/v1/users/current to give yourself permission to add featured projects?
Binary_Coder Attempting to send a POST request to https://studio.code.org/api/v1/users/current returns 404. I couldn't figure out what makes a featured project featured--it's probably just an array on their end.
CDO fucked up so bad bro.. yeah im taking acks word for it and moving to ka