codethief
Joined 16 years ago
Joined 16 years ago
Git commits get rebased, squashed, cherry-picked and edited retroactively, written during pair or mob programming sessions or rewritten during code review. And we also know that commit messages often suck. As a result, commits almost never tell you the full story about who exactly contributed, in what order or why.
The process is even messier when writing new bills. They get passed around between different departments, discussed & edited in various committees, etc.
Sure, you could force all participating parties to use git, prevent them from force-pushing or rewriting history even on their "feature branches", get them to sign their every commit, etc. But what you'd then likely just end up with is most negotiation & editing happening out-of-band.
Besides: At the end of the day it's the (majority of the) parliament that enacts a given law, so in my book they are all responsible, even if in practice laws get written by a small subset of people.
There was a time when I thought about figuring this out in detail and building an open-source alternative to Google Pay. But from what I've heard, integrating with credit cards is not something that can be done in an agnostic manner but actually requires support and buy-in by the issuing banks. Not a great perspective for such an app.
[0]: https://developer.android.com/develop/connectivity/nfc/nfc
PayPal also offers tap-to-pay, though I recently had to disable Graphene's "secure app spawning" feature for the PayPal app to get it to open.
> Quantum physics is a theory, as in "as far as we can tell, this is an exact mathematical description of the world".
Is it?
If by "mathematical exactness" you merely mean we have somehow been able to produce some numbers that later on we measured in experiments, then yes. (Though we haven't been able to produce such numbers in all cases, see e.g. [0].)
I my book, though, mathematical exactness means your model is mathematically consistent and is applied with the necessary mathematical rigor.
Quantum mechanics and quantum field theory, as they are commonly taught in universities, are everything but. They are a bunch of concepts and recipes that, albeit successful, are held together loosely with duct tape and lots of hand waving to make you ignore the logical gaps & jumps and the fact that many of the "mathematical" objects physicists refer to don't even exist[1]!
[0]: https://www.scientificamerican.com/article/this-simple-exper...
[1]: Haag's Theorem, Aizenman–Fröhlich Triviality Theorem, etc.
https://en.wikipedia.org/wiki/Decoherence
https://www.collinsdictionary.com/dictionary/english/decoher...
Weird, if the original messages have been published, why do both OP and the EuroNews article linked by the GP say that "Hackers have published 281 GB of AfD emails as AI summaries" and "A website published what it said were summaries of some of the emails but not the original messages"?
TIL there's something called a short ton.
> Now.. we’re really reaching the boundaries of my knowledge here, but as I understand, not all theorems in mathematics are provable by constructive proofs, which is what the Curry-Howard isomorphism gives us access to. So there will always be mathematical truths that are outside the reach of any type system, that are provable under for example the set of axioms known as Zermelo-Fraenkel set theory with the axiom of choice (ZFC). ZFC is provably more expressive than λC or any other type system we can come up with, because the axiom of choice gives us access to non-constructive proofs.
I am no expert on type theory nor logic but I think there are a few errors here:
- Curry-Howard is not restricted to intuitionistic logic / constructive type theories.
- Type systems can be made arbitrarily expressive.
- Non-constructive proofs exist in pure ZFC, too. They don't depend on assuming the Axiom of Choice. The core ingredient is the Law of Excluded Middle / proofs by contradiction.OP has written other fantastic posts, like this one on colors:
https://t3.at/blog/2026-08-21-color-1-rgb-cube/
@schindlabua: Your explanations made some things click for me for the very first time, thank you! (Also, the YouTube channel you linked to is indeed a fascinating rabbit hole: https://m.youtube.com/@ooqui )
In case you take suggestions for additional parts in that series: I would love to learn more about common color spaces such as DCI-P3 and Adobe RGB and how they relate to sRGB, and what the pipeline
(An application on, say, Linux/Wayland defines a pixel to have color C in color space S.)
->
(My color-corrected screen which supports/doesn't fully support color space S shows that color C.)
looks like exactly.[0]: See the link in https://news.ycombinator.com/item?id=50134172
Two suggestions: 1) Handwrite the website (mainly the copy but also the design) instead of letting Claude do that. Right now it is really hard to read and comprehend. 2) Drop the "frontend" terminology. Even if it makes sense from a technical perspective, people working in the legal field (who I suppose you want to reach) will likely find it confusing.