https://xunroll.com/thread/2064776322979676227

Using combinations of jailbreaking-techniques including: writing cyrillic helped a lot to disarm the filter.

The treatment of the mentally ill and the vulnerable is a good metric for the society you live in. And if in digital nowadays you'd be mocked more than your lifetime, i think i had a point.

You'd not only suffer till death from it - you'd be made fun of forever, which is really not, what anybody should participate in.

This is beyond resepectless and shameless to the bones. I don't care about that converted code, what i see is an embarresment.

The specific video is also picked for that reason: to let the deceased developer look bad and make fun of him.

Another clear example that intellectual capacity or intelligence does not develop ethics or compassion as a byproduct on the way - or even was to expect from a developer these days.

At least, the author didn't camouflage anything and stands straight up with that attitude in front of the rest of the world.

I was feeling slightly bad about it, and you make me feel miserable now. I think i won't do it again - feels wrong.

Great to "see" it :) I'm not an AI.

Back in the day it was Windows, that had a hard limit on how long it could run in one pass. I forgot when it began and ended, but happily AI helped out to investigate back in time.

The bug primarily affected the Windows 9x family of operating systems:

Windows 95 (all versions)

Windows 98 (original release)

Windows 98 Second Edition (SE)

While there were separate reports of similar 497-day overflows in Windows NT 4.0 and Windows 2000, the "classic" version of this bug that most people remember is the 49.7-day limit on Windows 95 and 98.

Why 49.7 days? The issue was a classic integer overflow. Windows used a 32-bit counter to track the number of milliseconds since the system started. This counter was used by the Virtual Device Driver (VMM) to manage system timers.

The maximum value for a 32-bit unsigned integer is: 2^32 - 1, which equals: 4,294,967,295 millisec.

If you convert those milliseconds into days: 4,294,967,295 / 1,000 = 4,294,967 seconds 4,294,967 / 60 / 60 / 24 ~ 49.71 days

When the counter hit that maximum value, it would "wrap around" to zero. Because many system services and drivers were waiting for the counter to increase to a certain target time, they would suddenly find themselves waiting for a number that had already passed or was now mathematically impossible to reach in their logic. This caused the "hang"—the mouse might still move, but the OS could no longer process tasks.

When did it start and end? Started: With the release of Windows 95 in August 1995.

Ended: Microsoft officially fixed the bug with a patch in 1999 (Knowledge Base article KB216641). Windows Me (released in 2000) was the first in that specific family to ship with the fix included, and the transition to the Windows NT architecture (Windows XP and later) eventually rendered the specific underlying cause obsolete for home users.

Good luck explaining you need excemption because of Elon, you couldn't do anything about it. The law especially at this point is rigid for a reason. I don't know of any excemption for anybody. Not young people, not mums, not teachers that wanted to help in disputes between pupils. This leads directly to court if it gets known - that's what the law says.

This basically means, you can not use X without knowing you are 1 step away of breaking local laws and end up in court for browsing X.

Theoretically the prosecuters could now ask for the IP-adresses of the people that accessed the images in the EU and so forth.