Add Fare Calculation to LibreTaxi
Budget: $10 – $30 USD
I maintain a fork of LibreTaxi (Telegram bot – GitHub repo here: https://github.com/ro31337/libretaxi) and now need a new core feature: automatic fare calculation.
Here is what I’m after:
• When a rider requests a trip, the bot should calculate a fare on-the-fly, based on distance and an adjustable per-kilometre (or mile) rate that I can later tweak in a simple config file or an admin command.
• Time-based or surge multipliers are a plus if you can keep the logic clearly separated so I can expand it later.
• The fare must be displayed to both driver and rider before either party confirms.
• No external payment processing is required right now—just the calculation and clear display.
LibreTaxi is written in Node.js and Telegraf, so please stay within that stack. All changes should be clean, well-commented, and submitted as a pull request against a dedicated branch. I’ll test by spinning up a local bot and verifying that:
1. Different origin/destination pairs return accurate fares.
2. Updating the price settings instantly affects new requests.
3. There are no regressions in existing ride workflow.
If you’ve built Telegram bots before or have touched LibreTaxi, that’s an advantage, but solid JavaScript/TypeScript skills and clear commit history are what really matter.
Here is what I’m after:
• When a rider requests a trip, the bot should calculate a fare on-the-fly, based on distance and an adjustable per-kilometre (or mile) rate that I can later tweak in a simple config file or an admin command.
• Time-based or surge multipliers are a plus if you can keep the logic clearly separated so I can expand it later.
• The fare must be displayed to both driver and rider before either party confirms.
• No external payment processing is required right now—just the calculation and clear display.
LibreTaxi is written in Node.js and Telegraf, so please stay within that stack. All changes should be clean, well-commented, and submitted as a pull request against a dedicated branch. I’ll test by spinning up a local bot and verifying that:
1. Different origin/destination pairs return accurate fares.
2. Updating the price settings instantly affects new requests.
3. There are no regressions in existing ride workflow.
If you’ve built Telegram bots before or have touched LibreTaxi, that’s an advantage, but solid JavaScript/TypeScript skills and clear commit history are what really matter.