zlacker

[parent] [thread] 3 comments
1. simonw+(OP)[view] [source] 2024-08-24 17:29:49
One option her is to inline all assets - images etc - as bas64 URIs. The HTML page ends up huge but it will at least be self-contained.
replies(1): >>jml7c5+A1
2. jml7c5+A1[view] [source] 2024-08-24 17:42:35
>>simonw+(OP)
Yes, but it's not guaranteed to be self-contained. I wouldn't want to open a random HTML file knowing that it could phone home, or that the content might break one day without me realizing. There's a practical and psychological aspect to sharing `steves_paper_2014.html` versus `steves_paper_2014.offlinesitebundle`. The latter feels safe and immutable.
replies(1): >>irq-1+vh
◧◩
3. irq-1+vh[view] [source] [discussion] 2024-08-24 19:40:34
>>jml7c5+A1
What you want is an HTML tag or response header that restricts network access, which the browser can then enforce. Offline or a list of allowed domains, this would be great for security in general. Not so great for advertisers though.
replies(1): >>mewpme+EBc
◧◩◪
4. mewpme+EBc[view] [source] [discussion] 2024-08-29 07:30:47
>>irq-1+vh
Then you have to verify that the tag is there, right? But if it has another extension like .offlinebundle you can know thay browsers will not make any extra requests.
[go to top]