Show HN: Practice for Your YC Interviews with Betafi https://ift.tt/sEkjZiT

Show HN: Practice for Your YC Interviews with Betafi Hi folks, Betafi is a product feedback platform build around moderated user interviews and usability testing sessions. To help folks applying for the W23 batch with interviews coming up this week, we just launched a project templates feature and catered onboarding for fellow founders to practice and conduct mock YC interviews with each other. You can use Betafi's interview script feature, "instant tags," and timestamped notes to take turns annotating rough spots and practicing rapid-fire responses to questions with your cofounder(s), to try and make the most out of those 10 minutes during your real YC interview. A big part of the joy of building Betafi is getting to support other early-stage founders who wind up using our product in interesting and creative ways. This project came out of several teams applying to the W23 batch, who organically started using Betafi to help prepare for their interviews, so we thought we might as well build "first class" support for it! Do let us know what you think, keen to hear your feedback, especially given this is a slightly different use-case from what we initially designed the product for! https://ift.tt/CfjxXQ3 November 10, 2022 at 02:30PM

Show HN: Shdoc generates docs for bash/zsh scripts with Awk https://ift.tt/D2Xk40u

Show HN: Shdoc generates docs for bash/zsh scripts with Awk https://ift.tt/cYduhyq November 10, 2022 at 11:54AM

Show HN: OpenAI for Coda – AI right in your doc alongside your existing tools https://ift.tt/LsyuJGj

Show HN: OpenAI for Coda – AI right in your doc alongside your existing tools Hi HN! I’m Spencer, a software engineer and creative technologist. I care about making tools that empower people’s creative agency, automate busy work, and imagine alternative futures. I work at Coda on the Pack ecosystem but built this in my spare time while tinkering on how to make AI more accessible. Over the past few months, I’ve been blown away by the capabilities the community has demonstrated with GPT-3 and DALL-E. But as mind expanding and powerful as they are, these possibilities have often required access to tools that are expensive, require in-depth technical expertise, or don’t integrate into your existing tools and workflows. I wanted to see how this power could be opened to everyone—not just engineers and AI enthusiasts—by bringing OpenAI into an endlessly customizable tool like Coda. So when OpenAI released its GPT-3 and DALL-E APIs, I set out to create an environment where anyone could leverage this capability for their own and team’s needs and have it work seamlessly with their existing data and services. The result is this OpenAI Pack for Coda. It provides building blocks for you to leverage GPT-3 and DALL-E with your data the way you want, so you can build off the existing Coda integration ecosystem to simply add on OpenAI’s power to the tools and workflows you use now (like Slack, Zoom, etc.) Here’s a few ways I’ve already used the OpenAI Pack to automate busywork and augment my creativity: * Synthesize raw meeting notes, long Slack threads, and Zoom transcripts into a tl;dr and automatically send it out in an email. * Brainstorm with my team and auto-generate new ideas to riff on the most popular ideas. * Fill out a story Mad Libs to imagine a story premise and generate a corresponding image.. This is only the beginning of what you can do, and all the source code is open source and available under the MIT License so would welcome contributions :) Play around with the pack and the starter template playground (linked above). I’m excited to see where the community takes this and would love to hear how you’d use it. https://ift.tt/EYDikTs November 10, 2022 at 03:50AM

Taxi Upfront Pricing Pilot Begins

Taxi Upfront Pricing Pilot Begins
By

The Taxi Upfront Fare Pilot Program began on November 9, 2022! 

In September 2021, the SFMTA Board authorized the creation of a one-year Taxi Upfront Fare Pilot Program. The pilot will give taxi customers the ability to book a taxi trip through a taxi e-hail app and pay a flat-rate, upfront fare. It will also allow customers to request a taxi through approved third-party apps.

Our hope is that the pilot benefits taxi users by providing them with upfront information about their fares, relieving meter anxiety, and allowing customers to price shop for similar on-demand services. We believe this will bring taxi services in line with what customers expect on similar services. We also believe it will increase business for the local taxi industry, especially the drivers. A successful pilot would increase overall taxi trips, encourage more people to become taxi drivers, and maintain or improve taxi services for all passengers. 

Beginning November 9, taxi customers have the ability to book a taxi trip through three approved taxi E-hail apps: Arro, Flywheel, and YoTaxi*. The approved E-hail apps will give taxi customers the option of choosing an upfront fare through the app, or they may choose to request a cab through traditional phone dispatch or street hail and simply pay for the trip based on the taximeter amount. The upfront fare offered to taxi customers will closely match the cost to the customer of a fare based on the Taximeter rate.

The pilot program will also allow customers to request or to be matched with a taxi through third-party apps. Uber is the first third-party app to participate in the pilot, which will lay the groundwork for other apps (including Muni Mobile) to refer trips to local taxis. Trips originated from a third-Party app will offer upfront fares that are not based on Taximeter rates. 

