Meta’s banning of two anti-Zionist comedians from Instagram is the latest example of Big Tech’s deep anti-Palestinian bias
#meta #facebook #instagram
For Democrats, Mamdani Is a Wake-Up Call--and a Bad Example (Tom Suozzi/Wall Street Journal)
https://www.wsj.com/opinion/for-democrats-mamdani-is-a-wake-up-call-and-a-bad-example-7e43189c?st=KqkjDk
http://www.memeorandum.com/250702/p146#a250702p146
EigenBench: A Comparative Behavioral Measure of Value Alignment
Jonathn Chang, Leonard Piff, Suvadip Sana, Jasmine X. Li, Lionel Levine
https://arxiv.org/abs/2509.01938 https://…
$L^p$ Estimates for Eigenfunctions of a Generalized Landau Magnetic Laplacian
Ben Gabriel Goldschlager
https://arxiv.org/abs/2507.00183 https://
Parsimonious Gaussian mixture models with piecewise-constant eigenvalue profiles
Tom Szwagier, Pierre-Alexandre Mattei, Charles Bouveyron, Xavier Pennec
https://arxiv.org/abs/2507.01542
I haven’t added an example of how you implement migrations with Kitten’s¹ built-in JSDB database² yet but here’s one that I just used when renaming a field (property) in a table (JavaScript object) from “account” to “data” that illustrates the general granular approach you should take within persisted instances of JavaScript classes.
This is, of course, an advanced use case of the built-in JavaScript database that all Kitten apps have.
Kitten is simple for simple use cases. So ch…
Challenges & Opportunities with LLM-Assisted Visualization Retargeting
Luke S. Snyder, Chenglong Wang, Steven Drucker
https://arxiv.org/abs/2507.01436 …
Birkhoff-Kellogg type results in product spaces and their application to differential systems
Alessandro Calamai, Gennaro Infante, Jorge Rodr\'iguez-L\'opez
https://arxiv.org/abs/2509.01392
How to tell a vibe coder of lying when they say they check their code.
People who will admit to using LLMs to write code will usually claim that they "carefully check" the output since we all know that LLM code has a lot of errors in it. This is insufficient to address several problems that LLMs cause, including labor issues, digital commons stress/pollution, license violation, and environmental issues, but at least it's they are checking their code carefully we shouldn't assume that it's any worse quality-wise than human-authored code, right?
Well, from principles alone we can expect it to be worse, since checking code the AI wrote is a much more boring task than writing code yourself, so anyone who has ever studied human-computer interaction even a little bit can predict people will quickly slack off, stating to trust the AI way too much, because it's less work. I'm a different domain, the journalist who published an entire "summer reading list" full of nonexistent titles is a great example of this. I'm sure he also intended to carefully check the AI output, but then got lazy. Clearly he did not have a good grasp of the likely failure modes of the tool he was using.
But for vibe coders, there's one easy tell we can look for, at least in some cases: coding in Python without type hints. To be clear, this doesn't apply to novice coders, who might not be aware that type hints are an option. But any serious Python software engineer, whether they used type hints before or not, would know that they're an option. And if you know they're an option, you also know they're an excellent tool for catching code defects, with a very low effort:reward ratio, especially if we assume an LLM generates them. Of the cases where adding types requires any thought at all, 95% of them offer chances to improve your code design and make it more robust. Knowing about but not using type hints in Python is a great sign that you don't care very much about code quality. That's totally fine in many cases: I've got a few demos or jam games in Python with no type hints, and it's okay that they're buggy. I was never going to debug them to a polished level anyways. But if we're talking about a vibe coder who claims that they're taking extra care to check for the (frequent) LLM-induced errors, that's not the situation.
Note that this shouldn't be read as an endorsement of vibe coding for demos or other rough-is-acceptable code: the other ethical issues I skipped past at the start still make it unethical to use in all but a few cases (for example, I have my students use it for a single assignment so they can see for themselves how it's not all it's cracked up to be, and even then they have an option to observe a pre-recorded prompt session instead).