Especially because the data that gets fed into training is first anonymized, so they’d need to look for navier stokes related stuff in the anonymized training set and then get make some sort of ad hoc process (with Tristan’s permission and sign off from legal) to compare the training data against his chats / Codex sessions to check if anything matches up. And that assumes his chats / sessions are still there, and not deleted to compare against.
My best guess is that from the perspective of the OpenAI people, Buckmaster was letting his paranoia about OpenAI training tank his opportunity to receive the Clay Prize (it seems like Buckmaster and Alpoge's result isn't quite the full result required for the Clay Prize, whereas apparently OpenAI does have that full result worked out, using the same approach that Buckmaster and Alpoge had been exploring).
Whether the Codex sessions could have indeed made their way into Astra training data is something I can only speculate on though.
"using the same approach that Buckmaster and Alpoge had been exploring" is imo mealy wording: it seems fairly likely that OA heard Buckmaster and Alpoge were close to a breakthrough, and decided to use their unlimited compute to quickly prompt based on their assumptions about B&As work.
Citation of what? this was unpublished work! This computational blitz really just reads as "might makes right" on OpenAi's part... which isn't surprising, but they should probably be honest about what they've done here.
Well, Buckmaster says both his and Alpöge's use of Codex was non-institutional, and OpenAI claims the right to train their models on inputs and outputs of non-enterprise users in their service policies [0]. So I'm not sure they were even promised that.
It isn't relevant whether they were promised that. Indeed I think the assumption must be that they were not promised that, since otherwise the author asking if they were would not make much sense.
If OpenAI did use the conversations from Buckmaster and Alpoge, then not disclosing it, explicitly, is plagiarism. If they planned to use that plagiarism to pressure the authors to publish, that is even more unethical. What the terms of use say does not make it any more or less ethical.
That's absolutely right. Why the downvotes? If OpenAI are using but not acknowledging the work of others that's plagiarism. If they don't know for sure, but aren't performing due dilligence to make sure they aren't, that's also plagiarism.
It's not as simple.
All our chats are being used by both labs for their future product (unless signed by ZDR).
Where should the acknowledgement begin? Who should be acknowledged? The whole world? All the 2B users of AI?
If I know person A is working on problem B.
I am free to work on problem B too. Why should person A be limited to working on it.
I can imagine excuses for unknowing plagiarism in this case. What is described in the article seems much more serious: a research program that was only initiated following reports of the author's similar program. In this case no excuses of "I didn't know" can apply, it is not like this revealed some obscure work from the 1980s nobody could reasonably have foreseen. And as far as I can tell this program was only really initiated to apply pressure to the researchers, without their knowledge/consent. It looks very weird.
Your comment was greyed out when I saw it earlier, maybe you missed some downvotes?
About the plagiarism issue, I model it as OpenAI being an advisor and their AI a PhD student. If the advisor puts their name on a paper behind that of their PhD and it turns out the PhD copied the text of the paper from somewhere else the advisor is also responsible of plagiarism, not just the student. The least the advisor can do is withdraw their authorship from the paper.
But, yeah, point well made: it could be much worse than that. Like an advisor instructing a student to copy someone else's paper.
I think "greyed out" just means "0 points or less", so if you get 1 downvote without any upvotes it'll be greyed out. For instance your initial reply to me is now greyed out, and I have since observed a few upvotes and downvotes on my original comment (the downvotes apparently from people who aren't willing/able to justify why).
Personally I don't like thinking of LLMs like a PhD student, because most PhD students remember where they learned things from, while LLMs essentially cannot. I think of it a bit more like someone using a search tool carelessly. Although in this case it is apparently more like deliberate misuse than carelessness.
Only for ChatGPT, if the user hasn’t opted out. Would mathematicians be using ChatGPT for this kind of work? Genuinely asking, I know nothing about this!
If I am reading your question correctly you are asking about chat interface Vs Codex/Claude code? If so, in my experience Codex/Claude code use is widespread for mathematicians who are seriously using these tools.
No that would be an argument to return to the original definition of planets (highly visible celestial objects that migrate across the sky, i.e. the Sun, Moon, Mercury, Venus, Mars, Jupiter, and Saturn).
If you believe in the "standard 9" you're just insisting on returning to a scientific definition of planets but one that is frozen on our scientific understanding from a few decades ago...
The argument is to not make any changes to what people call planets but to instead have taken the opportunity in 2006 to create a separate classification system. Use something vaguely Latin sounding like planitus or whatever.
Yes, but again, what people call planets was stable for over a thousand years before changing rapidly in the past few centuries (first with the Sun and Moon being removed during the Copernican revolution, then Ceres, Pallas, Juno, and Vesta being added before being removed when they discovered a bunch of other asteroids, then Neptune being added, and finally in the last century Pluto being added before being removed after they discovered a bunch of other dwarf planets).
If you don't like changes to what people call planets, you should be unrolling all the other changes that have also been made, and go back to the original definition that stood from ~200 BCE-1700 CE.
> The fix was to create new exceptions so that str.lower() would behave as if it was using Unicode 3.2.0 for only particular function. So, we go through each Unicode codepoint and record when the behavior of str.lower() is different when comparing the Unicode version shipped with Python and Unicode 3.2.0
This sounds like a really hacky solution compared to implementing a separate frozen Unicode 3.2.0 lower.
# B.3 is mostly Python's .lower, except for a number
# of special cases, e.g. considering canonical forms.
+# To enforce Unicode 3.2.0 behavior of .lower instead of
+# whatever Unicode version is included with Python we
+# add unassigned or newly case-folding codepoints to
+# the exception map, too.
b3_exceptions = {}
for k,v in table_b2.items():
if list(map(ord, chr(k).lower())) != v:
b3_exceptions[k] = "".join(map(chr,v))
+for cp in range(0x110000):
+ ch = chr(cp)
+ # Assigned in current Unicode version
+ # and supports case folding, but not
+ # explicitly in B.2 or B.3 tables.
+ if (unicodedata_current.category(ch) != "Cn"
+ and ch.lower() != ch
+ and cp not in table_b2
+ and cp not in table_b3):
+ b3_exceptions[cp] = ch # Identity.
That fragment doesn't mean much in isolation. You've just said that they didn't modify str.lower (because "that would be bonkers") but you've posted a fragment which, for all we know, is part of the str.lower implementation.
To be clear (because the snippet is non-explanatory).
For encode("idna") what they did is use lower() except where it would produce a result different to 3.2.0 and then instead use the result from 3.2.0 instead.
Essentially they've frozen the IDNA encoding to be based on 3.2.0 by overriding any changes.
Yeah. I can understand the confusion, though. The title claims the issue was in lower(). Though the problem was actually in encode('idna')'s usage of lower().
The article would probably get far fewer clicks if it were named "when encode('idna') is a security vulnerability"
Yeah, that's what I figured, but my worry upon seeing this is "what happens if lower() changes again and people forget to update the list of exceptions?".
Unless they have unit testing on the entire Unicode code space to ensure what they're doing is always identical to 3.2.0.
I feel like there are a lot of use cases where I’d opt for SQLite and a lot of use cases where I’d opt for Postgres + PgBouncer. I’m curious what kinds of features push towards using Postgres alone over SQLite.
The setup cost is basically zero anyway. Add apt repo, apt-get install the correct version. Easy to run different versions at the same time too. Upgrading is annoying.
Concurrency, data types, scalability, centralization, or replication push for Postgres. The push against PgBouncer is that you don't need it, unless you do. If you have an app-level connection pool, you probably don't need PgBouncer.
This is one of those times where I wonder if I'm a genius for knowing not to generate evidence of a crime by talking about it in recorded media, or if we're just seeing the bottom 5% of wrongdoers.
You just press backspace and hit the accent mark key or for a printing press stack the accent mark on top of the letter. People ditched accents because they were rarely used in English writing (only really being used for some loanwords), not because simplifications were forced by typewriters or the printing press (which handle non-English languages just fine).
For printing presses we're talking about the influence of the first printing presses hundreds of years before industrialization which were imported from Germany and even when they started making their own in England they were more like clones and used imported designs and parts. The early machines had a heavy influence on the written language particularly at times when under 1 in 10 people could write, and with the advent of movable type the people who learned to write were heavily influenced by what they read... books printed on German-design machines. You really only need one generation in a situation like that to dramatically change the language. Losing þ, æ, and ð
reply