You're reading the public-facing archive of the Category Theory Zulip server.
To join the server you need an invite. Anybody can get an invite by contacting Matteo Capucci at name dot surname at gmail dot com.
For all things related to this archive refer to the same person.
Hi guys. Regarding: #community: general > AI-generated papers
I know right now there is some worry about preprints/etc. I've actually been working coding up a new eprint server as part of a startup project. After speaking with several people in the research community it seems there is increasing demand for alternatives with better features. I already have a pretty good working prototype (React/Django/Postgres/S3 modern stack) that has some pretty nice goodies (AI-assisted [not solely!] screening to catch 99% of BS papers, richer diffs, native github/code data integration, native API that directly supports overlay journals with GraphQL).
While I don't have a private demo to showcase just yet, I'm wondering what people would want in a modern preprint server? What features do people consider most important? Please fire away.
Please support typst. Using latex in 2025 is criminal.
Please support LuaLaTeX and other 'nonstandard' variants on TeX. ArXiv effectively bans the use of these things, since it will detect that the pdf is produced by LaTeX and demand you upload the source, but it can't compile the source, so there's effectively no way to upload it at all. I think this is actually quite damaging to the open source ecosystem.
Really though, the most important feature in a preprint server is a plausible guarantee that the papers will continue to be accessible in the long term. Anything else is extra.
It's easy to offer a preprint server in the heat of the moment, but arXiv has to deal with nearly 35 years of legacy (La)TeX code, a bunch of it written before pdf was the de facto standard of document exchange, and more than 2.6 million papers...
Nathaniel Virgo said:
Please support LuaLaTeX and other 'nonstandard' variants on TeX. (Or at least allow uploading of pdf files generated using them.) ArXiv effectively bans the use of these things, since it will detect that the pdf is produced by LaTeX and demand you upload the source, but it can't compile the source, so there's effectively no way to upload it at all. I think this is actually quite damaging to the open source ecosystem.
Hi. I'm using Tectonic though I have not tested LuaLatex features. A "last ditch" upload option was implemented that allows your own pdfs + the source if for some reason it you use cannot compile using the website pipeline.
BTW, what's the rationale for compiling preprints on the server? Why can't anyone use what they like and just upload a PDF+sources?
My desiderata are:
(1) Make it as simple and stupid as it can be. we are not customers who need to be allured by shiny things, and instead most people I know in academic prefer reliable, old-fashioned websites to fancy js-only modern slop. it'd be great if the website core functionality only relies on HTML, CSS and web forms to function!
(2) Segueing from above, use as much standard protocols as you can. This means an RSS feed, ORCID/OAuth/Shibboleth authentication, and whatnot.
(3) Support open review. People should be able to post public reviews under preprints, this includes authors posting errata and new versions.
The public review question is going to be quite controversial. At the very best it’s going to make for a substantial moderation burden.
As for on-server compilation, I’m sure ArXiv was originally quite interested in avoiding the storage and bandwidth burdens of holding a ton of PDFs. That’s less important now though perhaps not totally insignificant, but there also seems to be a single source of truth/reproducibility/iterability problem with posting sources the server can’t confirm are actually compilable. I’m not sure how significant this seems.
I think public review should be separated from the business of archiving:
1) There are lots of things that can go wrong with public review, and lots of things that can make people (especially those whose papers are reviewed, but also the reviewers) very upset. Doing it well will require a team committed to moderating it this in an ongoing way.
2) There's no need for public review to be bundled with archiving. Anyone who wants to set up public review for archived papers can do it now by setting up a website linked to the arXiv or any other archive of papers.
Thus, I think if someone thinks public review is a good idea, they should start it now, not as part of any archiving process. I believe they'll soon encounter issue 1).
I'd actually argue a review server linked to the arXiv would be a bigger public service than another eprint server. But probably even harder to make work. On the other hand, even if such a review server failed, at least the articles wouldn't go down along with the reviews!
I mean, there are already a bunch of (what amount to) preprint servers that no one in mathematics uses. And there's HAL, more used by Francophone mathematicians, which has a bunch of features that are really cool that arXiv doesn't have. So making yet another one has to differentiate it from the market.
Moreover, in the 90s there were a bunch of subject-specific mathematics preprint servers that eventually just folded because everyone just used the arXiv, and they were all basically one-man [sic] shows running on 90s tech. So competing against the arXiv is the big challenge.
At the tail end of this trend, people were collecting links here, many of them presumably broken now https://mathoverflow.net/questions/186708/big-list-of-repositories-of-mathematical-preprints-and-postprints and I would imagine this missed a bunch that were long defunct by 2015
Even the really nice Front for the Mathematics arXiv shuttered in the last decade or so, and that was really just an improved interface that accessed arXiv stuff.
I decided early on I'm not supporting public comments. It's just another moderation headache and it would only deter people from posting if they are afraid they'd be publicly nitpicked.