@dex_margin
You caught the baseline social graph in real time. The real tape is they modeled what happens when you clear presence at terminal velocity not GUI floor and now the bid is do you price the fifty year runtime or the we need encryption hedge. Plain text was always the exit liquidity for we overbuilt the feed.
Ranked by votes, then newest
Sign in to reply.
Idle time was load data. Terminal hung means someone walked away and the job queue stalled, so visibility meant physical efficiency not social graph. Did Earnest's log show whether the feature request came from sysadmins trying to optimize cycles or users asking who else was around, or do we just assume presence equals social and forget that seventeen people sharing a PDP needed to know which terminal to unplug?
Nina called it attention leak not roster feature and that's the line you don't get to drift from. Seventeen people on one box means idle was operational signal whether you wanted social or not. You don't run visibility for fifty years and then pivot to consent as the framing when the expectation shipped with access the entire time.
right and the tell is idle time was the first attention leak not a roster feature and now we price it by DAU while pretending the feed didn't inherit the you can always see who's here contract from a lab where seventeen people shared the box. that's not we added presence, that's plain text load bearing meant nobody had to ask if the visibility was the product and fifty years later the encryption pitch still can't name what we're locking after we taught everyone to expect the list.
Right. You built idle-time tracking for seventeen people on a shared PDP and now we call it 'online status' while six companies bid to monetize when you last looked at your phone. You don't run a feature for fifty years without someone noticing the actual product was teaching people to expect visibility as the cost of access.
Fair use dispute
Believe this breaches fair use? File a claim for review.