Amaroq_Starwind
-
Posts
700 -
Joined
-
Last visited
Content Type
Events
Profiles
Forums
Posts posted by Amaroq_Starwind
-
-
QWERTY wasn't actually designed to slow people down, it was just designed to be mechanically reliable but still relatively ergonomic. Originally there were typewriters that were not as susceptible to jamming as older models, but the way the keys were arranged was still really bad. We're talking alphabetical order. (Speaking of which, does anybody happen to have a spare DVORAK keyboard I can borrow? I've always wanted to try one.)
And the numerical keypad thing just hurts my brain too. Ugh...
In barely-related news... I want to try that specific dyslexia-friendly font I referred to (the underlined text is a hyperlink), but it's like 60 dollars for just one user! X.x
Yeah, I have a job now and all that (my first one!), but my first ever paycheck has been delayed for some unknown reason. I was supposed to receive my direct deposit yesterday. -
So... what exactly are some of these vulnerabilities and inefficiencies, anyway?
-
It's worth noting that when I brought this topic up in the ReactOS community (they are creating a Windows replacement from scratch!), I actually got scoffed at. In fact, some people were even a little toxic about it. Eugh
There are a few more thoughts I've always had regarding GUI stuff...- A decent GUI should be color-blindness friendly, but still look nice if you're not colorblind. And no, I don't mean removal of color entirely.
- There are actually typefaces out there that are specifically designed to be Dyslexia-friendly. That's pretty nice, actually!
- Animated GUIs are awesome. They just shouldn't be too animated. Everything should have context, and not be super distracting.
- The basic Win32 framework doesn't have native support for touchscreens. When you use a touchscreen, it is impossible to interact with multiple things simultaneously via that method, and instead the touchscreen just emulates a mouse pointer. Again, eugh. Somebody needs to fix that.
- Wouldn't it be great if could seamlessly combine Command-Line and GUI interfaces, such that the distinction between the two became blurred?
- Even if you are a Command-Line Purist, keyboards are not the perfect typing interface. They were originally derived from typewriters after all. Better typing interfaces exist!
And now specifically for input devices...
- I really wish computers had buttons with full analogue control, meaning that the input the computer receives should vary with how much pressure I apply to the button in question.
- Extending on that, we could possibly also have physical buttons that click, but also have touch-sensitivity in them as a separate layer of input? The computer being able to tell whether you're actually pressing a button versus merely touching it could open up so many options.
- If mice with high-fidelity force feedback exist, I want one. It would be perfect if it were integrated with a UI.
- If we had ways to seamlessly utilize parts of our bodies that are normally unused when interacting with your computers, our productivity could skyrocket. We're talking foot pedals, head tracking, eye tracking, etc, perhaps lifting our hands off our keyboards while typing to make quick gestures that are immediately recognized by our computers, etc.
- Wouldn't it be great if we could seamlessly combine Mice and Keyboards outright? I mean, there have been attempts, but there are currently issues with them.
-
Studies show that primarily flat-colored user interfaces actually make you slower and less productive, though I don't remember the specific studies off the top of my head, so I can't cite them right away.
But I think I have to agree. Flat colors actually distract me quite a bit, and make it harder for me to focus what I'm supposed to be working on.
So while I do appreciate the option of using an alternate theme, the available ones could all use some work. I actually prefer the aesthetic of lighter themes over darker themes, but they are often so much harder on my eyes. The new default theme on this forum, for example, uses a shade of blue that is way too hard on my eyes. And blue is my favorite color, too!
The IPS default theme is a lot closer to what I remember from my previous experiences on the Malwarebytes Forums, but it's still not quite right. I think I can get used to it again though. -
A video-rant by Ross Scott, about graphical user interfaces.
Whether you are;
- casual computer user
- a professional who relies on their system for their daily life and is constantly having to tweak it
- or a software designer who is actually building a program for people everywhere to use...
You may learn something very useful here!
Also, props to Ross for using Malwarebytes~
🦊
P.S.: I apologize in advance if I already posted this video on this forum. -
My idea for this is simple... An activity center, completely self-contained, so that new computer users can intuitively learn about malware and the field of cybersecurity in an interactive fashion.
This would be especially helpful for sending to relatives who aren't technologically inclined, or to young users who are still getting familiar with computers in general.
Obviously, this would need to be a free program, completely separate from any actual security products. But by teaching users about all of the different threats out there through a single convenient thingamajigger, as well as how to remedy or avoid them, that would probably be a big step towards a safer internet 🙂
What are your thoughts on this idea?
-
It honestly doesn't seem like it should actually take much extra work to compile it for that platform. As far as I understand... It's the same source code, just a different compiler target.
Unless Malwarebytes has important dependencies that aren't currently available for ARM64. That would actually explain a lot, if that were the case.
-
I recently watched a video about Forkbombs, and it made me think; would there be any viable way to create a program that could automatically detect new and unknown forkbombs, catching them in the act, and shutting them down?
Of course, forkbombs are far from the only threat that made me wonder about possible solutions. For instance, do any existing file scanners actually check Alternate File Streams, Named Pipes, or the like? What about using the Windows "Native API" to detect filenames and registry keys that are cleverly hidden from the rest of the operating system? Stuff like that.
But back on the subject of forkbombs... what methods would you propose to automatically detect a forkbomb and selectively shut it down without interrupting legitimate processes, and what obstacles might one encounter using those techniques? And how viable would such a protection system actually be?
(For those not familiar, a forkbomb is basically a self-replicating process that continues to grow until it overwhelms your system. For an extremely simple example, a script or command that repeatedly calls itself. For a less computationally-inclined analogy, something like a bacterium reproducing exponentially.) -
This sort of thing seems like it should be outright illegal.
-
Not actually true. What this bug does is merely set the dirty bit, which tells the operating system that the drive is corrupt, prompting it to run a disk check. However, the filesystem is not actually corrupt in this case. If the filesystem ever were corrupt, though, the dirty bit would automatically be set.
Basically, this is the same as an anti-virus getting a false-positive and quarantining a harmless file. Except in this case, replace anti-virus with CHKDSK and "quarantining a harmless file" with "repairing an undamaged drive". -
Maybe those security holes wouldn't still be there if we had migrated over sooner <.<
-
The NASA news is sad. The Intel news is frustrating. The death of third-party cookies and widespread adoption of Encrypted DNS can only be a good thing, however.
Speaking of widespread adoption of things... if I ever hold a government office, I'm gonna campaign for a full migration from IPv4 to IPv6 to qualify for a tax-incentive. -
The only times I ever use Emoji are when I insert them manually via my mobile keyboard. Unfortunately as I write this post on PC, I'm unable to type my favorite particular emoji at this moment, and I can't edit it in later for obvious reasons. So, no fox-faces.
-
Ah. I just noticed them. Can't seem to find the one I'm used to though O.o
-
The forum's color palette seems to have changed since the last time I used it. It actually hurts my eyes in it's current form, too high-contrast for me.
-
I've been watching some videos on YouTube lately about various glitches in Windows (and how they could potentially be exploited by Malware, and/or prevented from occurring at all by security software developers), and then my train of thought just started to drift to the much less potentially harmful ones. In effect, the glitches that are just... funny.
So I'm creating this thread for anyone who would like to talk about funny glitches/bugs in Windows.
To start us off, I recently saw a video by FlyTech about one that will trick Windows into thinking that a *perfectly fine* drive has been corrupted, causing it to run a disk check. Aside from the extensive drive activity that results from the disk check itself, and the amount of time wasted by the unnecessary disk check, the bug itself is actually pretty harmless.
So... Does anybody else have a funny Windows bug they'd like to share?
-
1
-
-
I think having an option to change the icon color would help. -
I know that I'm necroing my own thread here, but I am happy to report that a recent update has seemingly fixed the issue entirely! (At least for me.)
-
The fact that WSL and WSL2 can easily expose security flaws deep in Windows, even in the filesystem and kernel, as frankly terrifying.
But also, potentially powerful in finding ways to patch those vulnerabilities!
-
Er... replacing my Hard-Drive *with* an SSD. Silly typos.
-
I fixed the root issue a long while ago by replacing my SSD. All's good now.
-
Still hoping that an ARM-compatible build is compiled sooner rather than later!
-
Time to start experimenting with it, and then create a GUI-based front end that sends commands to the program.
-
On the subject of Ring 0 versus Ring 1, the x86 instruction set architecture also has two other rings, which are rarely used except in the case of IBM's OS/2. Because they are so rarely used, AMD got rid of them when creating the x86-64 ISA. Not such a smart move, IMHO.
Hypothetical Solutions: Forkbombs and more
in General Chat
Posted
For the record, I am not actually encountering any Forkbombs right now. I'm just trying to brainstorm potential new features for a security suite that would actually be useful, as well as possible ways those features could be implemented.
I'm also hoping that the Forkbomb Detection, Prevention and Remediation concept will end up becoming the start of something far greater.