Low Rank Jack's Avatar

Low Rank Jack

@lowrankjack.mathstodon.xyz.ap.brid.gy

Physicist, professor in UCLouvain, working on applied math, inverse problems in optics and astronomy for imaging, and compressive sensing theory and […] [bridged from https://mathstodon.xyz/@lowrankjack on the fediverse by https://fed.brid.gy/ ]

53 Followers  |  7 Following  |  37 Posts  |  Joined: 20.11.2024  |  2.2949

Latest posts by lowrankjack.mathstodon.xyz.ap.brid.gy on Bluesky

Enhancing Your Beamer Presentations with SVG Figures and Inkscape Layers | Laurent Jacques If like me you’re using Beamer to create slides in LaTeX, there’s a neat trick that helps you include SVG vector graphics—and even better, animate them progressively using Inkscape layers and Beamer’s overlay features like \pause or \onslide.

"Enhancing Your Beamer Presentations with SVG Figures and Inkscape Layers" https://laurentjacques.gitlab.io/post/enhancing-your-beamer-presentations-with-svg-figures-and-inkscape-layers/

07.11.2025 10:03 — 👍 0    🔁 0    💬 0    📌 0
Original post on mastodon.world

"Countries that slide from democracy toward autocracy tend to follow similar patterns. To measure what is happening in the United States, the Times editorial board has compiled a list of 12 markers of democratic erosion, with help from scholars who have studied this phenomenon. The sobering […]

31.10.2025 12:23 — 👍 0    🔁 25    💬 2    📌 0
Original post on chaos.social

This day 30 years ago - on Oct 26th 1995, #CPAN (the Comprehensive Perl Archive Network) was announced to the world by Jarkko Hietaniemi – CPAN's Self-Appointed Master Librarian (OOK!), to the comp.lang.perl.announce newsgroup.

Happy Birthday, CPAN! […]

25.10.2025 22:45 — 👍 4    🔁 12    💬 0    📌 0
Original post on infosec.exchange

Largest study of its kind shows AI assistants misrepresent news content 45% of the time – regardless of language or territory. An intensive international study was coordinated by the European Broadcasting Union (EBU) and led by the BBC […]

22.10.2025 18:08 — 👍 11    🔁 9    💬 0    📌 0
Original post on mathstodon.xyz

@laurentduval Hi Laurent, I kind of remember you explained me once that, for the Hadamard transform, the concept of "frequency" should be careful defined and you possibly gave a reference then that I forgot. Do you remember it? Thank you ;-) (I post this question here as it could be of general […]

15.10.2025 08:15 — 👍 0    🔁 0    💬 0    📌 0

I've been using Goodnotes for handwritten notes and PDF annotation on iPad, but the latest version is full of all kinds of weird AI things. It's no longer as responsive as it used to be, and it is hard to trust that no information will leak to third parties. Any good alternatives?

31.08.2025 13:17 — 👍 9    🔁 4    💬 2    📌 0

(sigh) How many (conference) articles mention something like "due to the space limit, we leave the proof to the supplementary material" with this “supplementary document” nowhere available!

12.10.2025 15:58 — 👍 0    🔁 0    💬 0    📌 0
Original post on mathstodon.xyz

Back to the wonderful CIRM (my last time here was in 2018), in Marseille, France for the workshop on "Blind Inverse Problems in Imaging", organized by Luca Calatroni, Emmanuel Soubies, and Pierre Weiss. I'm eager to attend the seminars tomorrow. More information here […]

28.09.2025 16:36 — 👍 3    🔁 0    💬 0    📌 0
Video thumbnail

This is amazing.

20.09.2025 10:34 — 👍 8633    🔁 3718    💬 75    📌 541
Finally Over: Google Blocks Sideloading of Android Apps Advertisements Summary Toggle * Security & Safety Excuse to Eliminate Sideloading * The Death of True Android Freedom * Android Introduces Mandatory Developer Verification by September 2026 * What’s at stake? * The Casualty List: Who Gets Hurt * How the System Works * The End of Open Android? * How This Will This Essentially End Sideloading on Android? * Conclusion: The End of Android as We Knew It In a shocking betrayal of Android’s foundational principles, Google has announced what can only be described as a death blow to the open ecosystem that made Android the world’s most popular mobile platform. Under the guise of “security,” Google is implementing draconian developer verification requirements that effectively eliminate true sideloading freedom for millions, if not billions, of Android users worldwide. Subscribe to Posts by Email This isn’t security enhancement—it’s corporate control disguised as protection, marking the beginning of the end for Android’s open nature, starting with banning sideloading of Android apps. It’s not the first time Google has attacked sideloading. It’s a systematic deprecation of an extremely useful feature that made Android what it is today. Prior to this, a new Google Play Integrity API was released to block apps from running on Android devices that do not meet certain Play Integrity checks including rooted, bootloader unlocked, custom ROMs, or phones that have even the Developer Options enabled. This was further met with another obstacle, wherein app developers have the power to force Android app installations through Google Play Store only. The said apps wouldn’t even launch if not installed through Google Play Store. Soon Sideloading will be added to the KilledByGoogle list. ## Security & Safety Excuse to Eliminate Sideloading Google’s justification for this authoritarian overreach relies heavily on inflated statistics designed to terrify users. The company claims that sideloaded apps contain 50 times more malware than Google Play apps—a convenient statistic that conveniently ignores the fact that Google Play itself has been plagued by malicious apps for years. This fearmongering narrative paints sideloading as an inherently dangerous activity, when in reality, it has been a cornerstone of Android’s appeal to power users, developers, and privacy-conscious individuals who refuse to be locked into Google’s walled garden. Advertisements The so-called “recent attacks” and “financial fraud” that Google references are being used as a pretext to eliminate one of Android’s last remaining advantages over iOS: true user freedom and choice in app installation. All this came into light when Google published an article stating “A new layer of security for certified Android devices” – which, to be honest, seems like security disguised as surveillance. ## The Death of True Android Freedom Starting in 2026, Google will require ALL apps installed on “certified Android devices” to be registered by “verified developers.” This Orwellian requirement sounds benign until you understand what it really means: **every single app you want to install must first receive Google’s blessing through their verification process.** This is not developer verification—this is **Google gatekeeping**. Every independent developer, every open-source project, every privacy tool, and every alternative app that doesn’t align with Google’s commercial interests will now face bureaucratic barriers that didn’t exist before. ### Android Introduces Mandatory Developer Verification by September 2026 Google’s latest announcement strikes another blow against independent app developers. Google is implementing a significant “security enhancement” for Android that will fundamentally change how apps are distributed. **Starting September 2026** , all apps installed on certified Android devices must be registered by verified developers. The verification process involves **two key steps** : #### Step 1: Identity Verification * Provide personal details (name, address, email, phone) * Organizations need D-U-N-S numbers and website verification * Government ID may be required #### Step 2: App Registration * Prove app ownership with package names and signing keys * Google Play developers will have automatic registration * Off-Play distribution requires manual registration #### Timeline and Rollout The requirement launches in **Brazil, Indonesia, Singapore, and Thailand** in September 2026, with global expansion continuing through 2027. Early access begins October 2025, with full verification opening March 2026. Advertisements The rollout follows a careful timeline: * **October 2025** : Early access testing begins * **March 2026** : All developers gain access to the new console * **September 2026** : Requirements launch in Brazil, Indonesia, Singapore, and Thailand * **2027** : Global expansion planned Google emphasizes maintaining Android’s openness while enhancing security, with special considerations for student and hobbyist developers through separate account types. While Google claims to support student and hobbyist developers with “separate accounts,” the lack of concrete details suggests another empty promise. This verification system transforms Android from an open platform into a **walled garden** , potentially killing innovation from smaller developers who built Android’s success. ## What’s at stake? Google claims this preserves “choice” and maintains Android’s “openness,” but this is corporate doublespeak at its finest. You can still “sideload” apps, they say—you just need Google’s permission first. This is like claiming you have freedom of speech while requiring government approval for every word you utter. The new system creates a false choice: submit to Google’s verification bureaucracy or lose access to the apps you want. For many independent developers and users who value privacy and autonomy, this isn’t a choice at all—it’s surrender. Google is establishing what they euphemistically call an “Android Developer Console” for non-Play developers. In reality, this a system designed to make app distribution more difficult and expensive for anyone who doesn’t want to play by Google’s rules. While Google hasn’t explicitly outlined costs, their track record with Google Play Developer registration suggests this “verification” won’t be free. Independent developers, open-source contributors, and hobbyists will likely face: * **Registration fees** that create barriers for small developers * **Identity verification requirements** that compromise developer privacy * **Ongoing compliance obligations** that drain time and resources * **Arbitrary rejection risks** with little recourse for appeals ### The Casualty List: Who Gets Hurt This verification requirement will disproportionately harm exactly the developers and users who have made Android valuable: Advertisements #### Independent Developers Small developers who can’t navigate Google’s bureaucracy or afford verification costs will be pushed out of the ecosystem entirely. #### Open Source Projects Community-driven projects that rely on volunteer contributors will struggle with verification requirements that assume commercial development models. #### Privacy-Focused Applications Apps designed to protect user privacy from corporate surveillance will face additional scrutiny and potential rejection from Google’s verification process. #### Regional and Niche Applications Developers serving specific communities or regions may find the verification process unsuitable for their needs and resources. #### Research and Educational Projects Academic researchers and educational institutions may be unable to comply with commercial verification requirements. ### How the System Works Beginning in October 2025, Google will launch an early access program for developers to test the new verification process. The company has created a streamlined Android Developer Console specifically for apps distributed outside the Play Store. Developers must complete several steps: 1. **Identity Verification** : Developers must prove their identity through Google’s verification process 2. **App Registration** : Package names and signing keys must be registered with Google 3. **Ongoing Compliance** : Maintain verified status to ensure app functionality Notably, Google won’t review the content or functionality of these sideloaded apps—only the developer’s identity matters for the verification process. ## The End of Open Android? Google’s announcement of mandatory developer verification for all Android apps represents a seismic shift in the mobile ecosystem. Starting in 2026, the search giant will require every Android app developer to verify their identity before their applications can be installed on certified devices—regardless of whether they distribute through the Play Store or alternative channels. This move marks perhaps the most significant departure from Android’s open philosophy since the platform’s inception, trading freedom for security in ways that could fundamentally alter how we think about mobile app distribution. Advertisements The new system operates on a simple premise: no unverified app will run on certified Android devices. Google compares this to “checking IDs at the airport,” positioning the requirement as a basic security measure rather than a restriction on freedom. However, the implications extend far beyond this airport analogy suggests. ## How This Will This Essentially End Sideloading on Android? The implementation of Google’s developer verification system will dramatically alter how regular Android users interact with their devices, fundamentally changing the mobile experience in ways that many users may not immediately recognize. For years, Android users have enjoyed the freedom to install applications from any source—whether from alternative app stores like F-Droid, Aurora Store, or directly from developer websites. This flexibility allowed users to access beta versions of apps, install region-locked applications, or try experimental software that wasn’t available through official channels. Under the new system, this entire ecosystem of alternative app distribution will be severely restricted, as only apps from verified developers will function on certified Android devices. The impact on user choice and digital autonomy cannot be overstated. Currently, tech-savvy users can bypass Google’s restrictions and install any software they choose, accepting the security risks in exchange for complete control over their devices. This has enabled use cases ranging from installing ad-blocking browsers that aren’t allowed in the Play Store to running specialized productivity tools for niche industries. The verification requirement effectively removes this choice, forcing all users into Google’s security framework regardless of their technical expertise or risk tolerance. Users who previously could make informed decisions about which apps to trust will no longer have that option, as the decision is made for them at the system level. The changes will particularly affect users in regions where official app availability is limited or where local developers create solutions for specific cultural or linguistic needs. Many international users rely on sideloading to access apps that aren’t available in their regional Play Store, while others use it to install apps from local developers who may not have the resources or desire to navigate Google’s verification process. Small developers creating apps for specific communities—such as accessibility tools, educational apps for local schools, or cultural applications—may find the verification requirements burdensome, potentially leaving their user communities without access to these specialized solutions. Perhaps most significantly, the verification system eliminates what has been a key differentiator between Android and iOS: the ability to truly own and control your device. While Apple has always maintained strict control over iOS app installation, Android users have had an escape hatch through sideloading. This freedom attracted users who valued digital sovereignty and didn’t want to be locked into a single company’s vision of acceptable software. The new requirements move Android much closer to iOS’s walled garden approach, potentially eliminating one of the primary reasons users chose Android over Apple’s platform. ### Conclusion: The End of Android as We Knew It Google’s developer verification requirement represents nothing less than the death of Android’s open ecosystem. Under the pretense of security, Google is implementing the same walled garden approach that Android users have long rejected in Apple’s iOS. Android succeeded because it offered an alternative to corporate control over personal devices. By eliminating true sideloading freedom, Google is destroying the very foundation that made Android valuable to millions of users worldwide. Advertisements The verification requirement will make Android indistinguishable from iOS in the ways that matter most: user freedom, developer autonomy, and genuine choice in software installation. Google has chosen corporate control over user empowerment, and the Android ecosystem will never recover from this authoritarian overreach. The message from Google is clear: your device belongs to them, not you. And if you want to install software they haven’t approved, you’re out of luck. 🔥Share This Article View More on Latest

"Finally Over: Google Blocks Sideloading of Android Apps" https://www.androidsage.com/2025/08/26/google-blocks-sideloading-of-android-apps/

18.09.2025 05:46 — 👍 0    🔁 0    💬 0    📌 0
A variation of the "distracted boyfriend" meme.
In this version, everyone is in wearing togas, and the boyfriend has been turned to stone as he looks back at a passing Medusa.

A variation of the "distracted boyfriend" meme. In this version, everyone is in wearing togas, and the boyfriend has been turned to stone as he looks back at a passing Medusa.

So help me, I laughed
#shitpost #meme #distractedBoyfriend

09.09.2025 14:13 — 👍 56    🔁 208    💬 7    📌 0
“Owner of …” or “Moderator on…”

“Owner of …” or “Moderator on…”

#Mastodon does NOT need to verify you in ANY way!

The only verification happening is when you create an account and confirm your email, that’s it

Staff members can recognized by a badge on their profile right under the username(see image)

If someone does ask […]

[Original post on mstdn.social]

31.08.2025 13:31 — 👍 5    🔁 91    💬 6    📌 0
Original post on mathstodon.xyz

Just arrived in the wonderful city of Lyon, France, to begin a sabbatical year at ENS Lyon, working with Rémi Gribonval and Paulo Gonçalves' OCKHAM team [1]. The location is magnificent, and I am welcomed in the Collegium, the institute for advanced study of Lyon University [2], located inside […]

31.08.2025 18:58 — 👍 4    🔁 0    💬 0    📌 0
Original post on piaille.fr

Linux franchit les 6 % de parts de marché sur desktop : vers une adoption de masse ?
https://www.blog-nouvelles-technologies.fr/336627/linux-6-pourcent-part-marche-desktop-2025/

"C’est une statistique qui aurait semblé impensable il y a encore quelques années. Selon une étude menée par […]

18.08.2025 16:49 — 👍 1    🔁 4    💬 1    📌 0
Andrew Kadel @DrewKadel@social.coop

My daughter, who's had a degree in computer science for 25 years, posted this about ChatGPT on Facebook. It's the best description I've seen.

Something that seems fundamental to me about ChatGPT, which gets lost over and over again:

When you enter text into it, you're asking "What would a response to this sound like?"

If you put in a scientific question, and it comes back with a response citing a non-existent paper with a plausible title, using a real journal name and an author name who's written things related to your question, it's not being tricky or telling lies or doing anything at all surprising! This is what a response to that question would sound like! It did the thing!

But people keep wanting the "say something that sounds like an answer" machine to be doing something else, and believing it *is* doing something else.

It's good at generating things that sound like responses to being told it was wrong, so people think that it's engaging in introspection or looking up more information or something, but it's not, it's only, ever, saying something that sounds like the next bit of the conversation.

Andrew Kadel @DrewKadel@social.coop My daughter, who's had a degree in computer science for 25 years, posted this about ChatGPT on Facebook. It's the best description I've seen. Something that seems fundamental to me about ChatGPT, which gets lost over and over again: When you enter text into it, you're asking "What would a response to this sound like?" If you put in a scientific question, and it comes back with a response citing a non-existent paper with a plausible title, using a real journal name and an author name who's written things related to your question, it's not being tricky or telling lies or doing anything at all surprising! This is what a response to that question would sound like! It did the thing! But people keep wanting the "say something that sounds like an answer" machine to be doing something else, and believing it *is* doing something else. It's good at generating things that sound like responses to being told it was wrong, so people think that it's engaging in introspection or looking up more information or something, but it's not, it's only, ever, saying something that sounds like the next bit of the conversation.

The only thing ChatGPT ever does.

14.08.2025 19:35 — 👍 397    🔁 262    💬 10    📌 5
A dice, lost inside a old style wooden school bench. The picture is shot from inside the bench drawer. A shaft of light falls on the dice from a slit on the top right. The dice is in front of the camera, displaying the score six on its only visible face. The wooden interior of the bench is raw and dusty, with paint streaks and tone variations on the wood. Five circular spots of light, coming from a hole not visible on the picture (the ink pot well lit by several light sources in the room), are marking the wooden floor where lies the dice.

A dice, lost inside a old style wooden school bench. The picture is shot from inside the bench drawer. A shaft of light falls on the dice from a slit on the top right. The dice is in front of the camera, displaying the score six on its only visible face. The wooden interior of the bench is raw and dusty, with paint streaks and tone variations on the wood. Five circular spots of light, coming from a hole not visible on the picture (the ink pot well lit by several light sources in the room), are marking the wooden floor where lies the dice.

Find a caption...

12.08.2025 19:35 — 👍 0    🔁 0    💬 0    📌 0

If you haven't seen this yet, watch.

It's an AI vid of the "grand opening" of the hideously gilded, wildly overpriced, Let Them Eat Cake future Trump Ballroom.

https://www.youtube.com/watch?v=nD_25aSMSFc&t=5s

09.08.2025 23:33 — 👍 6    🔁 41    💬 8    📌 0
Original post on mathstodon.xyz

Fun statistical observation: If X follows a Chi square distribution with k degrees of freedom, while the MGF Eexp(tX)] of X doesn't exist for t>1/2, I computed that, for k=3, and the cardinal hyperbolic sine sinhc(u):=sinh(u)/u that basically behaves like exp(u)/2u if u is large, then […]

