100
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Oct 2026
100 points (97.2% liked)
Selfhosted
62860 readers
1845 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
Another idea I haven't pursued: something that monitors the movement of local transit (BART trains, and buses) so I can check their ETA's and locations from a phone browser. There are existing apps and sites for this but they unfortunately suck. They always answer "when will the next bus/train arrive at stop XYZ" which is almost never what I want to know.
What I want is usually either "I'm on the #123 bus RIGHT NOW and want to get off at XYZ, how many more stops do I wait?", or else "my friend is on BART and just passed station X. When will she get to station Y where I'm supposed to meet her?". Anyone implementing anything like that, please take it into account. The transit agencies usually have API's to get the relevant data.
Oh, yeah, that's a tough one, but seems workable.
It doesn't seem so technically difficult if you can get the transit data. The phone GPS supplies your current location for the bus version, or alternatively you can just identify the most recent stop you saw. San Francisco has around 1000 city buses (I looked that up a while back) and you can put fairly precise coordinates, bus number, and route number of a bus into 4 or 5 bytes. So the complete locations of all the buses is around 20K which is less data than the javascript bloat that nextbus.com sends on every new visit. You do want the route maps (from transit agency) and street maps (openstreetmap) but overall it's not huge.
Yeah, and things like arrival times could be flipped around, so time until your stop is also just the ETA of that bus to the stop anyway. Just changes to how you slice and dice the same data.
There might be other buses ahead of the one you are on, en route to that stop. You really want the phone GPS to figure out what bus you're on, maybe showing a selection of possible bus numbers or route numbers. It would be great if you then see a route map showing your location as you move.