Been cleaning things up and did some searches for
paths I haven't used for a long time ...found hundreds
of them too mostly in 'history' type files collected
by most progs. Maybe they should regularly check for
and CLEAR paths that are not readable.

--
"Peace is better than war; in peace the sons bury their
fathers, in wars the fathers their sons". Croesus

On 2023-04-14 14:09, bad sector wrote:
>
> Been cleaning things up and did some searches for
> paths I haven't used for a long time  ...found hundreds
> of them too mostly in 'history' type files collected
> by most progs. Maybe they should regularly check for
> and CLEAR paths that are not readable.

Paths? What paths? Where?

--
Cheers, Carlos.

Am 14.04.23 um 14:09 schrieb bad sector:
>
> Been cleaning things up and did some searches for
> paths I haven't used for a long time ...found hundreds
> of them too mostly in 'history' type files collected
> by most progs. Maybe they should regularly check for
> and CLEAR paths that are not readable.

You have a mess of gigantic dimensions. Why are you declaring that here
in the Usenet?

--
De gustibus non est disputandum

On 4/14/2023 8:09 AM, bad sector wrote:
>
> Been cleaning things up and did some searches for
> paths I haven't used for a long time  ...found hundreds
> of them too mostly in 'history' type files collected
> by most progs. Maybe they should regularly check for
> and CLEAR paths that are not readable.

You should add some context, as to what kind of files that would be.

https://www.bleachbit.org/forum/gnome-3-recent-files

I like the bleachbit package, not to actually use it, but
to examine the scripts it has, and see what "targets" the
scripts point to.

Paul

On 2023-04-14 08:09, bad sector wrote:
>
> Been cleaning things up and did some searches for
> paths I haven't used for a long time  ...found hundreds
> of them too mostly in 'history' type files collected
> by most progs. Maybe they should regularly check for
> and CLEAR paths that are not readable.
>
>
>
If it's that important to you, and you have the skills, maybe you should
write your own script that will clear out the clutter instead of trying
to coerce someone else to do it.

That way, *you* get to define what *you* see as clutter, and you don't
rely on someone else's definition.

TJ

On 4/14/23 14:27, TJ wrote:
> On 2023-04-14 08:09, bad sector wrote:
>>
>> Been cleaning things up and did some searches for
>> paths I haven't used for a long time  ...found hundreds
>> of them too mostly in 'history' type files collected
>> by most progs. Maybe they should regularly check for
>> and CLEAR paths that are not readable.
>>
> If it's that important to you, and you have the skills, maybe you should
> write your own script that will clear out the clutter instead of trying
> to coerce someone else to do it.
>
> That way, *you* get to define what *you* see as clutter, and you don't
> rely on someone else's definition.
>
> TJ

I just discovered this, and I don't have the skills but I'd be very
surprised if users really wanted history collected ad-infinitum by
default and without some sort of sanitization while collecting the
entries even if opted for.

Am 15.04.23 um 04:15 schrieb bad sector:
> On 4/14/23 14:27, TJ wrote:
>> On 2023-04-14 08:09, bad sector wrote:
>>>
>>> Been cleaning things up and did some searches for
>>> paths I haven't used for a long time  ...found hundreds
>>> of them too mostly in 'history' type files collected
>>> by most progs. Maybe they should regularly check for
>>> and CLEAR paths that are not readable.
>>>
>> If it's that important to you, and you have the skills, maybe you should
>> write your own script that will clear out the clutter instead of trying
>> to coerce someone else to do it.
>>
>> That way, *you* get to define what *you* see as clutter, and you don't
>> rely on someone else's definition.
>>
>> TJ
>
> I just discovered this, and I don't have the skills but I'd be very
> surprised if users really wanted history collected ad-infinitum by
> default and without some sort of sanitization while collecting the
> entries even if opted for.

That's the difference between hunters and gatherers.

--
De gustibus non est disputandum

On 4/14/23 15:44, Paul wrote:
> On 4/14/2023 8:09 AM, bad sector wrote:
>>
>> Been cleaning things up and did some searches for
>> paths I haven't used for a long time  ...found hundreds
>> of them too mostly in 'history' type files collected
>> by most progs. Maybe they should regularly check for
>> and CLEAR paths that are not readable.
>
> You should add some context, as to what kind of files that would be.

