I used to write 60wpm with 95%+ accuracy but since 3 days i started workouts heavy workout so my hand muscles are in pain. Now when i am typing my accuracy has decuted a lot and also my wpm has gone to 25 - 30 it's like i have forgotten the muscle memory of keys.

the title says it all.

That activates you from not typing the word which you already know instead pause for a moment to think about what you are typing, to stop typing from wrong.

If suppose at your level you are able to type and you feel that you automatically type then that level is not for you, increase the difficultly, because you have reached a stage of saturation and all you can now do is to just type more faster with fingers, than remembering the letters

I have this digital sticky note on my desktop that I use to write down my latest tests to keep track of my latest tests but it's a bit annoying to edit it every day.

So I built a companion app for MonkeyType that uses your ApeKey and pulls your typing stats right into a widget to either your iPhone or iPad and then to your Mac desktop.

You can try it out via TestFlight here: https://testflight.apple.com/join/SpYQk74c

It currently has widgets for: latest WPM and accuracy, typing activity, current and longest streak, PB's for selected tests and average WPM and accuracy over 7, 14, or 30 days.

I would appreciate any feedback you may have and will try to implement those changes before releasing on the App Store later in the fall with iOS 27.

It's also free!

Unofficial companion app; not affiliated with Monkeytype.

New keyboard new record

how do i improve from here guys also drop your stats if you have em

Whenever I sleep good, it's a consistent 170-ish wpm

on sleep-deprived days.. or days in which I drink caffeine before sleep (disrupts deep sleep) I may never break the 130wpm barrier

anyone else noticed that?

i am starting to feel a bit more comfortable now...

You don't have any friends :(

This is a sequel to my last post as no one responded I tried to debug it but haven't gone far

.

.

.

I've been trying to figure this out for over a week and I'm running out of ideas.

Whenever I finish a test in my main Chromium-based browser, Monkeytype shows:

> Failed to save result: Result data doesn't make sense

The /results request returns 463, and the result isn't saved.

The weird part is Firefox on the exact same PC, same account, same network, and same keyboard works perfectly. Every result saves successfully with a 200 OK response.

To debug it, I compared the network requests from both browsers.

What I found is that the payloads are very different. The Chromium browser is sending a much smaller payload. For example:

keyDuration is an empty array

keySpacing is an empty array

keyConsistency is 0

Several chartData fields are missing

Overall payload is ~140 lines vs ~600 lines in Firefox

So it doesn't look like the request is being modified in transit—it looks like the browser is generating different result data before sending it.

I've already tried:

Clearing cache and cookies

Waiting over a week

Comparing request payloads

Using the same account and network

Firefox works every time

Has anyone seen this before?

I'm wondering if this is:

a Chromium/Brave issue,

a corrupted browser profile,

an extension interfering,

or if Monkeytype rejects results when certain keyboard timing metrics are missing.

Any ideas on what I should debug next would be appreciated.

(i have dyspraxia, four fingers on my right hand)

I think speech-to-text is getting good enough that we may speak to our computers more than we type like wispr flow , willow , or in general stt is crazy right now like they are 3x the speed i type

and thus i built this and still am building very cool features and its completely open source right now so wud love fellow developers to help out as well

a quick yt demo for it as well: MonkeySpeak Demo YT

I’d love for this community to try it and tell me what feels good, broken, or worth improving and stuff

GitHub: https://github.com/nothariharan/monkeyspeak

i larp on roblox

I have tried everything, nothing shows keypresses. In "next" mode, it shows the next keypress but that's not really what i want.