Event JSON
{
"id": "3abf9902bd47195643cb41bc9d7a00a7ea696e6f48f6d622cb63366a290dd0c6",
"pubkey": "43fb5b901c8fc0f040ae9b1167d8a46d2ccaf0e41f7396728df43579a3d15f77",
"created_at": 1731196852,
"kind": 1,
"tags": [
[
"t",
"msdos"
],
[
"t",
"86box"
],
[
"t",
"retrocomputing"
],
[
"t",
"security"
],
[
"t",
"emulation"
],
[
"proxy",
"https://techhub.social/@dfx/113455716906734542",
"web"
],
[
"imeta",
"url https://files.techhub.social/media_attachments/files/113/455/706/538/257/383/original/3d421ef05d8de219.png",
"m image/png"
],
[
"t",
"privacy"
],
[
"t",
"dataleak"
],
[
"proxy",
"https://techhub.social/users/dfx/statuses/113455716906734542",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://techhub.social/users/dfx/statuses/113455716906734542",
"pink.momostr"
],
[
"-"
]
],
"content": "Not the first time I'm seeing this... this is actually a very old issue... but today, I just found it especially annoying!\n\nI do love retro systems, but I must admit, both MS-DOS 6.22 and PC-DOS 2000 are super messy and flawed when it comes to memory usage and privacy protection. Tonight, I just wanted to copy a few game files to a newly created disk image. I used the following command:\n\nCOPY C:\\TEMP\\*.* A:\\\n\nThis did work as intented, but when I checked the image a little later using the \"Disk Image Tool\", I noticed the system also wrote a lot of garbage data to each file's final cluster. Completely random parts of directory listings or even chunks of some README files. Imagine sharing a few innocent files with some co-workers, but your computer also secretly hands out all kinds of random snippets of your most private folders for everyone to enjoy!\n\nOh boy...\n\n#MSDOS #Privacy #DataLeak #Security #RetroComputing #Emulation #86Box\nhttps://files.techhub.social/media_attachments/files/113/455/706/538/257/383/original/3d421ef05d8de219.png\n",
"sig": "35ad82b3217ce586dee9f5783cb04e56945b6d157293973f0b9aef82bfd91eb01744db6762e89e1833a49803bcc1a9c15438d1e704e9936fed14d9d03588684f"
}
