Ok... the routes refresh button works similarly. There is still some occasional flickering in the status line to debug.

There are still some kinks to work out – the code is a little nasty (trying to avoid JavaScript is hard) – but enjoy! 😎

Next up: a similar small overhaul of the main (all nearby routes) update behavior.

That's clever, I like it!

One small issue: any logo that is intentionally evocative of the MBTA's logo would probably have to go through a trademark attorney and/or get explicit permission from the MBTA.

Totally worth it though! Can you turn your idea into an SVG?

A privacy policy is a great idea. 👌

Will do 🙂

The city of Cambridge has officially-designated neighborhoods such as "Cambridgeport", which is why you see "Routes near you in Cambridgeport, Cambridge". The location you provided is resolved via a geospatial index to the enclosing neighborhood and city.

When you manually provide latitude and longitude, the behavior is identical to allowing geolocation permission (that is, that exact location is passed along to the MBTA API in order to fetch nearby predictions).

Hi, I'm sorry, I think you've misunderstood. I'm referring to my own comments, not yours, about how the app is open source and can be verified to match what's deployed, which only amount to "theoretical" appeals to your privacy.

Or am I the one who's misunderstood you? 🤔

And second, I agree there are some use cases that involve entering an address. For now, you can manually provide latitude and longitude query params, like this: ttimes.boston?latitude=42....

A fuller version of this feature may come, but that's what's there for now 👍

Those are theoretical appeals to your privacy. I understand that realistically, for an app so new and small, no one has bothered to comb through the source code looking for misuses of their data. But they could.

All of my source code is online (share.unison-lang.org/@mitchellwro...). Furthermore, because it's written in Unison, it's possible for you (yes you!) to verify that the deployed version is exactly the same. 😎

Ah ha!

First, I hope to earn your trust, and I'll note it should be easier than any app you've ever used.

Noted! Tell me more – do you use other transit apps (Google Maps, MBTA Go, etc) without allowing geolocation permission?

Everything is open source, and I'm happy to go into further details, but that's the gist! 👍🚍

• What does the queue contain, exactly, though? It's... ok, simplifying a little bit... route+stop pairs. So when you hop on route X at stop Y, we push X+Y to the queue. This allows us to effectively capture different sets of recent routes at different parts of the world.

• The data structure backing the recent trips is a simple queue. Whenever you click into a trip, its route gets bumped to the front. In particular, this design explicitly avoids trying to intelligently incorporate route frequency into the ranking. Goal: user should understand why a route is there.

Here's a breakdown of how this feature works and the rationale behind the design:

• We consider a route "taken" whenever you click into an actual trip's details view. While it won't capture every bus or train you ever hop on, it allows us to avoid having any new interaction (e.g. a button).