>To get the tools, one can recompile distro's gvfs package and then, from the build directory, subdirectory metadata/.libs copy the files meta-get , meta-get-tree , meta-ls and meta-set to say /usr/bin/gvfs-meta-get etc
The simple usage instruction can be gotten in the usual way, through the "-h" option.
>Now to see what ~/.local/share/gvfs-metadata actually is used for, you can run:
gvfs-meta-get -r -f ~/.local/share/gvfs-metadata/user /
gvfs-meta-get -r -f ~/.local/share/gvfs-metadata/root />And after analyzing the output on my Slackware 14.2 system I discovered that the ONLY extended attribute stored in this whole sorry mess was numerous "download-uri" put there by Mozilla browsers for everything they've ever done. As some perverted kind of permanent, indelible download history.
>One can compile and run the above tool to make sure that on his/her own system, deleting the ~/.local/share/gvfs-metadata/* would not lose anything worth keeping. If so, the cleanup can be made a cron job or put into a shutdown script or whatever.
Just more evidence Mozilla is cucked.
It's open source just fix it yourself.
I've always had an intuition gnome gvfs was doing some deep shit so I never use gnome or pull such dependency.
The solution is to just avoid gnome lol.
The problem now would be the assistive technologies (at-spi) which seems to spawn up in the processes every time you open firefox and its forks (except based pale moon mind you).
Assistive technologies acts like narrator or some shit but it can be abused since it has access to everything the program has such as the contents of the entire window and input management (assistive is for blind or impaired people).
It was coincidentally another gnome/gtk project and I wouldn't be surprised that it's some deep shit again.
You can already guess what it does by just looking at its configuration (which cannot be configured somehow? hmm)
possible language: html, relevance: 52
Check it yourself bruh: /usr/share/defaults/at-spi2/accessibility.conf
<!-- Allow root to connect -->
<!-- Allow everything to be sent -->
<allow send_destination="*" eavesdrop="true"/>
<!-- Allow everything to be received -->
<!-- Allow anyone to own anything -->
Kinda sus ngl.
Surprisingly windows had a decade old bug that involves assistive technologies too such as the narrator/on-screen keyboard login screen bypass method.
You can rename the cmd.exe into narrator.exe or osk.exe (or use recovery hack) and bypass the login screen with a WindowsNT> command prompt that can wipe the user's password or even add administrator. This still works up to windows 10 I think but it's a clever shit unlike back in older 90s windows that you need some easter egg command prompt.
The only problem being you can't know the password but you can at least wipe or change it, you can even disable the encryption! LMAO.
I think anything involving assistive technologies / accessibility is a festive of backdoor, phones included.
I dont have the gvfs-metadata in my system for some reason.
But recently-used.xbel does exist.
How the fuck do I get rid of it?
can't believe I never heard of this dogshit till now
You can't overestimate the incompetence of Tor Browser developers, and/or GNOME developers
You mean malicious.
Same here. I use dwm, so that might be the reason. But what is recently-used.xbel for?
something you use a search engine for
On TailsOS its in the .local/share/gvfs-metadataNot in .tor-browser dir>>2792
>WTF is this $hit?
I assume this doesn't have to do with Tor but with GNOMe
Really Hate that TailsOS chose GNOME DE.
I have disabled GNOME Animations in DCONF with an autorun script on tails.
Any other ((( GNOME ))) bullshit I could disable in dconf or etc?