Hacker News: xucheng

New comment by xucheng in "NeurIPS bans submissions from US-sanctioned institutions"

xucheng — Wed, 25 Mar 2026 02:11:00 +0000

> Sanctioned Institutions

> The NeurIPS Foundation, like any entity operating within U.S. legal jurisdiction, is required by law to comply with U.S. sanctions and trade restrictions. Under these regulations, providing 'services' (which includes peer review, editing, and publishing) to individuals representing sanctioned institutions is prohibited. Consequently, we are unable to accept or publish submissions from these institutions. This list of US-sanctioned institutions is available here: https://sanctionssearch.ofac.treas.gov/

NeurIPS bans submissions from US-sanctioned institutions

xucheng — Wed, 25 Mar 2026 02:11:00 +0000

Article URL: https://neurips.cc/Conferences/2026/MainTrackHandbook

Comments URL: https://news.ycombinator.com/item?id=47512331

Points: 3

# Comments: 1

New comment by xucheng in "Don’t Look Up: Sensitive internal links in the clear on GEO satellites [pdf]"

xucheng — Tue, 14 Oct 2025 06:46:02 +0000

It’s quite common for a DOI to be assigned to a paper after it’s accepted during camera ready. However, the DOI won’t work until the conference or journal version is published on the official website (ACM in this case). The version you’re viewing now is simply a preprint directly from the authors.

17 Pages [video]

xucheng — Thu, 15 May 2025 04:14:09 +0000

Article URL: https://nebula.tv/videos/17pages

Comments URL: https://news.ycombinator.com/item?id=43991784

Points: 2

# Comments: 0

New comment by xucheng in "Reverse geocoding is hard"

xucheng — Sun, 27 Apr 2025 16:35:03 +0000

Can this be solved by storing a timestamp of the record along with precise GPS coordinates? Could we then utilize some database to compute the drift from then and now?

Nebula Sans

xucheng — Sat, 05 Apr 2025 06:03:40 +0000

Article URL: https://nebulasans.com/

Comments URL: https://news.ycombinator.com/item?id=43591225

Points: 348

# Comments: 101

New comment by xucheng in "When the Dotcom Bubble Burst"

xucheng — Mon, 17 Mar 2025 21:04:22 +0000

At least, Cisco survived. Nortel and Lucent were not so lucky.

New comment by xucheng in "iTerm2 critical security release"

xucheng — Fri, 03 Jan 2025 02:52:18 +0000

Many years ago, I reported an issue where iTerm2 leaks sensitive search history to preference files [1]. The issue was quickly fixed. But until this day, I can still find people unintentionally leak their search history in public dotfiles repos [2].

[1]: https://gitlab.com/gnachman/iterm2/-/issues/8491

[2]: https://github.com/search?q=NoSyncSearchHistory+path%3A*.pli...

New comment by xucheng in "FDA Authorizes First Over-the-Counter Hearing Aid Software"

xucheng — Fri, 13 Sep 2024 02:16:18 +0000

Interestingly, in the end of the article, the FDA links to an old article hosted on web.archive.org[1] even though the linked article was originally published by FDA themselves. Considering the linked article was only published at 2022, a merely 2 years ago, maybe the FDA should do more to prevent dead links.

[1]: https://web.archive.org/web/20221028042729/https:/www.fda.go...

New comment by xucheng in "Gilead shot prevents all HIV cases in trial"

xucheng — Fri, 21 Jun 2024 05:43:12 +0000

Maybe better url, the official press release : https://www.gilead.com/news-and-press/press-room/press-relea...

@dang

Framework for Legislating on Artificial Intelligence (2023) [pdf]

xucheng — Wed, 05 Jun 2024 06:45:17 +0000

Article URL: https://www.eff.org/files/2023/07/24/2023.07.14_ai_two_pager.pdf

Comments URL: https://news.ycombinator.com/item?id=40582045

Points: 2

# Comments: 0

New comment by xucheng in "SQL:2023 has been released"

xucheng — Thu, 01 Jun 2023 18:21:51 +0000

A related question: what is the state in term of supporting the SQL standard among the popular RDBMS? It seems that almost all database engines use their own custom syntax.

New comment by xucheng in "Tuned Mass Damper of Taipei 101"

xucheng — Mon, 19 Sep 2022 10:46:08 +0000

You are confusing two different units. The earthquake moment magnitude scale measures the amount of energy of a given earthquake. It does not concern the location you are and the shacking you felt. Therefore, for this particular Taiwan earthquake, its magnitude is 6.9 regardless of the location.

The intensity scale on the other hand measures the amount of shaking for a given location. Naturally, the further you are from the epicenter, the lower the intensity will be.

New comment by xucheng in "Git.io deprecation"

xucheng — Tue, 26 Apr 2022 07:03:19 +0000

I mean that it is hard to scrape these git.io links used in the research papers to build the archive. Unless of course, if Github provides a DB dump, it would help everyone a lot.

New comment by xucheng in "Git.io deprecation"

xucheng — Tue, 26 Apr 2022 06:52:23 +0000

It is unlikely because it is very difficult and maybe illegal to scrape research papers. See https://en.wikipedia.org/wiki/Aaron_Swartz for example.

New comment by xucheng in "HackerRank (YC S11) DMCA'ed the SymPy Docs [fixed]"

xucheng — Wed, 20 Apr 2022 01:12:16 +0000

List of takedown notices from HackerRank to GitHub:

https://github.com/github/dmca/search?q=HackerRank&type=

New comment by xucheng in "HackerRank (YC S11) DMCA'ed the SymPy Docs [fixed]"

xucheng — Wed, 20 Apr 2022 01:01:25 +0000

> figure out a way where we can do things like randomizing questions but preserving the integrity of it to ensure a fair evaluation, etc

How does any of these have anything to do with copyright infringement in the context of DMCA takedown? Do you even own the copyright to the alleged leaked solution?

New comment by xucheng in "C Package Manager"

xucheng — Tue, 08 Mar 2022 06:44:20 +0000

> The wiki listing of packages acts as the "registry" and populates the clib-search(1) results.

This seems to be an extremely bad idea. Since everyone can edit the GitHub wiki pages, it means its registry is vulnerable to all kinds of malicious attack.

New comment by xucheng in "GitHub Actions checkspelling community workflow GitHub_TOKEN leakage via symlink"

xucheng — Thu, 09 Sep 2021 09:04:58 +0000

> Importantly, you must do this for every open branch in your repo. It is not enough to do so for only your default branch since a malicious PR can target any of your open branches. That is, if you have an open branch that uses a vulnerable version of check-spelling then a malicious PR targeting that branch can leak a GITHUB_TOKEN which can then be used to impact any of your branches, including your default branch.

I think this is a big design flaw in GitHub Actions. Whenever there is a security patch, you have to make sure to apply them in every branch. This includes all the historical branches and stale branches which the repo owners forget to delete.

New comment by xucheng in "The problem of effects in Rust (2020)"

xucheng — Sat, 28 Aug 2021 10:16:36 +0000

Compared with Rust’s Result monad, which allows developers to clearly see the effects of error handling, there are two other hidden fallible effects in Rust that are much harder to tackle:

* Panic rewinding. I am not sure how to ensure your Rust function being panic safe. It is quite easy to cause soundness issue if some invariants no longer hold due to panic. I see `PanicGuard` sometimes used in Rust std library.

* Future cancellation. `tokio::select` is one of the infamous examples, where it is quite easy to introduce bug if the future cannot handle cancellation gracefully.

When trying to handle them properly, it feels more like writing traditional C code than Rust.