Like, there are exact cognates of this problem in human language. If I tokenise “how many Ls in ‘Lyla’” into katakana, it’s basically impossible to answer
Congress Member Profile|U.S. Representative|Republican|Oklahoma District 1
Kevin Hern
Source: Wikipedia • View full (CC BY-SA)
SoupScoreanalysis-first civic rating · view full breakdown
Loading…
Voting Record — 567
Yes76%
No21%
Present0%
Not Voting3%
Party align97%
Cross-party1%
SoupScore
District Map
Congressional District 1
U.S. Census Bureau boundary data.
Social & Web
External Resources
Kevin Hern
U.S. RepresentativeRepublicanOklahoma District 1
SoupScore
Kevin's ATmosphere Activity
20 recent posts · 17 sponsored · 30 cosponsored
Recent ATmosphere posts, sponsorships, and cosponsorships.
Thanks David
But it doesn’t! It’s very very specifically a problem with _tokenisers_, in a way that is true of almost no other general problem with LLMs/transformers
I’m nitpicking: the general point (reasoning models are going to be the main product here and that’s bad for the economics) is fine. But I think there’s a desire to generalise a _very_ specific problem in ways that tortures it
Definitely important! I’m not sure that the strawberry problem suggests it makes that confusion (honestly, I’m pretty sure it does not generalise in that direction at all)
I don’t understand, sorry. When is counting the Rs in strawberry while vibe coding?
Yes? So you use code to solve them not an LLM
Ehhh idk, if you give it a specific type of question that is structured specifically to be hard for a tokeniser it can’t answer it efficiently but why are you turning to a tokeniser to solve that question
I don’t think this party trick has any real impact on the estimates for cost per usable token
I do this on BA every time and it works 75-80% of the time
Used to be you had to travel to Berlin for easy access to cool industrial loads
You have two children
It’s the equivalent flex to a live action kids show just randomly having a massive crowd scene periodically
One of the mad things about Bluey is how often the show will do a single shot from an angle that it never uses again, an incredibly lavish directorial quirk for an animated show
Imagine having one daily. No thank u
Was thinking bout pando. What were that all about eh. Mad. Wouldn’t do it again personally
Judging by my inbox, “actually emailing patrons” is fine dining-coded? I get emails from Luca, the Clove Club, and JKS but not, like, any of my beloved neighbourhood joints where I would actually want to know about popups and guest chefs
If I follow a restaurant on instagram they definitely have my email address from when I booked with them. They could use it! I wouldn’t mind!
SoupScore Breakdown
Loading analysis metrics…
Voting History567 total votesExpandCollapse
Voting History
567 total votes
Recent roll calls with party-majority context so it is easier to scan how this member tends to vote.
| Date | Bill | Question | Position | Party Maj | Align? | Result |
|---|---|---|---|---|---|---|
| 2025-07-23 | H.R. 3357 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-22 | H.R. 1917 (119th) | Fast-track passage | NO | YES | ✕ | Passed |
| 2025-07-22 | H.R. 3937 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-21 | H.R. 3351 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-21 | H.R. 3095 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-18 | H.R. 4016 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-07-18 | H.R. 4016 (119th) | Send back to committee | NO | NO | ✓ | Failed |
| 2025-07-18 | H.R. 4016 (119th) | Approve amendment | YES | NO | ✕ | Failed |
| 2025-07-18 | H.R. 4016 (119th) | Approve amendment | YES | NO | ✕ | Failed |
| 2025-07-18 | H.R. 4016 (119th) | Approve amendment | NO | NO | ✓ | Failed |
| 2025-07-18 | H.R. 4016 (119th) | Approve amendment | NO | NO | ✓ | Failed |
| 2025-07-18 | H.R. 4016 (119th) | Approve amendment | YES | NO | ✕ | Failed |
| 2025-07-18 | H.R. 4016 (119th) | Approve amendment | NO | NO | ✓ | Failed |
| 2025-07-18 | H.R. 4016 (119th) | Approve amendment | YES | NO | ✕ | Failed |
| 2025-07-18 | H. Res. 590 (119th) | Approve resolution | YES | YES | ✓ | Passed |
| 2025-07-18 | H. Res. 590 (119th) | End debate now | YES | YES | ✓ | Passed |
| 2025-07-17 | H.R. 1919 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-07-17 | S. 1582 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-07-17 | H.R. 3633 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-07-17 | H. Res. 580 (119th) | Approve resolution | YES | YES | ✓ | Passed |
| 2025-07-16 | H. Res. 580 (119th) | Motion to Reconsider | YES | YES | ✓ | Passed |
| 2025-07-15 | H.R. 1717 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-15 | H. Res. 580 (119th) | Approve resolution | YES | YES | ✓ | Failed |
| 2025-07-15 | H. Res. 580 (119th) | End debate now | YES | YES | ✓ | Passed |
| 2025-07-14 | S. 1596 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-14 | H.R. 1770 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-14 | H.R. 1709 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-07-03 | H.R. 1 (119th) | Accept Senate changes | YES | YES | ✓ | Passed |
| 2025-07-03 | H. Res. 566 (119th) | Approve resolution | YES | YES | ✓ | Passed |
| 2025-07-03 | H. Res. 566 (119th) | Approve amendment | YES | YES | ✓ | Agreed to |
| 2025-07-02 | H. Res. 566 (119th) | End debate now | YES | YES | ✓ | Passed |
| 2025-07-02 | H. Res. 566 (119th) | Consideration of the Resolution | NOT_VOTING | YES | — | Passed |
| 2025-06-27 | H. Res. 516 (119th) | Approve resolution | YES | YES | ✓ | Passed |
| 2025-06-26 | H.R. 275 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-06-26 | H.R. 875 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-06-25 | H.R. 3944 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-06-25 | H.R. 3944 (119th) | Send back to committee | NO | NO | ✓ | Failed |
| 2025-06-25 | H.R. 3944 (119th) | Approve amendment | YES | YES | ✓ | Agreed to |
| 2025-06-25 | H. Res. 519 (119th) | Motion to Suspend the Rules and Agree, as Amended | YES | YES | ✓ | Passed |
| 2025-06-24 | — | Motion to Adjourn | NO | NO | ✓ | Failed |
| 2025-06-24 | H. Res. 530 (119th) | Approve resolution | YES | YES | ✓ | Passed |
| 2025-06-24 | H. Res. 530 (119th) | End debate now | YES | YES | ✓ | Passed |
| 2025-06-24 | H. Res. 537 (119th) | Kill the motion | YES | YES | ✓ | Passed |
| 2025-06-23 | H.R. 3422 (119th) | Fast-track passage | NO | YES | ✕ | Passed |
| 2025-06-23 | H.R. 3394 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-06-23 | H.R. 1998 (119th) | Fast-track passage | YES | YES | ✓ | Passed |
| 2025-06-12 | H.R. 2056 (119th) | Final passage | YES | YES | ✓ | Passed |
| 2025-06-12 | H.R. 2056 (119th) | Send back to committee | NO | NO | ✓ | Failed |
| 2025-06-12 | — | Motion to Adjourn | NO | NO | ✓ | Failed |
| 2025-06-12 | H.R. 4 (119th) | Final passage | YES | YES | ✓ | Passed |
Alignment stats consider only votes where a clear yes/no majority existed for the legislator's party. Cross-party marks divergence where the vote matched the opposite party majority. ↔ indicates cross-party divergence.