Any chance you've defined the new networks as "internal"? (using docker network create --internal on the CLI or internal: true in your docker-compose.yaml).

Because the symptoms you're describing (no connectivity to stuff outside the new network, including the wider Internet) sound exactly like you did, but didn't realize what that option does...

Is this just placing them vertically, nothing else?

I currently use the Tree Style Tab extension and really like how it handles sub-tabs and allows collapsing the tree nodes. If I can't have that this is probably not directly useful to me unless extensions can add that functionality.

I guess I'll be watching how this evolves though.

For MIT, why do you care? That's perfectly fine and explicitly allowed by the license. Same for Apache, but with a few extra requirements (like keeping a list of changes in the source code and preserving licensing information etc.).

As for how I know big corporations are using my code: the fact that a prominent project (publicly used by several tech giants) took a dependency on one of my tiny (permissively licensed) library packages is probably a clue.

There was some kind of incident between the artist and a camera woman. The exact details aren't public, AFAIK.

Assuming they went to signed 64-bit time, it should be about 3:28:32 pm UTC on Sunday, December 4, 292277026596. Yes, that last number is a year.

Given the state of US politics, what are the odds a "commitment" like this will survive the next election cycle?

You forgot one:

• They'll quietly re-introduce it in another 6-18 months.

I believe so, but in addition it is also a "the original meaning of 'barbarian' is non-Greek person" joke.

This War [...]

Unfortunately you'll have to be a bit more specific than that, too many wars going on at the moment...

My family shares a fairly uncommon surname with a professional athlete we are (as far as we can tell) completely unrelated to.

My father always joked that we should answer "we don't discuss that" when asked about it, as if there had been some huge falling-out.

Because you need a way to be reachable over HTTPS for other instances to be able to securely send you updates (new posts/comments/votes etc.), so you need a trusted certificate. While HTTPS does not strictly require a domain name^1^ it vastly simplifies the process.

^1^: It's possible to get a trusted certificate for an IP address, but not nearly as easy as getting one for a domain. And it's probably also more expensive than just getting a domain and using Let's Encrypt to get a certificate.

As of v0.18.2, Lemmy marks the "original URL" as the canonical URL so search engines know which page is the "real" one. Shouldn't that help?