when communities are selected in user settings, all feeds disappear #28

New Issue

chelsea · 2025-10-12T16:55:05-05:00

chelsea commented

2025-10-12 16:55:05 -05:00

No description provided.

chelsea commented

2025-10-12 17:50:01 -05:00

● CRITICAL DISCREPANCY IDENTIFIED!

Here's the major mismatch between the community selection system and the actual post data:

🔍 THE PROBLEM:

User Settings: {"communities": []} - Empty array means user doesn't see ANY posts.

Post Data Structure: Posts have "source": "hackernews" for ALL HackerNews posts, regardless of community.

📊 Actual Data vs. Expected Data:

What's Stored	What Post Contains	Expected by Platform Config
User settings: []	Post "source": "hackernews"	Should be "front_page", "ask", "show"
Form sends: community.id	Posts have generic platform names	Filtering doesn't match

🔧 Specific Discrepancies Found:

HackerNews Posts: All posts have "source": "hackernews" instead of specific communities like:
- "front_page" (from platform config)
- "ask" (Ask HN)
- "show" (Show HN)
User Settings: User "chelsea" has {"communities": []} - completely empty!
Community Selection Template: Sends community.id values like "front_page", "ask", "show" but no posts match these values.

🎯 The Filtering Logic Issue:

In app.py:461-464:
if (post_source == selected_community or
post_platform == selected_community or
selected_community in post_source):

Since:

post_source = "hackernews" (for all HN posts)
selected_community values would be "front_page", "ask", "show"
User's selected_communities = [] (empty!)

Result: NO POSTS EVER MATCH because user has no communities selected!

🔥 Two Separate Problems:

Data Collection Problem: Posts are stored with generic platform names instead of specific community identifiers
User Settings Problem: User has empty communities array, so even if data was correct, they'd see nothing

💡 Solution:

Quick Fix: Update some communities for the user:

Set user communities to enable them to see posts

user.settings = '{"communities": ["hackernews", "front_page", "ask", "show"]}'

Long-term Fix: Update data collection to store proper community identifiers in the source field.

● CRITICAL DISCREPANCY IDENTIFIED! Here's the major mismatch between the community selection system and the actual post data: 🔍 THE PROBLEM: User Settings: {"communities": []} - Empty array means user doesn't see ANY posts. Post Data Structure: Posts have "source": "hackernews" for ALL HackerNews posts, regardless of community. 📊 Actual Data vs. Expected Data: | What's Stored | What Post Contains | Expected by Platform Config | |--------------------------|-----------------------------------|---------------------------------------| | User settings: [] | Post "source": "hackernews" | Should be "front_page", "ask", "show" | | Form sends: community.id | Posts have generic platform names | Filtering doesn't match | 🔧 Specific Discrepancies Found: 1. HackerNews Posts: All posts have "source": "hackernews" instead of specific communities like: - "front_page" (from platform config) - "ask" (Ask HN) - "show" (Show HN) 2. User Settings: User "chelsea" has {"communities": []} - completely empty! 3. Community Selection Template: Sends community.id values like "front_page", "ask", "show" but no posts match these values. 🎯 The Filtering Logic Issue: In app.py:461-464: if (post_source == selected_community or post_platform == selected_community or selected_community in post_source): Since: - post_source = "hackernews" (for all HN posts) - selected_community values would be "front_page", "ask", "show" - User's selected_communities = [] (empty!) Result: NO POSTS EVER MATCH because user has no communities selected! 🔥 Two Separate Problems: 1. Data Collection Problem: Posts are stored with generic platform names instead of specific community identifiers 2. User Settings Problem: User has empty communities array, so even if data was correct, they'd see nothing 💡 Solution: Quick Fix: Update some communities for the user: # Set user communities to enable them to see posts user.settings = '{"communities": ["hackernews", "front_page", "ask", "show"]}' Long-term Fix: Update data collection to store proper community identifiers in the source field.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chelsea/balanceboard#28