edfungus
Re:Ask HN: What are you working on? (July 2025)
on Monday July 28, 2025 @03:53AM (#44708361)
Been working on a real time public transit app for the Bay Area and New York but recently decided to use the same data to create a visualization of all the transit vehicles moving in real time!
Initially wanted to make this before my app but it was quite a bit to process all the GTFS data. But now that the data is already processed for the app, the visualization was quite easy to make!
Currently trying to add geocoding so users can search for destinations for routing. Been interesting as I want to avoid Google Maps and other private data sources so open street maps it is.
Re:Using Rust and an Old Kindle to Display Real-Time Transit Info
on Thursday October 24, 2024 @11:11PM (#41941912)
I also live in SF and made an iOS app (A Better Ride) to solve this exact problem. Just shows you departure times of transit for stops around you. The goal is to make transit less stressful by making it predictable and explorable. It’s just a passion project I work on in my free time with zero monetization
Re:Fogging your Google search history with Python and Reddit
on Thursday December 08, 2016 @05:44PM (#13135005)
This is pretty much what I did to game Bing's search rewards with multiple users but I used Yahoo Answers instead. Worked well actually
Re:Show HN: Shameless plug for my IOT dashboard (open source)
on Wednesday August 03, 2016 @12:22PM (#12219117)
Yes, it requires a ws ready broker. I used the browser version of MQTT.js (https://github.com/mqttjs/MQTT.js) to connect to the broker
Re:Show HN: Shameless plug for my IOT dashboard (open source)
on Tuesday August 02, 2016 @10:56PM (#12215265)
Hello!
A while ago, I made a simple IOT dashboard in Polymer that relies only on a MQTT broker and I figure that I would share it with you all!
The dashboard displays cards which show you data and/or available controls for your devices. The dashboard connects as a MQTT client along with the other IOT devices so this can be easily added to existing MQTT networks. Cards displayed on the dashboard are defined by the devices themselves. The data flow between the dashboard and the devices is bi-directional so the cards will always reflect the state of the device. Also, as the devices go online/offline the cards will appear and disappear too.
Regarding the modularity of the project, each card is an independent polymer component so that more types of cards can be added to fit your needs. There is a handful of cards I have made to fit basic use cases but feel free to add more!
I hope you like it! Let me know what you all think.
Demo: http://crouton.mybluemix.net *Click the “connect demo for me” button or use default MQTT details and “crouton-demo” as device name