HN user

dinkelberg

248 karma
Posts2
Comments55
View on HN

Their shop is linked to in the bio. They don't seem to have a privacy policy up on the site. When in the checkout form it links to the generic Shopify privacy policy. No hints to the fact that uploaded images are processed by third parties, as far as I can tell. That should be corrected for sure.

From the analysis linked in TFA:

"The automated query can be based on: * Identity information included in the application or in travel documents, such as name, date of birth, national ID number, and/or * the fingerprint of an individual."

Sounds like they could send requests to that computer system just based on publicly available information on a person like name and date of birth, even if the person never applied for a visa or tried to enter the US.

obesity is a much bigger issue than hunger today

Hunger is acute suffering, mostly by people who cannot change anything about it, while obesity is more of an epidemiological problem and can in principle be avoided by eating (or in the case of dependent persons, feeding) less.

Biblical Hebrew has no vowel markings (well it does, but they are an interpretation), so it cannot be used in daily speech. Modern Hebrew is distinct from Biblical Hebrew

The same can be said about Latin (of which we do not exactly know how they used to pronounce words), or any other language. How to pronounce letters or words is always "interpretation" (or more accurately, tradition).

One more relevant study, but on the health effects of long term melatonin use:

https://newsroom.heart.org/news/long-term-use-of-melatonin-s...

"The main analysis found:

* Among adults with insomnia, those whose electronic health records indicated long-term melatonin use (12 months or more) had about a 90% higher chance of incident heart failure over 5 years compared with matched non-users (4.6% vs. 2.7%, respectively). * There was a similar result (82% higher) when researchers analyzed people who had at least 2 melatonin prescriptions filled at least 90 days apart. (Melatonin is only available by prescription in the United Kingdom.)

A secondary analysis found:

* Participants taking melatonin were nearly 3.5 times as likely to be hospitalized for heart failure when compared to those not taking melatonin (19.0% vs. 6.6%, respectively). * Participants in the melatonin group were nearly twice as likely to die from any cause than those in the non-melatonin group (7.8% vs. 4.3%, respectively) over the 5-year period."

However they were not able to control for severity of the insomnia and used dosage, because that data weren't in the dataset.

Melatonin pills seem to have extremely bad quality control:

"Melatonin content varied from an egregious −83% to +478% of labeled melatonin and 70% had melatonin concentration ≤ 10% of what was claimed. Worse yet, the content of melatonin between lots of the same product varied by as much as 465%.

[...]

The last disturbing finding was more than a quarter of melatonin products contained serotonin, some at potentially significant doses."

https://pmc.ncbi.nlm.nih.gov/articles/PMC5263069/

"In products that contained melatonin, the actual quantity of melatonin ranged from 74% to 347% of the labeled quantity. Twenty-two of 25 products (88%) were inaccurately labeled, and only 3 products (12%) contained a quantity of melatonin that was within ±10% of the declared quantity. [...] Serotonin was not detected in any product."

https://jamanetwork.com/journals/jama/fullarticle/2804077

"Half of the products tested met the label’s claim for melatonin, which means they fell between 76 and 126 percent of the claimed amount. Of the products tested, 20 had between 0 and 76 percent of the labeled content, and 35 had between 126 and 667 percent."

https://www.washingtonpost.com/wellness/2025/06/25/melatonin...

According to that blog post (https://security.googleblog.com/2024/09/eliminating-memory-s...), the vulnerability density for 5 year old code in Android is 7.4x lower than for new code. If Rust has a 5000 times lower vulnerability density, and if you imagine that 7.4x reduction to repeat itself every 5 years, you would have to "wait" (work on the code) for... about 21 years to get down to the same vulnerability density as new Rust code has. 21 years ago was 2004. Android (2008) didn't even exist yet.

XSLT RIP 8 months ago

If you want to keep XSLT in browsers alive, you should develop an XSLT processor in Rust and either integrate it into Blink, Webkit, Gecko directly, or provide a compatible API to what they use now (libxslt for Blink/Webkit, apparently; Firefox seems to have its own processor).

TFA itself has an incorrect DOCTYPE. It’s missing the whitespace between "DOCTYPE" and "html". Also, all spaces between HTML attributes where removed, although the HTML spec says: "If an attribute using the double-quoted attribute syntax is to be followed by another attribute, then there must be ASCII whitespace separating the two." (https://html.spec.whatwg.org/multipage/syntax.html#attribute...) I guess the browser gets it anyway. This was probably automatically done by an HTML minifier. Actually the minifier could have generated less bytes by using the unquoted attribute value syntax (`lang=en-us id=top` rather than `lang="en-us"id="top"`).

Edit: In the `minify-html` Rust crate you can specify "enable_possibly_noncompliant", which leads to such things. They are exploiting the fact that HTML parsers have to accept this per the (parsing) spec even though it's not valid HTML according to the (authoring) spec.