DNS is:

- simple

- battle hardened

- distributed

- affordable

blockchains are:

- essoteric, backwards, and not easily implemented

- new and unproven, frequently hacked

- effectively a ploy to centralize / redo Web 1.0 but owned by one blockchain

- ...waaaaaaay more about money and "owning something" than DNS is.

IaaS VPS's and rented colo VMs are definitely fine. PaaS is... slightly not? it's the grey edge!

SaaS is definitely not you running stuff you control or could move anywhere.

If it's a buck standard linux box, yeah that's self hosting!

self-hosting: running open source code that you could run on any computer.

if it's convenient to run mastodon on hetzner, that's STILL self hosting; because you /can/ move your app IN ITS ENTIRETY from any computer to any other.

HomeLab elites really are the most insufferable people out there.

It doesn't have to be open source. Plex is probably the most popular example of that. MongoDB is also no longer generally considered open source.

sticker shock / looking at alternative vendors

it's a weird effect:

imagine a beach, with icecream vendors. You'd think it would be optimal for two vendors to each split it half north, half south. However, in wanting to steal some of the other vendors' customers, you end up with two icecream stands in the center.

So too with outages. Safety / loss of blame in numbers.

oh hey, I've bricked a server remotely and had to drive 45 minutes to the DC to get badged in and reboot things :)

Reminiscing: this was a rite of passage for pre-cloud remote systems administrators.

Proper hardware (Sun, Cisco) had a serial management interface (ideally "lights-out") which could be used to remedy many kinds of failures. Plus a terminal server with a dial-in modem on a POTS line (or adequate fakery), in case the drama took out IP routing.

Then came Linux on x86, and it took waytoomanyyears for the hardware vendors to outgrow the platform's microsoft local-only deployment model. Aside from Dell and maybe Supermicro, I'm not sure if they ever worked it out.

Then came the cloud. Ironically, all of our systems are up and happy today, but services that rely on partner integrations are down. The only good thing about this is that it's not me running around trying to get it fixed. :)

so, funny story, my fiber got cut (backhoe) and it took then 12 hours to restore it.

If you had /two/ houses, in separate towns, you'd have better luck. Or, if you had cell as a backup.

Or: if you don't care about it being down for 12 hours.

Firefox shouldn't try to "be chrome", people who want chrome just use that. Firefox should be /not chrome/.

translation is moreso machine learning, not generative hallucinations or a chatbot

it's literally the same technology as LLMs. Transformers were proposed for translation.

(But I don't know what methods the Firefox translation uses. I assume it's a local model but don't even know that for sure.)

It is a local model: https://mozilla.github.io/translations/

personally, the golang highlighting is nice.

- dark blue: keywords (var, nil)

- light blue: variables (defines the scope you're looking at)

- blue-green: types (bool, string, your custom thing, the kind of the variables)

- dark green: comments

- yellow: functions/methods (jumping to another section)

- orange: strings (not variables, so static things here!)

- if/braces/parens/select/switch/defer/go: purple (control logic)