Didn't pay much attention, pages visited, files loaded,
that sort of fluff, many pointing to paths and URL's that
haven't existed for years. Theoretically this kind of
data seeding could even be construed as a security horror.
My beef was the mess that resulted after I renamed or
moved some of my rags, folders, icons etc. Partly my own
fault, I'm now taking care to link everything strictly in
relative terms but that isn't always possible either
beacuse the system or app refuses to respect it or because
it is structuraly impossible.

On 2023-04-15 04:15, bad sector wrote:
> On 4/14/23 14:27, TJ wrote:
>> On 2023-04-14 08:09, bad sector wrote:
>>>
>>> Been cleaning things up and did some searches for
>>> paths I haven't used for a long time  ...found hundreds
>>> of them too mostly in 'history' type files collected
>>> by most progs. Maybe they should regularly check for
>>> and CLEAR paths that are not readable.
>>>
>> If it's that important to you, and you have the skills, maybe you
>> should write your own script that will clear out the clutter instead
>> of trying to coerce someone else to do it.
>>
>> That way, *you* get to define what *you* see as clutter, and you don't
>> rely on someone else's definition.
>>
>> TJ
>
> I just discovered this, and I don't have the skills but I'd be very
> surprised if users really wanted history collected ad-infinitum by
> default and without some sort of sanitization while collecting the
> entries even if opted for.

What on earth are you talking about? History of what, where, how, who?

The only "history" I have is the bash history file, and it is limited in
size or age.

--
Cheers, Carlos.

On Sat, 15 Apr 2023 07:06:43 -0400
bad sector <forgetski@INVALID.net> wrote:

> On 4/14/23 15:44, Paul wrote:
> > On 4/14/2023 8:09 AM, bad sector wrote:
> >>
> >> Been cleaning things up and did some searches for
> >> paths I haven't used for a long time  ...found hundreds
> >> of them too mostly in 'history' type files collected
> >> by most progs. Maybe they should regularly check for
> >> and CLEAR paths that are not readable.
> >
> > You should add some context, as to what kind of files that would
> > be.
>
> Didn't pay much attention, pages visited, files loaded,
> that sort of fluff, many pointing to paths and URL's that
> haven't existed for years. Theoretically this kind of
> data seeding could even be construed as a security horror.
> My beef was the mess that resulted after I renamed or
> moved some of my rags, folders, icons etc. Partly my own
> fault, I'm now taking care to link everything strictly in
> relative terms but that isn't always possible either
> beacuse the system or app refuses to respect it or because
> it is structuraly impossible.

Maybe part of the problem is with the browser you are using. I use
firefox-esr. I have it set to use custom settings for history, that
way I can choose what to delete when it closes, and it doesn't
keep all those URL's.

On 4/15/23 00:46, Joerg Lorenz wrote:
> Am 15.04.23 um 04:15 schrieb bad sector:
>> On 4/14/23 14:27, TJ wrote:
>>> On 2023-04-14 08:09, bad sector wrote:
>>>>
>>>> Been cleaning things up and did some searches for
>>>> paths I haven't used for a long time  ...found hundreds
>>>> of them too mostly in 'history' type files collected
>>>> by most progs. Maybe they should regularly check for
>>>> and CLEAR paths that are not readable.
>>>>
>>> If it's that important to you, and you have the skills, maybe you should
>>> write your own script that will clear out the clutter instead of trying
>>> to coerce someone else to do it.
>>>
>>> That way, *you* get to define what *you* see as clutter, and you don't
>>> rely on someone else's definition.
>>>
>>> TJ
>>
>> I just discovered this, and I don't have the skills but I'd be very
>> surprised if users really wanted history collected ad-infinitum by
>> default and without some sort of sanitization while collecting the
>> entries even if opted for.
>
> That's the difference between hunters and gatherers.

It's more a question of numbers, as in what do MOST users want?

