Improve README (spelling and clarifications)
This commit is contained in:
parent
95f4964f1f
commit
62983d7ddd
21
README.md
21
README.md
@ -1,18 +1,16 @@
|
|||||||
What is randrss?
|
What is randrss?
|
||||||
================
|
================
|
||||||
Normal RSS readers usually fetch all feeds more or less at the same time
|
Normal RSS readers usually fetch all feeds more or less at the same time
|
||||||
at constant intervals. This leaves a signature for anyone who observes
|
at constant intervals. Anyone who monitors internet traffic can
|
||||||
internet traffic. By looking for this pattern, you are more easily
|
look for this pattern and therefore identify users.
|
||||||
identified.
|
|
||||||
|
|
||||||
randrss fetches all your feeds at random intervals at an random order
|
randrss fetches all your feeds at random intervals at an random order
|
||||||
over a certain period of time. The feeds will be downloaded and you then
|
over a certain period of time. The feeds will be downloaded and you then
|
||||||
serve tjhem using you a web server. The added benefits of this approach are
|
serve them using your own web server. This way you also don't have to
|
||||||
that you don't have to worry about how your client deals with cookies
|
worry about how your client deals with cookies etc.
|
||||||
etc.
|
|
||||||
|
|
||||||
Also, by having only one client fetching the feeds and your readers
|
Additionally, by having only one client fetching the feeds and your readers
|
||||||
pointed to the randrss's downloaded feeds, you avoid certain trackers
|
pointed to andrss's downloaded feeds, you avoid certain trackers
|
||||||
that may identify you across devices (google's feed proxy, cloudflare),
|
that may identify you across devices (google's feed proxy, cloudflare),
|
||||||
because it's very likely that the combination of feeds you read are
|
because it's very likely that the combination of feeds you read are
|
||||||
unique. As your feeds are on a single server now, you can isolate your
|
unique. As your feeds are on a single server now, you can isolate your
|
||||||
@ -21,16 +19,15 @@ 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
|
not contact the feed servers in any way. In Thunderbird, set
|
||||||
browser.chrome.favicons to false.
|
browser.chrome.favicons to false.
|
||||||
|
|
||||||
The only drawback of this approach is that the time you get new feeds
|
A drawback of this approach is that the time you get new feeds
|
||||||
is delayed, but that should be acceptable.
|
is delayed, but that should be acceptable.
|
||||||
|
|
||||||
By default, torsocks is used to fetch the feeds.
|
|
||||||
|
|
||||||
Usage
|
Usage
|
||||||
=====
|
=====
|
||||||
Fetchers
|
Fetchers
|
||||||
--------
|
--------
|
||||||
Scripts that request the feeds while trying to look like a normal client.
|
Scripts that request the feeds while trying to look like a normal client.
|
||||||
|
By default, they are launched with "torsocks".
|
||||||
|
|
||||||
Config file
|
Config file
|
||||||
-----------
|
-----------
|
||||||
@ -48,7 +45,7 @@ randrss [path to directory containing the config files] [fetchersfile]
|
|||||||
fetchersfile: take a look at the example file in the repo. It lists
|
fetchersfile: take a look at the example file in the repo. It lists
|
||||||
the paths to the fetchers that will randomly be used.
|
the paths to the fetchers that will randomly be used.
|
||||||
|
|
||||||
optional third paramater: "syncnow". Do not sleep for random intervals.
|
optional third parameter: "syncnow". Do not sleep for random intervals.
|
||||||
Fetch all feeds and exit.
|
Fetch all feeds and exit.
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user