4 ms·

> (I'm not going to share the particular details on which request and which query parameter that is) Why not ? It's not like that would matter anyway...

• kuba-orlik 4y ago
  Author here. I just don't want to make patching it easier for Bolt
  • natch 4y ago
    About one thing you said, Apple and Google need not be lumped together. They are as different as night and day.
    • unsafecast 4y ago
      I think they meant that ios and android are the only companies that apps are made for (so they're the only platforms people actually use), hence it's a duopoly.
      • deleted 4y ago
        [deleted]
  • andrew_ 4y ago
    That doesn't add up. Even if they become aware of the thread and were oblivious as to the side effect of omitting the parameter, they're going to be able to enumerate the query parameters they use internally fairly quickly.
  • Fiahil 4y ago
    Well, I don't like to be a party pooper, but there's only two way this can go : - nobody working at Bolt care that they geofencing is lame. The fault was there since the beginning and the two freelancers maintaining the web version have a long backlog, little visibility and no bargaining power. Plus, they haven't got their contract renewed yet. - They have no idea your workaround exists. Even if they are bored enough to read Hacker News on a Sunday, their web app is going to be discontinued on the next API upgrade anyway. Bonus point : An app is just a nice frontend. I'm pretty sure you could make your own web client and order your own ride with a few API calls even if they patch the fault.