- 🇺🇸United States illeace
I think this is a nice idea, but here are a few things to consider:
- Since the primary purpose of the embed feature is to use these H5P with external sites (like LMSs), we would want to preserve the default behavior of having these publicly visible (so we don't break existing installs)
- Adding the option to apply Drupal permissions to those embed paths sounds relatively straightforward
- ...but, all the individual *.h5p files that live in /sites/default/files/h5p/exports/ (i.e., in the public files directory) are going to be downloadable regardless, and they have very guessable names.
So, if the goal is to really protect the content of the H5Ps from anonymous users, then this becomes a bigger challenge.