Grammarly is an ipso facto security hole that is extremely likely to be pwned or controlled outright by a number of state security services. It should be treated like malware.
Ah, Tsutomo, my learned disciple!
The weirdest bug I've seen yet
281–290 of 334 posts
Re: The weirdest bug I've seen yet
#282Re: The weirdest bug I've seen yet
#283The weirdest bug I've seen yet was a concurrency race condition which led to 'spooky action at a distance'. Every time I tried to console.log() to observe some value to see the cause of the bug, the bug would go away.
But alas, I hadn't discovered some new quantum effect... It turns out to have been because the race condition was close within maybe 1 millisecond and adding the console.log() statement there meant that one part of the code would take a bit longer to execute and so the race condition would not occur.
Re: The weirdest bug I've seen yet
#284Earlier quoted context omitted.
There are a lot of people whose professional outcomes are meaningfully constrained by their ability produce clear business English. I know a guy who used to get inexplicable feedback about his communication that boiled down to “write better.” This limited his ability to get promoted. He runs all his comms through ChatGPT and asks it to “make this more professional” and doesn’t get that feedback anymore.
I get that people don't care or understand this, but that's also saying he cc's OpenAI, and therefore probably Microsoft, and therefore almost definitely the NSA, on all his business communications. What a world.
I’m not sure how to explain this but Microsoft doesn’t need OpenAI to get access to business emails.
Re: The weirdest bug I've seen yet
#285Earlier quoted context omitted.
The GIF cannot be responsible: as untrusted web content, if it can trigger a crash, the responsibility lies with the local software stack. So you have only two suspects: Chrome and Grammarly. The GIF is at most an accomplice.
more like a murder weapon
Thanks, that’s much better. I wasn’t at all happy with “accomplice” but my mind was blanking on what it should be.
Re: The weirdest bug I've seen yet
#286Once my college professor was working on her research paper and told me she was struggling get text to stay underlined. Assuming a simple user error, I expected to help her out in 5 minutes. Over three hours later, we discovered that the combo of her specific video card driver version along with her specific printer driver version would keep text from printing out underlined.
Much better than the Xerox bug that caused numbers in scanned documents to get changed. https://www.zdnet.com/article/xerox-scanners-alter-numbers-i... Ouch
I kind of remember this one. It wasn't really a bug. I think Xerox used software that was known to not be 100% trustworthy to recognize numbers when used at a certain compression level. It was even in the manual if i'm not mistaken.
Re: The weirdest bug I've seen yet
#287Can you share the `loader-spinner.gif` ? Preferably over a service that does not recompress it.
Re: The weirdest bug I've seen yet
#288Earlier quoted context omitted.
The Chromium source code is also available, not sure why they said they couldn't look at it. If it replicates with Chromium you can dig right in.
If you read carefully you will see that they said the bug didn’t replicate with Chromium
They did yeah, but did they try Chromium with Grammarly?
Re: The weirdest bug I've seen yet
#289Earlier quoted context omitted.
It's a just-so story. The null hypothesis is that it's not true.
That is the definition of null hypothesis, yes. Not to be blunt, but you might get a closer shave with Occam's Razor.
The null hypothesis isn't "it's not true" it's "what's has the highest prior probability?".
If my wife said "I'm going to the shops" I wouldn't assume she was lying until proven otherwise.
Re: The weirdest bug I've seen yet
#290The weirdest bug I've seen yet was a concurrency race condition which led to 'spooky action at a distance'. Every time I tried to console.log() to observe some value to see the cause of the bug, the bug would go away. But alas, I hadn't discovered some new quantum effect... It turns out to have been because the race condition was close within maybe 1 millisecond and adding the console.log() statement there meant that…