crtxcr
/
randrss
1
0
Fork 0
Code Issues 3 Pull Requests Releases Wiki Activity

updated README

This commit is contained in:
Albert S. 2019-08-27 13:42:10 +02:00
parent 52df5c69e4
commit 39e724dc90
1 changed files with 17 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
README.md
View File

@ -4,23 +4,26 @@ Normal RSS readers usually fetch all feeds more or less at the same time
at constant intervals. Anyone who monitors internet traffic can at constant intervals. Anyone who monitors internet traffic can
look for this pattern and therefore identify users. look for this pattern and therefore identify users.
randrss fetches all your feeds at random intervals at an random order In contrast, randrss fetches all your feeds at random intervals
over a certain period of time. The feeds will be downloaded and you then and also at an random order. The feeds will be downloaded and you then
serve them using your own web server. This way you also don't have to serve them using your own web server. It poorly attemps to look like
worry about how your client deals with cookies etc. normal browsers while fetching the feeds, and uses Tor by default.
Additionally, by having only one client fetching the feeds and your readers This has several advantages. You don't need to worry how your
pointed to andrss's downloaded feeds, you avoid certain trackers client deals with cookies for example. Since you point your favorite
that may identify you across devices (google's feed proxy, cloudflare), RSS client to randrss's downloaded feeds, you avoid certain trackers
because it's very likely that the combination of feeds you read are like google's feed proxy and cloudflare. They may identify you across
unique. As your feeds are on a single server now, you can isolate your devices as it is very likely that the combination of feeds you read
RSS reader to its own network container so it can only contact your is unique. In the context of "hardening", this is also useful to
server. This is probably what you should do to be sure your client does restrict the servers your RSS client can contact (for instance,
not contact the feed servers in any way. In Thunderbird, set by using network namespaces, etc.).
browser.chrome.favicons to false.
A 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. Furthermore, this tool
might leave a distinct signature itself. It should still be
better than fetching everything at once, however it's primary purpose
is to hide you from the mentioned (potential) trackers.
Usage Usage
===== =====