War is an unconscionable horror. The illusions of "international law" and "rules of war" have lead us to believe that war can be clean, managed, and "civilized."
But wars are fought by humans and humans are messy. Humans are not well suited to following orderly rules. Humans respond to their environment. Humans in extraordinary situations can be extraordinarily vindictive and brutal. Sufficiently traumatized humans can act without a conscience, spreading trauma like an infection. If humans respond to their situation, then there can be no "civilized" war because war is itself an situation outside of the society. It is a place that promotes antisocial behavior and punishes pro-social behavior. War cannot be expected to follow "international law" because it is what fills the void created by the failure of "international law" (so long as we rely on nations).
To call for war is to inflict atrocities on civilians. It is to kill the parents and children who serve, and to destroy the combatants who survive. It is to infect both sides with a trauma that will spread if untreated, when soldiers come home or when they become mercenaries in other wars.
And yet... there are times when the brutality, the incompetence, the evil becomes so unbearable that no other option exists, when taking up arms is simply bringing symmetry to an existing asymmetric conflict. There are times when the worst possible thing is inescapable, though it can never be justified.
In this new era of war, in the scramble of conflict under the collapsing of the (poorly named) "Pax Americana," I hope that we, the people, can understand that war is not a tool to fulfill an objective. It is not part of a larger strategy. It is not an extension of deplomacy.
War is a failure.
While it may be the only way to deal with the irrational - the genocidal, the slaver, the dictator - it is still a failure. It is a failure to build a world in which these people can't control armies and economies, can't turn populations in to cults and bend nations to their will.
And we will continue to have such wars until we unite against those who would use as as pawns, who would control our lives and lead us to our deaths. We will have these wars until we unite, as one world, against those rulers. This is what I mean, and what a lot of other people mean, when we say, "No War, but Class War."
Analyzing Black-Hole Ringdowns with Orthonormal Modes
Soichiro Morisaki, Hayato Motohashi, Motoki Suzuki, Daiki Watarai
https://arxiv.org/abs/2507.12376 ht…
The permutation dimension of the Klein 4-group
Henry Harman
https://arxiv.org/abs/2507.11469 https://arxiv.org/pdf/2507.11469
Momentum-Resolved Relaxation-Time Approach for Size-Dependent Conductivity in Anisotropic Metallic Films
YoungJun Lee, Jin Soo Lee, Seungjun Lee, Seoung-Hun Kang, Young-Kyun Kwon
https://arxiv.org/abs/2508.08622
Some fun facts about #Python limited API / stable ABI.
1. #CPython supports "limited API". When you use it, you get extensions that are compatible with the specified CPython version and versions newer than that. To indicate this compatibility, such extensions use `.abi3.so` suffix (or equivalent) rather than the usual `.cpython-313-x86_64-linux-gnu.so` or alike.
2. The actual support is split between CPython itself and #PEP517 build systems. For example, if you use #setuptools and specify `py_limited_api=` argument to the extension, setuptools will pass appropriate C compiler flags and swap extension suffix. There's a similar support in #meson, and probably other build systems.
3. Except that CPython freethreading builds don't support stable ABI right now, so building with "limited API" triggers an explicit error from the headers. Setuptools have opted for building explicit about this: it emits an error if you try to use `py_limited_api` on a freethreading interpreter. Meson currently just gives the compile error. This implies that package authors need to actively special-case freethreading builds and enable "limited API" conditionally.
4. A some future versions of CPython will support "limited API" in freethreading builds. I haven't been following the discussions closely, but I suspect that it will only be possible when you target that version or newer. So I guess people will need to be building two stable ABI wheels for a time — one targeting older Python versions, and one targeting newer versions plus freethreading. On top of that, all these projects will need to update their "no 'limited API' on freethreading" conditions.
5. And then there's #PyPy. PyPy does not feature a stable ABI, but it allows you to build extensions using "limited API". So setuptools and meson just detect that there is no `.abi3.so` on PyPy, and use regular suffix for the extensions built with "limited API".
This https://arxiv.org/abs/2506.04907 has been replaced.
initial toot: https://mastoxiv.page/@arXiv_csCL_…
Generalist Models in Medical Image Segmentation: A Survey and Performance Comparison with Task-Specific Approaches
Andrea Moglia (Politecnico di Milano), Matteo Leccardi (Politecnico di Milano), Matteo Cavicchioli (Politecnico di Milano), Alice Maccarini (Universit\`a di Pavia), Marco Marcon (Politecnico di Milano), Luca Mainardi (Politecnico di Milano), Pietro Cerveri (Politecnico di Milano, Universit\`a di Pavia)
Millisecond-scale Volatile Memory in HZO Ferroelectric Capacitors for Bio-inspired Temporal Computing
Luca Fehlings, Thomas Mikolajick, Beatriz Noheda, Erika Covi
https://arxiv.org/abs/2508.08973
A Unifying Algorithm for Hierarchical Queries
Mahmoud Abo Khamis, Jesse Comer, Phokion Kolaitis, Sudeepa Roy, Val Tannen
https://arxiv.org/abs/2506.10238 h…
Structural and Optical Properties of Crystal Ion Sliced BaTiO$_3$ Thin Films
Hossein Esfandiar, Fatemeh Abtahi, Trevor G. Vrckovnik, G. Quyet Ngo, Rene Heller, Ulrich Kentsch, Fabian Ganss, Stefan Facsko, Uta Lucchesi, Stephan Winnerl, Falk Eilenberger, Dennis Arslan, Sebastian W. Schmitt
https://arxiv.org/abs/2508.05874