Not sure where am I supposed to submit a bug report, so I’ll just write it here.
Bug #1 - Windows client 3.1
You have two different applications, either;
a) they share the same name on taskmgr.exe
(e.g. both PyCharm Community Edition and PyCharm Professional Edition are appeared as PyCharm on task manager), or
b) they don’t share the same name but share lots of code base
(e.g. Chrome 89 and Chromium 92. Chrome 89 is Google Chrome on Processes tab and chrome.exe on Details tab. Chromium 92 is, well, I guess it depends how you build and how you name the executables, but I think the default is Chrome. I tested as chromium.exe)
and launch both of them at the same time (sometimes, launch them back and forth without any overlapping also seem to trigger the same buggy result)
Buggy result, if those two conditions are satisfied:
Keystrokes/clicks counter (Input tab > Applications) for both applications got bricked. No more update for both. But other than the app-specific counters, it works fine. The client software still records the keystrokes and clicks for other apps, as well as overall keystrokes/clicks.
Once you bricked the app counter for those specific apps, a simple restart/reboot doesn’t seem to fix it. Even reinstall doesn’t work (haven’t tried uninstall and install it). The only way of resolving this issue (that I found so far) is resetting the stats in Input > Applications tab, and not using such similarly named (or similar) applications in the future, because it’ll brick those applications again.
Bug #2 - Windows client 3.1
not sure this is a bug, or just a known limitation, or intentional implementation, but;
a) in case of many system-related Windows apps; they often don’t register any input (not just application-specific count but also overall count), other than the first click when you select the apps.
a list of apps which behave this way - regedit, taskmgr, gpedit.msc, msinfo32
a list of apps which don’t behave this way (counted normally) - dxdiag
EDIT - #2. a) could be solved by running WhatPulse as Administrator. However, still no luck on #2. b).
b) in case of default UWP Windows apps (as well as non-default third party UWP apps); they often don’t have their own name on application tabs. all keystrokes/clicks on these apps are merged into one entry with a blank name and counted toward to it.
a list of apps which behave this way - ms-paint:, calc, ms-photos:, ms-settings:, ms-clock:, ms-people:, outlookmail: bingmaps: Adobe Photoshop Elements 2021
a list of apps (non-UWPs) which don’t behave this way (counted normally) - mspaint (the non-UWP old one), notepad, wordpad
Bug #3 - Linux client 3.1 and Website (statistics)
Keystroke/click statistics by applications are recorded correctly on Linux client, but it doesn’t show up on website.
a) Unlike macOS/Windows clients, any app-specific data from Linux client doesn’t show up on public profile page (https://whatpulse.org/USERNAME#apps)
b) It also doesn’t show up on dashboard (https://whatpulse.org/dashboard/my/applications). Linux clients aren’t counted toward the number of computers on each applications, and keystrokes/clicks data from Linux client is also missing.
Bug #4 - Website (forum)
I noticed this when I’m trying to sign up for a new account to make this thread. If you click the new thread button without signing in, it’ll take you to;
which does nothing for unregistered user. I think it should propmpt login or sign up screen for guests.
Bug #5 - Windows client 3.1
I also noticed this when I’m trying to sign up for a new account to make this thread (because I have to make a pulse to make a thread). If you log out the original account and log in with a fresh account on the existing client, every stats on overview tab does not reset itself, and just show you the accumulated keystrokes/clicks/traffic/etc. And if you log out the fresh account and log in with the original account, the accumulation happens once again, thus effectively doubling the every stats on overview tab. I don’t think it does anything to the stats on server side, so not much of a problem, but you still need to reset the stat, if you don’t like the inflated stats on overview tab.
Bug #6 - Windows client 3.1
Keystrokes/clicks are not counted when it’s remotely connected. I think you implemented this intentionally, so I wouldn’t say that is a bug. However, I found multiple walkarounds for this issue, hence there are some bugs. Since it seems to be an intentionally implemented feature, I wouldn’t publically disclose about the walkarounds, but PM me if you’re interested.