Constructing the Word's First JPEG XL MD5 Hash Quine
Posted by luispa 8 days ago
Comments
Comment by throw0101d 15 hours ago
---
Beware of having too-small fingerprint hashes though, or not checking enough of the digits.
$ echo -n retr0id_662d970782071aa7a038dce6 | sha256sum
307e0e71a409d2bf67e76c676d81bd0ff87ee228cd8f991714589d0564e6ea9a -
$ echo -n retr0id_430d19a6c51814d895666635 | sha256sum
307e0e71a4098e7fb7d72c86cd041a006181c6d8e29882b581d69d0564e6ea9a -
---Comment by Retr0id 14 hours ago
(Doing it the "obvious" way would involve infeasible amounts of storage space)
Comment by wizzwizz4 8 hours ago
Comment by zygentoma 16 hours ago
And also at the same time a good reminder for everyone to find a browser that supports JPEG XL. I wonder if that was part of the reason to do this. :)
Comment by embedding-shape 16 hours ago
That's probably furthest down on my list of features I look for in browser, where the top two are "Not run by a for-profit company living on extracting data from users" and "Can have tabs vertically in sidebar in a tree-based structured format".
Comment by MrAlex94 16 hours ago
- Supports JXL out of the box (including support for alpha transparency and animations)
- Vertical tabs with optional tree tabs (hired the original tree style tab developer to implement the feature)
- For profit, but I don’t want your data, collect it or use it to earn a living (telemetry/analytics/experiments disabled at build time and alongside a fair few patches on top to make sure external connections are limited to what’s necessary)
Sidebar, I’m the developer of Waterfox
Comment by embedding-shape 15 hours ago
While you're here, last time I came across your website (and it seems like it looks the same currently), I noticed that your browser comparison is not including Firefox, which is what you've forked from (as far as I can tell at least, it isn't made clear by the landing page actually, but the UI and name makes it obvious), which feels like it's a bit misleading almost intentionally.
Comment by MrAlex94 14 hours ago
Comment by embedding-shape 13 hours ago
Just adding Firefox in your comparison table really should be fine, and kind of makes me want to ask someone at Mozilla why others would be afraid of doing so.
Comment by progbits 14 hours ago
Chrome and Firefox are making a very reasonable decision to wait for a memory safe decoder.
Comment by F3nd0 14 hours ago
That said, have any of them subjected WebP or AVIF to the same strict requirements, or should we reserve those only for less complex codecs actually designed with images in mind?
Comment by wild_pointer 16 hours ago
Comment by bigbuppo 12 hours ago
Comment by QuaternionsBhop 5 hours ago
Comment by bigbuppo 2 hours ago
Comment by smokel 9 hours ago
Comment by b16m 2 days ago
Comment by blenderob 17 hours ago
Looks like it was banned: https://news.ycombinator.com/item?id=46188453
How is it still posting?
Comment by embedding-shape 16 hours ago
Banned accounts show up as [dead] as soon as they post, so most users don't see those comments, only those with showdead enabled. Commonly referred to as "shadowbanned" but usually operators also don't tell shadowbanned users they've been shadowbanned.
Comment by blenderob 16 hours ago
Comment by philipkglass 10 hours ago
Comment by poly2it 17 hours ago
Comment by jsnell 17 hours ago