[INTPenis]

Splitting hairs no? I mean you're comparing multi-hop with onion routing.

I'm just speaking as a layman end user. When I see multi-hop it's self-explanatory, it's literally in the name.

Onion routing is another type of multi-hop with the onion routing algorithm.

[judge2020]

Since it's the same company with access to both the first and second server, it wouldn't be too hard to log network on both ends and sync it up.

With iCloud Private Relay, it'd be harder for a single actor to de-anonymize requests; you'd either need collusion between the companies or a government entity would need to ask both companies to log network traffic at once, and this would complicate the "exit node" server since it can't filter/only record traffic from the target customer's connection without company 1 setting up a single server dedicated to being the proxy for that customer.

[teawrecks]

The point of multihop, tor or otherwise, is for each node in the route to not know what the other knows. The first node sees packets coming from you, but not where they're going. The second see's where they're going but doesn't know where they're from (and vice versa). If the two nodes exchange this info (ex. if same person runs both nodes) then there's no point. Nothing is gained, you just incur the overhead of the extra hop.

[INTPenis]

Where is this defined? Because the word multi-hop only implies more than one hop. Anything else needs to be defined as a specific algorithm, like onion routing for example. That's why I think this is semantics.