← Back to home
Comparison · Collab

CommaFeed vs LibrePhotos

A side-by-side editorial comparison of CommaFeed and LibrePhotos — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:self-hosted

CommaFeed vs LibrePhotos: at a glance

FeatureCommaFeedLibrePhotos
SectorCollabCollab
Velocity score5.00.0
Sparks · 30d00
Top themesrss-reader, self-hosted, security-hardening, ssrfself-hosted, photo-management, monorepo, semver
Last editorial update4h ago12d ago
WebsiteVisit →Visit →

What is CommaFeed?

CommaFeed is patching its way through the attack surface a self-hosted reader inherits

CommaFeed's 7.x line has become a sustained security pass. The newest patch closes Host header injection on the password recovery endpoint and adds a commafeed.password-recovery-public-base-url setting so the email base URL is configured rather than taken from the request. Behind it: local address blocking made secure by default alongside Google Reader API support in 7.3.0, javascript: URLs filtered at parse time in 7.2.1, and SSRF limits on the image proxy in 7.2.0.

Read the full CommaFeed trajectory →

What is LibrePhotos?

LibrePhotos folded five repositories into one and started versioning like a real product.

The project spent April through June on structural work rather than features. Backend, frontend, mobile app, docs, and Docker deployment were merged into a single repository with each project's git history preserved, and the versioning scheme moved to semver, producing the first 1.0.x releases. The releases since are consolidation: authorization hardening on the user API, a fix for the validation popups that hardening caused for non-admin users, and repeated pinning fights to keep the GPU image building.

Read the full LibrePhotos trajectory →

CommaFeed vs LibrePhotos: editorial side-by-side

C
CommaFeed
COLLAB
5.0

CommaFeed is patching its way through the attack surface a self-hosted reader inherits

◆ Current state

CommaFeed's 7.x line has become a sustained security pass. The newest patch closes Host header injection on the password recovery endpoint and adds a commafeed.password-recovery-public-base-url setting so the email base URL is configured rather than taken from the request. Behind it: local address blocking made secure by default alongside Google Reader API support in 7.3.0, javascript: URLs filtered at parse time in 7.2.1, and SSRF limits on the image proxy in 7.2.0.

◆ Where it's heading

Every release in this stretch closes a path where content or a request from outside the instance was trusted too far - feed URLs reaching internal addresses, proxied images, javascript: links, and now a header shaping an outbound email. That is the checklist of a project being run as a multi-user hosted service rather than a single-user tool, and it follows directly from the 7.0.0 decision to sandbox filter expressions. Feature work continues in parallel but is clearly the smaller half.

◆ Prediction

The remaining untrusted-input surfaces - OPML import and the feed fetcher's redirect handling - are the likely next targets. The pattern of shipping each fix as its own patch release should continue rather than batching them.

L0.0

LibrePhotos folded five repositories into one and started versioning like a real product.

◆ Current state

The project spent April through June on structural work rather than features. Backend, frontend, mobile app, docs, and Docker deployment were merged into a single repository with each project's git history preserved, and the versioning scheme moved to semver, producing the first 1.0.x releases. The releases since are consolidation: authorization hardening on the user API, a fix for the validation popups that hardening caused for non-admin users, and repeated pinning fights to keep the GPU image building.

◆ Where it's heading

This is a self-hosted project doing the unglamorous work that makes contribution and release possible at scale — one repo, unified CI and Dockerfiles, predictable version numbers. The backend changes running underneath it are about resilience rather than capability: retrying transient face-service drops, hardening metadata extraction against exif-service failures, preserving scan baselines during job cleanup. The recurring Renovate-versus-GPU-pin conflicts suggest the dependency story for the CUDA image is still fragile.

◆ Prediction

With the monorepo and semver in place, the next releases are likely to return to user-facing features on a 1.x line rather than more restructuring. The GPU image pins look like they will need a more durable fix than repeated Renovate overrides.

Alternatives to CommaFeed and LibrePhotos

Other Collab products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either CommaFeed or LibrePhotos.

See all CommaFeed alternatives → · See all LibrePhotos alternatives →

Recent activity from CommaFeed and LibrePhotos

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoCommaFeedHost header injection closed on the password recovery endpoint
  2. 8d agoCommaFeedGoogle Reader API support and secure-by-default local address blocking
  3. 16d agoCommaFeedjavascript: URLs now filtered at parse time, not just in the client
  4. 1mo agoCommaFeedFeed-declared icons, starred-entry search, and image-proxy SSRF limits
  5. 1mo agoLibrePhotos1.0.3 - Fix user list popup for non-admin users
  6. 1mo agoLibrePhotosGPU image: restore the onnxruntime and timezonefinder pins
  7. 1mo agoLibrePhotosGPU image: stop Renovate collapsing the scikit-learn pin
  8. 1mo agoLibrePhotosSwitching to semantic versioning
  9. 1mo agoLibrePhotosLibrePhotos moves backend, frontend, mobile and docs into one monorepo
  10. 4mo agoCommaFeedMobile unread count in the header plus a graceful refresh shutdown
  11. 5mo agoCommaFeedFilter expressions move from JEXL to a sandboxed visual query builder
  12. 7y agoLibrePhotos2019 release candidate: timezone environment variable

Frequently asked questions

What is the difference between CommaFeed and LibrePhotos?

Both compete on the same themes — self-hosted — within Collab. CommaFeed is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is CommaFeed better than LibrePhotos?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. CommaFeed is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.

What are the best alternatives to CommaFeed?

Top CommaFeed alternatives in Collab are ranked by recent ship velocity. Browse the "CommaFeed alternatives" section above for the current picks, or visit /alternatives/commafeed for the full list with editorial commentary on each.

What are the best alternatives to LibrePhotos?

Top LibrePhotos alternatives in Collab are ranked by recent ship velocity. Browse the "LibrePhotos alternatives" section above for the current picks, or visit /alternatives/librephotos for the full list with editorial commentary on each.