Email or username:

Password:

Forgot your password?
Royce's posts Back to profile
3 posts total
Royce Williams

Password cracking is the art of automating the math of psychology, at speed.

7 December at 22:57 | Open on infosec.exchange
Royce Williams

Tell me you've never helped seniors with tech, without telling me you've never helped seniors with tech.

And I don't just mean the person answering this question. I also mean whoever decided to remove this option.

Google forums question, titled: "How to stop scrollbar from hiding" with text: Trying to help my grandma, the scrollbars disappear when not hovering over them with the cursor. She uses an old trackball mouse and will not change so she doesn't have a scroll wheel. the setting "chrome://flags" "overlay scrollbars" doesn't show up at all, even when I reset the settings. Should I move her to a different browser or is there a setting that will help? ChromeOS doesn't seem very unfriendly. With metadata: "This question is locked and replying has been disabled" and "I have the same question (8)" Recommended Answer from "Kevin (Snails), Diamond Product Expert", with text: That flag was removed in 2019. Something will have to change. I suggest she get used to the touchpad. It may take a little while, but once she gets used to it I suspect she'll find it much easier to scroll with two fingers gently on the touchpad than clicking a scrollbar and dragging.
1 February at 0:07 | Open on infosec.exchange
Show previous comments
ThaCuber

@tychotithonus
companies nowadays:
- how do I do <accessibility thing that was deprecated or removed for no reason>
- you can't, learn how to do <thing I am physically unable to do>, smh what a skill issue

2 February at 17:38 | Open on mastodon.gamedev.place
Corb_The_Lesser

@tychotithonus Grandma should switch to Firefox, which has an option to always show scrollbars.

You don't need to be a grandma to want/need scrollbars. Removing them is bad, arrogant, design.

2 February at 18:23 | Open on mastodon.social
DELETED

@tychotithonus the war on scrollbars really pisses me off

2 February at 18:37 | Open on fosstodon.org
Royce Williams

@robertatcara As someone who personally discovered and fixed Y2K bugs that would have had significant real world impact, it is disturbing to hear someone propagate this myth [that it was a "big fuss about nothing"]. And it is a myth.

This is what really happened:
time.com/5752129/y2k-bug-histo

The testing methodology insured that these impacts were not hypothetical. At my company, the testing was performed by actually rolling the clock forward to test systems to see what would happen. For example, I discovered that every ATM in the state of Alaska operated by my company would have locked up until a PROM chip was swapped. Someone had to fly all over the state to proactively swap the chip beforehand, to avoid significant customer impact.

And that was just one story. I personally oversaw investigation and fixes for other hardware and software at that company that would have failed.

And that was just my company. I spoke with others in IT at that time with similar stories. And that was just the people I knew.

So no, it wasn't "a big fuss about nothing" - and saying so is both dangerously revisionist, and disrespectful of the work it took to prevent real impacts.

#Y2K

@robertatcara As someone who personally discovered and fixed Y2K bugs that would have had significant real world impact, it is disturbing to hear someone propagate this myth [that it was a "big fuss about nothing"]. And it is a myth.

This is what really happened:
time.com/5752129/y2k-bug-histo

30 Dec 2023 at 16:05 | Open on infosec.exchange
Show previous comments
leecarroll
GreenDotGuy

@tychotithonus @robertatcara I wasn't 'oversseing' anything back then, but I had tables of test equipment laid out in a warehouse, replicating almost everything we supported at the bank my company contracted for. We definitely identified things that would have gone really bad unless we applied Y2K patches. Also, there weren't many automated patching systems in use back then, we were trying to make it 'one visit per desk', often on the overnight shift.

3 January at 4:31 | Open on infosec.exchange
sverx🗨️

@tychotithonus @robertatcara

I am bewildered at how many companies had spent so much to make sure their software was Y2K compliant and at the same time NOT fix the Y2K leap year 'bug'.

So the 29th of February 2000 where I worked back then, some systems were displaying March 1 instead🤦

3 January at 9:35 | Open on mastodon.gamedev.place
Go Up