Backend
Making Sense of Audience Change: Causal Attribution and Boundary Management on Xiaohongshu
arXiv cs.HC0 views
arXiv:2610.38026v2 Announce Type: replace Abstract: Recommendation-driven platforms can reshape not only what users see, but also who becomes visible and how community boundaries are negotiated. We examine Xiaohongshu discussions surrounding a perceived World Cup-related audience influx to understand how users attributed community change and how those explanations related to boundary-management strategies. We analyzed 262 comments from eight high-engagement threads using researcher-led thematic analysis, structured coding, and permutation-based association analysis. Users described personalization as both social separation and a boundary that could fail, interpreted platform growth through audience acquisition and commercialization, and contested whether gender should define community membership. Among 70 comments with explicit attributions and strategies, attribution and strategy were strongly associated (Cramer's V = .583): algorithmic attributions concentrated in technical boundary management, while social-actor attributions more often aligned with social enforcement or normative socialization. These findings connect causal sensemaking with boundary management and show how audience restructuring can create governance consequences on recommendation-driven platforms.
Source:https://arxiv.org/abs/2610.38026PreviousWhat Is the Role for Humans in Creative Writing? Creativity and Diversity in Human-AI CollaborationNextInfrastructure and its Discontents: Contestations of Power in Canada's AI Governance Scaffold
Related posts
He arrested a hacker, then spent 18 months clearing his own name. Now he’s a cybersecurity VC.
0TechCrunch
How to Use DeepSeek Through an OpenAI-Compatible API
0dev.to
This is what ChatGPT personally feels about humans
0dev.to
Logging provider failures without storing anything about the user
0dev.to PHP
Failed Job Retries in Node.js: 3 Recovery Boundaries for Shipment Fanout in 2026
0dev.to Node
Message Queue Service for Delayed Email Scheduling: BullMQ or SQS (Node.js Recovery)
0dev.to Node