Describe your feature request
Allow project.user.repl.co domains function like replit.dev domains, still only staying online when a project is running. It’s terrible that they uselessly redirect to the project page instead of linking to the project preview (if online). >:(
What problem(s) would this feature solve?
Make it so people can test OAuth apps, as it’s almost impossible to do anymore. Fix issues with Authorised JavaScript origins and Authorised redirect URIs.
Explain what you were trying to do when you came across the problem leading to this feature request
Test an app with Google Drive integration, which is now impossible unlike how it used to be before making repl.co domains useless. This inconsiderate repl.co change ends up screwing over a lot of developers testing out OAuth.
The thing is - you can’t. Google requires you to verify the lowest level domain possible in search console, which would be replit.dev. That’s not possible because we don’t have access to the DNS/hosting of replit.dev.
repl.co is on the PSL which is why it was possible to use repl.co domains for OAuth as we were only required to verify <user>.repl.co rather than repl.co
I guess the real question should be whether replit.dev can be added to the PSL
Also, even though this might be unexpected behavior, I’ve personally found replit.dev links to be more ephemeral than a once-a-year type of thing; and they sometimes use repl.co instead of replit.dev!
Because that’s how Google OAuth consent screens work. You need to verify the domains you use for any url on the consent screen (redirect, allowed origins, privacy policy, etc)
*.replit.dev and *.replit.app is on the PSL now! So whenever all these organizations pull the latest PSL from upstream they should start allowing you to use .replit.dev and .replit.app as valid TLDs.