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.
Summary: Much Ado About Nothing
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.
micky <NONONOmisc07@fmguy.com> 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.
1) Who cares? 2) these days, WhatsApp on Windows is a WebView2-based (non-)app, so it's one big mess anyway (see it's *nine* processes in
Task Manager) and 3) so sue Meta, you can pretend to be the 31st state.
But seriously: Just use the app itself, either on the phone or on
Windows and leave the stuff under the hood alone, no need to look there.
On Fri, 8/21/2026 2:02 PM, Frank Slootweg wrote:
micky <NONONOmisc07@fmguy.com> 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.
1) Who cares? 2) these days, WhatsApp on Windows is a WebView2-based (non-)app, so it's one big mess anyway (see it's *nine* processes in
Task Manager) and 3) so sue Meta, you can pretend to be the 31st state.
But seriously: Just use the app itself, either on the phone or on
Windows and leave the stuff under the hood alone, no need to look there.
He has a trace of a WhatsApp discussion thread, that includes images
used in the thread. You can do those traces, with or without images,
so if you wanted just text, the trace shows the image is not
included. Micky is looking at some files which apparently
were extracted from the WhatsApp database. I expect the database
is encrypted, which is why you would not be doing that without
the tool for the job.
Remember back to the thread where "Narrow Non Breaking Spaces were
discussed, and the inability to print something". And the root cause
of the failure, might well be some SoftBank emoji which are not
standard Unicode.
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.
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 <G6JPG@255soft.uk> wrote:
So can WhatsApp not be used on a computer alone?--
No, as far as I know, it cannot.
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.
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.
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).
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
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 4 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 497099:23:12 |
| Calls: | 182 |
| Files: | 744 |
| D/L today: |
6 files (5,132K bytes) |
| Messages: | 73,551 |