I have once again been tinkering with the Privacy Policy in a probably vain effort to deal with a regulatory climate increasingly unfavorable to running any kind of website, even a purely personal blog. Since I haven’t been updating this blog in ages and its traffic is likely near-zero, it’s probably a moot point, but there will likely be further tinkering in the coming weeks. (ETA: I did again on Nov. 2, Nov. 3, Nov. 4, Nov. 5, Nov. 7, Nov. 8, Nov. 9, Nov. 10, Nov. 11, Nov. 13, Nov. 14, Nov. 15, Nov. 16, Nov. 17, Nov. 18, Nov. 19, Nov. 20, Nov. 23, Nov. 24, Nov. 25, Nov. 27, Dec. 3, Dec. 11, Dec. 19, Dec. 21, Dec. 22, Dec. 24, Dec. 25, Dec. 26, Dec. 27, and Dec. 28! I published a much more extensively revised version on December 29, with further tinkering Dec. 30, Dec. 31, Jan. 1, Jan. 2, Jan. 3, Jan. 4, Jan. 5, Jan. 6, Jan. 7, Jan. 8, Jan. 10, Jan. 12, Jan. 13, Jan. 14, Jan. 15, Jan. 16, Jan. 17, Jan. 18, Jan. 20, Jan. 21, Jan. 22, Jan. 23, Jan. 24, Jan. 26, Jan. 28, Jan. 29, Jan. 30, Jan. 31, Feb. 1, Feb. 2, Feb. 3, Feb. 4, Feb. 6, Feb. 7, Feb. 8, Feb. 10, Feb. 11, Feb. 12, Feb. 15, Feb. 16, Feb. 17, Feb. 18, Feb. 19, Feb. 20, Feb. 22, Feb. 23, Feb. 24, Feb. 25, Feb. 26, Feb. 27, Feb. 28, Feb. 29, March 2, March 3, March 4, and almost every day after that because the State of California is determined to stamp out people like me, and also free speech and common sense.)

Leave a Comment

Your email address will not be published. Required fields are marked *

Commenting also signifies your acceptance of the Comment Policy — please read it first! Comments may be moderated.

Privacy Preference Center

Privacy and Cookie Preferences

These strictly necessary cookies manage your cookie and privacy preferences. There will typically be several such cookies, each beginning with "gdpr" (e.g., gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, and gdpr[consent_types]). They normally expire after about one year. If you delete or disable these cookies, your existing preferences will be lost and you may not be able to save your privacy settings for this website.


Accessibility Settings

If you change certain aspects of the site's appearance using the accessibility sidebar, it may set these cookies to manage and remember your settings. The wahFontColor and wahBgColor cookies, which are set if you alter the site's color scheme, normally expire after about 14 days, but you can remove them immediately by clicking the "Restore Defaults" button on the sidebar. I may sometimes present an alternative version of the sidebar offering different options, which may set the a11y-desaturated, a11y-high-contrast, and a11y-larger-fontsize cookies if you change those settings. These a11y cookies normally expire after about seven days, but are removed immediately if you restore the applicable settings to their default values.

wahFontColor, wahBgColor, a11y-desaturated, a11y-high-contrast, a11y-larger-fontsize

Age Verification

Viewing certain site content may require you to first verify your age by entering your date of birth. If your birth date indicates that you are 18 or older, the website places the age_gate cookie (whose value is "1," meaning "yes, passed") to allow you to access age-restricted content. The cookie remains active for up to 14 days if you click the "Remember me" check box when you enter your birth date; otherwise, the cookie normally expires when you close your browser. If your birth date indicates that you are NOT 18 or older, the website may place the age_gate_failed cookie (whose value is also "1") to prevent you from trying again to access age-restricted content. (The website does not retain your birth date or your age. See the "Age Verification" section of the Privacy Policy for more information about how the age verification system works.)

age_gate, age_gate_failed


When you leave a comment, you may have the option save your information for future comments, storing the info in these cookies. The cookies are not placed unless you select that option when leaving a comment. They normally expire in just under one year, but you can delete the cookies in your browser at any time.

comment_author, comment_author_email, comment_author_url

YouTube Videos

These third-party cookies may be set by YouTube (which is now owned by and a trademark of Google LLC) in connection with embedded videos, for purposes such as managing video settings (such as tailoring the playback to your connection speed), storing video preferences, providing certain functionality such as allowing you to stop and restart a video without losing your place, showing you advertisements, associating your video viewing and other activity with your Google account (if any), and ensuring proper functioning of the service. The cookies may be set by various domains, including (but not necessarily limited to) youtube.com, youtube-nocookie.com, googlevideo.com, ytimg.com, google.com, accounts.google.com, and/or doubleclick.net. Some are session cookies that disappear when you close your browser; others may remain on your device as long as your browser settings permit. Some cookies Google sets in connection with your Google account and/or advertising served through YouTube (which may include others not listed here) are persistent cookies that may remain in your browser for as long as your individual browser settings permit. See Google's "Types of Cookies Used by Google" page for more information about the functions of their various cookies. To learn more about how Google uses the information they collect, see the Google Privacy Policy.

