gildas

No T-spins [1], impressive!

[1] https://harddrop.com/wiki/T-Spin_Guide

I think there's been a misunderstanding, there was an error in the article suggesting that zip.min.js is not inlined in the page. This error has been corrected meanwhile. I'm sorry for that. The goal is obviously to create pages that work offline, as shown in the demo.

A <noscript> script would be even more suitable, but I agree with the principle. I added a link to view the demo without downloading the file, see https://gildas-lormeau.github.io/Polyglot-HTML-ZIP-PNG/demo.... (it was not working previously because GitHub serves pages in UTF-8).

For the record, I've just added a link to view the file without downloading it.

That was just an example of syntax, nothing prevents you from blocking more resources and sandbox the page.

Thanks, it was an error on my part, now corrected.

This is done on purpose, so you can rename the file to make sure it's polyglot.

Indeed, for example the HTML of the files used for the presentation slides [1] use <noframe> tags to keep the HTML well-formed. This point is addressed in the conclusion of the presentation.

[1] https://github.com/gildas-lormeau/Polyglot-HTML-ZIP-PNG/raw/...

The request will be blocked by the CSP.

Here is the demo file (cf. the first paragraph and the end of the article): https://github.com/gildas-lormeau/Polyglot-HTML-ZIP-PNG/raw/...

Note that if you're on iOS, it's possible that the HTML page doesn't work at all because when it's opened from the filesystem, it's displayed by a viewer which doesn't support JS instead of Safari.

It's possible to define the Content Security Policy with a <META> tag in the "bootstrap page" and prevent this kind of security issue, e.g. <META http-equiv="content-security-policy" content="connect-src 'self' data: blob:;">

You're right, SingleFile (which is capable of saving pages in this format) does a little better than the demo, but it can also be optimized. In fact, I chose the JSON format to keep things as simple and didactic as possible for the presentation. I think I need to use your suggestions to optimize this structure in SingleFile ;)

Note that you can also take advantage of the fact that a ZIP can be password-protected and make your web page secret! For example https://gildas-lormeau.github.io/private/ (password: "thisisapage").

SingleFile respects your privacy, you can find the privacy policy here [1].

[1] https://github.com/gildas-lormeau/SingleFile/blob/master/pri...

I agree that it's debatable, which is why I used the word “almost” ;). The fact remains that this info isn't in RFCs and is hard to find on the web.

The saved page is encoded in windows-1252. It includes "consolidation data" to read the ZIP data as text from the DOM and recover the replacements of \r and \r\n occurrences (this is the only data loss and it represents approx. 1% of ZIP data), see the links below for more info.

https://gildas-lormeau.github.io/Polyglot-HTML-ZIP-PNG/en-EN...

https://gildas-lormeau.github.io/Polyglot-HTML-ZIP-PNG/en-EN...

https://gildas-lormeau.github.io/Polyglot-HTML-ZIP-PNG/en-EN...

I took another approach in SingleFile by offering a way to save pages as self-extracting pages (i.e. ZIP/HTML polyglot files), see [1] for more info.

[1] https://github.com/gildas-lormeau/Polyglot-HTML-ZIP-PNG

I'm actually referring to the "set of modifications" described here [1] and the fact that only Chromium can open (these) MHTML files today.

[1] https://docs.google.com/document/d/1FvmYUC0S0BkdkR7wZsg0hLdK...

Because the MHTML format produced by Chromium can almost be considered as proprietary.

See https://github.com/gildas-lormeau/SingleFile/blob/master/faq...

Thank you so much Niki :). The P2P sharing is a great idea. I really hope this feature will get things moving in the archiving field.

In the same vein, you can package HTML pages as self-extracting ZIP files with SingleFile [1]. You can even include a PNG image to produce files compatible with HTML, ZIP and PNG [2], and for example display the PNG image in the HTML page [3].

[1] https://github.com/gildas-lormeau/SingleFile?tab=readme-ov-f...

[2] https://github.com/gildas-lormeau/Polyglot-HTML-ZIP-PNG

[3] https://github.com/gildas-lormeau/Polyglot-HTML-ZIP-PNG/raw/...

Thanks for the upvotes. I've tried to communicate several times about this work here but I can't get any feedback. Please feel free to say what you think. I would really appreciate it.

For my part, I've had exactly the opposite experience. Without SSR or equivalent, you often have to wait weeks for your content to be indexed on Google, and the quality of the results varies. I'm talking about sites of at least several hundred/thousand pages.

In fact, I've only been making executable files available for a few weeks now. I'll have to see how to distribute them via Homebrew and so on.

You can find links to sponsor the project here [1] in the section "Sponsor this project" at the bottom right of the page.

[1] https://github.com/gildas-lormeau/SingleFile

Sorry for the confusion, I was referring to SingleFile run via the command line interface.

It's officially available on Firefox for Android [1] and Safari [2] on mobile. You might also be able to use it with Kiwi Browser [3] on Android.

[1] https://addons.mozilla.org/android/addon/single-file/

[2] https://apps.apple.com/app/singlefile-for-safari/id644432254...

[3] https://play.google.com/store/apps/details?id=com.kiwibrowse...

It's documented here: https://wiki.archiveteam.org/index.php?title=Restoring