Question about Lyft / Uber - Are they inflating costs on return trips?

Back to stories Open in a window
Article news.ycombinator.com

Question about Lyft / Uber - Are they inflating costs on return trips?

Has anyone else noticed this? I'm in Austin, and I help my 2 elderly parents. Dad gave up driving due to age-related macular degeneration -- and I'm really happy he did. We've been using Lyft (and to a lesser degree Uber) for 2+ years and it's been great for giving him mobility and reducing his risk.

But... one thing I've noticed is that if you book a trip, and then book a return trip... the return trip is ALWAYS more expensive than it should be. I think Lyft is deflating "leaving home" and inflating "going home" costs. I assume they are thinking, "Let's make it easy to take the trip, and then once we have you... we'll make up the difference."

Anyway our hack is just to take Uber one way, and Lyft the other. Seems to save a ton of money. Or book from one account one-way, and another for the return.

For example, this morning... Dad had a dental appointment, and the "to the dentist" cost at 7:30 AM was $35. The "return home" cost at 9:45 AM was $105! Crazy since traffic had died own a bit by then.

When I plotted the same course from my app at the same time, it was $32. So I just booked a trip for Dad on my Lyft account. The cost would have been over $70 more if he just "defaulted" to taking a Lyft home from the same account that he used to get to the dentist.

Don't get me wrong, these services are a godsend. But... can't help but feel like some of the shady from Taxi company history remains.

I've only got cursory evidence, but seems to be a trend. When Dad goes somewhere, the return cost is higher. I just have him call me and I book the return on my account. Almost always saves money.

Discussion 0 comments · 1 points · dbg31415 · 2022-04-26
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or a story row's Open in new reader window button to compare articles. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page and Open in a window are one-off actions that do not change your saved default. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.