Amazing!
I Stored a Website in a Favicon
11–20 of 120 posts
Re: I Stored a Website in a Favicon
#12I would have used a minimal service worker to unpack the web data and present it as if it were just a normal page being loaded.
Re: I Stored a Website in a Favicon
#13Instead of going via pixels, why not use a SVG favicon and directly store markup inside it and extract it? Use this favicon.svg: hello HN! use this in your to use a svg favicon: finally, use this in your to extract it and add it to your document body: fetch(favicon.href).then(r => r.text()).then(t => document.body.innerHTML += t.match(/ /)[0]);
Hey, yeah, I wrote the article. This (of course) would be more practical. Thanks for pointing it out. I wanted the payload to "live" in actual pixel data rather than hidden text inside an XML file. That’s why I went this way :)
Re: I Stored a Website in a Favicon
#14PNG has comment chunks tEXt, zTXt, and iTXt. You can have a completely normal image whose file is stuffed with as much content as you want. That is less fun, I suppose.
Yes, that would also work, thanks for pointing it out
Re: I Stored a Website in a Favicon
#15very cool and interesting
after reading just the title I wrongly assumed this would be about svg
Re: I Stored a Website in a Favicon
#16Instead of going via pixels, why not use a SVG favicon and directly store markup inside it and extract it? Use this favicon.svg: hello HN! use this in your to use a svg favicon: finally, use this in your to extract it and add it to your document body: fetch(favicon.href).then(r => r.text()).then(t => document.body.innerHTML += t.match(/ /)[0]);
Hey, yeah, I wrote the article. This (of course) would be more practical. Thanks for pointing it out. I wanted the payload to "live" in actual pixel data rather than hidden text inside an XML file. That’s why I went this way :)
The ico file format allows multiple resolution icons, so a lot of data
Re: I Stored a Website in a Favicon
#17Very cool. I wonder is it possible to make a simple game with also leveraging the webassembly?
Yes, probably. I guess, you’d need a bigger favicon since the minimal Rust WASM binary is around 20KB+ (?)
Re: I Stored a Website in a Favicon
#18Earlier quoted context omitted.
Hey, yeah, I wrote the article. This (of course) would be more practical. Thanks for pointing it out. I wanted the payload to "live" in actual pixel data rather than hidden text inside an XML file. That’s why I went this way :)
The ico file format allows multiple resolution icons, so a lot of data
Good point, I might add a section in the article where I list alternative approaches. Thanks
Re: I Stored a Website in a Favicon
#19Surprised that a minimal "website" only requires a small image = few pixels = few bytes to store it? Um, ok.
Re: I Stored a Website in a Favicon
#20Fascinating concept! Thanks for sharing this!