From 6a9849fe0943486790a3439bbb98157915647413 Mon Sep 17 00:00:00 2001 From: Albert S Date: Wed, 19 Aug 2020 19:43:06 +0200 Subject: [PATCH] README.md: Minor improvements --- README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 312b41f..8e06eb8 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,7 @@ like google's feed proxy and cloudflare. They may identify you across devices as it is very likely that the combination of feeds you read is unique. In the context of "hardening", this is also useful to restrict the servers your RSS client can contact (for instance, -by using network namespaces, etc.). +by using network namespaces or [qsni](https://gitea.quitesimple.org/crtxcr/qsni)). A drawback of this approach is that the time you get new feeds is delayed, but that should be acceptable. Furthermore, this tool @@ -38,12 +38,17 @@ For each feed, an individual config file is used. Example: A simple example config file for kernel.org: + +``` FEED_URL="https://www.kernel.org/feeds/kdist.xml" FEED_OUTPUT="/var/www/feeds/kernelreleases.feed" +``` Launch ------ +``` randrss [path to directory containing the config files] [fetchersfile] +``` fetchersfile: take a look at the example file in the repo. It lists the paths to the fetchers that will randomly be used.