fizzle

I basically just avoid exposing ports from containers unless I really do want them exposed on the host?

Most services go through my reverse proxy, traefik.

Things like databases don’t publish ports on the host because they’re only accessed internally, using their container name.

Yeah I’ve been using wireguard for a long time myself personally, and more recently for a small team to access an intranet.

I’m a big fan. After a half hour or so trying to understand configs it’s pretty manageable.

Maybe everyone already knows this but you can generally see better in your peripheral vision in low light.

Almost all of your color vision / cones are concentrated in a tiny central area of your retina.

The grey scale / rods are dispersed around that.

In some ways I think night vision is a kind of skill that some people might be better at than others, even if the mechanics of their eyes aren’t special.

Yeah me too. I think this is called “coil hum”. I notice it with things like usb-c thunderbolt ports. Often you can swap a cable or something and it’s resolved.

I’ve been trying to get zulip working.

Sounds like it addresses your requirements.

Seems to be a real bitch to self host - I’ve been doing this a while but the compose yaml is pretty arcane with hundreds of environment variables.

I didn’t “give up” exactly but it’s been on the back burner for a month or so now.

I’m honestly kinda surprised that Google is apparently not in fact doing this already and (according to the comments here) continues to not do so.

Hyperbole, surely.