Earlier quoted context omitted.
It doesn't seem to be LLM, but reads like one. The author is German, maybe it's a language expertise thing, maybe he likes the LLM style (unrelated to his nationality). But yeah, sentences that only have 3-4 word each feel like 3rd grade writing; I couldn't read it.
Hey, I've always written like this. In school I couldn't stand subordinate clauses and long sentences because I'd lose my train of thought. But yea, I've noticed that people often find it hard to read so I'm going to work on that
I Stored a Website in a Favicon
71–80 of 120 posts
Re: I Stored a Website in a Favicon
#72Instead 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]);
Regular expressions? Ugh. Encode it properly as XML in the correct namespace, load it so, and take it from that. Or just serve the SVG file and use to embed the HTML, and include inside it. In theory you should be able to define a and use , but in practice neither Firefox nor Chromium seems to be handling that properly in a favicon, which is disappointing.
Oh yeah and favicon isn't part of the DOM.
Re: I Stored a Website in a Favicon
#73also https://pong-in-a-favicon.franzai.com/ for further favicon (mis)use
Re: I Stored a Website in a Favicon
#74Instead 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]);
Re: I Stored a Website in a Favicon
#75Nope, you can do it all in a single file with an html/png polyglot (and nowadays you can get better compression ratios with newer formats like webp).
https://web.archive.org/web/20120801001616/http://daeken.com...
Re: I Stored a Website in a Favicon
#76You can use the favicon cache as storage too, by redirecting users across domains. It's been proposed as a potential fingerprinting risk[0], and if a browser naively reuses the cache for incognito mode, it could be used to track users across browser profiles. [0]: https://www.schneier.com/blog/archives/2021/02/browser-track...
Wasn't this fixed or mostly fixed?
Re: I Stored a Website in a Favicon
#77> You still need a tiny bootstrap loader to decode the image. Nope, you can do it all in a single file with an html/png polyglot (and nowadays you can get better compression ratios with newer formats like webp). https://web.archive.org/web/20120801001616/http://daeken.com...
Re: I Stored a Website in a Favicon
#78Earlier quoted context omitted.
It doesn't seem to be LLM, but reads like one. The author is German, maybe it's a language expertise thing, maybe he likes the LLM style (unrelated to his nationality). But yeah, sentences that only have 3-4 word each feel like 3rd grade writing; I couldn't read it.
Hey, I've always written like this. In school I couldn't stand subordinate clauses and long sentences because I'd lose my train of thought. But yea, I've noticed that people often find it hard to read so I'm going to work on that
I thought the lack of fluff was refreshing!
Re: I Stored a Website in a Favicon
#79I found the agressively staccato, clearly LLM-generated content extremely difficult to read.
Too me, the author is just trying to get to the point. They know people start skimming if there is too much text.
Re: I Stored a Website in a Favicon
#80Earlier quoted context omitted.
Just because it's my windmill to tilt at: `[\s\S]` can be written shorter and more precisely as `[^]`.
ai says [^] is not portable; I did not test it. Too bad, I'll stick to [\s\S].