mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-26 07:45:57 +03:00
[GH-ISSUE #119] multible (repeated) key in keylog and very long line #56
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#56
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DragonzMaster on GitHub (May 10, 2015).
Original GitHub issue: https://github.com/quasar/Quasar/issues/119
when you play as an example and you open the keylog
you see something like that
[Call of Duty® Ghosts]
wwwssssssssssssssssssssssss3wwwwwwwwwwwwwwwssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssrwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww
you can see that the letter is repeted many times which is someway annoying
so it is possible to make changes to prevent that
and another thing the line is too too long :/
and it is very annoying to scroll horizontally for long time
so can we limit the line char number (70 characters for example)
so it can be more comfortable
*note : i copied a very small sample of the keylog just to clarify the problem and it was really too long
@yankejustin commented on GitHub (May 11, 2015):
What do you suggest we do about repetitive keystrokes?
@ghost commented on GitHub (May 11, 2015):
This reference might contain a solution: http://stackoverflow.com/a/9356006
@DragonzMaster commented on GitHub (May 11, 2015):
like if the key is pressed it won't be logged more than once unless if i put up my finger and press it again
is it possible ? @yankejustin
@ghost commented on GitHub (May 11, 2015):
To be fair I don't see this as a problem, but I think I know a way to fix it
@yankejustin commented on GitHub (May 11, 2015):
Yes, it is absolutely possible. However, without this behavior someone that does this intentionally when typing something can cause loss of accuracy.
@DragonzMaster commented on GitHub (May 11, 2015):
may be (it is your opinion) but it is logs unnecessary keys which make the log looks bad and what can i benefit from a log contains hundreds of repeated "s" and "w" and similar keys used
and it increase Line's Length and log's size @d3agle
@yankejustin commented on GitHub (May 11, 2015):
Well, I am not speaking of my opinion, I am speaking factually. Purposely ignoring subsequent keystrokes due to their proximity is an intentional loss of data (or the accuracy of data).
@DragonzMaster commented on GitHub (May 11, 2015):
so can we make it optional ? @yankejustin
i was talking to @d3agle in my previous comment
Edit : I respect both of your views so do what you see it is suitable
@yankejustin commented on GitHub (May 12, 2015):
Certainly an optional thing because there are many cases to where it is necessary to show them.
One way I can think of is to generate a collapsible table (basic html).
@DragonzMaster commented on GitHub (May 12, 2015):
ok
now what about Line Char number limitation (the second part of issue) to prevent the line from being too long ?
@yankejustin commented on GitHub (May 12, 2015):
Personally I think that the keylogger should be making a folder for each day anyways... Then place a limited amount of data in each file to divide them up.
@bitterypaul commented on GitHub (May 12, 2015):
if same key is repeated more than 5 times, then we can make keylogger to log it as 5[w]
@m6m4m2 commented on GitHub (May 12, 2015):
Nice work you guys I have an idea here's a picture to explain it
http://mizr.org/p/f/repository/z/01.gif
if you think its useful I'll release the source if not .. will then I'll think of another solution
@bitterypaul commented on GitHub (May 12, 2015):
correct me if i am wrong. since quicklz is used, the log will be compressed. so the log will shrink in its size during transmission.
@yankejustin commented on GitHub (May 12, 2015):
@xmizrx That would be a useful addition to the keylogger. :)
I was actually thinking the same thing when I looked back at the logs and realized how inaccurate I am with a keyboard! x)
@m6m4m2 commented on GitHub (May 12, 2015):
@yankejustin Thanks here's the source although it still has some bugs but simple to fix
you need
3* textboxs
2* buttons
1* timer
The source
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Text;
using System.Windows.Forms;
namespace xServer.Forms
{
public partial class FrmRePlay : Form
{
public FrmRePlay()
{
InitializeComponent();
}
private int i;
private string strMessage;
}