• Re: Screenshots etc.

    From Herbert Kleebauer@klee@unibwm.de to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sat Feb 7 13:39:27 2026
    From Newsgroup: alt.windows7.general

    On 2/7/2026 4:22 AM, Kenny McCormack wrote:

    And, the point is: Usenet *is* a text-only medium, by definition and
    decree, even if lots of people have abused it over the years.

    Good joke. The usenet is nearly completely binary only in these days.

    https://www.newsdemon.com/usenet-newsgroup-feed-size

    Daily Volume Date
    27.80 TiB 2017 Jan
    37.35 TiB 2018 Jan
    60.38 TiB 2019 Jan
    62.40 TiB 2020 Jan
    100.71 TiB 2021 Jan
    147.9 TiB 2022 Sep
    156.6 TiB 2022 Oct
    160.3 TiB 2022 Nov
    196 TiB 2023 Feb
    220 TiB 2023 Aug
    300 TiB 2024 Mar
    365 TiB 2024 Jul
    475 TiB 2024 Nov
    500 TiB 2025 June

    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From J. P. Gilliver@G6JPG@255soft.uk to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sat Feb 7 20:03:54 2026
    From Newsgroup: alt.windows7.general

    On 2026/2/7 3:22:5, Kenny McCormack wrote:
    In article <10m5ujv$h4sl$3@dont-email.me>,
    J. P. Gilliver <G6JPG@255soft.uk> wrote:
    ...
    But for Kenny's question above, most of us use some form of free
    image-hosting web site, where the one I use most asks for no login.

    No worries; I have no desire to post any screenshots here.

    I was just amused by the idea of someone requesting a screenshot on Usenet.

    As Tim Walz would say, weird!

    And, the point is: Usenet *is* a text-only medium, by definition and
    decree, even if lots of people have abused it over the years.
    People have been requesting screenshots - and in response, people have
    been uploading them to file/image sharing sites, and posting the URL of
    the uploaded file (thus remaining within "text-only" rules) - for years, decades I think.
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From J. P. Gilliver@G6JPG@255soft.uk to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sat Feb 7 20:08:56 2026
    From Newsgroup: alt.windows7.general

    On 2026/2/7 12:39:27, Herbert Kleebauer wrote:
    On 2/7/2026 4:22 AM, Kenny McCormack wrote:

    And, the point is: Usenet *is* a text-only medium, by definition and
    decree, even if lots of people have abused it over the years.

    Good joke. The usenet is nearly completely binary only in these days.
    That may be the case for commercial usenet. For free usenet, few or no
    "binary" 'groups are carried. (I think the same applies to "cheap"
    usenet too, but that's not going to continue for much longer, unless
    something has popped up to replace "the Berlin Server" that I don't know about.)
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sat Feb 7 16:42:09 2026
    From Newsgroup: alt.windows7.general

    J. P. Gilliver wrote:
    And, the point is: Usenet *is* a text-only medium, by definition and
    decree, even if lots of people have abused it over the years.

    People have been requesting screenshots - and in response, people have
    been uploading them to file/image sharing sites, and posting the URL of
    the uploaded file (thus remaining within "text-only" rules) - for years, decades I think.

    And, I might add, since of the million things we should know about privacy,
    we only know about six of them, PNRU fingerprinting becomes unreliable once people upload images online after destroying the subtle sensor-noise
    patterns those fingerprinting technique depend on.
    <https://i.postimg.cc/Gmbyp807/windows-android.jpg>

    PNRU (Photo-Response Non-Uniformity) relies on tiny, device-specific noise patterns which we obfuscate as a privacy hygiene habit BEFORE we post them.

    Those are screenshots, and not camera images, but if we don't know this
    tidbit about privacy, we allow our cameras to be uniquely identified.

    This won't bother most of us, but let's say someone posts to two different social media sites using the same camera as when they post to Usenet.

    *The camera 'can' uniquely be tracked across all three postings.*

    As processing power and storage gets better and better, the more it will be that we're tracked by our own online activities, such as this screenshot.
    <https://i.postimg.cc/xTDmWpt4/organization-phone-pc.jpg>
    --
    Privacy is knowing how to do the simplest of things, all day, every day.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sat Feb 7 19:56:06 2026
    From Newsgroup: alt.windows7.general

    On Sat, 2/7/2026 3:03 PM, J. P. Gilliver wrote:
    On 2026/2/7 3:22:5, Kenny McCormack wrote:
    In article <10m5ujv$h4sl$3@dont-email.me>,
    J. P. Gilliver <G6JPG@255soft.uk> wrote:
    ...
    But for Kenny's question above, most of us use some form of free
    image-hosting web site, where the one I use most asks for no login.

    No worries; I have no desire to post any screenshots here.

    I was just amused by the idea of someone requesting a screenshot on Usenet. >>
    As Tim Walz would say, weird!

    And, the point is: Usenet *is* a text-only medium, by definition and
    decree, even if lots of people have abused it over the years.

    People have been requesting screenshots - and in response, people have
    been uploading them to file/image sharing sites, and posting the URL of
    the uploaded file (thus remaining within "text-only" rules) - for years, decades I think.


    And the web sites hosting the materials, have been throwing
    away content for a similar period of time. The dead
    sites like imageshack and so on. PostImage did not
    keep all its content. There's a generation of material
    missing from there, too.

    Posting an image on USENET is never going to work well,
    due to the max size of posted content. And posting a series
    of chunks to build a file, that's a bore.

    Paul

    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From JJ@jj4public@gmail.com to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 11:13:58 2026
    From Newsgroup: alt.windows7.general

    On Sat, 7 Feb 2026 13:39:27 +0100, Herbert Kleebauer wrote:

    Good joke. The usenet is nearly completely binary only in these days.

    Usenet message is based on email message standard, and email was intended
    for text only. Initially.

    https://en.wikipedia.org/wiki/Usenet#Binary_content

    But technology evolve. I think it all started when MIME was created (in
    early 90s) and allow messages to be delivered in full 8-bit glory instead of just 7-bit. [*]

    UTF-8 encoded messages may be in 8-bit form instead of 7-bit depending on
    the sender's usenet/email client application. i.e. literally have ASCII character above 0x7F, for the raw UTF-8 encoded text.

    [*] Even though 8-bit form is possible, I'm not sure Null character can be successfully sent.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From R.Wieser@address@is.invalid to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 08:21:52 2026
    From Newsgroup: alt.windows7.general

    Herbert,

    And, the point is: Usenet *is* a text-only medium, by definition and
    decree, even if lots of people have abused it over the years.

    Good joke. The usenet is nearly completely binary only in these days.

    https://www.newsdemon.com/usenet-newsgroup-feed-size

    That list is useless, as it doesn't show what part of those numbers is from binaries and what from text-only messages. Nor does it include the number
    of posters in either group.

    And you're just looking at the ammount of data, making it sound as if a
    single persons 1MB upload trumps 200 people uploading 5KB text-only
    messages.

    Also, a number of "usenet servers" act as defacto (payed access)
    file-servers, just using NNTP as its transfer mechanism. That doesn't make them part of usenet, it just skews the numbers you posted.

    Their peerage is limited to other defacto file-servers, with the actual
    usenet servers, like Ethernal September, mostly staying far away from them.

    Yes, the ammount of resources used by binary posters is staggering, but they are still just a tiny fraction of the total number of usenet posters.

    Regards,
    Rudy Wieser


    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From R.Wieser@address@is.invalid to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 09:10:58 2026
    From Newsgroup: alt.windows7.general

    Paul,

    Posting an image on USENET is never going to work well,
    due to the max size of posted content.

    And yet it has been working well for decades now - proven by the fact that binary newsgroups are still thriving.

    And posting a series of chunks to build a file,

    And yes, thats exactly how its done. Which you no doubt already know.

    that's a bore.

    That's why you let a program/script do the uploading. And downloading, if
    you are a leecher.

    Regards,
    Rudy Wieser


    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From R.Wieser@address@is.invalid to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 09:51:12 2026
    From Newsgroup: alt.windows7.general

    JJ,

    But technology evolve. I think it all started when MIME was
    created (in early 90s) and allow messages to be delivered in
    full 8-bit glory instead of just 7-bit. [*]

    I think you got your cause and effect reversed. BASE64 was used before
    MIME. In that time newsgroup readers recognised the BASE64 encoded block
    and could decode and save it. MIME just defined the proccess better.

    UTF-8 encoded messages may be in 8-bit form instead of 7-bit

    What about *must* be in 8-bit form ? Otherwise, when the high bit is stripped, you are left with jumbled ASCII. :-)

    depending on the sender's usenet/email client application.

    The problem was not the client, but the (intermediate) newsgroup servers.
    In the early days those could be 7-bit ASCII only (mechanical teletype terminals) - besides that other characterset encodngs could be used, like EBDIC. A transparent translation between characterset encodings was the intention of the early NNTP rules.

    [*] Even though 8-bit form is possible, I'm not sure Null character
    can be successfully sent.

    NNTP specified which contol characters where allowed, which excuded most of the characters below 0x20. Including the 0x00 character.

    Regards,
    Rudy Wieser


    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Frank Slootweg@this@ddress.is.invalid to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 10:52:52 2026
    From Newsgroup: alt.windows7.general

    JJ <jj4public@gmail.com> wrote:
    On Sat, 7 Feb 2026 13:39:27 +0100, Herbert Kleebauer wrote:

    Good joke. The usenet is nearly completely binary only in these days.

    Usenet message is based on email message standard, and email was intended
    for text only. Initially.

    https://en.wikipedia.org/wiki/Usenet#Binary_content

    But technology evolve. I think it all started when MIME was created (in
    early 90s) and allow messages to be delivered in full 8-bit glory instead of just 7-bit. [*]

    As others have mentioned, binary content on Usenet/NetNews precedes
    MIME by quite a long time. At first, uuencode was used, which works for
    a 7-bit data path.

    For example the DOS binary of uudecode.com was transmitted as a *text*
    file to overcome the Catch-22 problem of the recipient not (yet)
    having uudecode.com needed to decode the uuencode-d binaries [1].

    [...]

    [1] The (59KB) 'CBIP Starter's Kit' posted to comp.binaries.ibm.pc
    contained:
    1) Instructions
    2) Text source for UUDECODE
    3) UNZIP, ZIP file extractor, in UUENCODE form
    "All you need is a file editor."
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From J. P. Gilliver@G6JPG@255soft.uk to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 15:06:28 2026
    From Newsgroup: alt.windows7.general

    On 2026/2/7 21:42:9, Maria Sophia wrote:
    J. P. Gilliver wrote:

    []

    People have been requesting screenshots - and in response, people have
    been uploading them to file/image sharing sites, and posting the URL of
    the uploaded file (thus remaining within "text-only" rules) - for years,
    decades I think.

    And, I might add, since of the million things we should know about privacy, we only know about six of them, PNRU fingerprinting becomes unreliable once

    []

    *The camera 'can' uniquely be tracked across all three postings.*

    As processing power and storage gets better and better, the more it will be that we're tracked by our own online activities, such as this screenshot.
    <https://i.postimg.cc/xTDmWpt4/organization-phone-pc.jpg>

    "Just because you're paranoid, doesn't mean they _aren't_ out to get
    you" - but!

    I think the vast majority of screenshots uploaded are actually screen _captures_, which obviously do not have the pixel-stains of a camera
    shot. On the whole, the only time a camera is used is in discussion of
    BIOS and similar screens (or, occasionally, where things happen too fast
    - though you then probably need a video camera in order to be able to
    get the image you want; even then, screen capture can be video).

    So, yes, your privacy concern _can_ be valid - but only for a small
    fraction of screen "shots".
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

    Who's General Failure & why's he reading my disk?
    (Stolen from another .sig)
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From J. P. Gilliver@G6JPG@255soft.uk to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 15:18:10 2026
    From Newsgroup: alt.windows7.general

    On 2026/2/8 0:56:6, Paul wrote:
    On Sat, 2/7/2026 3:03 PM, J. P. Gilliver wrote:
    On 2026/2/7 3:22:5, Kenny McCormack wrote:
    In article <10m5ujv$h4sl$3@dont-email.me>,
    J. P. Gilliver <G6JPG@255soft.uk> wrote:
    ...
    But for Kenny's question above, most of us use some form of free
    image-hosting web site, where the one I use most asks for no login.

    No worries; I have no desire to post any screenshots here.

    I was just amused by the idea of someone requesting a screenshot on Usenet. >>>
    As Tim Walz would say, weird!

    And, the point is: Usenet *is* a text-only medium, by definition and
    decree, even if lots of people have abused it over the years.

    People have been requesting screenshots - and in response, people have
    been uploading them to file/image sharing sites, and posting the URL of
    the uploaded file (thus remaining within "text-only" rules) - for years,
    decades I think.


    And the web sites hosting the materials, have been throwing
    away content for a similar period of time. The dead
    sites like imageshack and so on. PostImage did not
    keep all its content. There's a generation of material
    missing from there, too.

    Posting an image on USENET is never going to work well,
    due to the max size of posted content. And posting a series
    of chunks to build a file, that's a bore.

    Paul

    I think, for the purposes covered here (someone asked for/suggested a screenshot, someone else said how do you do that on a text-only medium,
    I and others said you don't - you put it somewhere else and post the URL
    of where you've put it on the text-only medium), the _longevity_ of the
    image storage isn't that important: someone is posting a problem (or a solution), others see it within the time it's kept, and suggest
    solutions (or note the one shown).
    --
    J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

    Who's General Failure & why's he reading my disk?
    (Stolen from another .sig)
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Maria Sophia@mariasophia@comprehension.com to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Sun Feb 8 19:26:28 2026
    From Newsgroup: alt.windows7.general

    J. P. Gilliver wrote:
    "Just because you're paranoid, doesn't mean they _aren't_ out to get
    you" - but!

    :)

    I was trained in TLA-level privacy, so to speak, where I was told you don't protect against what you think they'll do, but what you know they can do.

    Privacy is a million things, most of which are easy to do, where protecting camera images from fingerprinting is something that's relatively easy.

    Of course, as you noted, screenshots are different from camera images.
    In theory, GPU drivers or font renderers could introduce artifacts, but operating systems treat a screenshot as a direct copy of the framebuffer,
    (not as a photograph of the screen). That design choice eliminates most of
    the natural device-specific quirks that camera forensics relies on.

    For example, this is a screenshot of an image posted to this ng long ago.
    <https://i.postimg.cc/Gh22Sb2N/desktop.jpg>


    I think the vast majority of screenshots uploaded are actually screen _captures_, which obviously do not have the pixel-stains of a camera
    shot. On the whole, the only time a camera is used is in discussion of
    BIOS and similar screens (or, occasionally, where things happen too fast
    - though you then probably need a video camera in order to be able to
    get the image you want; even then, screen capture can be video).

    So, yes, your privacy concern _can_ be valid - but only for a small
    fraction of screen "shots".

    I never disagree with a logically sensible statement so I agree with you
    that for "screenshots" camera sensor imperfections don't show up in them.

    For operating system newsgroups, as you noted, camera shots are rarely
    posted, but sometimes we post our equipment configurations to the ng.
    <https://i.postimg.cc/6QJqK6Cj/desktop02.jpg>

    Note though that privacy is a million things, of which most people only
    know a half dozen, where a screenshot of a camera image confers privacy.

    Only visible artifacts from the camera photo will carry over, such as:
    a. Noise that is visibly present in the image
    b. Lens distortion that is visibly present
    c. Chromatic aberration that is visibly present
    d. Compression artifacts
    e. Blurring, vignetting, etc.

    If the camera photo shows grain, color shifts, or distortion, the
    screenshot will faithfully copy those pixels. but these are not the
    forensic "sensor fingerprints" used to identify a specific device.

    So one basic privacy step is to screenshot camera images before posting.
    --
    Often those who most deprecate privacy are those who least understand it.
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Char Jackson@none@none.invalid to alt.comp.os.windows-xp,alt.windows7.general,alt.comp.os.windows-10,alt.msdos.batch.nt on Mon Feb 9 20:06:51 2026
    From Newsgroup: alt.windows7.general

    On Sun, 8 Feb 2026 09:10:58 +0100, "R.Wieser" <address@is.invalid>
    wrote:

    Paul,

    Posting an image on USENET is never going to work well,
    due to the max size of posted content.

    And yet it has been working well for decades now - proven by the fact that >binary newsgroups are still thriving.

    I was going to respond to Paul, but you covered it nicely, thanks.

    Taking a casual look just now, the biggest *single* post that I see is 2,796,888,255 KB, (about 2.8 TB!), so yeah, size limits aren't a real
    thing. Besides, if you need a larger capacity you just break it into
    pieces, as mentioned directly below. Easy peasy.

    And posting a series of chunks to build a file,

    And yes, thats exactly how its done. Which you no doubt already know.

    that's a bore.

    That's why you let a program/script do the uploading. And downloading, if >you are a leecher.

    --- Synchronet 3.21b-Linux NewsLink 1.2