Content Feed Rendering Failure

📖

Bug Description

Feed System Malfunctions

Critical failures affecting content discovery and user engagement:

Feed Loading Issues

• Infinite loading loops
• Blank/empty feed displays
• Partial content loading
• Timeout errors

Content Filtering Bugs

• Incorrect relevance sorting
• Duplicate post displays
• Missing recommended content
• Broken pagination

Performance Note: Include load time metrics and network waterfall analysis if available.

🎯

Eligibility Criteria

Acceptance Criteria:

1. Issue must affect multiple users or user segments
2. Reproducible with fresh browser sessions
3. Not caused by individual user preferences
4. Demonstrable impact on user experience

📋

Submission Requirements

🔍

Detailed Description

Provide a comprehensive description of the bug, including what it does, who is affected, and when it occurs.

🔧

Reproduction Steps

Step-by-step instructions to reproduce the bug. Number each step clearly.

⚖️

Expected vs Actual

Clearly state what should happen vs what actually happens due to the bug.

📎

Evidence Required

Must include supporting evidence as specified below.

📎

Required Evidence

The following types of evidence must be included in your submission:

🖼️ Screenshot 🌐 Network logs 🖥️ Console logs 📎 Performance metrics

📝

Submission Template

Feed Bug Submission Guidelines:

Required Report Information:

• Feed Type: Specify affected feed (Home, Explore, Personalized, Trending)
• User State: Indicate if logged in, following active users, or anonymous
• Technical Details: Include API responses, error codes, console output, and network logs
• Performance Metrics: Document load times, response delays, and resource usage
• Reproduction Consistency: Note if issue occurs consistently or intermittently

Example Feed Bug Report:

Feed: Explore Feed - Infinite Scroll Failure

User: Logged in with 50+ followed accounts

Issue: Scroll stops loading after page 3, shows "No more content" incorrectly

Console Error: "TypeError: Cannot read properties of undefined"

Network: API returns 500 error on page=4 parameter

Consistency: 100% reproducible across Chrome and Firefox

⏱️

Processing Timeline

Within 24 hours

Initial review and acknowledgment of your report

3-5 days

Detailed assessment by security team

7-14 days

Resolution and reward processing

💬

Was this helpful?

Help us improve by letting us know if this bug description was clear and useful.

👍 Yes

👎 No