Post APmKBZPjYQMjcAzLd2 by js@podcastindex.social
 (DIR) More posts by js@podcastindex.social
 (DIR) Post #APmCiEtw2gRXuzBKtc by chidgey@engineered.space
       2022-11-19T23:13:39.810128Z
       
       0 likes, 0 repeats
       
       @js What end user tools exist to examine the OP3 data at this stage? Anything in Alpha/Beta? Or is it just raw API queries?
       
 (DIR) Post #APmDKvUM9SQV0MfHai by js@podcastindex.social
       2022-11-19T23:20:09Z
       
       1 likes, 0 repeats
       
       @chidgey None that I know of, just the low-level api.Recently I've been heads down in user-agent land, since that's important to get right for OP3 stats.  Ended up creating a new user-agent pattern db and donated it to the OPAWG: https://github.com/opawg/user-agents-v2Download stats api and pages are up next.Do any of your shows currently have the OP3 prefix?  If so, I'll be able to back calc user-facing stats (once avail) from whenever you added it.
       
 (DIR) Post #APmDR4tM6To5uEI7xA by chidgey@engineered.space
       2022-11-19T23:21:39.175224Z
       
       0 likes, 0 repeats
       
       @js Yes I’ve added the prefix to all of them except Causality. Pragmatic will likely get the next most traffic. I was looking at how to validate it was picking up correctly in OP3 is all.
       
 (DIR) Post #APmHqbeVpxfuZEmEoi by js@podcastindex.social
       2022-11-19T23:23:32Z
       
       0 likes, 0 repeats
       
       @chidgey Head over to https://op3.dev/setup and validate every show you expect to be there!
       
 (DIR) Post #APmHqcCtm7BGHsrhPk by chidgey@engineered.space
       2022-11-20T00:11:06.369242Z
       
       0 likes, 0 repeats
       
       @js Did that already. More interested in the API queries to return data from the OP3 system.
       
 (DIR) Post #APmKBZPjYQMjcAzLd2 by js@podcastindex.social
       2022-11-20T00:18:30Z
       
       0 likes, 0 repeats
       
       @chidgey Ah ok - you might try hitting the (only) api endpoint in a browser or curl and filtering using the 'url' parameter with a wildcard ending based on your common episode url.i.e. for pragmatic (all hits starting 24hr ago)https://www.typescriptlang.org/play?#code/PQKgUGCCAOCWAEATA9gYwM4C54AsAue0Wwwy0AzAHSICmAbsAIZzAoYDEejA5sAE41EsAajwBaADbJu6UtBp9GeWMgB2wAI4BXBQE8ASoOE1RAGWnoIAMVgS8C+HmTxG8ABRTV3MTVXIt3DgAlPC+qFLoWgLwURLw0AIAZrAAHjHosF6OODTwAOSxefGMigC2EDSU3JTwich88AAKitylSrCoADTw6Fx8ylkATAAsOHzoLtzImGD4hMRyVLQMzLDAAIz8RiLiUjIA-L0leAC8YiM4AGR1fG2nAFboapdOANa+Jwn0sDQA7gAMAHZUDRLrETnMiJgSGQlvRgDRgKUjIxevVKr5uJkaApBJRVDQ8L96q9gAkeHcOqAICBgEA
       
 (DIR) Post #APmKBZs5qz3D28Fzpg by james@social.crid.land
       2022-11-20T00:35:03Z
       
       1 likes, 0 repeats
       
       @js @chidgey My ambition is to write something that works in the browser that would query a day’s worth of OP3 logs and give you downloads, geo-data, time-of-day-download data, and other things. I can write that in PHP easily, but would prefer to do it all in JavaScript if it’s possible to do. It might not be with CORS, I guess.
       
 (DIR) Post #APmXLKms5dqGYBnU2a by js@podcastindex.social
       2022-11-20T03:04:08Z
       
       1 likes, 0 repeats
       
       @james @chidgey OP3 is cors-friendly, you should be able to do everything in client-side JS