Tag: Imported Post

Originally posted somewhere else (ex. a blog I don’t use anymore, or a social networking site) and moved here sometime later. Usually keeping the original posting date.

Posted on
by

One of the things I find fascinating about the Tunguska and Chelyabinsk impacts is that in one case it took decades of scientific research and multiple theories to settle on what probably caused it, while in the other we have video footage and the actual meteorite.

But there were eyewitnesses to Tunguska despite its remoteness, and somehow I’d never read their reports before.

As for the debate about what caused the Tunguska event: it was clearly something from space, but no one has ever found an impact crater or an actual meteorite, just damaged forest. Plus the scientific expeditions weren’t carried out until years later. Current consensus is that it was a meteor, but it exploded in the air before impact, causing the visible fireball across the sky, intense heat, shock waves, atmospheric disturbances and so on but no crater.

Posted on
by

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.

Posted on
by

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!!!!!