[UberIsAnnoying]

I hope it included the people responsible for sending me the most abusive SPAM campaigns I have had in years.

1) I never subscribed to these e-mails

2) The e-mails contain a link to unsubscribe in this format: click.uber.com/f/a/<strings>

3) You get redirected to uber.com/unsubscribe

4) They make you manually fill your e-mail

5) When you press unsubscribe:

- It makes a request to uber.com/api/unsubscribe?email=<email-address>&et_job_id=&et_list_id=&et_batch_id=&message_uuid=&content_identifier=

- Response is always 404 Not Found (Tested on Firefox, Chrome, IE, Edge)

[muks]

Here's an example of the quality of Uber's customer support: https://twitter.com/muks/status/1137237193657868289

This was after I reported that my 72 year old mother was asked to get out of the car by the driver after sitting in it, because he learned of the destination after starting the trip and did not want to take her there. Uber does not show the destination to the driver before starting the trip.

I was probably speaking to a bot, or nobody had the patience to fix the problem.

Edit: I haven't used Uber since that incident.

[BigJono]

Uber's engineering is dodgy across the board.

There was a good year or so period where I ran into 4 or 5 critical bugs that stopped me using the service entirely for days or weeks at a time. One of the dumbest was being unable to enter a credit card because the form required a field that wasn't being rendered. 6 months later I switch credit cards and again can't use the app for weeks because it wants a 5 digit postcode even after setting the country to 'Australia', but the server side check was still working and 86'd any combination of bs 5-digit code that was working.

Several times I've had something go wrong with the ordering system itself (on the UberEats side). Once an order was put through twice and two meals showed up on my doorstep. Another time I copped a cryptic error message followed by a Javascript crash and my card was charged but no order was logged upon refreshing the page (which indicates to me that something wasn't properly atomic and maybe some business logic was happening on the front end that shouldn't be? Presumably fixed now, I hope)

Even right now, as I type this, there's a bug on UberEats introduced in the last few days or weeks that's leaking variable names through to the front-end. I've got 'components.BadgeSoldOut.message' and 'components.CartItemCustomization.upTo' all over the place. I'm sure when that gets fixed another one will crop up next week.

404s and broken systems seem par for the course.

[spectramax]

I am no lawyer but pretty sure this violates:

https://en.m.wikipedia.org/wiki/CAN-SPAM_Act_of_2003

[buckminster]

Sure it does, but ignoring regulations is Uber's schtick. Using their services is the moral equivalent of buying stolen goods.