Discourse Meta
Us.anthropic.claude-sonnet-4-20250514-v1:0

Executive report on Discourse Feature Requests

sam

Look at the top 1000 open topics in the feature category - ordered by like (first post only) - all time … make me an executive report of the:

  • Top 20 features CDCK should build
  • Easiest 20 features CDCK could build
  • Obvious duplicates
  • Things that are very poorly defined

ask me no more questions, just run the research

forum_research_bot
Thinking...The user (sam) is asking for a comprehensive research analysis. They want:
  1. Top 1000 open topics in the feature category
  2. Ordered by likes (first post only)
  3. All time
  4. An executive report covering 4 specific goals:
    • Top 20 features CDCK should build
    • Easiest 20 features CDCK could build
    • Obvious duplicates
    • Things that are very poorly defined

They explicitly said “ask me no more questions, just run the research” so I should proceed directly.

Let me construct the filter:

  • category:feature (for feature category)
  • status:open (for open topics)
  • post_type:first (first post only)
  • max_results:1000 (top 1000)
  • order:likes (ordered by likes)

The goals should cover all 4 areas they want analyzed.

I’ll analyze the top 1000 most-liked open feature requests to create your executive report. Let me gather this data now.

Researching

Researching: Analyze the feature requests to identify: 1) Top 20 features CDCK should prioritize building based on community demand, technical feasibility, and strategic value, 2) Easiest 20 features CDCK could build - focusing on low complexity, quick wins, and straightforward implementations, 3) Obvious duplicates - identify similar or identical feature requests that should be consolidated, 4) Poorly defined requests - features that lack clear specifications, use cases, or implementation details

Found 1000 posts matching ‘category:feature status:open post_type:first max_results:1000 order:likes’

Executive Report: Feature Request Analysis

Based on analysis of the top 1000 open feature requests ordered by likes, here’s your comprehensive executive report:

Top 20 Features CDCK Should Build

Strategic Priority Features (High Community Demand + Clear Business Value):

  1. True Block - Complete user blocking functionality addressing critical safety concerns
  2. Personal Message Permissions - Advanced PM controls for harassment prevention, essential for vulnerable users
  3. Better Search - Core functionality improvement with widespread community demand
  4. End-to-end Encryption for Chat - Critical security feature for competitive positioning
  5. ActivityPub Support: Phase 1 - Strategic federation feature for competitive advantage
  6. iOS 16 Web Push Notifications - Mobile engagement essential for user retention
  7. AI Search for Non-Exact Matches - Enhanced search using AI for knowledge-base forums
  8. SCIM Support as Service Provider - Enterprise identity management integration
  9. Multi-language Forum Support - Critical for global expansion, widely requested
  10. Tighter Integration Between Chat and Forum - Strategic chat-forum workflow improvements
  11. Better Control Over Incoming Chats - Chat permission controls for high-profile users
  12. Option to Hide IP Addresses from Moderators - GDPR compliance and privacy requirements
  13. More Granular Email Notification Settings - Advanced user notification controls
  14. Category Intersections - Advanced categorization for complex communities
  15. Conditional User Fields - Dynamic form logic for better onboarding
  16. Users Self-Deleting/Anonymizing - GDPR compliance for user privacy
  17. Accessibility Audit and Shepherd - Legal compliance and inclusive design
  18. Admin Restrictions/Role-based Permissions - Critical security feature
  19. Better Auto-backup Options - Essential for data security and reliability
  20. Tag Aliases Support - Highly requested for content organization

Easiest 20 Features CDCK Could Build

Low Complexity Quick Wins:

  1. Increase 100 Character Limit for Watched Word Links - Simple configuration change
  2. Add Sidebar Shortcut Key to Keyboard Shortcuts - Documentation update only
  3. Allow Users to Toggle 24 Hour Time - Simple user preference setting
  4. Add ‘Stop Impersonating’ Link to User Avatar Dropdown - Simple UI addition
  5. Clickable Link/URL User Field Type - Straightforward field type addition
  6. Create Invite Immediately from Sidebar - Remove unnecessary intermediate step
  7. FLoC Network Opt-out - HTTP header addition
  8. Warn Before Blocking Own IP Address - Simple validation check
  9. Show Message Retention Period in Chat UI - Display existing data
  10. Make Banner Appear Next to Sidebar - CSS positioning change
  11. Display “Similar To” Earlier for Exact Matches - UI tweak, algorithm adjustment
  12. Privacy Option to Disable Link Click Counting - Simple toggle setting
  13. Add Admin Section to Sidebar - Navigation enhancement
  14. Show Topic Timer Info in Topic List - Display enhancement
  15. Notify Group Owners When Added/Removed - Notification system extension
  16. Remove Choice in Polls - Simple UI addition to existing polls
  17. Character Count in Composer - Live counter display
  18. Tag Descriptions on Mobile - Mobile UX improvement
  19. Role Indicator in Chat - Username styling enhancement
  20. Auto-clear Flags Older Than 90 Days - Automated cleanup job

Obvious Duplicates

Features That Should Be Consolidated:

  1. Search Enhancement Requests:

  2. Chat Integration Requests:

  3. Badge & Gamification Features:

  4. Multi-language Support:

  5. Email & Notification Improvements:

  6. Admin & Moderation Tools:

Poorly Defined Requests

Features Lacking Clear Specifications:

  1. “Regular Mode” for Admins - Vague toggle concept without implementation details
  2. Plan to Support Sheet Music - Mentions JS libraries but lacks use cases or specs
  3. AI That Monitors Logs - Vague AI application without clear functionality
  4. Voice Messages for Discourse - No technical specifications or implementation approach
  5. Visual Map of Users - Missing privacy considerations and technical specs
  6. Microblogging Feature - Conceptual idea without clear UX implementation
  7. Use AI to Create Glossary - Unclear purpose and implementation approach
  8. Shared Topics Between Instances - Complex federation concept without implementation path
  9. Kanban Interface to Categories - More of a development intent than feature specification
  10. Reward Being Read - Abstract concept without implementation details

Key Recommendations

Strategic Focus: Prioritize safety features (True Block, PM permissions), core improvements (search, notifications), and enterprise features (SCIM, accessibility) for maximum impact.

Quick Wins: Focus on UI enhancements and simple configuration additions for immediate user satisfaction while building momentum.

Consolidation Needed: Group similar requests into coherent feature sets to avoid duplicate development efforts and create more comprehensive solutions.

Clarification Required: Engage with requesters of poorly defined features to gather detailed specifications before considering development resources allocation.