0xrsydn/research
1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Deepen comuline analysis: repo timeline, dormancy evidence, upstream drift

Browse source
This commit is contained in:
hermes 2026-10-12 12:59:31 +00:00
commit 1032de68be
4 changed files with 20 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
comuline-krl-data/next-steps.md
View file

@ -2,7 +2,7 @@
## Open questions
- Why did comuline's sync stop (~2025-03-30)? Project dormancy, token expiry, or upstream change — not observable from outside. (Author is reachable via the links in [[comuline-krl-data/sources|Sources]].)
- ~~Why did comuline's sync stop?~~ **Mostly resolved (see [[comuline-krl-data/analysis|Analysis]] timeline):** operations stopped ~2025-03-30 — no in-repo automation existed to fail (external/manual runs ended), and upstream drift since (endpoint renames, yearly token rotation) went unmerged. Residual: whether the author revives it (contactable via [[comuline-krl-data/sources|Sources]]).
- Current shape of the upstream partner API's data model (`krl-station`, `schedule`) — unverified; no credentialed call was made.
- **Live KRL tracking sources:** community trackers claim ~30 s updates (trackmycommuter, krljakarta.com, botkita). Where do their positions come from? A dedicated audit would be its own subtopic (KRL realtime — likely a different upstream than schedules).
- MRT Jakarta / LRT Jabodebek data sources (`jakartamrt.co.id` API was referenced by one community project) — candidates for umbrella subtopics.