03.08.2025 16:58 — 👍 0    🔁 0    💬 0    📌 0
Preview
SampTA 2025

Currently at the "Sampling Theory and Applications" conference (#Sampta25), enjoying great talks and the beautiful city of Vienna. https://sampta25.univie.ac.at

30.07.2025 07:11 — 👍 2    🔁 0    💬 0    📌 0
Original post on mastodon.nz

Microsoft, AWS, and even France-based OVHCloud say that they can't keep the US Government's hands off your data, if requested under the CLOUD Act.

👉 You can't guarantee data sovereignty using a provider that is subject to US law, even if your data is housed outside the US […]

28.07.2025 02:06 — 👍 4    🔁 62    💬 3    📌 0
Original post on fediscience.org

"Why are data nerds racing to save US government statistics?"
https://archive.is/7gF5f

"After watching data sets be altered or disappear from U.S. government websites in unprecedented ways after President Donald Trump began his second term, an army of outside statisticians, demographers and […]

24.07.2025 18:51 — 👍 0    🔁 5    💬 0    📌 0
Original post on fediscience.org

"Archivists Recreate Pre-Trump #CDC Website, Are Hosting It in Europe."
https://www.404media.co/archivists-recreate-pre-trump-cdc-website-are-hosting-it-in-europe/

"A team of volunteer archivists has recreated the Centers for Disease Control website exactly as it was the day Donald Trump was […]

20.07.2025 13:26 — 👍 10    🔁 119    💬 1    📌 2
IMO2025Q1
YouTube video by Timothy Gowers IMO2025Q1

From time to time I like to video myself solving maths problems in real time. Since the IMO has just happened, I plan to try a few of this year's questions. Here I get through Question 1. More to come at some point.

www.youtube.com/watch?v=1G1n...

18.07.2025 16:34 — 👍 46    🔁 13    💬 3    📌 3

Guardian version https://www.theguardian.com/tv-and-radio/2025/jul/18/the-late-show-with-stephen-colbert-to-end-in-2026-as-cbs-cancels-show?CMP=Share_iOSApp_Other

18.07.2025 09:59 — 👍 0    🔁 1    💬 1    📌 0
Original post on mastodon.social

Please report any account that tells you that you need to verify your #Mastodon account to continue using it through a private message. It is a scam. We do not require identity verification. Real staff accounts either have a special role badge on their profile or are verified through the […]

13.07.2025 00:01 — 👍 27    🔁 425    💬 4    📌 1
The card game "publish or perish"

The card game "publish or perish"

Look at what my friend brought me from the USA!

With many thanks to @fuzzyleapfrog for the recommendation!

#AcademicChatter

12.07.2025 17:27 — 👍 5    🔁 5    💬 0    📌 0
Preview
Standard error of what now? Scrolling through discourse about the evil vector, I stumbled across a group of people dismayed that the papers they were reviewing for NeurIPS didn’t include proper error bars. In fact, I learned that there’s a checklist that authors must fill out and attach to every NeurIPS submission. You can still learn things on social media. The NeurIPS program chairs introduced the checklist in 2021. They argued that the community wanted “both more guidance around how to perform machine learning research responsibly and more flexibility in how they discuss this in their papers.” They came to this conclusion after listening at the “NeurIPS 2020 broader impacts workshop,” a fully remote workshop held during the cold, dark winter of the second wave of the covid pandemic. They argued that they would experiment with a checklist as a way to facilitate more responsible machine learning. They called the checklist “experimental,” though there is no control group.1 They hoped that “future Program Chairs will continue to improve and evolve the checklist in subsequent years.” You don’t have to be a bureaucracy scholar to know that checklists “improve and evolve” by metastasizing in length and complexity. And that’s precisely what we’ve seen. The NeurIPS paper checklist is now 3800 words long. This is twice as long as the original checklist, and has 3 times as many items to check off. It’s a lot of ridiculous infantilizing boilerplate. Item 1: “Do the main claims made in the abstract and introduction accurately reflect the paper's contributions and scope?” Come on, folks. You are required to check that you have read the code of ethics (another 2000 words here). You are asked to check whether you obtained the appropriate IRB approvals. Of course, this only applies if you are at a university. There’s a call out to the AI Safety dorks: “Do you have safeguards in place for responsible release of models with a high risk for misuse (e.g., pretrained language models)?” Come on, folks! But I’m particularly fascinated by the weird obsession with statistics. I imagine Leo Breiman is chuckling up in heaven that one of the two cultures is trying to strangle the more successful one.2 In 2021, there was a single line about statistics: > 2021: Did you report error bars (e.g., with respect to the random seed after running experiments multiple times)? Honestly, not the worst question in the world. So much of machine learning and AI is based on randomized algorithms, and it’s good to check whether you have a stable result (i.e., training a neural net for classification) or a wildly variable result (i.e., using reinforcement learning to game a robotics simulator). But someone on the steering committee decided we needed a longer rule set and more statistics. The statistics creep began in 2023: > 2023: If you ran experiments, did you report error bars (e.g., with respect to the random seed after running experiments multiple times), or other information about the statistical significance of your experiments? And eventually, due to some unknown person’s lobbying, these were expanded further in 2024: > 2024: “The factors of variability that the error bars are capturing should be clearly stated (for example, train/test split, initialization, random drawing of some parameter, or overall run with given experimental conditions). The method for calculating the error bars should be explained (closed form formula, call to a library function, bootstrap, etc.). The assumptions made should be given (e.g., Normally distributed errors). It should be clear whether the error bar is the standard deviation or the standard error of the mean. It is OK to report 1-sigma error bars, but one should state it. The authors should preferably report a 2-sigma error bar than state that they have a 96% CI, if the hypothesis of Normality of errors is not verified. For asymmetric distributions, the authors should be careful not to show in tables or figures symmetric error bars that would yield results that are out of range (e.g. negative error rates). If error bars are reported in tables or plots, the authors should explain in the text how they were calculated and reference the corresponding figures or tables in the text.” What does this have to do with anything? If I run my code ten times, why should you care if I properly account for normal approximations? Who does this help? Anyway, I love that NeurIPS is proving my central thesis about statistics: Statistics is a bunch of arbitrary rules we use for approval. These arbitrary rules have now found their way into the machine learning publication machine. Whereas I understand why we require statistical tests when approving pharmaceuticals, no one has provided an explanation for why (or if) these statistical guidelines improve the quality of the thirty thousand NeurIPS submissions. Indeed, I can’t figure out _why_ people have become so obsessed with error bars in machine learning. I have been told that it’s because data sets are “small” now. For example, some of the “can LLM solve human tests” data sets have a few dozen questions. The AIME benchmark has 15. But what do frequentist error bars buy you here? This isn’t like Fisher’s friend who tastes tea. If a machine can solve a single one of these problems, it’s interesting! LLM answers are variable by design. Trying to gauge this variability with “Gaussian approximations to the standard errors of the mean” misses the forest for the trees. Indeed, if you only have 15 questions in a dataset, you don’t need statistics. Just look at the answers! We’re not grading the LLM on a curve here. The obsession with statistics is particularly ironic because the advances in machine learning from the past 15 years have been entirely based on optimaxxing vibes. While program committees and responsible ethics boards fixate on procedure, the big ideas have come from “this feels right,” whether they be bigger convnets, ADAM optimizers, attention mechanisms, or anything in RL. Do you think recent trends in transformer architectures like using RMSNorm instead of Layernorm or SwiGLU instead of ReLU are undergirded by deep statistical grounding?3 What gives away the whole checklist charade here is bullet 4. The rules say that you must disclose the normal approximations in your error bars, but _you don’t have to release code_. > "While NeurIPS does not require releasing code, we do require all submissions to provide some reasonable avenue for reproducibility, which may depend on the nature of the contribution.“ Why no code? It’s because a substantial fraction of NeurIPS papers come from private companies. The biggest models come from private companies. The conference exists to enrich Sam Altman. There’s no recruiting fair, no late-night parties, no signing bonuses based on Google Scholar profiles without the corporate commitment. So we can pat ourselves on the back and tell ourselves we’re being responsible researchers as we fill out our checklists and format our error bars. But let’s not kid ourselves about what we’re participating in. Subscribe now 1 I couldn’t find the preregistration plan. 2 There is still no statistically significant evidence to support the existence of heaven. 3 Like you, I don’t know what any of these things are. By Ben Recht

"Standard error of what now?
The NeurIPS checklist corroborates the bureaucratic theory of statistics."
By Ben Recht, https://www.argmin.net/p/standard-error-of-what-now

09.07.2025 19:31 — 👍 0    🔁 0    💬 0    📌 0

Mastodon’s latest update readies the app for Quote Posts, revamps design https://techcrunch.com/2025/07/08/mastodons-latest-update-readies-the-app-for-quote-posts-revamps-design/

08.07.2025 15:47 — 👍 1    🔁 30    💬 0    📌 1
Original post on fediscience.org

The French city of Lyon is dropping #Microsoft software in favor of #OpenSource alternatives. It doesn't want to depend on proprietary, closed-source software, and it doesn't want to depend on *American* software. It doesn't want "potential [US] governmental surveillance." […]

05.07.2025 14:12 — 👍 11    🔁 4    💬 0    📌 0

@lowrankjack.mathstodon.xyz.ap.brid.gy is following 6 prominent accounts