On November 1st 2025 I’m going to dismantle the entirety of infrastructure that powers tt-rss.org, cgit, this forum, and other related sites. The reasons for this are many but the tl;dr is that I no longer find it fun to maintain public-facing anything, be it open source projects or websites. As for tt-rss specifically, it has been ‘done’ for years now and the “let’s bump base PHP version and fix breakages” routine is not engaging in the slightest. You have a month to mirror any interesting re...
  • vegetaaaaaaa@lemmy.worldOPEnglish
    23·
    7 months ago

    I have copied the latest git revision c67b943aa894b90103c4752ac430958886b996b2 from https://gitlab.tt-rss.org/tt-rss/tt-rss to my gitea instance which is mirrored to https://gitlab.com/nodiscc/tt-rss and https://github.com/nodiscc/tt-rss.

    I don’t intend to make changes or bugfixes (it’s working fine), but I will try to keep it compatible with the PHP version in Debian stable, since I’ve been using it for years and would really like to keep doing so.

    • cyberwolfie@lemmy.mlEnglish
      3·
      7 months ago

      I like FreshRSS - I also have some readers that connect to my instance, like FluentReader that provides a better full article view, but I mostly use FreshRSS directly these days.

      • tehWrapper@lemmy.worldEnglish
        1·
        7 months ago

        Looks like it supports a wide range of readers with two different API .

        FreshRSS supports access from mobile / native apps for Linux, Android, iOS, Windows and macOS, via two distinct APIs: Google Reader API (best), and Fever API (limited features, less efficient, less safe).