Hacker News new | past | comments | ask | show | jobs | submit login

> Similarly, data should be open to stimulate innovation... At OP3, we apply this philosophy to both our podcasts and our data. Currently, OP3 focuses mainly on providing data to podcasters, then to podcast applications, and finally to the industry as a whole. The idea is not to allow the download of a complete database like PodcastIndex.org does, but to provide specific statistics and analyses. Users can get data on specific podcasts if they know their URLs. We may consider making the data more widely available on a paid basis in the future to support the project.

That is not open data as I understand it. How can data be called open when it's locked on someone's server and I have to pay them to access it? What's the difference between this open data standard and collecting data about users and selling it to marketing companies?




Yea that part got lost in translation.

The OP3 API is completely free to use: https://op3.dev/api/docs


> OP3 API is completely free to use

Is there a license for the data provided by the API?

> The idea is not to allow the download of a complete database like PodcastIndex.org

Can an API data client publish a private or public mirror of the entire database?


It's freely available to anyone - the data (after securely hashing IPs) is provided as a service for everyone in the open podcast system.

There is a bit about the data api in the privacy policy [1]. Feel free to engage over on the github repo if you are blocked on anything or to chat about it [2].

[1] https://op3.dev/privacy [2] https://github.com/skymethod/op3/discussions


  The Open Podcast Prefix Project (OP3) is a free and open-source podcast prefix analytics service committed to open data and listener privacy.
It would be helpful to link "open data" to an op3.dev/opendata page that either defines data usage rights or states something like "podcast analytics data is intended for use by individual podcast publishers. For usage of aggregated data, please contact []". Maybe an FAQ with examples of acceptable commercial usage.

The "listener privacy" text could be linked to op3.dev/privacy.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: