frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Unlimited OCR: One-Shot Long-Horizon Parsing

https://github.com/baidu/Unlimited-OCR
131•ingve•2h ago•36 comments

Steam Machine launches today

https://store.steampowered.com/news/group/45479024/view/685257114654870245
1732•theschwa•20h ago•1478 comments

The Coming Loop

https://lucumr.pocoo.org/2026/6/23/the-coming-loop/
91•ingve•2h ago•71 comments

Plotnine

https://plotnine.org/
121•tosh•4d ago•27 comments

Will It Mythos?

https://swelljoe.com/post/will-it-mythos/
211•mindingnever•9h ago•139 comments

GLM-5.2 – How to Run Locally

https://unsloth.ai/docs/models/glm-5.2
467•TechTechTech•16h ago•217 comments

Crypto in 2026: Oh, This Is the Bad Place

https://www.stephendiehl.com/posts/bad_place_2026/
164•ibobev•3h ago•177 comments

VibeThinker: 3B param model that beats Opus 4.5 on reasoning with novel SFT+GRPO

https://arxiv.org/abs/2606.16140
261•timhigins•11h ago•121 comments

The Traditional Vi

https://ex-vi.sourceforge.net/
35•exvi•4h ago•21 comments

In praise of memcached

https://jchri.st/blog/in-praise-of-memcached/
204•j03b•12h ago•76 comments

Show HN: Neural Particle Automata

https://selforg-npa.github.io/
39•esychology•5h ago•10 comments

Epidurals are a miracle technology

https://worksinprogress.co/issue/the-wonder-of-epidurals/
21•karakoram•2d ago•8 comments

Apple is going to raise device prices, but when?

https://daringfireball.net/linked/2026/06/22/apple-device-prices-when
40•tosh•2h ago•26 comments

Show HN: Shumai – open-source Frame.io alternative for creative work

https://github.com/shumaiOne/shumai
14•Yiling-J•3h ago•0 comments

OpenAI DayBreak – GPT-5.5-Cyber

https://openai.com/index/daybreak-securing-the-world/
148•AaronO•12h ago•104 comments

My Mathematical Regression

https://blog.dahl.dev/posts/my-mathematical-regression/
326•aleda145•4d ago•125 comments

Giant Banana Pulled Over: Driver Says Cops Have Stopped Him 100s of Times

https://cowboystatedaily.com/2026/06/18/giant-banana-pulled-over-in-montana-driver-says-cops-have...
96•speckx•2d ago•12 comments

8086 Segmented Memory was a good idea

https://owl.billpg.com/8086-segmented-memory-was-a-good-idea-almost/
39•billpg•1d ago•66 comments

The new HTTP QUERY method explained

https://kreya.app/blog/new-http-query-method-explained/
182•CommonGuy•7h ago•121 comments

Oracle shed about 20k roles globally in the last year

https://www.bbc.com/news/articles/c4gy0x0j5deo
68•Lyngbakr•1h ago•68 comments

Optocam Zero: a Pi Zero based digital camera made using off the shelf components

https://github.com/dorukkumkumoglu/optocamzero
195•iamnothere•18h ago•52 comments

An Introduction to YOLO26

https://blog.roboflow.com/yolo26/
87•teleforce•11h ago•31 comments

CL-BBS: the schemeBBS-like textboard rewritten in Common Lisp

https://github.com/ryukinix/cl-bbs
36•lerax•2d ago•1 comments

Moebius: 0.2B image inpainting model with 10B-level performance

https://hustvl.github.io/Moebius/
304•DSemba•23h ago•77 comments

Improvements to Std:Format in C++26

https://mariusbancila.ro/blog/2026/06/19/improvements-to-stdformat-in-c26/
32•jandeboevrie•2d ago•17 comments

Show HN: Oak – Git alternative designed for agents

https://oak.space/oak/oak
199•zdgeier•22h ago•170 comments

Matrix and Quaternion FAQ

https://j3d.org/matrix_faq/matrfaq_latest.html
18•signa11•9h ago•3 comments

Kyber (YC W23) Is Hiring a Head of Engineering

https://www.ycombinator.com/companies/kyber/jobs/FGmI8mx-head-of-engineering
1•asontha•16h ago

Who Does What? Team Topologies for the Agentic Platform

https://blog.owulveryck.info/2026/06/22/who-does-what-team-topologies-for-the-agentic-platform.html
30•owulveryck•9h ago•19 comments

Show HN: A pure ARM64 Assembly web server, now on Linux with CGI for no reason

