379 karma · joined February 3, 2020
Steganography fundamentally requires you to be able to know where the data is, which requires you to have the original image to compare against. The only other strategy I'm aware of is setting known pixel positions to exact data, which is very easy for basic tools to spot and decode. Or to add the data to non-visual data blocks if the image format supports those, which is also quite easy to spot.
No, this is a much more benign form of government overreach, one born out of a normal desire to suppress citizens, and perhaps a healthy amount of regulatory capture by large corporations.
Hearsay and gossip from the "juicy grape vine" along with implying Jarred is too stupid to critically think about his own path in life because he didn't go to university are not exactly statements of fact. They're elitist and vindictive, but those are not synonymous with honest.
> If that was your read, I think you're taking more from sources that aren't this post.
I'd encourage you to reread the post and try to catch how weirdly spiteful and inconsistent it sounds in places:
> But having graduated from the Thiel Fellowship school of thought rather than university...
> Jarred was a stinky manager. Poor communication, unrealistic expectations, low empathy, no experience. Just a total shit show, from an employment perspective.
> Jarred was already writing slop well before he had access to LLMs.
> Now, it's not our business to police what our users do... We made futile attempts to guide them towards better programming practices.
We have very different ideas about what kindness looks like. Honesty and rudeness are not synonyms.
I don't interact with Zig or Bun, but I certainly haven't been enticed to try Zig after this.
All of those are fixable of course, and the idea is neat! It's just a bit of a rough showcase, at least on Firefox.
How much was this article proof-read? Didn't they just get finished talking about how heap flattening won't work for objects with > 64-bit representations? Their `Point` is at least 65 bits (two 32-bit ints plus the null flag). The "plus a possible null flag" and oddly short following statements seem to suggest this was some AI that got sidetracked by trying to make emphatic statements... oh and also the "[IMAGE: the same Point[] array in two variants..." block halfway down the page is unfortunate.
> A lot of people mistakenly try to compare "cookies vs. JWT". This comparison makes no sense at all, and it's comparing apples to oranges - cookies are a storage mechanism, whereas JWT tokens are cryptographically signed tokens.
And yet the author seems not to have noticed, or something? Odd.
... are these not the same thing? I suppose from a technical standpoint they'd differ, but they achieve the same result: reusable, modular building blocks for creating interfaces.
Man, it's a rough environment right now marketing-wise. I don't know if they're contractually obligated to say the funny magic words, but the term AI is nearly entirely meaningless at this point. Akin to saying "behold my mighty calculator app: it prevents divisions by zero through artificial intelligence!"
I don't know about you, but if a random webpage takes 60+ seconds to load, I just close it and choose to never interact with that site again (unless it's my bank, which is a real and annoying occurrence).