I was thinking of doing similar for Audiotarky.com, but decided that it wasn’t suitable for music, so wrote a simple server to protect the content. I’m also wondering about a next step with some kind of drm, though maybe that’s over kill for CC licensed stuff (which is the MVP).
I think you’re right that so long as you’re clear about what can be done you are ok.
I think it all depends on your objectives and constraints. I really don't want to write a server because of three reasons:
I don't want to offer a SaaS.
I don't want to deal with support for installing and maintaining it.
That is why static deployment is right for me. The user will be free to host the files in any solution they want. It also enables the generated site to be distributed outside the normal web with IPFS, Hyper, and similar protocols.
I was thinking of doing similar for Audiotarky.com, but decided that it wasn’t suitable for music, so wrote a simple server to protect the content. I’m also wondering about a next step with some kind of drm, though maybe that’s over kill for CC licensed stuff (which is the MVP).
I think you’re right that so long as you’re clear about what can be done you are ok.
I think it all depends on your objectives and constraints. I really don't want to write a server because of three reasons:
That is why static deployment is right for me. The user will be free to host the files in any solution they want. It also enables the generated site to be distributed outside the normal web with IPFS, Hyper, and similar protocols.
Yeah, makes sense :)