mbirth

If you’re happy with how Apple Password works for you, I can recommend StrongBox. It keeps all data in a KeePass2 database and integrates into Apple’s AutoFill API. That means it feels almost native when using it. No browser plugin needed. (At least not for Safari.) And you can decide how you sync the database file.

I prefer the term "sophisticated text completion".

Doesn’t get any more secure than a battle-tested web server hosting simple MP3 files and a text file.

Convenience might be a thing, though. I’m in the Apple ecosystem so their Podcasts app shows that feed on all devices and tracks listening progress, etc.

If I didn’t have that, I’m still a lifetime customer with PocketCasts and PocketCasts Web. So, that’s that. But if you don’t have anything similar in place, a self-hosted streaming server might be the best way to go, yes.

Do you need a web player? I’ve got several years of a radio show on my web server and wrote a script that created an RSS feed for them. This way I can open that in any podcast player (even web based ones) to listen to it.

It got better in Beta 2!

Settings --> Accessibility --> Display & Text Size --> Reduce Transparency

but I didn’t use the word “flower”

Well, hopefully you've added an ALT text to the picture for all those visually challenged people out there - which then also helps search engines.

Balfron Tower. But the designer was Ernő Goldfinger.

There's also Marginalia if you're looking for some rather traditional web search.

I’ve entered the serial number of my Germany-bought model and it said it’s not from the affected batch and safe to use.

Probably BigBlueButton, or maybe Jitsi. Or, they’re still using Teams but didn’t want it mentioned in the article.

Does the paper take into account the energy required to compile the code, the complexity of debugging and thus the required re-compilations after making small changes? Because IMHO that should all be part of the equation.