Oyenza (trafik.live) and Luca Cada Lora: Where the Data Sits on the Openness Spectrum

This post is my technical analysis of public posts by @lucaxyzz (Luca Cada Lora) about Oyenza, the name trafik.live goes by. I am not a party to the thread. It accuses no one of a crime or a breach of terms, and it is my opinion, not a finding by any court or regulator. Source for observations: my passive look at trafik.live in a normal browser, 19 Nov 2026, 03.53 WIB.
Other posts in this series: a relay is still an API, the data openness spectrum, Pasal 332 and the "tanpa hak" test, Live became Simulasi and the stronger answer. Earlier record: right of reply for Luca Cada Lora.
When people asked Luca Cada Lora (@lucaxyzz) whether the API behind Oyenza (trafik.live) was open to the public, they were asking a fair question: where does this data sit between "official and licensed" and "forbidden"? The answer matters more than who sounded clever.
The spectrum
From safest to forbidden: official API (documented, licensed); open data (downloads, schedules); undocumented site endpoints; APIs behind a login; leaked secrets. By my reading, the CCTV feed on Oyenza sits at "undocumented site endpoint": an endpoint the source site uses itself, not promised to outsiders.
What is right and what is not
Right: it is not an official TJ or DJKA API; a relay is a sound pattern; one pull can serve many viewers; the simulation and schedule labels are written clearly; the CCTV source is credited.
Not right: "nobody uses an API" conflicts with "my own server's API" and with the /api/ paths I observed; reverse engineering finds an API but the need for one does not go away; a relay does not change the permission status of the upstream data.
Five risks that stay with a relay
- Brittleness: an undocumented endpoint can change without notice.
- Load: a government server also carries another product's traffic.
- Permission and terms: the right to use and re-broadcast is not clear.
- Accuracy: a position simulated from a schedule can be wrong.
- Security: a relay should use an allowlist, not act as an open proxy.
A checklist for any product built on someone else's data
Record the source endpoint, owner and documentation status; keep a licence, terms or an access request letter; use cache, rate limits and one pull per camera; label data as live, schedule or simulation; and keep a kill switch and a contact for the data owner.
I do not know Oyenza's server configuration, cache or permissions, so I make no claim about them.
Luca Cada Lora and Oyenza (trafik.live) can reply at admin@infraloka.co.id. A substantive response may be published alongside this article, and if reliable evidence shows a factual statement here is wrong, I will correct it promptly and note the change.
Published by Rahmat Wibowo, InfraLoka — infraloka.co.id
#Oyenza #TrafikLive #LucaCadaLora #FairRecord