From Newsgroup: alt.comp.os.windows-11

On 2026/8/22 10:35:41, Frank Slootweg wrote:
[]

If Micky wants to look 'under the hood', he should do so on his phone.
The WhatsApp app on Windows just has a temporary partial cache so you
can use the big screen, keyboard and 'mouse'. But the complete and
actual data in on the phone, not on Windows.

[]
So can WhatsApp not be used on a computer alone?--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()ALIS-Ch++(p)Ar++T+H+Sh0!:`)DNAf

You cannot simply assume someone is honest just because they are not an MP.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

J. P. Gilliver <G6JPG@255soft.uk> wrote:

On 2026/8/22 10:35:41, Frank Slootweg wrote:
[]

If Micky wants to look 'under the hood', he should do so on his phone. The WhatsApp app on Windows just has a temporary partial cache so you
can use the big screen, keyboard and 'mouse'. But the complete and
actual data in on the phone, not on Windows.

[]
So can WhatsApp not be used on a computer alone?--

No, as far as I know, it cannot.

In the old days you could only use WhatsApp on the computer if
WhatsApp on the phone was available, i.e. the sending and receiving was
done by the phone and the computer was only a 'terminal' for the
display, keyboard and mouse.

AFAIK, these days you can use WhatsApp on the computer 'even' if the
phone is not up. But as I indicated, that is only a temporary thing. If
you don't have a phone with a WhatsApp account on that phone, you cannot
use WhatsApp on the computer. As far a WhatsApp is concerned, the
computer is only a 'Linked device' to the phone.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 8/22/2026 5:52 PM, Frank Slootweg wrote:

J. P. Gilliver <G6JPG@255soft.uk> wrote:

So can WhatsApp not be used on a computer alone?--

No, as far as I know, it cannot.

> AFAIK, these days you can use WhatsApp on the computer 'even' if the

phone is not up. But as I indicated, that is only a temporary thing. If
you don't have a phone with a WhatsApp account on that phone, you cannot
use WhatsApp on the computer. As far a WhatsApp is concerned, the
computer is only a 'Linked device' to the phone.

But, as far as I know, you can install an Android emulator in Windows
and use WhatsApp in this emulator. It should be even possible to
connect the Windows version of WhatsApp with the app in the emulator,
so you only have to start the emulator every few weeks to connect with
the Windows version and in the other time use the Windows version only.



--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 08/21/2026 12:05 PM, micky wrote:

In alt.comp.os.windows-10, on 18 Aug 2026 15:13:29 GMT, Frank Slootweg <this@ddress.is.invalid> wrote:

micky <NONONOmisc07@fmguy.com> wrote:

No wonder our children can't read. Windows and Whatsapp have conspired
to use up all the letters. This is the name whatsapp gave a file, a
copy of an image.

This is a profligate waste of characters.

"C:\Users\mmm\AppData\Local\Packages\5319275A.WhatsAppDesktop_cv1g1gvanyjgm\LocalState\
sessions\F04C4D1BD02108439088985FC629970DC4886EBE\transfers\2026-33\WhatsApp
Image 2026-08-13 at 7.10.30 AM.jpeg"

To pick a nit, the *file* name isn't that long and quite descriptive:

WhatsApp Image 2026-08-13 at 7.10.30 AM.jpeg

The *path* contains a *folder* whose name is quite long, but that long
name is 1) not for normal use and 2) stored only once, i.e. not for
every file.

You're right!

Summary: Much Ado About Nothing

But whatsapp chose the folder names.

As noted earlier that is normal behavior for WhatsApp.
The filename numbering is a UUID (Universally Unique Identification, 36-character random text string) and represents the nomenclature the app creates(i.e. on their platform) to ensure no 2(or more) filenames get
the same name.

Not a waste of characters or using up all letters, but a practical and purposeful reason complying with standard industry practice to prevent overwriting and naming conflict(s).
--
...w¡ñ§±¤ñ
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On Sat, 8/22/2026 2:00 PM, ....winston wrote:

On 08/21/2026 12:05 PM, micky wrote:

In alt.comp.os.windows-10, on 18 Aug 2026 15:13:29 GMT, Frank Slootweg
<this@ddress.is.invalid> wrote:

micky <NONONOmisc07@fmguy.com> wrote:

No wonder our children can't read.  Windows and Whatsapp have conspired >>>> to use up all the letters.   This is the name whatsapp gave a file, a >>>> copy of an image.

This is a profligate waste of characters.

"C:\Users\mmm\AppData\Local\Packages\5319275A.WhatsAppDesktop_cv1g1gvanyjgm\LocalState\
sessions\F04C4D1BD02108439088985FC629970DC4886EBE\transfers\2026-33\WhatsApp
Image 2026-08-13 at 7.10.30 AM.jpeg"

  To pick a nit, the *file* name isn't that long and quite descriptive: >>>
  WhatsApp Image 2026-08-13 at 7.10.30 AM.jpeg

  The *path* contains a *folder* whose name is quite long, but that long >>> name is 1) not for normal use and 2) stored only once, i.e. not for
every file.

You're right!

  Summary: Much Ado About Nothing

But whatsapp chose the folder names.

As noted earlier that is normal behavior for WhatsApp.
The filename numbering is a UUID (Universally Unique Identification, 36-character random text string) and represents the nomenclature the app creates(i.e. on their platform) to ensure no 2(or more) filenames get the same name.

Not a waste of characters or using up all letters, but a practical and purposeful reason complying with standard industry practice to prevent overwriting and naming conflict(s).

F04C4D1BD0 2108439088 985FC62997 0DC4886EBE <=== Hexadecimal character set 0123456789 0123456789 0123456789 0123456789 <=== 40 characters

That's 160 bits, and most likely to be a SHA1.

That's the match I could find for 160 bits.

I'm still waiting for someone to do

sha1sum "WhatsApp Image 2026-08-13 at 7.10.30 AM.jpeg"

and see if that hex string is the result.

Paul


--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.comp.os.windows-11

On 08/22/2026 2:57 PM, Paul wrote:

On Sat, 8/22/2026 2:00 PM, ....winston wrote:

On 08/21/2026 12:05 PM, micky wrote:

In alt.comp.os.windows-10, on 18 Aug 2026 15:13:29 GMT, Frank Slootweg
<this@ddress.is.invalid> wrote:

micky <NONONOmisc07@fmguy.com> wrote:

No wonder our children can't read.  Windows and Whatsapp have conspired >>>>> to use up all the letters.   This is the name whatsapp gave a file, a >>>>> copy of an image.

This is a profligate waste of characters.

"C:\Users\mmm\AppData\Local\Packages\5319275A.WhatsAppDesktop_cv1g1gvanyjgm\LocalState\
sessions\F04C4D1BD02108439088985FC629970DC4886EBE\transfers\2026-33\WhatsApp
Image 2026-08-13 at 7.10.30 AM.jpeg"

  To pick a nit, the *file* name isn't that long and quite descriptive: >>>>
  WhatsApp Image 2026-08-13 at 7.10.30 AM.jpeg

  The *path* contains a *folder* whose name is quite long, but that long >>>> name is 1) not for normal use and 2) stored only once, i.e. not for
every file.

You're right!

  Summary: Much Ado About Nothing

But whatsapp chose the folder names.

As noted earlier that is normal behavior for WhatsApp.
The filename numbering is a UUID (Universally Unique Identification, 36-character random text string) and represents the nomenclature the app creates(i.e. on their platform) to ensure no 2(or more) filenames get the same name.

Not a waste of characters or using up all letters, but a practical and purposeful reason complying with standard industry practice to prevent overwriting and naming conflict(s).

F04C4D1BD0 2108439088 985FC62997 0DC4886EBE <=== Hexadecimal character set 0123456789 0123456789 0123456789 0123456789 <=== 40 characters

That's 160 bits, and most likely to be a SHA1.

That's the match I could find for 160 bits.

I'm still waiting for someone to do

sha1sum "WhatsApp Image 2026-08-13 at 7.10.30 AM.jpeg"

and see if that hex string is the result.

Paul

Yes, thanks for counting! :)

WhatsApp uses a 40 character cryptographic hash(SHA-1) instead of the
standard 36-character UUID.
--
...w¡ñ§±¤ñ
--- Synchronet 3.21d-Linux NewsLink 1.2