Network/Register/Consumption Edge Privacy And Visibility
Gap Register
G-049Public

Consumption-edge privacy and visibility

Tier 2 — Structurally thin, not launch-blocking
Status
Open — not started
Owner
Creator
Why now
Treating users as graph entities captures reads and likes as edges; default visibility is both a privacy risk and an engagement-optimization trap.
Related
Entry 027, G-010, G-019

Decide which consumption edges (reads, likes) are public, the per-user controls, retention, and the guardrail against optimizing discovery on them.

Why this matters

Entry 027 captures consumption edges (reads, likes) deliberately. The unresolved decisions are exactly the ones that sank Facebook's "frictionless sharing":

  • Default visibility — which consumption edges, if any, are public by default versus private-by-default with opt-in sharing.
  • Per-user controls — granularity of what a member can hide or expose, and whether consumption history is exportable / deletable (ties to G-019 data portability).
  • Retention — how long raw consumption events are kept versus aggregated.
  • The optimization guardrail — discovery and recommendation must not optimize on raw engagement signals (G-010); consumption edges feed the graph, not the ranking objective.