https://github.com/imtomt/ymawky/tree/linux
40•imtomt•9h ago•11 comments
Open in hackernews

Unlimited OCR: One-Shot Long-Horizon Parsing

https://github.com/baidu/Unlimited-OCR
127•ingve•2h ago

Comments

Oras•1h ago
OCR has been solved long time ago with vision models. Solutions are consistent, reliable, and stable. What is the point of reinventing the wheel?

I would definitely understand post processing, like extracting data, answering question .. etc, but why re-doing the OCR engine itself?

vulture916•1h ago
I haven't done much long-run OCR, so unsure of the current state, but it would seem they overcome this (from their paper):

"A widely held view is that employing a large language model (LLM) as the decoder allows the model to leverage the prior distribution of language, leading to improved OCR performance. However, the downside is equally evident: as the output sequence lengthens, the accumulated KV cache drives up memory consumption and progressively slows down generation."

ta988•1h ago
Cost, throughput, latency...
Oras•1h ago
Traditional OCR is faster, cheaper, and much more reliable than LLMs
ta988•1h ago
I don't think that's a universal statement that aplies to every kind of documents and languages. Mistral OCR is able to do things no "traditional" OCR was ever able to.
j16sdiz•1h ago
If you consider non-English script, traditional OCR is not more reliable.

CJK have lots of character and high confusion rate.

Arabic scripts are complex and have lots of morphs.

Vietnamese have easily confused diacritics.

Thai have lots of non-standard fonts.

JodieBenitez•50m ago
I wish it were. Alas...
cannonpalms•1h ago
I guess, in theory, the prior distribution of language would allow for improved performance in some cases, especially where input quality is low.
ta988•1h ago
This is already used in OCR, tesseract uses that.
chpatrick•1h ago
It absolutely hasn't been solved, it's just got pretty decent in recent years.
malfist•14m ago
Pretty decent might be quiet the stretch. I'd term it almost acceptable, but only if you're using commercial solutions like amazon's textract, doing it with open source tools is at best, extremely painful and vaguely accurate.
JohnKemeny•1h ago
OCR has definitely not "been solved long time ago", what are you talking about?

In your opinion, what is SOTA here?

sscaryterry•1h ago
Detecting characters almost, layout no.
wongarsu•54m ago
Exactly my experience. If you try to OCR hand-filled forms with a fixed structure, traditional OCR models are great. Vision-llms can improve a bit on character recognition, but at the cost of harder to detect failure modes.

But if you are trying to ingest diverse documents with headings, multi-column layouts, headers and footers, ad space in the middle of your text, etc, vision-llms are a giant step forward. But you need the context of the previous page to make good decisions about the current page, which is where things quickly get janky (or slow, if you choose the naive approach)

Vision-llms also seem to deal much better with variance in scripts. Cursive, random Japanese in the middle of the text, weird math symbols, handwriting from three centuries ago, all "just works" without you even having to remember that this can happen

Aboutplants•55m ago
lol nope it hasn’t been solved. I deal with this constantly and we still have a longggg ways to go
joss82•45m ago
I've been working on Parseur for the last 10 years, and OCR has not been solved yet, let me tell you.

OCR still sucks in 2026. Hopefully this might improve the situation but I haven't tested it yet.

ljouhet•42m ago
Real question: what tool do you use? (for long/complex documents with tables, code, maths)

- marker (with --force-ocr) gives me the best results

- Mistral OCR (seems really great, but I never managed to get it work)

- Mathpix (tried a long time ago)

- docling (gives me garbage, I must use it wrong)

- Unlimited OCR (will try it)

- ???

Oras•24m ago
- Azure Document Intelligence (has an option to return markdown too including headers and footers).

- AWS Textract

mschuster91•35m ago
> I would definitely understand post processing, like extracting data, answering question .. etc, but why re-doing the OCR engine itself?

Well... the idea seems to be (as far as I understand it, at least) that optical errors and artifacts can now be compensated as the OCR engine is now context-aware.

Say, for example, some random long ass name chemical. It's not going to be in a word correction database, but a context-aware engine (ideally, one that has been supplemented with chemistry data) can now correct "bad" reads of the chemical's name.

Of course, there remains the issue of how to prevent the infamous Xerox bug [1]...

[1] https://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres...

robotswantdata•1h ago
Very interesting.

The way I understand this works is that the researchers found a clever architectural hack to stop AI from hoarding memory when reading long documents.

