Skip to content

Stop treating gizmoduck age 0 as a confirmed underage viewer - #133

Closed
Pitchfork-and-Torch wants to merge 1 commit into
xai-org:mainfrom
Pitchfork-and-Torch:cursor/sensitive-viewer-age-zero-15a8
Closed

Stop treating gizmoduck age 0 as a confirmed underage viewer#133
Pitchfork-and-Torch wants to merge 1 commit into
xai-org:mainfrom
Pitchfork-and-Torch:cursor/sensitive-viewer-age-zero-15a8

Conversation

@Pitchfork-and-Torch

Copy link
Copy Markdown

Bug

Gizmoduck age_in_years: Some(0) is a missing-birthday sentinel. Visibility filtering mapped it to ViewerAge::Known(0). viewer_is_underage treated any Known(age) < 18 as a child, so SensitiveViewerUnderageDropRule hard-dropped sensitive media worldwide for those accounts.

RPC error already fails open as Unknown. Existing users with no usable birthday should be NotStated (jurisdiction-scoped via NSFW_GATING_COUNTRIES). Home-mixer and Phoenix already treat 0 as missing. VF did not.

Fix

Some(age) if age > 0 → Known. Else existing user → NotStated. Else → Unknown. Underage is logged-in + age in 1..18.

Age gates stay. Logged-out, confirmed underage, and no-stated-age-in-gating-country drops are unchanged.

Also: BidirectionalFollowHydrator now runs after CoreData and skips author_id 0 (leftover from #128). InNetwork order from #128 is unchanged.

SensitiveViewerUnderageDropRule used Known(0) as underage, so a missing
birthday sentinel hard-dropped all sensitive media worldwide. Classify
non-positive age like a missing birthday (NotStated if the user exists,
Unknown otherwise). Move BidirectionalFollowHydrator after CoreData and
skip author_id=0 so unhydrated rows are not stamped false mutual-follow.
@Pitchfork-and-Torch
Pitchfork-and-Torch force-pushed the cursor/sensitive-viewer-age-zero-15a8 branch from 9d4e5e5 to 902a06f Compare September 8, 2026 23:12
@Pitchfork-and-Torch

Copy link
Copy Markdown
Author

Parking this intern-stack PR per operator GitHub cleanup (2026-09-08). Hunt notes remain local. Not a reject of the class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant