This looks cool: Mozilla has released a translation tool as an add-on for Firefox that can do web page translation locally instead of sending data to the cloud! It’s based on Project Bergamot and implemented in WebAssembly.
IMO translation is one of those things like speech recognition that ideally should have always have been local (for obvious privacy reasons), but the processing and data just wasn’t there yet when Google Translate and similar services launched.
In response to girrodocus’s question: #PersonalWebsite creators… what’s your rationale for deciding when to use a subdomain or a subdirectory?
I usually prefer to put sections in subdirectories. That makes it possible to make the entire site portable (depending on authoring tools, anyway). Ideally, I want something that could be zipped up and moved. Or sent to Archive Team. (One of the downsides of dynamic site generators is that you can’t do this.)
When I use subdomains, it’s typically because I want some sort of isolation between the content, or the server apps, etc. But in those cases I’m as likely to use another domain entirely.
I put my main blog in a subdirectory (/journal), but if I set up my own git repository or something like that, I’d probably put it in a subdomain.
That said, I’m currently trying to sort out what I want to keep at the domain I’ve had for the last 20 years and what to move to my IndieWeb identity site.
It took 4 or 5 years from me discovering IndieWeb to actually building support into my website(s), because Hyperborea.org, named after a fictional place, felt like a digital home, but not an identity. So I set up KVibber.com as my digital identity instead.
I’ve been considering several approaches:
I might move my scenic and nature photos over to KVibber but leave the funny and comic-con photos on Hyperborea, or move my tech articles over but leave the personal posts.
I’m also planning to put together a light microblog, probably on KVibber, to be the canonical location for short posts on Mastodon/Twitter/etc that I want to keep, but don’t feel big enough for a full blog entry. That’ll probably go on KVibber, even though it’ll blur the pro/fun and original/fan distinctions.
Originally on Wandering.shop (and a followup post).
Update September 2022: I guess I’ve tabled the whole question at this point. For now, I’m just using KVibber as a profile page and putting everything else on Hyperborea, like I was doing before.
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.
Two hot takes (so to speak):
Auto-updaters shouldn’t run when the system is really busy.
And installers that check to see the whether the same or newer version is “already installed” should either be really thorough about what they’re checking, or offer to do a repair install anyway.
I’d fired up a game of No Man’s Sky, which even after redoing the thermal paste and adding another case fan still pushes the limits of my system’s cooling, especially if I forget to wait for all the background processes to finish loading on Windows startup. I left a space station, landed on a planet, started mucking around with the structure I had found, and hit a waypoint pole to save again—
And the system shut down.
I turned it back on to get the fans running again and help cool off. Which worked. But when I logged in, I had a bunch of errors with Google Drive. Apparently its auto-update launched during my GPU-intensive game and overheated it enough to reach the shutdown threshold.
Fortunately, I’d just saved my game — or so I thought.
I spent about half an hour trying to fix Google Drive before I decided to just go back to the game for now.
No Man’s Sky picked up seamlessly…at the previous save. Maybe the write cache hadn’t been flushed yet or something. I’m glad I only lost about a minute of gameplay, though… I’ve got several hundred hours on this save file, and I’d hate for it to get lost or corrupted!
Anyway, back to Google Drive. I couldn’t reinstall it because I couldn’t uninstall it, and despite my efforts I couldn’t remove enough traces of it for the installer to be willing to run. You can read the whole reinstalling Drive saga on my troubleshooting site, along with the taskbar that lost its icons halfway through.
I eventually fixed it by copying the installed program files from another system and running the uninstaller manually. That resolved both the taskbar icons and the Drive installer being willing to run.
Then I dragged myself into bed.
Yeah, it was a fun Saturday night. 🙄
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!!!!!
