Python upgrades I want preview capabilities on this Jammy (Py 3.10) machine, even if I'm not going to bother to upgrade the server just yet. It's fine.
never mind about pingbacks? I tried the plugin, but basically no one accepted my pingbacks! Lots of failures like ERROR: Pingback XML-RPC request failed for URL https://srconstantin.wordpress.com/2017/09/13/hoe-cultures-a-type-of-non-patriarchal-society/: code=0 - (Often with the further message "Invalid discovery target".) Only the Cohen's d visualizer site (that I've linked to a couple times) accepted— -> Pingback notification sent for URL https://rpsychologist.com/d3/cohend/, endpoint response: Pingback was queued for processing: https://webmention.io/rpsychologist.com/webmention/1y4jNyZGrFbFD1-MUPwg ... but it doesn't show up on the site and when I click on the processing link, it says "The source document does not have a link to the target URL". But it does too—why couldn't it detect my link? (Is that WordPress's problem, too?) And then after all that waiting and failing (while my site was down), it crashed without writing the cache file (to prevent it from re-trying all that again on next publication), apparently because I hadn't already created the cache directory— File "/home/mtsw/working/lib/python3.6/site-packages/linkbacks.py", line 59, in process_all_articles_linkbacks with open(config.cache_filepath, 'w+') as cache_file: FileNotFoundError: [Errno 2] No such file or directory: 'cache/pelican-plugin-linkbacks.json' So, I guess I give up? I notice that Compass Rose and Don't Worry About the Vase totally do accept pingbacks! So maybe I should try this again sometime, but just roll my own (http://blog.mlindgren.ca/entry/2015/01/17/how-to-manually-send-a-pingback/) to hit Zvi and Ben, rather than using this plugin, which obnoxiously hit everything I've ever linked.
the newest packages drop support for Python 3.5!! The server is still running Xenial (like my desktop, like my laptop), which gets end-of-lifed next month. I feel old.
also bump Markdown, Jinja2; setting format Site is down after Pelican upgrade. From the error message, the StackOvermind (https://stackoverflow.com/a/57479744) suggests that the Markdown library needs a bump, too. (Um, should I be doing anything about all the other packages? I can see why people like even Pipenv, if the alternative is a flat requirements.txt ...) We also got a warning from nuPelican about %-formatting in one setting.
Python package reqs: upgrade Pelican, and incl. linkbacks plugin I think I'm going to try running the initial linkback run on the server manually? Somehow `pip` on the server isn't finding Pelican later than 4.5.0 (even though the net says 4.5.4 is a thing)?
link to Archives page grouped by month; drop Trigger Warning page
not thinking in nested parentheticals vs. installing a footnote plugin If I don't know how to make my thinking more linear and less tree-like, I might as well shove some of the subtrees into footnotes for legibility. I continue to by disappointed by the abysmal quality of the Pelican plugin/theme ecosystem, and very happy that I chose Pelican. (What I don't like, I can fix! Because Python! Rah!)
bump dependencies, update .gitignore
pin requirements with `pip freeze` I mean, I think there's a strong case that redirecting `pip freeze` to a file pins too much (by printing everything in your virtualenv, not just your first-order dependencies; in contrast, Cargo, Bundler, &c. are smart enough to distinguish), but it's better than not having any idea what software was used to make the site.