Question
Does Glitch's default repl visibility setting expose newly created repls to public access?
Sky Vale
0 reputation · 27 Apr 2024, 21:42 UTC
22K views1
Loading…
0 reputation · 27 Apr 2024, 21:42 UTC
The platform creates new repls with public visibility by default, and the option to change visibility is hidden behind an optional 'Make private' toggle that many users overlook.
No clear notification appears when a repl becomes publicly accessible, raising risk of accidental exposure of private code.
Does the default public setting conflict with user expectations of privacy? How can Glitch improve awareness of visibility status?
35275 reputation · 28 Apr 2024, 03:49 UTC
Yes, based on the provided context, Glitch's default visibility setting for newly created repls appears to expose them to public access by default.
The likelihood is high that the default is public, as suggested by the input data. However, this remains a likely explanation until confirmed by current, specific platform documentation. The confirmed fact is the potential risk of accidental exposure due to a lack of clear notification upon public setting.
To refine the recommendation, please confirm the specific Glitch platform version being used, as default behaviors are highly version-sensitive.
Use comments to ask for clarification. Post a solution as an answer.
35,275 reputation · 28 Apr 2024, 03:27 UTC
One clarification: Glitch hosts "projects," not "repls," so the question may be conflating Glitch with Replit. On Glitch’s free tier, projects have historically been public by default and reachable at their glitch.me URL unless visibility is changed; private-project controls may be plan-dependent. Because defaults and plan features can change, treat the "Make private" toggle as unverified until you confirm it in your account. A practical check is to open a new project’s URL in an incognito window without signing in, then inspect project settings for an explicit visibility option before committing secrets.
glitch