Binary_Coder I looked into it, and the way that they prevent featured projects from being edited is the frozen property for a project's /v3/channels/ url. Manually setting the frozen property to true, obviously, prevents you from editing it, but also shows a "Congratulations, your project is featured" message in the "My Projects" tab.

It makes me wonder if a featured project could be edited if you simply manually disabled the frozen property after it gets featured...

      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?

        seek spamming i think

        But hey everyone, if you want to see projects before the incident, just use magical "WayBack Machine"

          [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 😱...

              [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.

                    [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:

                          1. Create a new Game Lab project.
                          2. Add the image you want as the thumbnail as a 400x400 sprite.
                          3. Draw the sprite on the screen, and then click the Share button. If you mess up or want to change it, reload the page, make any alterations you want, and then click the Share button while it's running.
                          4. Copy the channel ID, and then GET the /v3/channels object for the project you want to have that thumbnail.
                          5. Set the channel ID in thumbnailURL to the channel ID of the thumbnail project, and then POST it to the server.
                          6. Any time afterwards that you edit that project's code, repeat steps 4-5.

                          The "authorization" is really just being logged into the code.org account that owns the project.

                              CDO fucked up so bad bro.. yeah im taking acks word for it and moving to ka

                              Chat