Update Kink.yml for USA users - #2832
Open
USAstephan2009 wants to merge 1 commit into
Open
Conversation
Noticed issues with Kink.com presenting **** in some tags, this yaml should correct that detection for other USA users.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[Kink] Fix masked titles & tags (kink.com word-obfuscation)
Summary
kink.com now obfuscates "sensitive" words in its visible page content - titles in the h1, and category names in the scene's Categories section (e.g. "Pure S*********", "A***", "G*******"). This was breaking Title and Tags from this scraper.
Key finding: the obfuscation is not length-preserving and not reversible ("squirting" and "sadism" both render "S*****"; "blowjob" and "bondage" both render "B******"), so a display-text-to-name dictionary cannot be reliable.
Changes
Title - source from JSON-LD instead of the h1.
The scene's application/ld+json VideoObject block carries an always-unmasked "name". Verified on live pages:
h1 (masked): JSON-LD "name": D** Surrenders and Submits! Dom Surrenders and Submits! Pure S********* Pure Submission Janice Griffith ... P**** ... Janice Griffith ... Pussy ...
This mirrors the existing Details selector, which already reads the same VideoObject block.
Tags - scrape the /tag/ URL slug instead of anchor text, then map slug to name.
Category URLs are never masked and contain the full word ("/tag/anal-bdsm", "/tag/bondage", ...). The selector now takes @href, strips the domain / query string / channel suffix, and passes through a slug-to-display-name map (~245 entries) generated from the live kink.com and kinkmen.com tag directories. This also disambiguates words that collide when masked ("bbc"/"bbw", "blowjob"/"bondage", ...).
Verification
Only the Title and Tags blocks changed; all other fields and the driver section are byte-identical to upstream.
YAML parses cleanly; map size = 245 entries.
Masked examples now resolve correctly: A*** -> Anal, B****** -> Blowjob/Bondage (by slug), Double P********** -> Double Penetration, S***** -> Sadism/Squirting (by slug).
Notes for maintainers
The map is generated (script logic documented in the PR) and keys on kink.com + kinkmen.com slugs; kinkmen.com labels win on overlaps since scene URLs can point to either domain.
If a smaller footprint is preferred, the Title fix alone is a low-risk standalone change; the slug map is the only way to fully fix Tags while the site keeps obfuscating display text.