Utilize a Different Scratch Auth Frontend.

Steve0Greatness commented 1 year ago

Hey! I'm aware of this project's relative popularity in the Scratch modding space. I'm also aware that PenguinMod uses the default provided front-end of Scratch Auth for authentication. This, on it's own, is not a problem. What is a problem, however, is that people frequently spam the comments section of Looky(the creator, owner, and primary-maintainer of Scratch Auth) with comments relating to issues they face while using PenguinMod.

I don't think anyone should be spammed, I hope you agree with me. Which is why I'm requesting that you stop using the unmodified front-end of Scratch Auth without changing it to make it clear that this project is not affiliated with Scratch Auth.

What Do I Mean By "Front-End"

Scratch Auth works with it's own backend API, an API that just happens to have CORs enabled, meaning it can be accessed from anywhere by both JS code, and backend JS code. It's API is pretty ok-ly documented, although you have to do some digging. I already did this digging.

GET https://auth.itinerary.eu.org/api/auth/getTokens Query Options: redirect* - String ( base64 encoded url ) method - Enum ( "cloud", "comment" ) authProject - String ( ID of the Scratch project used for authentication )
GET https://auth.itinerary.eu.org/api/auth/verifyTokens/:privateCode Query Parameters: privateCode* - String ( private code given by getTokens ) Query Options: redirect* - String ( base64 encoded url, only required when oneClickSignIn is true ) oneClickSignIn - Boolean
GET https://auth.itinerary.eu.org/api/auth/oneClickSignIn Headers: Authorization* - String
POST https://auth.itinerary.eu.org/api/auth/oneClickSignIn/:username Headers: Authorization* - String Query Parameters: username* - String Query Options: redirect - String ( base64 encoded url )
DELETE https://auth.itinerary.eu.org/api/auth/oneClickSignIn/:username Headers: Authorization* - String Query Parameters: username* - String

* = required

Based off of this image of a forum post on the original Scratch Auth Forum Topic(before it got dustbinned).

RedMan13 commented 1 year ago

people frequently spam the comments section of Looky

how would we fix this

RedMan13 commented 1 year ago

and also how would we edit the front end of scratch auth?

RedMan13 commented 1 year ago

nvm ignore the second and the first one comment

JeremyGamer13 commented 1 year ago

there are a lot of long tasks related to the API so unfortunately this isn't gonna be able to happen soon

Ianyourgod commented 1 year ago

i think this is a good idea, ive seen that comment section. But as JG said we have other problems

Steve0Greatness commented 1 year ago

i think this is a good idea, ive seen that comment section. But as JG said we have other problems

there are a lot of long tasks related to the API so unfortunately this isn't gonna be able to happen soon.

That's fair. I just thought it'd be smart to bring this to yall's attention, as well as give details that could help solve it.