The Upfront Fare Pilot allows two types of trips:

1. Taxi Pilot Trips:

• Originate with a customer ride request through an approved taxi E-Hail app
• Dispatched by a taxi E-Hail app
• Provided by a permitted San Francisco taxi driver in a permitted SF taxi vehicle
• Upfront fare is based on the estimated taximeter amount 

2. Third-Party Pilot Trips:

• Originate with a customer ride request through a third-party app
• Provided by a permitted San Francisco taxi driver in a permitted SF taxi vehicle
• Upfront fare is not required to be based on the estimated taximeter amount

Requesting a Taxi through a permitted Taxi E-Hail App

Taxi customers may request taxi rides through three permitted apps: Arro, Flywheel, and YoTaxi*. 

To request a ride, customers can open the app of their choice and input a payment method. After inputting a payment method, customers can request a ride within the app and will be provided with an upfront fare based on the estimated taximeter amount. 

Upon completion of the trip, the payment will be processed by the E-Hail app. No separate payment to the driver will be needed at the end of the trip.

*Currently, Arro and Flywheel are approved, while YoTaxi is eligible to participate and is conditionally approved.

Receiving a Taxi through Uber

Third-party pilot trips will allow San Francisco taxicabs to be matched with Uber customers. Currently, Flywheel is the only Taxi E-Hail App approved to provide Third-party trips.

Customers can request a ride through Uber as normal, but in some instances may be matched with a taxi. Customers will still receive an upfront fare, but the fare will not be based on the estimated taximeter amount. Uber customers will always be notified if they’re matched with a taxi, and if they prefer, can choose to get re-matched. 

Upon completion of the trip, the payment will be processed by Uber. No separate payment to the driver will be needed at the end of the trip.

SF Paratransit Customers

Currently, both YoTaxi and Arro are unable to book paratransit customers as a part of this pilot, and Flywheel will only provide a fare estimate. SFMTA plans on working with the Taxi E-Hail apps to allow for this in the future.

SF Paratransit riders can continue to request rides through the regular process.

Next Steps and Comments 

The SFMTA will report quarterly on the results of the pilot to the taxi industry, our board, and to other stakeholders. We will be having quarterly taxi outreach meetings about this pilot and other topics affecting the industry. 

If you have comments about the pilot, we are taking written feedback.

Published November 10, 2022 at 06:39AM
https://ift.tt/ZjPh4mq

Show HN: Unblob – accurate, fast, and easy-to-use extraction suite https://ift.tt/PBWJnCS

Show HN: Unblob – accurate, fast, and easy-to-use extraction suite https://unblob.org/ November 10, 2022 at 12:16AM

Show HN: Hypertest - A test runner for developers with ADHD https://ift.tt/01O9sHm

Show HN: Hypertest - A test runner for developers with ADHD TL;DR: a test runner focused on making devs w/ ADHD happy. Hello HN! My name is Yuval, a dev with ADHD. I believe there's different design constraints on tooling for devs with ADHD compared to their "normal"counterparts. That's what I'm here to solve. I gathered experiences of other ADHD devs, to summarize: ( https://ift.tt/soy7Yql ) - Memory: People w/ ADHD have horrendous short term memory (hard to keep grasp of the current *thing/task*) - Distraction: Are easily distracted, tend to fall off the focus wagon easily. - Boring Maintenance: They need and use lists, but are bad at maintaining them. A star would feel awesome (MIT licensed): https://ift.tt/RyF6MUQ https://nabaz.io November 9, 2022 at 10:56PM

Show HN: Auto-file bugs to GitHub issues with console logs and network requests https://ift.tt/exDwk5W

Show HN: Auto-file bugs to GitHub issues with console logs and network requests Hi HN, my team and I have been working on a new tool to improve how bugs are reported to engineers. I used to be a developer, and I thought it was ridiculous the little amount of bug repro details I would get in JIRA tickets. Then I became a product manager, and I realized how time consuming and tedious it was to write good tickets for developers (and then understood why most tickets lack enough detail!) That’s why my team and I decided to build a browser extension for anyone to create bug reports that auto-include: console logs, network requests, session replay, timestamp, url, browser, OS and device specs, and wifi speed. With this extension, it’s faster than the old-school way to report bugs (a few clicks, plus no switching tabs). And, for the developer receiving the bug reports, it should be faster to debug because all the information is right there. We started with a Chrome extension and soon we’re going to build extensions for other browsers too. (Which should we add next? We’re thinking Firefox). We built this in react, typescript, mobx, and graphql. It’s privacy-focused: everything happens locally on your browser until you choose to share, and you can even select which specific websites you want the extension to run on in settings. Today we shipped an integration with GitHub - meaning it’s now just a few seconds to create a really good GitHub issue. I hope you check it out and I hope it helps bring about the end of bad tickets for you and your team! If you have any suggestions or questions, please let me know here! https://jam.dev/github November 9, 2022 at 07:59PM