Love how the same people who are all “COVID isn’t a problem” are also dead set on keeping certain people out of the country just in case they might bring COVID in.
No wonder they distrust actual public health measures and think the government is just using COVID as an excuse for…something. Because that’s what they would do. That’s what they have done.
For human-readable HTML, I can write:
<a href="https://example.com">Lois Lane</a>
For machine-readable HTML:
<a rel="author" href="https://example.com">Lois Lane</a>
For IndieWeb microformats:
<a class="p-author h-card" href="https://example.com">Lois Lane</a>
But for inline Schema.org I have to write:
<span property="author" typeof="person"><a property="url" href="https://example.com"><span property="name">Lois Lane</span></a>
I’ve been grumbling about all the redundancy in putting multiple sets of metadata on a page: classic meta tags, OpenGraph, Twitter cards, Schema.org, microformats2. So I’ve been looking to consolidate as much as I can.
I thought, Hey, Schema.org has inline markup implementations! I can probably just tag the same elements I used for microformats2!
But there are so many things like author where it wants a multi-part hierarchy when you could easily use a single tag.
At this point the added complexity to the code isn’t worth it. I may as well stick with the JSON-LD lump of text in the header. Heck, the extra spans and divs might actually add up to more bytes than the no-longer-duplicated content.
It’s not actually that much extra space, though, and the site in question generates all the markup from one set of markdown front matter. It just bugs me that to fill in all of them I need multiple copies of everything.
Though it is kind of funny to compare design decisions:
Facebook: We want a single block that can be copied and pasted and all looks the same. We don’t want to reuse existing tags and we don’t care about DRY.
IndieWeb: Invisible metadata inevitably gets out of date, and all this stuff that should already be on the page or in the head anyway, so let’s use what’s there and make it simple to mark up the actual page content.
Schema.org: CATEGORIZE ALLLLL THE THINGS!!!!!
Saw this while out walking this morning. I guess holiday decorations can last as long as you want them to!
WTF?
It turns out all Raspberry Pi CPUs appear as 2835 in the kernel?!?!?
I decided to put BOINC on an old phone instead. I don’t feel like installing a new OS on the Pi. *sigh*
I’m not ready to give up on the flexibility of WordPress for my main blog yet, but holy crap are these pages heavy. Even with compression. There’s no reason it should take 450K (before compression) and 20 requests to display a 500-word post.
And I don’t even do ads, popups, social sharing buttons or anything else like that.
By contrast, my Les Mis blog, where I post about once a year, is currently generated by Eleventy using a custom minimal theme that only takes around 10K of HTML, 3K CSS, and a third request for the icon. And another 40K for the header font, which I recently set up locally so it no longer has to call out to Google Fonts.
One domain, just four requests, and only 50K for the first hit and 10K for each subsequent page.
Never mind the Gemini version of the blog which is around 2-5K per page and a single request per page!
Compression cuts down on those 500Kb WordPress pages — all the text and code compresses really well so only around 200K bandwidth is needed. But it’s still got multiple JavaScript and CSS requests going on.
I was able to cut it down significantly by switching to a lighter theme and turning on the minimize/combine feature in WP-Optimize so it’s making fewer script calls. But it’s still way bigger than the minimalist setup I have with 11ty.
Some of it is images, though. I still have my latest Flickr posts in the sidebar, and I’m using Jetpack’s related posts feature which includes thumbnails. I could cut out a big chunk by removing those, but I kind of still like the idea of having them in there.
I think I need to take a look at how much extra stuff I really want on this site and rip some of it out. Eventually I’d like to replace all the JetPack features because they just seem to keep adding more scripts. Plus I want an entirely local stats package instead of one that’s offloaded to a third party even if they’re less awful than, say, Google or Facebook.
On the other hand, I want to keep Gravatar on the comments sections (on the older posts where people actually commented) because that’s actually useful to readers as an aid for following a conversation better. But that’s all on top of the base page size.
