[GH-ISSUE #915] add an ability to use api keys in web #1978

Closed
opened 2026-04-11 06:22:34 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @clepdn on GitHub (Nov 14, 2024).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/915

describe the feature you'd like to see

I'd like to be able to supply an API key for a community instance.

I'm wondering if it's worth my time to make a PR

I'd like for a way to use an authenticated instance from the frontend.

Here's what I think this change could look like on /settings/instances (please ignore the horrifying CSS job)

image

additional context

Maybe there's something I'm overlooking, or this behavior is deliberate.

As far as I can tell the only way to protect an instance is with turnstile or an API key.
I haven't looked into turnstile, as API keys fit my use-case, but as far as I can tell it seems like it's just bot detection for a public frontend

Originally created by @clepdn on GitHub (Nov 14, 2024). Original GitHub issue: https://github.com/imputnet/cobalt/issues/915 ### describe the feature you'd like to see I'd like to be able to supply an API key for a community instance. I'm wondering if it's worth my time to make a PR I'd like for a way to use an authenticated instance from the frontend. Here's what I think this change could look like on /settings/instances (please ignore the horrifying CSS job) ![image](https://github.com/user-attachments/assets/90a09932-4a44-496e-ba0d-76cac43eb9e6) ### additional context Maybe there's something I'm overlooking, or this behavior is deliberate. As far as I can tell the only way to protect an instance is with turnstile or an API key. I haven't looked into turnstile, as API keys fit my use-case, but as far as I can tell it seems like it's just bot detection for a public frontend
GiteaMirror added the feature request label 2026-04-11 06:22:34 -05:00
Sign in to join this conversation.