Infraloka Logo
Professional Blacklist: personal dispute documentation
OyenzaTrafik LiveLuca Cada LoraFair Record

Oyenza (trafik.live) and Luca Cada Lora: The Stronger Answer, an ADR Checklist and What I Do Not Conclude

Header illustration: Oyenza, trafik.live and Luca Cada Lora, a five-point checklist

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.

If someone asks Luca Cada Lora (@lucaxyzz) or Oyenza (trafik.live) where the data comes from, what is a better reply than calling the question foolish? Here is the answer I would write as an architect.

A stronger answer

"It is not an official API. Our server calls the endpoint the DJKA CCTV site uses, through a relay with a cache. Users' browsers never call the government server directly. Bus positions are simulated from the official schedule and labelled as such. We are applying for official access; the data owner can reach us at this address."

The point is to state the position on the spectrum clearly. A label for the asker is not needed.

An ADR checklist for products using someone else's data

  • Source: record the origin endpoint, owner and documentation status.
  • Permission: a licence, terms, or an access request letter.
  • Load: cache, rate limit, one pull per camera.
  • Quality: label live, schedule or simulation.
  • Exit: a kill switch and a contact for the data owner.

What I do not conclude

  • I do not say a crime or a terms breach occurred.
  • I do not assess Luca's ability or character beyond the posts shown.
  • I do not know the server configuration, cache or permissions behind the relay.
  • I do not know why the label changed from Live to Simulasi.

Closing

A relay is a good architecture decision, and it is still an API. Reverse engineering yields a map of an API, and permission still has to be answered. A question about the data source is due diligence and deserves a clear, calm answer.

Sources

Screenshots of @lucaxyzz posts and replies, 17 and 18 Nov 2026 (third-party identities hidden); the referenced table of the Kemenhub CCTV site, not re-verified; the @grok reply of 18 Nov as machine context; my passive observation of trafik.live on 19 Nov 2026 at about 03.53 WIB (no third-party endpoint was called by me); UU 1/2023 (KUHP) Pasal 24 to 30, 332, 333, 622; UU 1/2026; UU 11/2008 (ITE) Pasal 32, 33, 48, 49, 52 from Wikisource; UU 1/2024 Pasal 43; UU 20/2025 (KUHAP) Pasal 1 angka 45 and 46, 5, 23; KUH Perdata Pasal 1365 from general knowledge.

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