Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Current Limitations

While Listsome is functional, it has some limitations to be aware of. This page explains what’s not implemented yet and how it affects your experience.

Search Capabilities

Current State

  • Simple text matching only - No advanced search features
  • No fuzzy matching - Exact spelling required
  • Limited filtering - Only by content type
  • No relevance ranking - Results ordered by confidence score only

Impact

  • Search results may include irrelevant matches
  • Typos in search queries won’t find results
  • Can’t filter by difficulty, time, or materials
  • Results may not be in the most useful order

Workaround

  • Use specific, correctly spelled keywords
  • Add more context to search terms
  • Use content type filters to narrow results
  • Parse more content to improve result relevance

Content Discovery

Current State

  • Manual URL entry only - No automatic crawling
  • No content suggestions - No “related content” features
  • Limited parsing strategies - May not work with all websites
  • No batch processing - One URL at a time

Impact

  • Can’t discover content automatically
  • No recommendations for similar content
  • Some websites may not parse well
  • Time-consuming to add many URLs

Workaround

  • Manually find and add content you’re interested in
  • Use RSS feeds to stay updated with known sources
  • Focus on well-structured websites
  • Build your collection gradually

Data Storage

Current State

  • SQLite only - No multi-user support
  • No PostgreSQL backend - Limited scalability
  • Single-user focused - Not designed for teams
  • No data export/import - Difficult to migrate

Impact

  • Can’t share collections with others
  • Limited to personal use
  • No collaboration features
  • Data stays on your local machine

Workaround

  • Use the platform for personal content management
  • Share RSS feed URLs for others to subscribe
  • Export content through RSS feeds
  • Run your own instance for personal use

User Interface

Current State

  • Basic HTML interface - No advanced features
  • No user accounts - No personalization
  • No saved searches - Can’t save favorite queries
  • No content management - Limited organization tools

Impact

  • Can’t save preferences or settings
  • No personalized recommendations
  • Can’t organize content into collections
  • Limited content management features

Workaround

  • Use browser bookmarks for important searches
  • Manually organize content through RSS feeds
  • Use external tools for content organization
  • Focus on core discovery and search features

Content Processing

Current State

  • Rule-based parsing only - No AI/ML enhancement
  • No duplicate detection - May have duplicate content
  • Limited content types - Basic classification
  • No quality scoring - All content treated equally

Impact

  • Parsing may miss complex content structures
  • Duplicate content may appear in results
  • Content classification may be inaccurate
  • No automatic quality assessment

Workaround

  • Focus on well-structured, simple content
  • Manually review and remove duplicates
  • Use confidence scores to gauge parsing quality
  • Parse content from reputable sources

RSS Feeds

Current State

  • Basic feed generation - Limited customization
  • No feed management - Can’t edit or delete feeds
  • No social features - Can’t share or follow feeds
  • Limited feed formats - Basic RSS/Atom only

Impact

  • Can’t customize feed content or appearance
  • No way to manage multiple feeds
  • Can’t collaborate on feed curation
  • Limited integration options

Workaround

  • Use feeds as-is for basic subscription
  • Share feed URLs manually
  • Use external feed management tools
  • Focus on content discovery rather than feed management

Federation & Social Features

Current State

  • Basic ActivityPub endpoints - WebFinger, Actor, Inbox exist
  • Blogroll discovery - Follow other instances via RSS aggregation
  • No full ActivityPub flow - Follow/Accept not fully implemented
  • No fediverse connectivity - Can’t connect to Mastodon/Lemmy

Impact

  • Can discover content from followed instances
  • Can’t accept/manage followers yet
  • Limited social interaction features
  • No connection to broader fediverse

Workaround

  • Add instances to your blogroll manually
  • Share your RSS feed URL for others to subscribe
  • Use RSS readers to follow content
  • Focus on blogroll-based discovery

Performance & Scalability

Current State

  • Single-threaded processing - Limited performance
  • No caching - Every request processes from scratch
  • SQLite limitations - Not designed for high traffic
  • No background processing - Everything happens synchronously

Impact

  • Slow response times with large content databases
  • No caching for frequently accessed content
  • Limited concurrent users
  • Resource-intensive operations

Workaround

  • Keep content database manageable in size
  • Use for personal or small team use
  • Avoid very large search result sets
  • Run on capable hardware

Why These Limitations Exist

Design Philosophy

These limitations are intentional and by design:

  • Start simple - Focus on core functionality first
  • Personal use focus - Designed for individual users initially
  • Progressive enhancement - Build advanced features over time
  • Resource efficiency - Keep requirements minimal

Development Approach

  • Phase-based development - Core features first, advanced features later
  • User feedback driven - Build what users actually need
  • Open source model - Community can contribute improvements
  • Sustainability - Focus on maintainable, reliable features

Future Improvements

These limitations will be addressed in future updates:

  • Enhanced search with full-text indexing and relevance ranking
  • Full ActivityPub flow with Follow/Accept management
  • Federated blogrolls for cross-instance discovery
  • Fediverse connectivity to connect with Mastodon/Lemmy
  • Multi-user support with PostgreSQL backend

Getting Help

If You Encounter Issues

  • Check this page to see if it’s a known limitation
  • Try the workarounds suggested above
  • Review the future features to see if it’s planned
  • Check the getting started guide for basic usage

Contributing

  • Report issues on the project repository
  • Suggest improvements or new features
  • Help with documentation or testing
  • Contribute code for new features

Next Steps

💡 Remember: These limitations represent the current state, not the final vision. The platform is designed to grow and improve over time.