If the code is obfuscated and the author did not add a license or link to the repository in the HTML of the website (or even better, make their site librejs compatible) then it can be very hard to track down if the website is actually using free javascript or not.
But I gotta admit this is something I'm personally guilty of as well, I still gotta make all the websites that I host librejs compatible, eventually...
@SuperDicq Generally it's best to go in the opposite direction; <script> /* GPLv3-or-later */ document.head.innerHTML = '<meta charset="UTF-8"><title>JavaScript detected</title>' document.body.innerHTML = 'We have detected that you have JavaScript enabled in your browser, please disable it to continue. Why is your browser automatically running malicious JavaScript?' </script>
@Suiseiseki@freesoftwareextremist.com Yeah also the librejs plugin is programmed in such a way that it detects "trivial" javascript that is too insignificant for copyright and marks it as freedom respecting.
LibreJS isn't great, but isn't terrible, as it compromises partially on freedom to make some sites that are light on JavaScript for navigation frills work.
Haketileo is the ideal solution, but using it is difficult due to the poor design of browsers.
@purple In my reading, I determined that the CC0 isn't a well written dedication, as it contains corporate propaganda, doesn't license patents and has numerous other issues.
This dedication is better, although unfortunately it isn't done yet; https://wpdd.info/
@Suiseiseki@freesoftwareextremist.com i specifically use cc0 on my website, with the intention of anyone being able to use any part of it, including the graphics, markup, styling, content, and even the two lines of javascript i use to tell chrome users to stop using chrome.
they are designed for creative works. a website is a creative work 💯
@Suiseiseki@freesoftwareextremist.com Oh yeah I've seen this project before but I forgot its name. Very good idea to crowdsource custom free javascript for websites that do not work with librejs.
@purple The 2 "WTFPL" licenses are poorly written informal licenses.
It is unclear if version 1 even gives you legal permission to modify or distribute software or HTML pages, or anything else.
Version 2 is not as bad, but it's still legally questionable and if you apply it to software, technically you are giving warranty for the software, as you haven't disclaimed it (although if such warranty claim somehow ended up in court, a judge would most likely conclude that it should have been obvious that there was no warranty, or may not) - the website FAQ advises that a warranty disclaimer is added in the source code if it's used for software; http://www.wtfpl.net/faq/