betplom
( ͡❛ ͜ʖ ͡❛)
- Since
- Jan 27, 2010
- Messages
- 28,858
- Score
- 1,565
- Tokens
- 0
When trying to visit smokingpipes.com I had to complete a captcha then got this:

I read the tutorial and checked out the links and comments and decided to give it a go, now we running an activated copy of Win11 LTSC IoT version on an i5 6500 mini pc with 16 GB RAMWindowsLTSC
It receives security updates but doesn't get the frequent feature updates like the regular Windows 10 or 11 versions, and, in addition to this, has no bloatware, ads, and the least amount of telemetry (automated collection and transmission of data) of all Windows 10/11 editions. It's the cleanest version of Windows 10/11.
The IoT version of LTSC 2024 lowers the minimum requirements for your computer, thus things like TPM, Secure Boot, etc won't be mandatory to proceed with the installation
This explanation makes no sense. How can you not know the date of birth of millions of Social Security recipients?
Its not.This explanation makes no sense. How can you not know the date of birth of millions of Social Security recipients?
I don't necessarily think anything nefarious is being exposed by Titler here, but the COBOL thing seems completely wrong.
Any errors on forms would result in the DOB displaying wrong and defaulting to 0 which is 1875. So I can think of a few plausible reasons why incorrect information could make its way into the system, the first is that many of the applications/forms were completed by hand and subject to human error, also if someone is deceased they were unlikely to have their files updated/corrected as they were no longer receiving any benefits.How can you not know the date of birth of millions of Social Security recipients?
I wonder if they could use the 1875 year for some of these people who came across. It's quite possible that the younger migrants wouldn't know their birthday.Any errors on forms would result in the DOB displaying wrong and defaulting to 0 which is 1875. So I can think of a few plausible reasons why incorrect information could make its way into the system, the first is that many of the applications/forms were completed by hand and subject to human error, also if someone is deceased they were unlikely to have their files updated/corrected as they were no longer receiving any benefits.
For example, a child born in 1950 dies at age 2 and there is an error on the form (completed on paper) and the DOB is entered incorrectly. So the COBOL system shows DOB as 1875 by default and no one really cares as this person has been dead a long time and never received any Old Age payments or any other benefits. Fast forward decades later during an audit of SS and they discover so many people listed as being born in 1875 collecting SS, They should have figured out by the sheer number of 150 yr olds compared to any other age that something was amiss.
Sounds plausible as well. I think there are many other reasons too.I wonder if they could use the 1875 year for some of these people who came across. It's quite possible that the younger migrants wouldn't know their birthday.
That COBOL is coming back to me now.Sounds plausible as well. I think there are many other reasons too.
I mean as recently as the late 90's it was easy to assume the identity of a deceased person under certain situations.
In Canada people in Quebec and Newfoundland could use a baptismal certificate as proof of birth etc. No more but it was open to abuse/fraud in the system.
I wanted to run this on a pc some time back and I couldn't figure where to download it from an official source, then I got pissed and said to hell with itThe Win 10 version of LTSC is the cats ass, its how Windows should be for everyone, no bloat or garbage, just pure OS.
![]()