If it's a settlement then both parties have signed on, not just one.
-
-
This Tweet is unavailable.
-
Replying to @RuinTaughtMe @arthur_affect
Yes, which means Uber is also responsible for this policy, not just NFB.
1 reply 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @RuinTaughtMe @arthur_affect
We can't really say what the law requires because Uber agreed to this approach as a settlement. They could have continued to fight the lawsuit (and perhaps prevailed) or could have agreed to a different settlement. This is a Uber policy as much as it is 'imposed' by NFB.
1 reply 0 retweets 0 likes -
-
You're being deliberately disingenuous here too, NFB, the plaintiffs in this lawsuit, reported it to their membership as a victory and as their demands being met
1 reply 1 retweet 10 likes -
Replying to @arthur_affect @RuinTaughtMe
I'm sure if Uber discussed the settlement they would have declared their own version of victory out of it too. Seems routine.
1 reply 0 retweets 0 likes -
Replying to @AeonCoin @RuinTaughtMe
No, the fact that they avoided discussing it at all except to announce they were abiding by it makes it pretty obvious who "lost" and who "won"
2 replies 1 retweet 8 likes -
The real issue here is that Uber is generally terrified of having to defend their drivers' status as "independent contractors" in court - it's what their whole business model depends on and yet most outside observers find the idea ridiculous
1 reply 2 retweets 13 likes
The settlement was a way for Uber to try to make this go away They're allowing NFB to impose conditions on them that make them act like the drivers' boss for *this issue and this issue only* so they could avoid a ruling on the underlying issue of whether drivers are employees
-
-
Replying to @arthur_affect @RuinTaughtMe
See, now that's where this was a "win" for Uber. By contractually precluding any of their own discretion, they're not acting as an employer.
2 replies 0 retweets 0 likes -
This Tweet is unavailable.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.