Eric Lippert was my hero back when his blog was hosted on MSDN. Sad to see him go into retirement when he's at his prime. Hope he finds some new exciting project.
lbrandy has it right here. If your definition of "tracking" is "web server log analysis," then nearly every web site you visit is tracking you.
It's really nothing to worry about though, unless Facebook is doing something to de-anonymize that (otherwise stateless) data. They could probably do that (by noting the IP and User-agent seen when logging out, for example), but they explicitly claim not to in a number of places, most recently by lbrandy in this thread.
UberEats drivers who accept delivery of multiple orders, so you wait for everyone else's orders to be cooked and delivered before your cold burger and fries arrive. This problem is exaggerated by either these orders being on opposite sides of the city or…
Unfortunately the Eats drivers (of which I am one) don't have a choice. If the Uber dispatch algorithm determines that we should pick up two orders at the same time, then it gives us instructions to that effect. It also decides which of the two orders to deliver first. We don't even get to see where the second order is going until the first has been dropped off.
And yes, the algorithm is terrible. Sometimes we drop off the first order all the way across town, and the second order turns out to be for a customer a few blocks away from the original pickup location! It's also quite common for a new order coming in result in the driver (who has just arrived at the restaurant to pick up your food) needing to wait an extra 10 minutes while the new order is prepared and cooked.
The end result is customers getting cold food. I'm amazed that Uber Eats has repeat customers.
(And here in New Zealand, the restauarnt pays Uber 35% of the menu price - plus the customer is still paying a delivery fee on top! It's again amazing that any restaurant would even bother with Uber Eats.)
