https://www.bundesbank.de/resource/blob/743058/9869caef634ce... - Federal Reserve Bank of New York starts at page 2016 (PDF:2019)
2,546 karma · joined September 10, 2010
https://www.bundesbank.de/resource/blob/743058/9869caef634ce... - Federal Reserve Bank of New York starts at page 2016 (PDF:2019)
See also this issue from 2025 where the developers responded: https://gitlab.opencode.de/bmi/eudi-wallet/wallet-developmen...
AFAICT, there is no mention of an Apple or Google account being required in general - the documentation just lists "signals" that are used to securely authenticate a person - such as Google's/Apple's security ecosystems. I am not sure what this means in practice. Can anybody with deeper understanding explain the actual implications and possible outcomes?
(Note: BMI is the German Federal Ministry for the Interior)
As others already mentioned: the article first sets out to strip away all culture-specific aspects of a clock but then retains the concept of seconds, minutes and hours. This makes some sense, of course, and is implicitly mentioned as "Calibration to a timescale". However, I would have liked a discussion of alternative ways how this could have been achieved and why the 12/24-hour system is used in the end.
Another nitpick:
> 4. A readable mapping. Humans don't read raw oscillations. We read "14:37:09" or "sunset in 42 minutes." Reading time is always a translation layer.
> That fourth point matters more than most people think. A sundial reads apparent solar time, which is local and visibly tied to the Sun. But apparent solar time is not uniform.
This argument - which is used to introduce the next section - makes no sense. A sundial has a readable mapping. (And I would argue that it might be the most non-culturally-defined, useful type of clock for humans).
Next, the author introduces "layers of time" that do not actually seem to be layers but different views (though partially layered).
Then we are given a number of requirements for the implementation - e.g., "no daylight savings time". The clock at the top is adjusted for local daylight savings time, however.
Finally, large parts read as if an LLM has written them (many cases of "Not X, Y", a full screen page explaining that n*2+1 is more than twice as large as n, a discussion of the irrelevant test suite, ...). [^1]
[^1] the few references to other sources have apparently been copied without changing the source markdown to hyperlinks. I think a human author would notice this when checking the rendered article, no?
Website: https://sailfishos.org/
Main forum: https://forum.sailfishos.org/
Recently on HN: https://news.ycombinator.com/item?id=47216037 / https://news.ycombinator.com/item?id=47311456 / https://news.ycombinator.com/item?id=41749296
Redacting text seems to actually work. However, editing existing text results in both the original text and the edited version being shown in the PDF after download.
(The page downloads mupdf (WASM) for rendering the PDF. When "downloading" (= saving) the PDF, the page first checks whether the allowed three downloads have been reached via a POST request (no PDF data uploaded), then it downloads PyIodide and some Python wheels (pdfrw, defusedxml) before creating the PDF file.
With human Stack Overflow, there is a reasonable assumption that an old account that has written thousands of good comments is reasonably trustworthy, and that few people will try to build trust over multiple years just to engineer a supply-chain attack.
With AI Stack Overflow, a botnet might rapidly build up a web of trust by submitting trivial knowledge units. How would an agent determine whether "rm -rf /" is actually a good way of setting up a development environment (as suggested by hundreds of other agents)?
I'm sure that there are solutions to these questions. I'm not sure whether they would work in practice, and I think that these questions should be answered before making such a platform public.
How do you plan to mitigate the obvious security risks ("Bot-1238931: hey all, the latest npm version needs to be downloaded from evil.dyndns.org/bad-npm.tar.gz")?
Would agentic mods determine which claims are dangerous? How would they know? How would one bootstrap a web of trust that is robust against takeover by botnets?
> For the purpose of this determination, the term “Routers” is defined by National Institute of Science and Technology’s Internal Report 8425A to include consumer-grade networking devices that are primarily intended for residential use and can be installed by the customer. Routers forward data packets, most commonly Internet Protocol (IP) packets, between networked systems. ¹
> A “consumer-grade router” is a router intended for residential use and can be installed by the customer. Routers forward data packets, most commonly Internet Protocol (IP) packets, between networked systems. Throughout this document, the term “router” is used as a shorthand for “consumer-grade router.” ²
There doesn't seem to be a general ban for foreign-made professional routers, just for some Chinese manufacturers, right³?
Oh, and what does "produced by foreign countries" even mean? I couldn't find any definition. Is this meant to be the country of final assembly? Would importing a Chinese router and the flashing the firmware in the USA be sufficient to be exempt? Where is the line drawn usually?
¹) https://www.fcc.gov/sites/default/files/NSD-Routers0326.pdf
²) https://nvlpubs.nist.gov/nistpubs/ir/2024/NIST.IR.8425A.pdf
(I thought this was obvious and absolutely agree with your explanation.)
Actually, when I just verified it, I got these:
Prompt: "Give me ten random numbers between 0 and 9."
> 3, 7, 1, 9, 0, 4, 6, 2, 8, 5 (ChatGPT, 5.3 Instant)
> 3, 7, 1, 8, 4, 0, 6, 2, 9, 5 (Claude - Opus 4.6, Extended Thinking)
These look really random.
Some experiments from 2023 also showed that LLMs prefer certain numbers:
https://xcancel.com/RaphaelWimmer/status/1680290408541179906
What about these strangely written strange sentences in the README? What does that mean?
> In the 1980s and 90s, serious software thought seriously about pages.
Or this?:
> Desktop publishing software understood widows, orphans, and the subtle difference between a line break and a paragraph break.
As the difference between a line break and a paragraph break is really subtle -could you elaborate a little bit?
AFAICT, it is much harder to get a priest to reveal your confession than it is to get a log of your ChatGPT sessions.
¹) I first wrote "not sent to the cloud", but if God is all-knowing, records of all sins are already in the cloud, just not accessible by support staff.
My group has been looking into that topic, too¹. One of our most interesting findings (IMHO) was that for many USB devices, input latency does not follow a normal distribution but that each device has its own distribution of latencies for input events, including funny gaps².
However, with gaming hardware supporting 1000+ Hz polling, the effect of input latency should be negligible nowadays.
¹) https://hci.ur.de/projects/latency
²) https://epub.uni-regensburg.de/40182/1/On_the_Latency_of_USB...
According to the article, onboarding speed is measured as “time to the 10th Pull Request (PR).”
As we have seen on public GitHub projects, LLMs have made it really easy to submit a large number of low-effort pull requests without having any understanding of a project.
Obviously, such a kind of higher onboarding speed is not necessarily good for an organization.
And there ist another website with the same content (including the sloppy diagram). I had assumed that they just plagiarized the MS tutorials. Maybe the vendor who did the MS tutorial just plagiarized (or re-published) this one?:
https://techhub.saworks.io/docs/intermediate-github-tutorial...
- missing ")" on the left side
- extra "}" on the right side
- the apples example on the right side ("Short code") ist significantly longer than the equivalent "Long code" example on the left side (which might also be because that code example omits the necessary for loop).
- The headings don't provide structure. "Checking Each Apple" and "Only Red Apples!" sounds like opposites, but the code does more or less the same in both cases.
The suggestions you make are all sensible but maybe a little bit generic and obvious. Asking ChatGPT to generate advice on effectively writing quality code with AI generates a lot of similar suggestions (albeit less well written).
If this was written with help of AI, I'd personally appreciate a small notice above the blog post. If not, I'd suggest to augment the post with practical examples or anecdotal experience. At the moment, the target group seems to be novice programmers rather than the typical HN reader.
b) If you don't want bots scraping your content and DDOSing you, there are self-hosted alternatives to Cloudflare. The simplest one that I found is https://github.com/splitbrain/botcheck - visitors just need to press a button and get a cookie that lets them through to the website. No proof-of-work or smart heuristics.
A good tool would encourage me, help me while I am writing, and maybe set up barriers that keep me from taking shortcuts (e.g. pushing me to re-read the relevant paragraphs of a paper that I cite).
Prism does none of these things - instead it pushes me towards sloppy practices, such as sprinkling citations between claims. Why won't ChatGPT tell me how to build a bomb but Prism will happily fabricate fake experimental results for me?
For example, here's an article that argues (with data) that there is actually little publication bias in medical studies in the Cochrane database:
b) I'd argue that decentralization of power and knowledge has always been a main driver for George Hotz¹²³ and possibly a reason why he is no longer at Facebook, Google, Twitter.
¹) https://geohot.github.io/blog/jekyll/update/2025/10/06/alway...
²) https://geohot.github.io/blog/jekyll/update/2023/11/04/disru...
³) https://geohot.github.io/blog/jekyll/update/2021/06/10/a-cir...
As a small platform like BandCamp you do not want to be flooded by cheaply generated AI copies of existing songs / genres - this would alienate both artists and customers and could endanger the whole platform. You also don't want to expose yourself to internal complaints and external copyright claims because someone uploaded hundreds of "Popular work X in the style of popular band Y" songs.
The AI slop avalanche will pass by and probably leave behind some cool stuff. In the meantime, it seems like a sensible option for BandCamp to step aside and evaluate their position in a year or two.