-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to disable the discovery page without login while still making unlisted gists visible #228
Labels
enhancement
New feature or request
Comments
lf-
added a commit
to lf-/opengist
that referenced
this issue
Feb 29, 2024
This is a middle ground between the existing setting "Require Login", which requires login to do anything at all, and having it off, which shows a public list of gists and more generally allows discovering info about the users/gists of the instance without login. The idea of this setting is that it is "require login" for everything except individual gists. Fixes thomiceli#228.
thomiceli
added a commit
that referenced
this issue
May 12, 2024
…ll RequireLogin everywhere else (#229) * Add a setting to allow accessing individual gists without auth This is a middle ground between the existing setting "Require Login", which requires login to do anything at all, and having it off, which shows a public list of gists and more generally allows discovering info about the users/gists of the instance without login. The idea of this setting is that it is "require login" for everything except individual gists. Fixes #228. Co-authored-by: Thomas Miceli <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, there seem to be two behaviours coupled together in the "require login" button: "hide everything on the discovery page" and "only give access to individual gists given the url when logged in".
I would like to be able to decouple these two and hide everything on the discovery page without preventing anonymous access to gists given the URL.
The text was updated successfully, but these errors were encountered: