Thanks. The main problem is the restrictions imposed by the streaming services, but there's room for many features...

Yeah sure. My point is that I have to leave the streaming apps and use third-party services in the first place. If finding where to watch something requires another app or website, I’d argue the ecosystem itself has a UX problem

Apple TV comes the closest, if you ignore the Netflix sized hole.

Ok, I didn’t know this, thanks

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 actually feel the opposite of what most people are saying here. I thought your writing style was great. It felt like you respected my time as a reader and got to the fucking point.

I thought the lack of fluff was refreshing!

You're good fr. People on here who try to make their day about being AI detectives. You're trying to work on it and that's what matters

Yes, probably. I guess, you’d need a bigger favicon since the minimal Rust WASM binary is around 20KB+ (?)

You might find my tinkering useful: https://strich.io/blog/posts/embedding-webassembly-in-qrcode... A QR code isn’t much different from a favicon I guess. :)

The link is 404

It’s not for me?

you're right. The problem is with my Android application. Clicking the link through the website leads to a page

Yes, that would also work, thanks for pointing it out

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

Or just put the entire website in a <foreignObject> and render it in the favicon.

You can use any image format. Try using an animated gif.

I don't know what this is but it's huge.

https://news.ycombinator.com/favicon.ico

If you wanted to play around and do something a little more challenging (though you'd be bulking up the javascript) then one thing you could do is play with a bespoke html compression. You could store the tags in 4 bits `0001` first bit, tag open or close, and the remaining 3 bits indicate which tag is being used (div/p/b/h1/etc). With at least one of the values like `0111` indicating text is following and another tag like `1111` indicating that an unsupported tag follows.

If you extend it out to 8 bits you can pretty nearly store all the html tags (it'd give you 256 tags to play with).