Nice, however:
> Vanilla JavaScript (ES6+) CSS3 with CSS Grid Minimal external libraries: marked.js, exifr, highlight.js, sql-formatter (all from CDN) No frameworks, no bundlers, no npm Hosted on Github Pages
One problem. - "Hosted on Github Pages"
I don't think either using GitHub or hosting it on Github Pages respects the user's "privacy".
A better way is to self-host on your own server + domain instead.
I fail to see how “hosted on Github Pages” has anything to do with the user’s privacy… This is not a snark, I really would like to understand.
It allows Microsoft to collect the traffic data. Generally it also implies the code is also hosted on Microsoft GitHub—which requires an account, accepting ToS, training the Copilot models by interacting with the platform.
Users do have the option to 'Git' or simply download the pages and use them locally, can't get more private than that.
Likewise the CDN's, probably.
CDNs are necessary for some tools, they wouldn't work without. The do CDNs help eliminate bloat.
I mostly do front-end work, so I get why you would default to CDNs - it's more likely that users ALREADY have that CDN link downloaded and cached on their machine than not. It's absolutely an upgrade for 99.9% of most use cases.
Here, on the other hand, you are trying for peak privacy, though, so the situation reverses. Every single third-party request is a potential attack vector. Contrary to general best practices, you would want to force yourself to include every CDN package unless there was some MASSIVE benefit to excluding them (and disabling the utility that relies on it), like hundreds of MBs of data for a rarely-used utility, or something that you wouldn't want to force on the majority of users.
That aside, I really appreciate this collection! Local first will always be preferred to server apps as far as I'm concerned, so this is fantastic!
> it's more likely that users ALREADY have that CDN link downloaded and cached on their machine than not
This isn’t how it’s worked for years. Browser isolate isolate assets like this to mitigate fingerprinting which renders the whole concept of use-CDN-since-it’ll-be-cached moot.
> CDNs are necessary
What exactly can't be repackaged / hosted alongside?
The bloat is still there, regardless of where its downloaded from.
It could all be done alongside but this seems redundant to me, the resources are already hosted elsewhere specifically for this purpose.
Right, including extra user tracking.
Yes, everything online seems to want to track you. I will seriously consider making all resources local. Then the tools could be used offline as well.