Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a3fe03cff97034fc

Jump to content

Talk:Uber

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 1 month ago by Tofubird in topic NPOV structure, proposed regrouping

Wiki Education assignment: Computer Science Principles

[edit]

This article was the subject of a Wiki Education Foundation–supported course assignment, between 29 March 2022 and 19 June 2022. Further details are available on the course page. Student editor(s): MarshWicker (article contribs).

Trademark disputes of uber

[edit]

Can someone help add the section on trademark disputes for Uber? I have a good article explaining it. https://www.reuters.com/legal/litigation/uber-hit-with-trademark-lawsuit-over-new-travel-services-2022-05-12/ WikiGrower1 (talk) 14:58, 27 December 2025 (UTC)Reply

NPOV structure, proposed regrouping

[edit]

As the article stands, we have flat history chronology with no subheadings, and it's an NPOV problem, not just a readability one.

A few examples:

  • "In January 2022, Uber acquired Australian car-sharing company Car Next Door." The next paragraph is a leak of 124,000 internal documents.
  • DOJ criminal charges against the former Chief Security Officer for obstruction of justice. Then immediately followed by the 2040 carbon-neutrality pledge. Consecutive paragraphs, comparable length.
  • A gold membership in the Linux Foundation gets its own paragraph. So does an $271.8M class action settlement.

This isn't just difficult to navigate. It's scattering related material all over the place.

Significant regulatory, labour, and safety material is interleaved with routine acquisition announcements and minor corporate milestones, and so on. These are items of very different weight reading at the same level, a clear violation of WP:WEIGHT, and ultimately WP:SUMMARYSTYLE and WP:STRUCTURE:

Watch out for structural or stylistic aspects that make it difficult for a reader to fairly and equally assess the credibility of all relevant and related viewpoints.

Related material that recurs in multiple places like this makes it difficult to follow any one thread and actively works against NPOV.

When the record on these events is this extensive and significant, the undifferentiated dating is actively diluting it. We have driver classification issues sprinkled across five separate places, data breaches in four, regulatory evasion in three, all scattered across three thousand words of history, and the reader is structurally prevented from following any of this material end to end at all.

A very sophisticated POV push, and it's completely unreadable.

I propose that content should be grouped along these lines:

  • History - founding and early growth (2009-2013). Expansion and regulatory conflict (2013–2017). Leadership change and restructuring (2017–2019). Public company (2019–present)
  • Operations - Services. Business model. Autonomous vehicles.
  • Legal and regulatory issues - Driver classification. Regulatory evasion. Data privacy and breaches. Consumer protection. Passenger safety litigation.
  • Corporate culture
  • Finances

To be clear on the structure point: these subsections are organized by subject, not by stance. Company responses would stay folded into the relevant narrative rather than being answered back at in a separate passage, as it should be. tofubird | 06:44, 8 August 2026 (UTC)Reply