On 4/15/23 08:37, Carlos E.R. wrote:
> On 2023-04-15 04:15, bad sector wrote:
>> On 4/14/23 14:27, TJ wrote:
>>> On 2023-04-14 08:09, bad sector wrote:
>>>>
>>>> Been cleaning things up and did some searches for
>>>> paths I haven't used for a long time  ...found hundreds
>>>> of them too mostly in 'history' type files collected
>>>> by most progs. Maybe they should regularly check for
>>>> and CLEAR paths that are not readable.
>>>>
>>> If it's that important to you, and you have the skills, maybe you
>>> should write your own script that will clear out the clutter instead
>>> of trying to coerce someone else to do it.
>>>
>>> That way, *you* get to define what *you* see as clutter, and you
>>> don't rely on someone else's definition.
>>>
>>> TJ
>>
>> I just discovered this, and I don't have the skills but I'd be very
>> surprised if users really wanted history collected ad-infinitum by
>> default and without some sort of sanitization while collecting the
>> entries even if opted for.
>
> What on earth are you talking about? History of what, where, how, who?

I killed many of them

> The only "history" I have is the bash history file, and it is limited in
> size or age.

Items like what files turned up in kfind, kwrite etc. with their THEN
fully qualified paths. *Unless I ask some prog to remember* where it's
been or what it's seen there shouldn't be ANY of this.

Otterrc .config
"Recent Files[$e]=bookmarks.html,file:///0/dxh/bookmarks-2022-12-19.html"

Bookmarks.bak .config
Recent Files[$e]=bookmarks.html,file:///0/dxh/bookmarks-2022-12-19.html
Recent URLs[$e]=file:///0/,file:///,file:///0/dxh/

histrory.properties .tuxguitar-1.5.4/config
history.count=3
history.2=file\:/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am/midi/AnyConv.com__r2H-FranscoisPretorius-ShjJd1uVG-front-spot-on.midi
history.path=/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am
history.1=file\:/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am/Tr2H-2022-10-27.mid

session-2.0 .bluefish
recent_files: file:///0/dx/adat/Vehicles/Belarus-MTZ/overview.html

Hundreds of them, it's a snooping hacker's wet dream for crissake and
all of the above with paths I haven't used in quite a while soit's not
like 'let's retain the last 3 or 4 or the last hour' worth for safety.

Anyone can just do a search for paths they have used...

On 2023-04-16 00:01, bad sector wrote:
> On 4/15/23 08:37, Carlos E.R. wrote:
>> On 2023-04-15 04:15, bad sector wrote:
>>> On 4/14/23 14:27, TJ wrote:
>>>> On 2023-04-14 08:09, bad sector wrote:
>>>>>
>>>>> Been cleaning things up and did some searches for
>>>>> paths I haven't used for a long time  ...found hundreds
>>>>> of them too mostly in 'history' type files collected
>>>>> by most progs. Maybe they should regularly check for
>>>>> and CLEAR paths that are not readable.
>>>>>
>>>> If it's that important to you, and you have the skills, maybe you
>>>> should write your own script that will clear out the clutter instead
>>>> of trying to coerce someone else to do it.
>>>>
>>>> That way, *you* get to define what *you* see as clutter, and you
>>>> don't rely on someone else's definition.
>>>>
>>>> TJ
>>>
>>> I just discovered this, and I don't have the skills but I'd be very
>>> surprised if users really wanted history collected ad-infinitum by
>>> default and without some sort of sanitization while collecting the
>>> entries even if opted for.
>>
>> What on earth are you talking about? History of what, where, how, who?
>
> I killed many of them
>
>> The only "history" I have is the bash history file, and it is limited
>> in size or age.
>
> Items like what files turned up in kfind, kwrite etc. with their THEN
> fully qualified paths. *Unless I ask some prog to remember* where it's
> been or what it's seen there shouldn't be ANY of this.
>
> Otterrc    .config
> "Recent Files[$e]=bookmarks.html,file:///0/dxh/bookmarks-2022-12-19.html"
>
> Bookmarks.bak   .config
> Recent Files[$e]=bookmarks.html,file:///0/dxh/bookmarks-2022-12-19.html
> Recent URLs[$e]=file:///0/,file:///,file:///0/dxh/
>
> histrory.properties   .tuxguitar-1.5.4/config
> history.count=3
> history.2=file\:/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am/midi/AnyConv.com__r2H-FranscoisPretorius-ShjJd1uVG-front-spot-on.midi
> history.path=/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am
> history.1=file\:/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am/Tr2H-2022-10-27.mid
>
> session-2.0  .bluefish
> recent_files: file:///0/dx/adat/Vehicles/Belarus-MTZ/overview.html
>
> Hundreds of them, it's a snooping hacker's wet dream for crissake and
> all of the above with paths I haven't used in quite a while soit's not
> like 'let's retain the last 3 or 4 or the last hour' worth for safety.
>
> Anyone can just do a search for paths they have used...

