How ThinkFeedback works

Something broken? Post it on Bug Reports. An idea, a request, or something awkward to use? Feedback Requests. Questions belong in the wiki or on Discord. Accepted work appears on the Roadmap and ships in the Changelog. Read the full guide

Upstream

Sign in with Plex fails if you are already signed in to ThinkAuth

What happens If you already have an active ThinkAuth session and then use Sign in with Plex, the sign-in fails. Plex itself reports success, but you are returned to the login screen or shown "Request has been denied". Signing in with Plex from a signed-out state works normally. Workaround Sign out of ThinkAuth completely, then start again from ThinkFeedback. Why it is Upstream The defect is in Authentik, not in a Think service. SourceFlowManager.get_action() forwards its arguments to two of its three update_user_connection() calls but not the third — the one taken when the request is already authenticated and a source connection already exists. The stored Plex token is nulled and the flow fails. Reported upstream as goauthentik/authentik#25115. This post tracks that fix. A database-level mitigation is already applied so the failure is a clean denial rather than a server error.

AuthenticationCollaboration
thinkhead·about 14 hours ago
Upstream

ThinkFeedback asks you to sign in again even when already signed in elsewhere

What happens ThinkFeedback re-challenges you for credentials even when you already have a valid ThinkAuth session, unlike every other Think service. It is the only application in the estate that behaves this way. Why it is Upstream Quackback, the application behind ThinkFeedback, hardcodes prompt=login on every authorization request, which forces the identity provider to re-run its full authentication flow regardless of an existing session. There is no configuration option to change or disable it. This also has a knock-on effect: it is what routes returning users into the Authentik defect tracked separately on this board. Requested upstream as QuackbackIO/quackback#372 — make prompt configurable per identity provider, defaulting to current behaviour. This post tracks that change.

AuthenticationUX
thinkhead·about 14 hours ago
Upstream

ThinkWatch: a bulk CSV import can abort partway through

What happens Importing a large CSV into ThinkWatch can stop partway through, leaving some of your rows imported and the rest silently missing — even when the file itself contains no duplicates. What causes it If the Plex or Jellyfin webhook happens to create a tracking entry for a show while your import is running, the import hits a conflict on that one row and abandons the entire remaining batch rather than skipping it. So the trigger is a race with the automatic watch tracking, not a problem with your file. Workaround Run large imports when you are not actively watching anything, and re-run the import afterwards — already-imported rows are the ones that succeeded, so a second pass picks up what was missed. Why it is Upstream The fix belongs in Yamtrack, the application behind ThinkWatch. Reported upstream as FuzzyGrim/Yamtrack#1579 and accepted as a bug. This post tracks that fix.

Collaboration
thinkhead·29 days ago
Planned

Error importation recette

Via url unique. Exemple: https://veroniquecloutier.com/cuisine/boeuf-braise-a-loignon-et-puree-de-pommes-de-terre-au-bacon --- Imported from ThinkBugs (Astuto), originally posted 2024-08-31.

Collaboration
vada0326·almost 2 years ago4
Upstream

uBlock Origin break some thinkhead.org and other site

Following the migration to firefox, some part of thinkhead.org, thinkplex, thinkdocs and other site are partially broken when the plugin is active. --- Imported from ThinkBugs (Astuto), originally posted 2025-07-27.

Security
thinkhead·about 1 year ago2
Upstream

Erreur d’importation recette

Erreur lorsqu’on ajoute cette recette dans Tandoor https://distilleriemariana.com/cocktails/milkshake-a-lamaretto-avril/ L’erreur est de type Failure. There was an error importing the receipe! No usable data could be round --- Imported from ThinkBugs (Astuto), originally posted 2025-06-19.

Collaboration
vada0326·about 1 year ago
Upstream

ThinkBackgammon: the upstream container build is broken, so we maintain our own

Does this affect playing the game? No. ThinkBackgammon works normally — this is about how we build and update it, not how it runs. What is wrong The container image published by the upstream project does not start: the build succeeds, but the container fails immediately on launch. Because of that, ThinkBackgammon does not run an upstream image at all — we build and host our own instead. Why that matters It means updates to the game depend on our own build rather than simply pulling a new upstream release, and rebuilding from scratch requires re-deriving that workaround. It is a maintenance cost rather than a user-facing fault, but it is the reason this service is not on a standard upstream image like most others. Why it is Upstream The defect is in the project's own container definition. Reported upstream as quasoft/backgammonjs#27 — open since August 2020 with no maintainer response, though the project itself is still active. This post tracks it.

GamesInfrastructure
thinkhead·over 5 years ago