2017-04-15 16:24:28 +02:00
|
|
|
What is randrss?
|
|
|
|
================
|
|
|
|
Normal RSS readers usually fetch all feeds more or less at the same time
|
2017-08-17 10:34:35 +02:00
|
|
|
at constant intervals. Anyone who monitors internet traffic can
|
|
|
|
look for this pattern and therefore identify users.
|
2017-04-15 16:24:28 +02:00
|
|
|
|
|
|
|
randrss fetches all your feeds at random intervals at an random order
|
2017-08-16 21:17:01 +02:00
|
|
|
over a certain period of time. The feeds will be downloaded and you then
|
2017-08-17 10:34:35 +02:00
|
|
|
serve them using your own web server. This way you also don't have to
|
|
|
|
worry about how your client deals with cookies etc.
|
2017-04-15 16:24:28 +02:00
|
|
|
|
2017-08-17 10:34:35 +02:00
|
|
|
Additionally, by having only one client fetching the feeds and your readers
|
|
|
|
pointed to andrss's downloaded feeds, you avoid certain trackers
|
2017-04-15 16:24:28 +02:00
|
|
|
that may identify you across devices (google's feed proxy, cloudflare),
|
|
|
|
because it's very likely that the combination of feeds you read are
|
2017-04-16 21:00:34 +02:00
|
|
|
unique. As your feeds are on a single server now, you can isolate your
|
2017-08-16 21:17:01 +02:00
|
|
|
RSS reader to its own network container so it can only contact your
|
2017-04-16 21:00:34 +02:00
|
|
|
server. This is probably what you should do to be sure your client does
|
|
|
|
not contact the feed servers in any way. In Thunderbird, set
|
|
|
|
browser.chrome.favicons to false.
|
|
|
|
|
2017-08-17 10:34:35 +02:00
|
|
|
A drawback of this approach is that the time you get new feeds
|
2017-04-16 21:00:34 +02:00
|
|
|
is delayed, but that should be acceptable.
|
|
|
|
|
2017-04-15 16:24:28 +02:00
|
|
|
Usage
|
|
|
|
=====
|
2017-08-16 21:17:01 +02:00
|
|
|
Fetchers
|
|
|
|
--------
|
2017-08-17 10:34:35 +02:00
|
|
|
Scripts that request the feeds while trying to look like a normal client.
|
|
|
|
By default, they are launched with "torsocks".
|
2017-08-16 21:17:01 +02:00
|
|
|
|
|
|
|
Config file
|
|
|
|
-----------
|
|
|
|
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.
|
2017-04-15 16:24:28 +02:00
|
|
|
|
2017-08-17 10:34:35 +02:00
|
|
|
optional third parameter: "syncnow". Do not sleep for random intervals.
|
2017-08-16 21:17:01 +02:00
|
|
|
Fetch all feeds and exit.
|
2017-04-15 16:24:28 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|