HOW I USE ZOTERO TO MANAGE REFERENCES
Recently, there have been several discussions about papers citing references that do not actually exist, allegedly because of AI hallucinations. But this is not fundamentally an AI problem. Whether a citation suggestion comes from a coauthor, colleague, advisor, search engine, or AI tool, we are still responsible for checking that the source exists and, more importantly, reading it ourselves. AI may help us discover relevant work, but it cannot replace the process of engaging with a paper, learning from it, and noticing connections that a short summary may miss. AI should help us do better work, not give us a reason to shift responsibility or evade accountability. ...
HOW TO SELF-HOST GOOGLE FONTS AS WOFF2 FILES FOR BETTER WEB PERFORMANCE
When I was optimizing this website, I ran into a small tradeoff with Google Fonts. Loading fonts directly from the Google Fonts API is convenient, but it may raise privacy concerns under the General Data Protection Regulation (GDPR), the European Union’s data privacy and security law. When fonts are loaded remotely through the API, the user’s browser sends requests to Google’s servers, which may include the user’s IP address. This has led to concerns that using Google-hosted fonts without consent could violate GDPR. (See Merane and Stremitzer’s working paper for a discussion of the legal case and its broader impact.1) ...
USING THE APSR CITATION STYLE WITH BIBTEX
My colleague, Sam Jens, found several inconsistencies between the APSR style in natbib and the APSR submission guidelines. The command fixes the comma between authors and year, but not other citation-style issues. To address these inconsistencies, I modified the .bst file from the official APSR template on Overleaf....