HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
wcgbg
terpstrakeyboard
HTML2025–2025
wcgbg / terpstrakeyboard

terpstrakeyboard

http://terpstrakeyboard.com/web-app/keys.htm

2Distinct people
2Mentions
1Explicit recommenders
69GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

http://terpstrakeyboard.com/web-app/keys.htm

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

My favorite variant: https://novayashkola.org/janko/ , https://en.wikipedia.org/wiki/Jank%C3%B3_keyboard , https://en.wikipedia.org/wiki/Isomorphic_keyboard Since a year ago, I…

nayuki used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2025-06-18 12:04:21 UTC to 2025-06-18 19:00:41 UTC.

012025-06-18 12:00:00 UTC to 2025-06-18 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 18, 12:002025-06-18 13:00:00 UTC to 2025-06-18 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-18 14:00:00 UTC to 2025-06-18 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-18 15:00:00 UTC to 2025-06-18 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 18, 15:002025-06-18 16:00:00 UTC to 2025-06-18 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-18 17:00:00 UTC to 2025-06-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-18 18:00:00 UTC to 2025-06-18 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-18 19:00:00 UTC to 2025-06-18 20:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 18, 19:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 18, 12:002025-06-18 12:00:00 UTC2025-06-18 13:00:00 UTC101
Jun 18, 13:002025-06-18 13:00:00 UTC2025-06-18 14:00:00 UTC000
Jun 18, 14:002025-06-18 14:00:00 UTC2025-06-18 15:00:00 UTC000
Jun 18, 15:002025-06-18 15:00:00 UTC2025-06-18 16:00:00 UTC000
Jun 18, 16:002025-06-18 16:00:00 UTC2025-06-18 17:00:00 UTC000
Jun 18, 17:002025-06-18 17:00:00 UTC2025-06-18 18:00:00 UTC000
Jun 18, 18:002025-06-18 18:00:00 UTC2025-06-18 19:00:00 UTC000
Jun 18, 19:002025-06-18 19:00:00 UTC2025-06-18 20:00:00 UTC101

What Hacker News says

2 sources
I'm impressed how responsive the keys are! Will definitely be checking out on desktop if I can see how the audio rendering code works (unless someone here already knows). I presume the audio synthesis API and ontouchstart but maybe there's something clever in addition like prerendering the audio samples rather than synthesising them on press Maybe it also helps that I've got a headphone jack plugged in instead of the Bluetooth I'm used to from listening to things during the day, but even so, my touchscreen just doesn't feel this responsive normally, including in games. It's on my list of things to check the delay of, but since my phone's 960 fps camera is the equipment I use to check that, it is a bit tricky Edit: ontouchstart calls noteOn method https://github.com/wcgbg/terpstrakeyboard/blob/03d526a0ed5c7... This eventually calls into au
Read the rest
dio api start with 0 delay https://github.com/wcgbg/terpstrakeyboard/blob/03d526a0ed5c7... The data to play was retrieved from the server (based on the instrument you selected) and parsed ahead of time https://github.com/wcgbg/terpstrakeyboard/blob/03d526a0ed5c7... It loads samples at four frequencies and plays the nearest one at the appropriate rate (proportional to the target frequency) https://github.com/wcgbg/terpstrakeyboard/blob/03d526a0ed5c7... The settings.audioContext variable is simply an instance of the web audio API as expected (with a fallback to support Safari/webkit) https://github.com/wcgbg/terpstrakeyboard/blob/03d526a0ed5c7... This gainNode it's connecting is just about playback volume it seems https://developer.mozilla.org/en-US/docs/Web/API/BaseAudioCo... and "audioContext.destination", MDN says, you can think of as a speaker device So nothing too special here: of course preloading server data but then simply creating a new sound source during ontouchstart is enough. I guess delay in other software comes from the extra cruft they have such as big libraries (and Bluetooth, in the cases where I use that), not from any actual delay in touchscreen or audio rendering
In Terpstra Keyboard

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.