yt.innertube::nextId, yt.innertube::requests, yt-remote-cast-installed, yt-remote-connected-devices, yt-remote-device-id, yt-remote-fast-check-period, yt-remote-session-app, yt-remote-session-name, recently_watched_video_id_list, use_hotbox, demographics, GPS, LOGIN_INFO, PREF, VISITOR_INFO1_LIVE, YSC, AID, ANID, APISID, CONSENT, DSID, FLC, GAPS, IDE, NID, HSID, OTZ, SID, SNID, SIDCC, TAID, exchange_uid, 1P_JAR

Vimeo Videos

These third-party cookies may be set by Vimeo in connection with embedded videos, for purposes such as managing video settings, storing video preferences, providing certain functionality (such as allowing you to pause a video at a particular point), associating your video viewing and other activity with your Vimeo account (if you have one), showing you advertising, and compiling user analytics data. (The cookies whose names begin with "_ga" and "_ut" are associated with Google Analytics, which is a trademark of Google LLC and subject to the Google Privacy Policy); the ones whose names begin with "_ceg" are associated with the Crazy Egg web analytics service; the ones that begin with "optimizely" are associated with the Optimizely digital experience optimization service; and the ones beginning with "adsense" or listed in all caps are associated with Google advertising). Vimeo's Cookie Policy does not currently disclose the normal durations of their cookies, but some are persistent cookies that may remain in your browser for as long as your individual browser settings permit; some Google Analytics cookies can persist for up to two years. For more information about how Vimeo uses the information they collect, see the Vimeo Privacy Policy.

_abexps, aka_debug, clips, continuous_play_v3, embed_preferences, has_logged_in, is_logged_in, jsessionID, player, search_click_position, Sarchtoken, stats_end_date, stats_start_date, sst_aid, uid, v6f, vimeo, vuid, _ga, _gads, _utma, _utmb, _utmc, _utmv, _utmz,_ceg.s, _ceg.u, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, APISID, GAPS, HSID, NID, N_T, PREF, SAPISID, SID, SNID, SSID

PayPal® Buttons

The payment or donation buttons that may appear on portions of the back-end administrative dashboard (which are not visible to non-logged-in users) contain embedded content served by PayPal® (via paypalobjects.com). They may set the third-party cookies PYPF (via paypalobjects.com), which appears to check whether or not you are a logged-in PayPal user and is used for the PayPal user login process, and/or 01A1 (via abmr.net), which stores certain technical information about your device and browser (including your IP address), probably to facilitate the login and shopping cart functions. The PYPF cookie normally expires in approximately four weeks, the 01A1 cookie in approximately one year. If you use the button to make a payment or donation, PayPal sets additional cookies (not listed here) to manage your PayPal login and transaction data. For more information on what data PayPal collects and what they do with it, visit their Legal Agreements page to review the PayPal Privacy Policy and Statements on Cookies and Tracking Technologies that apply in your location.

PYPF, 01A1

Administrative and Login Cookies

These functionality cookies are used to manage user logins and other WordPress administrative functions, such as post editing. If you are not an administrative user, they shouldn't normally be placed at all unless you somehow access the login area, which is off-limits to non-administrators. Accessing the login page places the wordpress_test_cookie (a session cookie that tests whether your browser will allow the cookies needed to login and disappears when you close your browser) and the itsec-hb-login-xx cookie (which expires after about one hour and helps protect the site against "brute force" attempts to hack user passwords). After logging in, the wordpress_logged_in_xx, wordpress_sec_xx, and wordpress_xx cookies store your user login credentials to allow access to the administrative dashboard; these cookies may last up to 15 days if you click the "Remember Me" when logging in, but if you don't, they normally expire when you close your browser (or, failing that, within about two days). The wp-settings-UID and wp-settings-time-UID cookies store configuration settings for logged-in users and normally expire after about one year. The wp-saving-post cookie is placed after saving or updating a post, contains the post ID number and last action, and expires after about 24 hours. The wp-donottrack_feed cookie, which controls a blog feed, may be set by accessing the dashboard menu for the WP DoNotTrack plugin (if I currently have that plugin enabled) and expires in about one year. (For all of these administrative and login cookies, the "xx" will be a cryptographic hash while "UID" will be the administrative user's user ID number in this website's WordPress database.)

wordpress_test_cookie, itsec-hb-login-xx, wordpress_sec_xx, wordpress_logged_in_xx, wordpress_xx, wp-settings-UID, wp-settings-time-UID, wp-saving-post, wp-donottrack_feed

Change Font Size
High Contrast Mode (Note: This option sets cookies to save your settings)