@shellsharks Thanks. I'm still envious of the POSSE stuff, but I guess I don't need it. It will just take a lot of time to implement POSSE. I'll get there eventually.
@shellsharks A simple page explaining that all the JavaScript code is under such-and-such license would suffice. Machine-readable licenses would be neat, but I just need to know if all the JS on the site has a free software license. Sorry for the confusion.
@kolev Beyond that, my in-line .js is not “packaged” in such a way that it would be easy to export, modify and re-deploy per-say as it is a bit haphazardly used from page to page, but it certainly isnt, as a matter of function, something that is invasive, or used to track/snoop/etc… I use it to show/hide some page elements or to do some crummy searching, but nothing devious in nature.
This is something that I've bookmarked though and want to look more into how to become "compliant" as it were 👍
@kolev I'm new to this site you linked to and new to this concept in general. Specifically, this idea of software being "free" (open). The article you linked to is a bit meandering and I admit I've read it a few times top to bottom and I’m still not entirely sure what it expects me to do. I’ll start by saying I have some imported js libraries (e.g. jquery, lunr.js, particles.js, etc…) which I've tried to keep enumerated here https://shellsharks.com/.well-known/pubvendors.json