you know you’ve hit rock bottom when
Proof that MD5 collision exist.
So.. I have almost 0 knowledge of Java and I’m here learning how to code an Android app…. this is going to be great!
First part, getting my head around layouts, fragments and how it all works together
I haven’t been doing much lately, time is taken by a lot of other project that are not yet in the public eye.
Don’t worry, I’m not stopping in STO GTFS data project, just paused for a bit.
«It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change.» - Author unknown
Making progress, at least now I can pull the stops, routes and now trips.
The STO just (literally tonight) changed the way 1 data was shown, kinda annoying when it crash and you don’t know why….
If you take the 62 going to La Gappe station during the week, here is the full CSV of all the stops, their infobus number and the time it pass.
Next… make that data useful then starting doing it for more routes. I still need to generate a GTFS trips file correctly with some test data.
Dunno if it’s accurate but it’s what I’ve gather so far, now if only I could get some kind of GPS data for them….
It’s on GitHub for people interested in opening up the data.
So reverse engineering the STO site is fun… discovering that a stop can have 2 different identifiers bring more questions. There is also 2 sets of indexes per route.
Some bus route have 2 identifiers, I have my idea on this but I don’t know how accurate it is…. more research needed!
If you’re interested, I’m dumping the data I built on github.
Doing some reverse engineering on the STO Planibus is a full on dive in WTF ocean…
AS an example, just selecting the first bus stop in the departure section generate a 149 KB ajax response!
Or an initial visit to the site gives:
At least the load time stays low.
Disclaimer: I have a 50 mbps fiber internet.
Super popular new Australian Psychological adventure game.
I came for a strange strategy scroller…. walk out with a different opinion.
In an interesting work-around, Levison complied the next day by turning over the private SSL keys as an 11 page printout in 4-point type. The government, not unreasonably, called the printout “illegible.”
“To make use of these keys, the FBI would have to manually input all 2,560 characters, and one incorrect keystroke in this laborious process would render the FBI collection system incapable of collecting decrypted data,” prosecutors wrote.