Site Info
This site is generated with Emacs using org-mode, adding my own hacks on top of ox-html. This has proven much more configurable than my previous setup (using Pelican). It has also finally forced me to actually learn to use the power of Emacs afforded by lisp.
This site is currently accessible from the following URLs:
-
This git repository is the source of truth for this website. It is hosted by github pages with a CNAME file pointing to reillyraab.com.
-
This domain is registered with Namecheap, using Cloudflare’s nameservers.
Cloudflare provides SSL, caching, and DNS resolution with A records pointing to github.io’s IP addresses.
http://users.soe.ucsc.edu/~rraab (redirects to my CV)
My user home directory with SOE has an .htaccess file that reads
RedirectMatch 301 ^/$ https://reillyraab.com/about.html
Privacy
I store no information about you whatsoever.
Network resources (javascript, css, fonts, etc.), including library code, have been copied (consistent with open-source licenses) and are hosted by this site itself in order to avoid content delivery networks (which can track you).
That being said, I’m using Cloudflare, which means all your network requests can be tracked anyway (by Cloudflare):
Third-Party Privacy Policy
By using this site, you are an end user of Cloudflare’s services.
TL;DR: Cloudflare is tracking which pages you look at on this website.
Cloudflare acts as a reverse proxy for reillyraab.com and handles HTTPS encryption / decryption with your browser, technically acting as a man-in-the-middle for communication with the origin server at github.io.
For all intents and purposes, when your browser is communicating with this site, it’s communicating with Cloudflare’s servers. While HTTPS might hide which specific interactions you have with this site from your ISP, this does not hinder Cloudflare in seeing your specific network requests for the content of this site (that is, which pages you read). The lack of end-to-end encryption in this configuration has limited consequences, since the only interaction this website provides is serving you rather mundane, static content, but it may not be appropriate for all types of online services.
We collect End Users’ information when they use our Customers’ websites, web applications, and APIs. This information may include but is not limited to IP addresses, system configuration information, and other information about traffic to and from Customers’ websites (collectively, “Log Data”).
…
Cloudflare may aggregate data we acquire about our Customers and their End Users, including the Log Data described above… Non-personally identifiable, aggregated data may be shared with third parties.
– Cloudflare’s privacy policy