So, you are talking of the list of recently opened files in kwrite?
Gosh, speak clearly, I don't understand what you are talking about.

I don't use kwrite, anyway. But I see it has a "clear list", so use it
and be done.

--
Cheers, Carlos.

On 4/15/23 23:30, Carlos E.R. wrote:
> On 2023-04-16 00:01, bad sector wrote:
>> On 4/15/23 08:37, Carlos E.R. wrote:
>>> On 2023-04-15 04:15, bad sector wrote:
>>>> On 4/14/23 14:27, TJ wrote:
>>>>> On 2023-04-14 08:09, bad sector wrote:
>>>>>>
>>>>>> Been cleaning things up and did some searches for
>>>>>> paths I haven't used for a long time  ...found hundreds
>>>>>> of them too mostly in 'history' type files collected
>>>>>> by most progs. Maybe they should regularly check for
>>>>>> and CLEAR paths that are not readable.
>>>>>>
>>>>> If it's that important to you, and you have the skills, maybe you
>>>>> should write your own script that will clear out the clutter
>>>>> instead of trying to coerce someone else to do it.
>>>>>
>>>>> That way, *you* get to define what *you* see as clutter, and you
>>>>> don't rely on someone else's definition.
>>>>>
>>>>> TJ
>>>>
>>>> I just discovered this, and I don't have the skills but I'd be very
>>>> surprised if users really wanted history collected ad-infinitum by
>>>> default and without some sort of sanitization while collecting the
>>>> entries even if opted for.
>>>
>>> What on earth are you talking about? History of what, where, how, who?
>>
>> I killed many of them
>>
>>> The only "history" I have is the bash history file, and it is limited
>>> in size or age.
>>
>> Items like what files turned up in kfind, kwrite etc. with their THEN
>> fully qualified paths. *Unless I ask some prog to remember* where it's
>> been or what it's seen there shouldn't be ANY of this.
>>
>> Otterrc    .config
>> "Recent Files[$e]=bookmarks.html,file:///0/dxh/bookmarks-2022-12-19.html"
>>
>> Bookmarks.bak   .config
>> Recent Files[$e]=bookmarks.html,file:///0/dxh/bookmarks-2022-12-19.html
>> Recent URLs[$e]=file:///0/,file:///,file:///0/dxh/
>>
>> histrory.properties   .tuxguitar-1.5.4/config
>> history.count=3
>> history.2=file\:/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am/midi/AnyConv.com__r2H-FranscoisPretorius-ShjJd1uVG-front-spot-on.midi
>>
>> history.path=/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am
>> history.1=file\:/0/dx/adat/Muz/muz-2021-11-23/Tr2H-Am/Tr2H-2022-10-27.mid
>>
>> session-2.0  .bluefish
>> recent_files: file:///0/dx/adat/Vehicles/Belarus-MTZ/overview.html
>>
>> Hundreds of them, it's a snooping hacker's wet dream for crissake and
>> all of the above with paths I haven't used in quite a while soit's not
>> like 'let's retain the last 3 or 4 or the last hour' worth for safety.
>>
>> Anyone can just do a search for paths they have used...
>
>
> So, you are talking of the list of recently opened files in kwrite?

Those too

> Gosh, speak clearly, I don't understand what you are talking about.
>
> I don't use kwrite, anyway. But I see it has a "clear list", so use it
> and be done.

Touché, I really should take more time to express my rants

Again, what do MOST users want? That's what defaults should cater to.

On 2023-04-16 10:09, Carlos E.R. wrote:
> Reminds of a paper by some teacher or university professor that found
> his students did not have the foggiest idea about what a directory is.
> They just tell the machine to save the work, and it is "somewhere",
> maybe a thousand work files in the same directory, no organization. Thus
> a tool like the above is an absolute need.