Normally, when an AI transcribes a 100 page PDF, it tries to remember every single word it has already ingested. This short-term memory (the KV cache) grows linearly O(N) until the model runs out of VRAM and crashes (or caps it) To avoid this, developers are forced to build janky code that chops PDFs into individual pages, processes them one by one, and glues the text back together.

Unlimited OCR uses Reference Sliding Window Attention (R-SWA) to split the AI's focus into two paths:

Global Reference: The AI keeps full, uncompromised sight of the original document image so it never loses context.

Local Generation: The AI restricts its memory of its own typed text to a tight, moving window (like the last 128 words) and safely forgets the rest.

Will be very interesting for local AI and can’t wait to see what the community builds and extends with it!

d675•25m ago
See, leetcode is useful. As I do this leetcode grind, I’ve been why techniques exist / how they’re used irl. Lots of interesting stuff there
ai_fry_ur_brain•4m ago
Who said it wasnt useful, dont listen to those people.
KitN•1h ago
"We would like to thank Deepseek-OCR, Deepseek-OCR-2, PaddleOCR for their valuable models and ideas."

Class Act.

gcr•51m ago
I don’t understand the shade being thrown ?
nickspacek•38m ago
It's the opposite of shade, unless GP is being sarcastic. "Class act" is normally a compliment, and in the context here it sounds to me like they're congratulating Baidu/the researchers in being transparent about where their ideas came from.
manipalite•1h ago
Whatever happened to Reducto, was very promising 12-15 months ago
ramon156•52m ago
I love that the entire goal is to push Deepseek OCR further. The west can learn greatly from these companies
pmarreck•43m ago
my attempts at using AI to do OCR have always resulted in invented artifacts, which is not production feasible. does this suffer from that as well?

A simple example is words that are supposed to be in other languages being automatically translated to English, which ruins the effect

overflowy•35m ago
What are the requirements for running this locally?
alansaber•32m ago
We've invented chunking? We are so back.
ahknight•13m ago
Streaming.
peatmoss•26m ago
I recently bought a tablet for sheet music, mostly to replace a stack of jazz "Real Books" at jam sessions. And the phone camera scans I made are okay, but fixed in size and have a lot of artifacts. And it would be great to transpose on the fly for e.g. Bb or Eb instruments, but being a scan this is obviously not possible.

I got digging into the state of optical music recognition and came away concluding that music is basically a greenfield for AI wherever you look. Optical music recognition is pretty terrible. AI understanding of music theory is terrible (actually looking at music that is; LLMs do okay at text descriptions of theory concepts where you can imagine some online texts making it in).

I think the issue is that we still don't have great digital formats that encode the dots on paper that musicians read. Music notation is pretty rich. Midi doesn't capture all of what's needed for symbolic understanding, because it was mostly made for capturing aspects relevant for playback or performance. MusicXML seems to be the closest for a digital format that encodes the information a musician would want, but there aren't great corpora of training data that would connect a MusicXML representation to sheet music images or to audio. I think that's because MusicXML falls short of encoding enough information to engrave music. Tools like MuseScore need to track a bunch of layout information that isn't encodable in MusicXML. Lilypond format is less verbose that MusicXML and contains a bit more information that is useful to the score creators, but most people don't create sheet music in lilypond. (As an aside, Lilypond bums me out with the state of jazz fonts. I hate looking at "legit" scores in jazz context)

I realize this is mildly off topic, but every time I see people making incremental gains on OCR, which to my mind is pretty good, I am reminded of how abysmal OMR is.

singpolyma3•18m ago
What about sheet music typesetting formats like https://abcnotation.com/ ?
peatmoss•7m ago
I forgot to mention ABC. I have seen a few LLMs look at that. There was a model / paper published a couple years back called ChatMusician that built around it.

With the caveat that I'm not terribly fluent in ABC, it seems to me that simple things are simple, but hard things seem to be nearly pathological. And (again, maybe a lapse in my understanding) it seems like there may be a fair number of concepts that are impossible to convey in ABC?

Lastly, if I understand correctly, ABC got its start and is mostly popular as a simplified format for church songbooks. I'd imagine that would, uh, influence the training corpora towards sounding a bit... church songbooky.

WhitneyLand•16m ago
“there aren't great corpora of training data that would connect a MusicXML representation to sheet music images or to audio”

It may not be necessary…a lot of the training pairs/data for this could probably be procedurally created via code.

Would be pretty fun to work on and see it come to life.

mcbetz•14m ago
I observe that space regularly and the only really good solution is soundslice. You scan and review some edge cases and get really good results. Paid service by a small company, very worthy to be supported!