ap-andersson
Joined 5 years ago
Joined 5 years ago
Also if you, like me, wanted to blame or view history for specific files there does not seem to be a way by clicking in the GUI to achieve it. But by using Ctrl+P you get the command search and can search for "Blame" or "File history".
There is a good community out there on github and discord that have flight tracking as a hobby. In addition to ADS-B there is also voice radio transmissions from aircraft (airband) and text messages (ACARS) etc. If you get hooked there is lots of different things to tinker with.
- Hacki for Hacker News
- Immich
- Organic Maps
- Synchting-Fork
- VLC
- Voice Audiobook Player
There could be some improvements on the process of adding an app though. I recently made a very small app for myself that I thought "maybe a couple of people would find this useful, I should add it to F-Droid".
I started by reading their docs on how to add a new app. I created an account on gitlab, forked their repo and added my app. Their pipeline failed without telling me why. After reading and re-reading everything a bunch of times I had to give up and look for help. The instructions said to fix all pipeline problems before creating a merge request.
So I go to the contact page where there are a bunch of options. I chose IRC and join. Ask for help. No answer or any message sent in the channel for the next 24 hours. At this point I am getting a bit irritated and are thinking about truly giving up. Then eventually someone answers in the channel and says "create a merge request and someone will help you". Which is what the docs said NOT to do. Fine. Ok. I will create it.
I go to Gitlab and chose the right template for the merge request. And now I get a whole bunch of new instructions and questions that I have to answer that the docs never mentioned. And it even mentions in that template that I should TRY to fix pipeline problems, or someone will help me (still going against official docs on their site). Since there was a bunch of questions I would have to look up to properly answer I did not have the time to do it right away... And I still have not done it. Its on a todo-list.
tl;dr: F-Droid works okey but the whole process of submitting a new app for someone that has not gone through it before could be made way better with some updated and unified instructions.
There are a bunch of different protocols used to exchange scheduled and live transit information out there. And there are also a lot of different companies actually operating the vehicles (Transport Authorities). Sometimes several within one large city. But even if they have different systems underneath often they expose one of the popular protocols. Often there are even rules/law about certain protocols that you HAVE to support.
In USA that is mostly GTFS and GFTS-RT. I dod not think its a law but something about what you have to do to get funds maybe? I'm in Europe so my memory is foggy.
In EU I believe its NeTEx and SIRI. And every member nation needs a national hub where all transport authorities shares its data openly.
GTFS + GTFS-RT is very popular among consumer apps since its both pretty simple and pull-based. Static data is in CSV-files in a ZIP-file and the realtime data comes via Protobuf. If you check sources on the page this post is about you will se many GTFS sources. Ofc even transit systems built for the european standards can expose GTFS via a translation layer to support a broader range of consumers easily.
When it comes to signs at bus-stops there are those that are fed with this kind of data and can show both timetable data and realtime data based on the vehicles position. Here those signs are everywhere (Sweden) and I know there are plenty in the rest of Europe aswell. Outside of that I don't know if they are used as much.