Skip to content

Latest commit

 

History

History
52 lines (33 loc) · 2.54 KB

README.md

File metadata and controls

52 lines (33 loc) · 2.54 KB

Stash Checker

Stash Checker is an userscript for porn websites to check if a Scene/Performer is in your Stash instance. It shows a checkmark if an item was found in your Stash. Hovering over the checkmark gives you a tooltip with information about the item in your Stash.

tooltip

Features

  • A tooltip for matched entries including basic metadata and a link to the entry
  • Supported websites: StashDB, TPDB, IAFD, JavLibrary and many more (see @match section in the userscript; go here to request more)
  • Many different types of entries: Scene, Performer, Movie, Gallery, Studio and Tag (not yet supported by Stash)
  • Match entries by: StashId, URL, Studio Code, Name and Title
  • Multiple Stash endpoints
  • Dark mode (check your browser preferences)

Installation

You need a browser plugin like Tampermonkey or Violentmonkey to run userscripts.

The newest release of Stash Checker can be found in the release section to the right. Opening index.prod.user.js under Assets should prompt Tampermonkey to install the script.

Settings

Settings can be opened on any supported website using the Tampermonkey dropdown menu.

menu

Here you can edit the Stash URL and API key or add another Stash endpoint.

settings

Troubleshooting

Stash endpoint shows no connection

  • Check for the correct URL. It should include the scheme (http/https) at the beginning and end with /graphql.
  • Check the API key. Leave the field empty, if none is required.
  • Tampermonkey may block the connection. Make sure, that the domain is whitelisted in the Tampermonkey settings.
  • Firefox's "HTTPS only mode" can block a connection, if the URL uses http but does not include localhost. The whitelist doesn't help, you have to deactivate the feature.
  • Some websites can block connections due to a strict Content-Security-Policy-Header (CSP). Change Tampermonkey settings to remove this header.

Stash endpoint shows wrong URL

  • Check for the correct URL. It should include the scheme (http/https) at the beginning and end with /graphql.
  • Some users had problems with Tampermonkey which got fixed by switching to Violentmonkey.

Development

See here.