DEV Community

StarkMan
StarkMan

Posted on

Watcharr title and body counts agree, so the authentication path becomes the question

Watcharr title and body counts agree, so the authentication path becomes the question

Watcharr is a self-hostable watched list for films, television, anime, and games. Its public page is easy to recognize, and the deployment model is intentionally small. A title count is therefore more useful than it would be for a product whose name appears in documentation everywhere.

On 2026-11-17, title="Watcharr" returned 769 total matches at 07:46:59 +08:00. http.body="Watcharr" returned 834 at 07:47:00 +08:00. Both used sub_type=all, page 1, and pagesize=1. The close values suggest a more product-specific body population, although the fields still describe pages, not unique installations.

The first user becomes the administrator

Watcharr's Docker Compose guide states that the first user created becomes the administrator. The service can use Jellyfin or Plex as an authentication provider. The provider choice changes account mapping and login recovery. It should be recorded before the first invitation is sent.

The documentation for Jellyfin authentication warns that changing the setting can prevent users from logging in to the correct account. That is a migration risk, not a vulnerability by itself. A provider change needs a test account, a rollback path, and a clear decision about existing users. A public demo or open registration page is not the same as an organization's production instance.

Data and backup boundaries

The tracker stores viewing history, ratings, status values, and account data. Those records may be personal even when they are not regulated. Review the database and cache volumes, backup location, restore owner, and whether a public status page or integration reveals user activity.

Watcharr's documentation recommends backing up before an update. A database copy should include the WAL file when the database is backed up while stopped according to the product guidance. A backup that captures only the main file may lose recent changes. The recovery test should include the admin account and provider configuration.

Validate the host, not only the count

The two counts are close enough to support a candidate list, but they do not identify all installations or prove that each page belongs to the same product. Check the login page, version, certificate, Jellyfin or Plex redirect, and owner records. Exclude demo pages and documentation hosts.

For the 769 title candidates, classify the authentication mode and first-user state. For the 834 body pages, confirm that the product is actually served. The next action is to contact the owner of any production instance with an open registration path or an unreviewed provider migration.

References

[1] ZoomEye title query. https://www.zoomeye.ai/searchResult?q=dGl0bGU9IldhdGNoYXJyIg%3D%3D

[2] ZoomEye body query. https://www.zoomeye.ai/searchResult?q=aHR0cC5ib2R5PSJXYXRjaGFyciI%3D

[3] Watcharr documentation. https://watcharr.app/

[4] Watcharr Docker Compose guide. https://watcharr.app/docs/installation/docker-compose

Top comments (0)