infomate.club

Why it's ranked here

It solves a clear reading problem with an unusually understandable operating model. Curated boards reduce subscription noise, while filtering, caching, article extraction, and summaries add practical value. The author explicitly calls it a weekend pet project, however, and says it has no tests, so treat it as useful source code rather than production-ready infrastructure.

What's good

Configuration is centralized and expressive: curators can group feeds, hide boards, require login, disable page parsing, and exclude articles by title terms. Feed parsing combines RSS discovery with page extraction, while safeguards skip unsuitable or excessively large content. Heavy page caching and scheduled refresh jobs keep presentation work separate from ingestion.

Tradeoffs

Operation requires more than starting a web server. PostgreSQL stores parsed data, three scheduled scripts handle initialization, updates, and cleanup, and production needs a reverse proxy plus repository secrets. The project has no tests, uses several pinned older dependencies, and describes neither formal architecture nor business-grade support.

How to use it well

Use it when a curator wants a self-hosted, browser-based briefing assembled from known feeds. Start with Docker, define focused boards, disable parsing for troublesome sources, and apply title conditions sparingly. It fits scheduled discovery and scanning. It does not replace a personal subscription reader, notification service, or fully managed publishing platform.

Observed

License

Apache 2.0

Primary language

Python

Interface

Django web application with browser pages and a Telegram-channel feed endpoint

Packaging

Setuptools package named infomate, declared for POSIX

Local installation

Docker Compose build and startup workflow

Data store

PostgreSQL

Quality checks

Make targets run flake8 and mypy; the README states there are no tests