I believe it. 25 years ago my computer of choice was an Atari STe. It
worked well for what I did with it, but the time finally came when I
decided I needed to access the Internet like everyone else. So, I bought
a used Windows 98SE PC (an actual IBM!) from my brother.

As he was explaining to me how Windows worked (?), I distinctly recall
he said "Everything goes into My Documents." It made absolutely no
sense, to someone who had used directories on an STe hard drive, but as
the student I held my tongue.

After he left me on my own, I organized my stuff into sub-directories
the way I wanted it, so I could find it when I wanted it. But of course
I fought with Windows for the two miserable years that I used it,
because it wanted to just put anything and everything I saved into My
Documents.

Mandrake 8.2 was more sensible.

TJ

On 2023-04-16 06:58, bad sector wrote:
>> So, you are talking of the list of recently opened files in kwrite?
>
> Those too
>
>> Gosh, speak clearly, I don't understand what you are talking about.
>>
>> I don't use kwrite, anyway. But I see it has a "clear list", so use it
>> and be done.
>
> Touché, I really should take more time to express my rants
>
> Again, what do MOST users want?  That's what defaults should cater to.
>
Ah, a light dawns. You want the Friendly Folks at KDE to set defaults
the way YOU want them. Not gonna happen.

Most users want things left alone, looking and feeling the way they are
used to having them look and feel. The Friendly Folks at KDE don't agree
with that philosophy. It seems that with each new version of Plasma they
have moved something or change the settings from what the *user* wants
to what the Friendly Folks at KDE think they *ought* to want.

Ranting won't help that problem. They, in their infinite wisdom, know
better than you.

TJ

On 2023-04-16 15:45, TJ wrote:
> On 2023-04-16 06:58, bad sector wrote:
>>> So, you are talking of the list of recently opened files in kwrite?
>>
>> Those too
>>
>>> Gosh, speak clearly, I don't understand what you are talking about.
>>>
>>> I don't use kwrite, anyway. But I see it has a "clear list", so use
>>> it and be done.
>>
>> Touché, I really should take more time to express my rants
>>
>> Again, what do MOST users want?  That's what defaults should cater to.
>>
> Ah, a light dawns. You want the Friendly Folks at KDE to set defaults
> the way YOU want them. Not gonna happen.
>
> Most users want things left alone, looking and feeling the way they are
> used to having them look and feel. The Friendly Folks at KDE don't agree
> with that philosophy. It seems that with each new version of Plasma they
> have moved something or change the settings from what the *user* wants
> to what the Friendly Folks at KDE think they *ought* to want.
>
> Ranting won't help that problem. They, in their infinite wisdom, know
> better than you.

I just learned that Gnome goes even further:

<https://en.wikipedia.org/wiki/GNOME_Activity_Journal>

GNOME Activity Journal

GNOME Activity Journal is a semantic desktop browser-like application
for the GNOME desktop environment. Instead of providing direct access to
the hierarchical file system like most file managers, GNOME Activity
Journal uses the Zeitgeist framework to classify files according to
metadata. This includes time and date of previous accesses, location of
use (using GPS positioning), file type, tagging and more. In addition to
local files, GNOME Activity Journal also organizes web browsing history,
email and other data sources.

GNOME Activity Journal was ported to GTK3 and Python3 in version 1.0.0.
It is available as part of Debian, Fedora, Arch Linux (AUR) and Ubuntu.[1]

<https://en.wikipedia.org/wiki/Zeitgeist_(free_software)>

Zeitgeist (free software)

In free software, Zeitgeist is a software service which logs the users's
activities and events, anywhere from files opened to websites visited
and conversations. It makes this information readily available for other
applications to use in the form of timelines and statistics. It is able
to establish relationships between items based on similarity and usage
patterns by applying data association algorithms such as "Winepi" and
"Apriori".

Zeitgeist is the main engine and logic behind GNOME Activity Journal
which is currently seen to become one of the main means of viewing and
managing activities in GNOME version 3.0.[1][2]

Reminds of a paper by some teacher or university professor that found
his students did not have the foggiest idea about what a directory is.
They just tell the machine to save the work, and it is "somewhere",
maybe a thousand work files in the same directory, no organization. Thus
a tool like the above is an absolute need.

--
Cheers, Carlos.