Here’s a filtered selection of my personal bookmarks. Using a shell script, I regularly export specially-tagged entries from my buku database to a JSON file. During site rebuilds, Hugo automatically pulls content from that file to build this page. This approach allows me to use an interactive interface to build my bookmarks database without needing a dynamic site.
Timestamp format: YYYY-MM-DD HH:MM, as per RFC 3339
Tags: microdata, rdfa, semantics, web
This is one reason why my site uses microdata instead of RDFa Lite: it conflicts with standard use of plain-old, semantic HTML (POSH). Good POSH can silently upgrade RDFa Lite to full-fledged RDFa Core, which will cause compliant parsers to interpret the property attribute differently. RDFa Lite is therefore not an option for me. I’d love to use full-fledged RDFa, but parsers don’t always “upgrade” from RDFa Lite to RDFa Core correctly. That leaves me with microdata. Sigh.
Tags: capitalism, favorite, hardware, opinion
An anti-consumerism guide to building long-lasting devices that respect the limitations of the environment, our wallets, and our attention. Instead of disposable ultraportable always-online devices, we should have study machines to help us work. Some of this resonated with my store-and-forward workflows for working with email, the Fediverse, and the IndieWeb.
The idea of tuning optimization algorithms in the opposite direction to create deliberately harmful results, with the prime example being using medical tools to create bioweapons. Scary yet thought-provoking.
An interesting take on the problems with HTML 5. I disagree with some of these criticism, but agree with others. Much of these issues are solved by ensuring compatibility with the Weblite specifications and by following some of my website best practices article.
Tags: documentation, reference, writing
An overview to the four quadrants of documentation: tutorials, how-to guides, explanation, and reference. It introduces each section with a cooking analogy.
I’d add “user interface” as a fifth, when applicable. Features like tooltips can serve as a form of “lite” documentation on their own.
A detailed criticism of the WCAG 2.0. Some of these points have been addressed by the revisions and companion documents that followed, especially the Web-specific tutorials. Other criticisms still stand.
The WCAG 3.0 fixes a few issues with the WCAG 2.X, but it exacerbates some of Joe’s other criticisms. I think the best solution would be a companion document that “translates” the WCAG into something Web-specific, requirement-by-requirement. Currently, advice is split across many pages detailing “how to meet requirement X”.
One of my favorite websites. It presents an alternative to “scaling”: reduction and finding low-tech solutions to our problems. Renewables are good, but they’re not enough to solve our environmental impact. We need to reduce reliance on industrial resource consumption.
I’m no anarcho-primitivist, but I like the idea of being able to do the “same thing with less”.
Tags: favorite, indieweb, microformats, web
Getting familiar with IndieWeb is a daunting process; this page distills it down to a process that’s easy to follow. These bookmarks are part of my plan to IndieWebify seirdy.one as per this guide.
I don’t like the order too much; IMO, webmentions should come much earlier than some other steps, as they’re quite simple to set up and the basis for the entire social element of the IndieWeb. I should bring that up later.
A reality check for transhumanism that doesn’t denigrate the idea. Instead, it shows how unrealistic it is for us to achieve the transhumanist ideal of implants, augmentation, and eventually “transcendance” in a reasonable timeframe even if the process has already started.
A generally cynical look at design trends. Commercial apps are increasingly made in ways that ignore the desktop paradigms that users expect in favor of paradigms that are both bespoke and mobile-friendly.
I’d imagine that there are some parallels to accessibility. The “Content Usable” WCAG guidance seems quite relevant.
Tags: microformats, reference, semantics, web
An incredibly useful reference for making content compatible with various reading modes. I’m not a fan of complying with proprietary, non-standard quirks; however, it looks like most reading mode implementations are aware of open standards such as microformats1, microformats2, microdata, and POSH. Supporting these standards should help improve compatibility.
I hate most forms of advertising, so this post spoke to me. Unfortunately, traditional adblocking mechanisms (browser adblockers, yt-dlp’s Sponsorblock integration or mpv’s sponsorblock script, etc) are limited to digital content. This post challenges us to take adblocking to the next level by blocking ads in real life, the only ways we can.