Preparation for GDPR/DSGVO
If you are using Podlove Publisher Tracking/Analytics, an update to this version is highly recommended.
Tracking uses a request_id to be able to determine when two requests came from the same user and should be counted as one unique access. This request id used to be a hash of the original IP address and the user agent. This approach however is vulnerable to a brute force attack to get the IP address back from the hash. Here’s what we are doing about that:
First, we anonymize the IP before generating the hash. So instead of using 171.23.11.209, we use 171.23.11.0.
Second, you need to deal with the existing request_ids. There is a new “DSGVO” section under “Tools” with a button that will rehash all existing request_ids with a randomly generated salt. That way it will become unfeasible to determine the original IP address but your analytics will stay the same.
In case you have a lot of downloads (let’s say much more than 50.000), you may want to do this via command line because that will be much quicker than via the tools section. You need wp-cli, then simply call wp eval 'podlove_rehash_tracking_request_ids();'. On a multisite, pass the blog id as a parameter: wp eval 'podlove_rehash_tracking_request_ids(42);'.
Other
- fix Podlove Subscribe Button language parameter
- fix
rel="self"link in show feeds - fix Podlove Subscribe Button not delivering show feeds
- templates: handle episode.show access when there is no show
- templates: allow episode filtering by show, for example:
{% for episode in podcast.episodes({show: "example"}) %}
