Redirection of news feed

It's not always simple to animate a project, especially to write articles to keep the community aware of what's new. It's been more than 2 years since the last article on the FreshRSS blog and we're not very proud of it. It is quite ironic for a feed aggregator team to have an inactive feed, isn't it? (credit to Kevin Papst for this one!) We didn't sit idly by for all that and we released 12 (twelve!) new versions of FreshRSS since our last article, that's almost 6 per year.

After few discussions, we have decided to redirect the website feed to the FreshRSS GitHub feed which announce new releases. At least, you should hear of us again! :) For the moment, we will not kill the blog so articles will stay here.

The redirection will become effective within the next week.

Also, if you're interested in the project, please note our community is always pleased to welcome new contributors. There is still work to accomplish and fresh ideas can help us to make FreshRSS a better aggregator.

FreshRSS 1.2.0 is the new stable

After nearly 9 months, we are proud to announce a new stable version for FreshRSS. This 1.2.0 brings a more powerful interface for administrators, some cool features (such as support for PubSubHubbub) and fix a lot of annoying bugs. The complete list of changes is in our changelog.

Note that FreshRSS is now supported in 6 languages (Czech, Dutch, English, French, German and Italian): it's always amazing to see people all around the world helping us to translate this software. A big thanks to our translators!

We hope you will enjoy these new versions (1.3.0-beta is released at the same time but there are both identical).

[Marien speaking] Also, it's time to announce my “retirement” from the project. I started this project 3 years ago as a personal RSS aggregator software but realized soon after there was potential to reach more people than just me. Today, I'm quite proud to have reached this level of quality but I don't find my own satisfaction to work on FreshRSS anymore since I consider the product is nearly finished. Also, I have a lot of other projects in my mind that I want to start.

Leaving the project doesn't mean its dead but maybe a new start. I worked during this last year to give all the keys to the community to be able to maintain the project alive and I'm still working on but it's nearly finished. One of my latest tasks will be to write a post to explain how I see potential improvements and restarting the project from scratch is one of them (if you are motivated :D).

I'll continue to keep an eye on FreshRSS and there are still Alexandre and Alexis from time to time on GitHub or on the mailing lists so you are very welcomed to help the project!

You can comment on GitHub.

FreshRSS supports PubSubHubbub

We just released FreshRSS 1.1.2-beta which comes with some nice features such as the possibility to create account for anonymous users, proxy configuration and… PubSubHubbub support!


We know it's quite hard to pronounce (we'll short it by “PuSH” later) but we really think you will LOVE this feature. So what is PuSH? It is a protocol which was initially designed to extend Atom and RSS protocols to add them real-time notifications. In few words, you can receive new articles in FreshRSS as soon as they are published!

For that, we need a new actor: a “hub”. Hubs are (or can be) independent from publishers (e.g. this blog) and subscribers (e.g. FreshRSS). Publishers write articles and post a notification to the hub. Once the hub received the notification, it calls all subscribers to send them the new article. Quite simple, isn't it?

FreshRSS ♥ PuSH

PuSH requires subscribers expose a public access point: FreshRSS' one is located at ./p/api/pshb.php. It means this file must be accessible from an external server and we realised that's not always the case (especially when we develop on our personal machines). To avoid unwanted PuSH requests, we introduced two new configuration parameters (in ./data/config.php):

  • base_url which corresponds to the most basic public URL of your FreshRSS instance (e.g.
  • pubsubhubbub_enabled is set at true to use PuSH or false otherwise. If your server is corresponding to a “localhost” one, it is set to false automatically.

These two new parameters are required to use PuSH and are created during installation or automatic update. If you do the update with Git or manually, you have to add these parameters by yourself!

We need your help!

So what's next then? We would enjoy to see PuSH spreads the world! And guess what? It's really easy. You have only one mission: add a hub information to your RSS / Atom feed.

  • If you are using a self-hosted Wordpress blog, just install this plugin created by the Wordpress team. It includes a hub feature directly in your Wordpress;
  • If you are not using Wordpress, have a look at Superfeedr documentation for publishers;
  • If you don't own any blog or website, just speak about PuSH around you and let the web being a bit better :).

If you want to learn more about PuSH protocol, you can have a look at the official GitHub page or read its Wikipedia page. Also, there is this nice presentation you could be interested in (but it's a Google doc ;)).

You can comment on GitHub.

Announce of the mailing lists

Did you know that FreshRSS has two mailing lists since few weeks?

In order to welcome our users and developers, we decided to open them so we can discuss about FreshRSS without forcing the use of GitHub and still keeping a community discussion.

  • is mainly for users: if you have questions and you're not sure if it's interesting to ask them on GitHub, you can join us on this mailing. We'll also announce development progress once a month so you'll always know what will be the next great FreshRSS features.
  • is destined to developers only. If you want to know more about the source code, what are the libraries included in FreshRSS, how do pull requests work, etc. this is the place to be!

Mailing lists are hosted on our server and you can subscribe to one or both of them by following this link. Archives are public so you are able to see what have already been written, especially the “welcome-message”.

Note that if you want to participate (i.e. send mails on mailings) it is required to subscribe to them. English is the preferred language but since FreshRSS has a great French-community, it may happen that French is used instead. If you want to participate to such discussions, don't hesitate to ask to continue in English.

We are waiting for you!

You can comment on GitHub.

FreshRSS gets a new website

We have worked a lot to improve community processes since last weeks. Today we are opening a new section on the website: a blog!

You were a lot to ask for an official English thread associated to a RSS feed to follow us (that was the last straw for FreshRSS!). It is now available so don't forget to add our feed in your favourite aggregator.

The paint is still wet but things should work smoothly since the blog is very basic.

Under the hood, there is a static website powered by Pelican. The initial theme has been ported to this great static website generator tool and improved a bit (e.g. the header navbar). It is already available on GitHub (FreshRSS/Freshican) such as the content (FreshRSS/

As you may notice, there is no possibility to comment directly our articles: we want to avoid spam and moderation. Nevertheless you can meet us on GitHub, there will be a ticket associated to each article!

Since we want to adopt a “community-friendly” process, you will have the possibility to modify and/or write articles in order to be published here. If you want to contribute to this blog, please fork the project on GitHub, create a new branch, write your article and send a pull request. The only condition will be that you must speak about RSS/Atom aggregation :).

To finish, stay in touch with us since there are still some great news to come in the next few days!

You can comment on GitHub.