pveierland

Mandating and accepting broad use of text watermarking at scale seems prime to enable all sorts of dumb and chaotic downstream effects. Not only do you start to pollute further corpus at scale - hijack text space bandwidth and fidelity - but you open the societal door to gradually add additional pieces of information - such as author identities or ad tracking information - which can then not just directly reveal a single author, but potentially larger graphs of information propagation without it being clear to anyone propagating such a trace.

> While Fraser's explanation was technical and specific, he hit a light-hearted note to summarise it: "LLMs [large language models] won't wipe out humanity because they just don't have that dog in them."

Never underestimate the drive of a good while loop.

Funny that this is the only Dropbox post I've seen on HN besides infamous references to their launch post. You'd think there would be plenty of interesting improvements to make.

Having been a paid user for the last decade my current experience is just getting error messages on my phone every week that something failed to sync, and that I have to re-enter the app every ~month to disable/enable syncing for my offline files, otherwise it doesn't work. I can't remember any time I've been pleasantly surprised by any change to the service.

They are clearly progressing now as a project and the world definitely needs what they are building - it's literally something you can download and run right now.

Rust was started in 2006 (20 years ago) and is now one of the most powerful programming languages, while the Servo project was started in 2012. If they reach parity and beyond of current browsers this could clearly become one of the most important browser engines in the future. Effort very well spent in my opinion.

I don't think it's an either or - additional data signals that need to correlate to authenticate will increase confidence. You can use multiple other signals to evaluate whether something is truly a landscape photo, and in that case not require a LiDAR capture, but if you are inside and at close range then you could assume that it should be part of scoring the authentication.

Similarly, LiDAR alone will help disqualify cases where someone is just taking a picture of e.g. a landscape target of the Golden Gate, but that it shown on a screen 1 meter away.

Still, that means that either the fake target scene and your screen presenting it would need to be outside of LiDAR sensor bounds, or you'd need to find a way to make the depth sensor data conform with your fake scene, both increasing the difficulty of producing a forgery.

Websites could use it to implement less power consuming behavior when you are low on power, e.g. defaulting to run an expensive computation when requested instead of automatically.

Ignoring browser fingerprinting, it seems like most of these signals could be used to implement some feature benefiting the user.